A WordPress redesign or domain change can improve usability while quietly weakening your organic visibility and backlink profile. This checklist shows how to inventory existing URLs, protect valuable inbound links, map redirects, test the new site and monitor rankings, traffic and crawl signals after launch.
Overview
Website migration SEO is not only about moving content from one WordPress installation to another. It is also about preserving the connections that have accumulated around the site: backlinks from other websites, internal links, indexed URLs, branded searches and landing pages that already attract visitors.
The risk is greatest when a migration changes several variables at once. Examples include moving from HTTP to HTTPS, changing domain names, switching hosting providers, restructuring folders, deleting old content or replacing WordPress URLs with a new navigation system. A redesign may look similar to visitors but still produce different URLs, canonicals, headings, internal links or crawl directives.
Use this process for a planned redesign, a WordPress rebuild, a subdomain move or a full domain migration. Keep a copy of the pre-launch data so that post-launch performance can be compared with a known baseline rather than with memory.
For a broader technical process, see the SEO website migration checklist. This article focuses especially on the link equity and recurring monitoring work that is easy to overlook.
What to track
1. Build a complete URL inventory
Export URLs from the current website before development begins. Combine a crawl of the live site with URLs found in XML sitemaps, Google Search Console, analytics reports and backlink tools. Do not rely on the WordPress media library or the current navigation alone; important pages may be linked only from older blog posts or external websites.
For each URL, record:
- Current URL and proposed new URL
- Page type, such as service, location, product, blog post or resource
- Organic clicks, impressions and ranking trends where available
- Referring domains and notable backlinks
- Target keywords or search intent
- Whether the page will be kept, merged, replaced or retired
- Its redirect destination and implementation status
Prioritise pages that attract organic visits, convert visitors, have strong internal links or have relevant backlinks. A page with few visits may still matter if a reputable, relevant website links to it.
2. Protect backlink destinations
Backlinks usually point to specific URLs, not just to a domain. If an article, supplier directory, local organisation or industry publication links to an old service page, changing that page address without a suitable redirect can interrupt the visitor journey and reduce the value of the link.
Create a backlink preservation list containing the source page, old destination, new destination, link relevance and outreach status. Where a high-value link will point to an inaccurate or irrelevant replacement, consider contacting the publisher with the correct new URL. This is particularly useful after a domain change, a major service restructure or the consolidation of several resources.
Use genuine one-to-one replacements wherever possible. Redirecting every old URL to the homepage is rarely a useful substitute for a relevant destination. If there is no equivalent page, a clear, useful parent page may be more appropriate; if the content has genuinely been retired, document the decision rather than creating a chain of weak redirects.
3. Maintain a redirect mapping table
A practical redirect map can use the following columns:
| Old URL | New URL | Reason | Status | Checked |
|---|---|---|---|---|
| /old-service/ | /services/new-service/ | URL structure changed | 301 planned | Pending |
| /guide-example/ | /resources/guide-example/ | Content retained | 301 tested | Launch QA |
Use a permanent redirect when an old URL has a clear, permanent replacement. Avoid long redirect chains: the old address should lead as directly as possible to the final canonical URL. After launch, test samples from every page type, including URLs with trailing slashes, uppercase characters, query parameters and old folder paths where those variations exist.
4. Compare technical signals
Before launch, record the intended values for canonical tags, indexability, robots.txt rules, XML sitemap URLs, hreflang implementation if relevant, structured data and internal links. Check that staging restrictions do not remain on the live site, while also confirming that the staging site itself is not unintentionally exposed in search.
For WordPress-specific performance work, use the workflow in Core Web Vitals fixes for WordPress. Performance changes should be tested alongside, rather than instead of, redirect and crawl checks.
Cadence and checkpoints
Before launch
Complete the inventory, approve the redirect map and crawl the staging site. Check that key pages return a successful response, have self-consistent canonicals and are linked from the new site architecture. Test forms, tracking, breadcrumb links, navigation and XML sitemap generation. Save screenshots or exports of the old site’s most important templates and reports.
Launch day
Deploy redirects and the new site together where practical. Immediately test the homepage, top landing pages, high-value backlink destinations, sitemap, robots.txt and a sample of old URLs. Check both the preferred HTTPS hostname and any non-preferred versions. Review the live source code rather than assuming the staging configuration carried across.
Submit the current XML sitemap in Google Search Console and inspect representative URLs. If the domain has changed, follow the relevant property and migration steps shown in the current Search Console interface. Keep the old site or redirect layer available for as long as the migration plan requires; do not remove it before old URLs have been checked.
Seven days after launch
Review crawl errors, indexed pages, organic clicks, impressions, conversions and ranking changes. Compare results with the pre-launch baseline while allowing for normal day-to-day variation. Look for patterns rather than reacting to one keyword or one page.
Thirty and ninety days after launch
At 30 days, audit redirect coverage, new internal links, sitemap processing, canonical consistency and referring domains. At 90 days, assess whether important pages have recovered their previous visibility and whether any backlink sources still reference obsolete URLs. Update the redirect map with new findings and remove temporary notes that are no longer useful.
A reporting dashboard can make these comparisons easier. The GA4 and Search Console dashboard template provides a useful structure for organising traffic, search and conversion data.
How to interpret changes
A post-migration decline does not automatically mean that redirects have failed. First separate technical problems from normal performance movement. A sharp fall in indexed URLs, widespread redirect errors or a blocked robots directive points to an implementation issue. A stable number of indexed pages with changes limited to a few restructured sections may require content, intent or internal-link analysis instead.
Use these diagnostic questions:
- Are old high-value URLs returning the intended permanent redirect?
- Does each redirect resolve to a relevant final page rather than another redirect?
- Are new pages indexable and included in the intended sitemap?
- Did canonical tags, navigation or contextual internal links change?
- Are backlinks still landing on useful, relevant content?
- Did several pages become too similar after content consolidation?
- Are traffic changes limited to search, or do analytics and conversion tracking also need checking?
If multiple old pages were merged into one new page, review whether the new page satisfies all of the original search intents. If rankings fluctuate among similar pages, investigate internal competition using the guidance in the keyword cannibalisation checklist.
Do not make repeated structural changes before you have identified the cause of a decline. Altering redirects, titles and content simultaneously makes the evidence harder to interpret. Record each change, its date and the pages affected.
When to revisit
Revisit this checklist before every redesign, domain change, hosting migration or major WordPress rebuild. Keep a light monthly review during the first few months after launch, then move to a quarterly check once performance and crawl patterns are stable.
Run an additional review when you publish a new site section, retire a service, change URL conventions, merge content or receive important new backlinks. Review external links after digital PR campaigns and partnership activity so that valuable referring pages are not left pointing to obsolete destinations. The white hat link building tracker can help connect outreach records with migration checks.
For your next review, take these five actions:
- Export the latest organic landing pages, indexed URLs and referring domains.
- Compare them with the original migration inventory and mark changed pages.
- Test a sample of old URLs from every template and backlink category.
- Inspect Search Console coverage, sitemap processing and representative live URLs.
- Record findings, assign fixes and set the next monthly or quarterly review date.
A migration is complete when the new site is not merely live, but consistently reachable, crawlable and useful for visitors arriving through search or external links. Treat the checklist as a working record rather than a one-off launch document, and it will remain useful for the next redesign as well as the current one.