To keep visitors using your old links after a website redesign, retain useful URLs where possible and map the addresses that must change. Each moved page should lead directly to an equivalent replacement in the right language. Check both the server response and the final content: reaching a page with a “200” response is not enough if it is the wrong page.
This guide covers public pages on a small business website when its structure or domain changes. It provides a preparation and acceptance-testing method, not a universal redirect rule for forms, APIs or payments.
Find the links you need to preserve
An old address may still appear in bookmarks, emails, a business listing or search results. Before the redesign, collect URLs from the existing site, its sitemaps, available Search Console reports and request logs. Add important links used in business communications. No single source guarantees a complete inventory.
Record variants that people actually use: HTTP or HTTPS, with or without “www,” the original language and parameters that change the content. Do not discard every query parameter: a product identifier serves a different purpose from a campaign tag. Keep confidential data out of the shared inventory.
If a link already fails, record the complete address, observation time and response. Consult available logs before diagnosing an outage or blaming the redesign. A browser can hide a redirect chain or display an error page with a success status.
Plan access, responsibilities and costs
You need a page inventory, the future structure, a content owner and someone who can configure redirects in the right place. Depending on the site, that may be the server, CDN, hosting platform or CMS. Identify which component actually answers the old address; changing WordPress alone is insufficient if a server rule runs first.
Allow time for mapping, review and testing, any paid features or extensions, and continued operation of the old domain and HTTPS certificate if the domain changes. Check your hosting arrangements: no particular tool or subscription is mandatory in every situation. An approved, exportable mapping also makes it easier for another provider to take over.
Before switching over, keep a copy of the current configuration and decide who can stop the launch if an essential journey fails. Prepare rollback with the technical team instead of improvising while visitors are using the new site.
Decide what happens to each old page
Google’s guidance on URL changes recommends mapping old addresses to new ones and redirecting to the final destination. It discourages sending many old pages to an unrelated destination such as the homepage; that can be treated as a soft 404 error.
Give each URL an explicit decision:
- The page is still useful and its address stays the same: retain it and verify its content.
- The page moves: map it to the page serving the same need.
- Several pages are consolidated: confirm that the destination genuinely covers their useful content. A shared word in their titles does not establish equivalence.
- The page is removed without a comparable replacement: return an actual 404 or 410 response with a helpful error page, rather than an arbitrary redirect. Google explains this in its crawling-error guidance.
An English page should not end at a French default when its English equivalent exists. If a translation has been discontinued, have the content owner decide how to handle it instead of inventing an equivalent.
Build a mapping record that can be tested
A spreadsheet is enough for the review. Use one row for each old URL with these fields:
- Old address: complete URL and where it was found.
- Decision: retain, move, consolidate or remove.
- Destination: the exact final address, or an explicit decision that no replacement exists.
- Reason: the need served and expected language, approved by the content owner.
- Expected result: initial status, final destination and a title or content element that identifies the right page.
- Verification: environment, date, observed response, discrepancy and person responsible for resolving it.
In a fictional example, a service business replaces /en/business-site/ with /en/websites/. The new page presents the same service and retains a way to enquire, so that mapping can be approved. Sending /en/workshop-2022/, a discontinued event without a replacement, to the same service page would be a different decision requiring justification. It is not automatically equivalent.
This record becomes the test reference. It prevents the team from merely checking that a configured rule does what it was configured to do: decide the expected business result before inspecting the technical result.
Configure precise rules with the technical team
For a page that has permanently moved, Google recommends a permanent server-side redirect, including 301 or 308. Select and configure it for the platform in use. Temporary redirects serve a different purpose; do not select one simply because it is the first option in an interface.
Point the old address directly to the intended final destination. An intermediate page that redirects again creates another dependency and makes diagnosis harder. Check that general language, domain or trailing-slash rules do not send the request back to its starting point.
Review broad rules carefully: they may intercept a file, subdirectory or feature they were not meant to affect. Decide which parameters must be retained based on the expected content, and test representative examples, including encoded addresses.
Forms and APIs need separate analysis. The HTTP specification allows a client to change POST to GET after a 301 response. A 308 preserves the method, but that does not automatically make the redirect appropriate for a business operation. Exclude those routes from the public-page rules until the responsible person has verified their behaviour.
Test the response and the visitor’s journey
In a validation environment, use a tool that shows HTTP responses and the steps followed. Then use a browser to inspect the visible result. For every mapping row, record the first status, any hops, the final address and the content. A loop, missing destination or incorrect language requires a correction.
If the validation domain differs, explicitly map production addresses to test addresses. Success there does not prove the public domain will apply the same rules. Include URLs that should remain unchanged and addresses that do not exist; neither should automatically become the homepage.
Walk through essential pages on desktop and mobile. Check the heading, service information, images, links and access to the enquiry form. A correct destination must still let the visitor complete the intended task. Our guide to verifying website form delivery covers the next check; an actual test submission needs its own agreed scope and suitable test data.
We ran 16 scenarios against a local HTTP server using fictional URLs and content: seven valid cases and nine deliberate faults. All 16 expected results were obtained, including checks of destinations, languages, query parameters, loops, 404/410 responses and selected metadata. We did not test a production site, a real form, a payment or Google’s behaviour.
Align links, languages and SEO signals
Update internal links to point to the new destinations. Review canonical URLs, language alternates and sitemaps so they describe the final pages intended for indexing, rather than continuing to identify old addresses as the main pages. Google’s guidance for language versions calls for consistent, reciprocal annotations between the relevant versions.
Keep the validation site protected from indexing using the method chosen by your team. If it contains non-public information, control access as well: noindex does not protect confidentiality. Before launch, check that the protection has not been left on public pages. Be careful: Google must be able to read a noindex directive; blocking crawling through robots.txt is not equivalent. Do not remove protections indiscriminately without identifying what should become public.
A working redirect does not guarantee immediate indexing or preservation of a search position. Distinguish a successful technical test, a search engine’s crawl and the performance observed afterwards.
Repeat the checks after launch and keep the old entry points
After the authorized launch, run the list against the public URLs again. Check old domains, HTTPS and the recorded variants. Then review request errors, reported broken links and available Search Console reports. Compare defined periods and separate visits, received enquiries and sales; a change alone does not identify its cause.
Google recommends keeping redirects as long as possible, generally for at least one year. That is not an automatic removal date: bookmarks and external links may remain useful. Assign someone to maintain the domain, certificate and rules.
Retain the approved mapping and test results. When a destination changes again, review the old entries to avoid accumulating hops. Investigate new discrepancies as documented cases instead of turning every 404 into a homepage redirect.
Acceptance checklist
- Important old URLs and their variants have been inventoried.
- Each destination serves the same need in the expected language.
- Removed pages without replacements have an explicit treatment.
- Statuses, hops, content and essential journeys have been checked.
- Unverified rules do not intercept forms, APIs or payments.
- Internal links, canonicals, language annotations and sitemaps match the final pages.
- Someone owns the public verification and ongoing redirect maintenance.
For a redesign, bring your list of old pages and proposed destinations. Services Hamdi can include this preparation and acceptance testing in a website project for a Greater Montréal small business.

