How to Protect URLs, Search and Enquiries When Moving an Old Website
Moving to a new website involves more than carrying over design and copy. URLs reached from search, addresses in sales material, form recipients and measurement settings are part of the working site too. They need to be understood before the change, not discovered by accident afterwards.
Protecting a route does not mean never changing it
Pages may be combined, URLs may be simplified and forms may be rebuilt. The useful discipline is to record why each change is happening, where the old route leads, and how it will be checked before and after launch.
1. Take an inventory of the current site
List the important pages, URLs referenced by PDFs or other websites, search entry points and pages that contribute to enquiries. Traffic alone does not set the priority. Explanations used by sales or support, guidance for existing customers and pages a candidate expects to find may also matter.
2. Make an old-to-new URL map
For each old URL, record the replacement page, a combined destination, or the reason it is being retired. Where the content has moved, consider a permanent redirect; where it has not, give the visitor a useful next action. Sending every old page to the home page makes the relationship between the old and new information less clear for people and search engines.
| Field for each old URL | What to record |
|---|---|
| Content decision | Retain, rewrite, combine or retire |
| New destination | The one URL with the closest corresponding purpose |
| Search signals | Title, H1, canonical, index policy, sitemap and internal links |
| Language relationship | Japanese/English counterpart, switching and hreflang |
| Known references | Menus, copy, PDFs, campaigns, external links and QR codes |
| Ownership | Implementer, pre-launch reviewer and post-launch monitor |
3. Test enquiries and measurement in real conditions
Do more than look at the form confirmation screen. Send a test, check that the notification arrives, confirm the reply route and consent text, and review how spam protection behaves. Check telephone links, booking, payment and connected services in the same way. Search Console and analytics answer different questions, so search entry points and on-site behaviour should not be treated as one figure.
4. Include images, PDFs, structured data and connected services
A migration involves more than HTML pages. It may include PDFs used by sales or search visitors, referenced image URLs, form recipients, tag management, social-sharing images, structured data, feeds and APIs. Record the owner and effect of each dependency. The goal is not to carry everything over, but to retain useful assets deliberately and retire obsolete public material and configuration deliberately.
5. Define the release decision and recovery path
The launch plan should identify timing, ownership, DNS or cache effects, conditions that stop the release, how long the previous environment remains available, backups and the recovery decision. Not every migration can use the same rollback method. Once new data or enquiries have entered the new environment, simply restoring the old one may be unsafe; agree a configuration-specific approach with the technical owner.
6. Assign responsibility after launch
At launch, check important URLs, redirects, canonicals, sitemaps, forms, measurement, language switching and mobile experience. Continue to review search, site use and enquiries separately, because crawling and re-evaluation can involve change over time. Knowing who investigates an issue and who can make a correction helps a team respond calmly.
Next: review the first 30, 60 and 90 days
After immediate migration checks are complete, review search entry points, on-site use, enquiry quality and operational burden separately, then choose one useful improvement.
PLAN THE MOVE
Could you make the important routes visible before the migration begins?
Starting with the current site, URLs, forms and technical conditions, we can help establish a practical migration plan.
Review and sources
Reviewed 17 August 2026. See Google Search Central’s guide to site moves with URL changes and its explanation of Google Analytics and Search Console.
