What Happens to QR Codes When a Website URL Changes?

A printed QR code does not automatically update when you change a website URL. What happens next depends on whether the code contains the page address directly or points to a managed redirect service. In either case, a redirect from the old address can help people reach the new page—but it does not rewrite the QR code itself.

Key Takeaways

• A static QR code encodes a destination URL. Changing your website does not change that encoded address.
• A dynamic QR code usually points to a service-managed URL that can be redirected to a different destination, subject to the provider’s service and settings.
• Redirecting the old URL to the new page can keep a static code useful, provided you maintain control of the old domain and configure the redirect correctly.
• Test the printed code on several phones, check every redirect hop, and keep the old address working for as long as people may use the code.

Static and dynamic QR codes work differently

A static QR code contains the destination URL itself. For example, a code might encode https://example.com/spring-sale. If you later move the page to https://example.com/offers/spring, the printed code still sends scanners to the old address. The code has not changed; the URL it contains has.

A static code can still lead visitors to the new page if the old URL redirects there. That redirect is configured on the website or hosting system, not in the printed code.

A dynamic QR code commonly encodes a URL managed by a QR-code provider, such as a short link on the provider’s domain. The provider’s system then sends visitors to a destination you can change in its dashboard. The printed code stays the same while the provider changes the destination behind it. Check the provider’s terms and account settings: the redirect may depend on the service remaining available and your account retaining access.

“Dynamic” does not mean the QR image updates itself, and it does not guarantee that a link will work forever. It describes how the destination is managed.

What happens after a website URL changes?

Suppose a printed code contains https://example.com/event, and you move the event page to https://example.com/events/community-day.

• If the old URL still serves the page, scanners may continue to reach it, though its content could be outdated.
• If the old URL redirects to the new page, scanners can follow the redirect and arrive at the updated destination.
• If the old URL returns an error or no longer resolves, scanners may see an error instead of the new page.
• If the code points to a managed dynamic-QR URL, the configured destination may be changeable in the provider’s service. If that service or account is unavailable, the code may stop working as expected.

A redirect preserves access; it does not change the destination encoded in a static QR code. Anyone who scans that code still initially requests the original URL.

Check the old URL and look for redirect-chain problems

Before changing or retiring a page, open the exact URL encoded in the printed code. If you do not know it, scan the code with a phone and inspect the link preview before opening it. You can also use a URL-inspection tool to read the QR code’s contents.

Then check the old URL’s response and final destination with a redirect-checking tool, or inspect it with a command-line client. For example, curl can follow redirects and show response headers:

curl -sS -L -D - -o /dev/null --max-redirs 10 https://example.com/event

This requests the URL, follows redirects, prints response headers, and discards the response body. Review the sequence of status codes and Location headers, then confirm the final URL is the intended page. The --max-redirs limit prevents an endless redirect loop from being followed indefinitely. A redirect checker may present the same hop-by-hop information in a graphical interface.

A chain such as old URL → temporary URL → new URL adds extra steps and can fail if an intermediate address is removed. Prefer a direct redirect from the old URL to the final destination. Also check for:

• Loops: two URLs redirect back and forth, so the page never loads.
• Wrong destinations: the old page redirects to a homepage or unrelated campaign page instead of the replacement.
• Broken paths: the domain redirects, but the specific path encoded in the code returns an error.
• Lost query parameters: campaign or tracking parameters disappear when the redirect is applied.
• HTTP/HTTPS problems: the old address fails before it can reach the secure version, or redirects inconsistently between versions.

Redirect status codes such as 301 or 308 are commonly used for permanent moves, while 302 or 307 are commonly used for temporary ones. The right choice depends on how your site is configured and whether the move is actually permanent. Whatever you choose, verify the behavior in a browser and with a redirect check; the status code alone does not prove the final page works.

Practical checklist for a site change

Before the change

1. Scan a real printed code. Record the exact URL it contains. Do not assume it matches the current website address.
2. Identify who controls the destination. For a static code, this is usually your website or domain setup. For a managed dynamic code, check the provider account and its settings.
3. Choose the replacement page. Confirm it is published, loads over HTTPS, and contains the information visitors expect.
4. Plan the redirect. Map the old URL directly to the new page, not just to the site homepage. Preserve useful query parameters when your site depends on them.
5. Keep control of the old domain and hosting. A redirect cannot work if the old address no longer resolves to infrastructure you control.

After the change

1. Test the old URL in a browser. Confirm it reaches the right page without a warning, error, or unexpected sign-in requirement.
2. Inspect the redirect hops. Check for loops, unnecessary chains, missing paths, and lost parameters.
3. Scan the printed code on multiple phones. Try both iPhone and Android devices if available, and use more than one camera or QR-scanning app. Camera behavior can differ, so test the flow people will actually use.
4. Test the physical print. Scan the code from the distance and angle customers are likely to use, under realistic lighting. Check that the code is large and clear enough to scan.
5. Check the final page on mobile. Confirm it loads, is readable, and provides the intended next step.
6. Recheck after launch. Repeat the test after DNS, hosting, or redirect changes have settled, and monitor the old URL for errors or unexpected traffic patterns.

Common Mistakes

• Assuming a static QR code changes when the web page moves. It does not; the code retains its original URL.
• Redirecting every old address to the homepage. Visitors may not find the content they expected. Redirect each code’s old destination to the closest relevant replacement.
• Removing the old domain too soon. Printed materials can remain in circulation long after a site change. Keep the old address active while those codes may still be scanned.
• Testing only by clicking the new URL. That skips the old address and the redirect. Test the printed code and its original destination.
• Checking only on one device. A code can be hard to scan in real-world conditions even when it works on a desktop screen.
• Relying on a dynamic-code provider without checking account access. Confirm you can still manage the destination and understand what happens if the service or subscription changes.

Best Practices

• Keep a record of the URL encoded in each QR code and the corresponding current destination.
• Use stable, human-readable URLs for printed materials when practical, so future page changes can be handled with redirects you control.
• Make each redirect direct, relevant, and HTTPS-enabled; avoid unnecessary hops.
• Retain control of old domains and redirect rules for as long as printed codes remain in use.
• Treat provider-managed dynamic codes as a service dependency, and document the account owner and recovery process.
• Include a short readable URL near important printed QR codes when space allows, so people have an alternative if scanning fails.

Conclusion

A changed website URL does not alter a printed QR code. A static code continues to request its original address, while a redirect can carry visitors to the new page. A dynamic code may let you change its managed destination, but it depends on the provider. Identify what the code contains, configure the right redirect, and test the actual print on multiple phones before relying on it.