Preserve
Keep the URL and core intent when the page performs a useful job. Improve clarity without discarding the substance that earned visibility.
SEO migration checklist · Updated August 2026
SEO Website Redesign Checklist
A redesign changes how a website looks and often changes the signals search engines use to understand it. Protect useful rankings by inventorying the current site, preserving proven intent, mapping every URL decision, testing the production candidate, and monitoring by page and query after launch.
Before design: preserve the evidence
- Crawl the current website and save URLs, status codes, titles, descriptions, canonicals, headings, word content, structured data, images, and internal links.
- Export Search Console pages and queries for a meaningful comparison period, plus analytics landing pages and recorded conversions.
- Identify pages with external links, branded mentions, direct traffic, campaign use, downloads, and customer-service value.
- Save XML sitemaps, robots rules, redirect configuration, navigation, breadcrumbs, and important content hubs.
- Annotate seasonality, campaigns, outages, tracking changes, and the planned launch date.
Totals conceal risk. A site can hold overall traffic while losing the one page that generated qualified leads. Create page groups for services, locations, products, resources, comparisons, and brand queries.
During planning: give every URL a decision
Consolidate
Combine genuinely overlapping pages into the strongest destination, preserve unique value, update internal links, and redirect retired sources directly.
Create
Add a page when research shows a distinct customer intent that the existing structure cannot satisfy well. Assign one primary destination before writing.
Retire
Remove content that is inaccurate, useless, or unsupported. Use a relevant replacement when one exists and clean up all internal references.
Do not change URLs merely to make them shorter or match a new navigation label. A stable, descriptive address has value. When a change is necessary, map one old URL to one best destination and avoid redirect chains.
Protect on-page meaning in the new templates
| Signal | Redesign requirement |
|---|---|
| Title and H1 | Keep each page’s purpose explicit and unique. Do not replace descriptive language with brand slogans. |
| Content | Carry forward accurate, useful answers, proof, specifications, locations, FAQs, and decision support. |
| Internal links | Preserve hub and contextual relationships using descriptive anchor text and final destination URLs. |
| Structured data | Match visible content, use valid types, retain stable entity identifiers, and avoid invented facts. |
| Media | Preserve meaningful images, text alternatives, captions, filenames where useful, and correct responsive delivery. |
| Indexability | Use the intended status, canonical, robots directive, language, and sitemap inclusion on production pages. |
Test the production candidate
Crawl staging with authorization before launch, then compare it with the current inventory and migration map. Confirm page counts, missing content, accidental noindex directives, canonical hosts, broken links, redirect targets, orphan pages, structured-data validity, and the absence of staging addresses.
Test rendered navigation, mobile links, filters, pagination, search, and JavaScript-dependent content. Search engines must be able to reach important content through normal links. Confirm that error pages return error statuses and that redirect rules do not create loops or broad unrelated matches.
Keep staging blocked from public indexing, but prepare the exact production robots and sitemap configuration in advance. The launch checklist must explicitly remove staging-only controls.
Launch, verify, and measure
- Deploy the approved production build and redirect map.
- Test the homepage, priority pages, historical URLs, forms, analytics, robots rules, canonicals, and sitemap on the public host.
- Crawl the live site and compare status, indexability, content, and internal links with the approved plan.
- Submit or refresh the sitemap in Search Console and inspect representative priority pages.
- Monitor crawl errors, index coverage, page groups, queries, impressions, clicks, positions, conversions, and server errors.
- Investigate changes by URL and query intent before assuming the redesign caused every movement.
Do not declare success from indexation alone. Indexation confirms discovery and eligibility. Rankings, qualified clicks, conversions, revenue, and the stability of valuable pages determine whether the redesign improved the acquisition system.
Use the broader website redesign planning guide to scope content, design, development, and operational work around this SEO checklist.
Frequently asked questions
SEO Website Redesign Checklist FAQ
Can a website redesign improve SEO?
Yes, when it improves content, architecture, internal links, accessibility, speed, structured data, and customer usefulness while preserving established value. A redesign can also reduce visibility if it removes or weakens important signals.
Should URLs change during a website redesign?
Only when there is a clear structural or business reason. Keep stable descriptive URLs where possible. When an address changes, create a direct permanent redirect, update internal links, and include the final canonical URL in the sitemap.
Should old low-traffic pages be deleted during a redesign?
Traffic alone is not enough to decide. Check search impressions, conversions, backlinks, customer-service use, campaign use, accuracy, and overlap. Improve, consolidate, redirect, or retire each page according to its actual job.
How should SEO performance be measured after redesign?
Compare page groups and query intents using Search Console, analytics, conversions, and revenue. Account for seasonality, campaigns, tracking changes, and normal ranking variation. Investigate important page-level losses quickly.
When should the new sitemap be submitted?
Submit or refresh the canonical production sitemap immediately after launch and public verification. It should contain only indexable canonical URLs that return successful status codes and use the preferred host and protocol.
Turn the plan into a website that sells
North Star designs, rebuilds, hosts, and supports business websites remotely across Canada. Bring the checklist or brief to a scope call and we will translate it into a clear proposal.
Request a Website ScopeExplore Web Design