Plan your website
Website Redesign SEO Checklist: Protect Useful URLs
Prepare a URL inventory, redirect map and post-launch checks before a redesign. Includes a free migration worksheet without ranking guarantees.
JNS Digital Solutions · Updated · 3 min read
Get the free worksheetA redesign can change how your site looks without changing every URL. Before removing pages or reorganizing navigation, find out which existing pages receive useful traffic, links or customer inquiries. Those pages represent information people already rely on.
This checklist helps you plan a controlled handoff between an old site and a replacement. It cannot guarantee unchanged rankings. Search engines must process significant changes, and even a well-planned move can involve fluctuations. Reduce avoidable mistakes by making URL decisions explicitly.
Inventory before you delete
Start with your current sitemap, navigation and available Search Console page data. Record each public URL, its purpose and whether its content remains useful. Include important downloads and images when they receive links or are part of customer instructions. A page with low recent traffic may still serve a necessary customer task.
Assign one decision to each URL: keep, improve in place, merge into a relevant page or remove because the information is no longer available. Keep URLs stable when there is no clear benefit to changing them. Export useful records and retain a recoverable copy of the current website before making release changes.
Use the Search Console worksheet to identify pages and queries worth reviewing before a redesign. A Simple Search Console Report for Small Businesses.
Map changed URLs to relevant destinations
When a page moves, map its old URL to the most relevant replacement, not automatically to the homepage. A service explanation should lead to the updated explanation of that service. If there is no relevant replacement and the page is genuinely gone, an appropriate not-found response is clearer than sending everyone to an unrelated page.
Ask your developer to use permanent server-side redirects for permanent moves and to avoid chains. Update internal links to point directly to the final URLs. Review the mapping as business content, not only as technical configuration: a redirect can work correctly while taking the customer to the wrong answer.
- Old URL and reason for the change.
- New destination and why it matches the original intent.
- Expected response and person responsible for testing.
Verify production, then monitor
After launch, test important old URLs, new pages, the sitemap, canonicals and any temporary indexing restrictions used during development. Confirm that pages intended to be public are accessible and that form delivery still works. Compare page content with the approved inventory so a working route does not hide an accidentally removed explanation.
Record the release date and monitor indexing, relevant search queries and customer inquiries. Investigate major changes rather than assuming every dip is normal or every improvement came from the redesign. Keep a rollback decision and owner ready. Google’s site-move documentation below covers the search-specific mechanics in more detail.
Pair the migration checks with a full website launch review. Website Launch Checklist for Small Businesses.
The practical takeaway
Preserve useful URLs where possible, map necessary changes deliberately and verify the live output. A redesign is not permission to discard existing search value.
Free download · No email required
Redesign URL mapping worksheet
A reusable migration record for old URLs, destinations and verification. Duplicate the URL record for every existing public page. Review decisions before changing redirects or deleting content.
Download free worksheet (.txt)Preview the worksheet
- Release owner and planned date: ____________________
- Backup / rollback location (no credentials): ____________________
- Old URL: ____________________
- Current customer task / useful search data: ____________________
- Decision: keep / improve / merge / remove
- New URL or intended 404/410: ____________________
- Why this destination matches the original page: ____________________
- Expected redirect response if moved: ____________________
- Tester and result: ____________________
- [ ] Internal links point directly to final URLs
- [ ] Canonicals, sitemap and public indexing settings checked
- [ ] Forms and inbox delivery verified
- Post-launch observation and next review date: ____________________
Sources and further reading
Prepared with AI assistance using the linked primary sources and original planning worksheets. Examples are illustrative, not JNS client results. Platform rules can change; check the linked guidance before making account changes. This guide does not promise rankings, traffic or legal compliance.