Website Redesign SEO:
A Migration Checklist Before Launch

A redesign can change URLs, templates and content at the same time. This checklist covers what to inventory, redirect and check before launch, and what to watch afterwards.

11 min read

Website redesign SEO is mostly about continuity. Search engines have learned which of your URLs answer which questions. A redesign that changes addresses, removes text or changes how pages are rendered asks them to learn it again. Google's own guidance on moving a site says rankings may fluctuate while it recrawls and reindexes the pages. The work below helps keep the relearning short and pages from being lost by accident.

The short answer: before launch, list every URL that earns traffic or links and map each changing URL to its closest new page with a permanent (301) redirect. Keep the content and internal links those pages relied on, give each new page a self-referencing canonical, publish a sitemap of the new URLs and remove any staging blocks. After launch, watch the Search Console reports for the moved URLs until they settle.

The redirect map can only be as complete as the list it starts from. Google recommends starting with your sitemaps, a URL export from your content management system and your server logs, and including the images and videos that pages embed. Add the pages that receive clicks in the Search Console Performance report, the landing pages in your analytics and the pages other sites link to. PDFs and old campaign pages are easy to miss.

For each URL, record what it is worth before anything changes:

  • Search: Clicks, impressions and the main queries it appears for.
  • Business: Visits and the enquiries or other key events it starts.
  • Links: The external sites that link to it.
  • Template: Which page type it uses, so the template owner knows what to check.

This baseline is what you compare against after launch. With it, a drop in traffic can be traced to the pages that caused it.

Map redirects one to one, not to the homepage

Once you have the list, decide where each old URL should go. Google recommends server-side permanent redirects, such as 301 and 308, where technically possible, and sending each one straight to its final destination rather than through a chain. Pages that now cover the same subject are the right targets: the new service page for the old service page, the merged guide for the two guides it replaced.

Redirect each old URL to the page that now answers the same question, not to the homepage.

Google warns against sending many old URLs to one irrelevant destination such as the homepage, because it can confuse users and be treated as a soft 404. If content is removed and nothing replaces it, the old URL should return a 404 or 410.

One decision per old URL: where it should go and which response it returns.

Where should each old URL go? Work through the questions for every URL that changes.

Show the path to

An old URL that earns traffic or links

  1. Is the same content on the new site?

    Yes

    301 redirect to its new URL

    Same subject, new address.

    No: continue to question 2

  2. Was it merged into another page?

    Yes

    301 redirect to the page that now covers it

    No:

    Removed, and nothing on the new site replaces it

    Return 404 or 410

    Not a redirect to the homepage: Google may treat it as a soft 404.

Already a redirect from an earlier site? Update it to point straight at the final new URL, in one hop, instead of adding a chain.

Check old redirects from previous redesigns too. If they point to URLs that are now redirected again, update them to point at the final page. Google says to keep redirects for as long as possible, and generally for at least a year.

A page can keep its URL and still lose what made it useful in search. A redesign can shorten copy, move text into images, drop FAQ sections or rewrite headings to fit the new layout. Before signing off a template, compare each important page with its old version: the main heading, the body text, the questions it answered, the title and the meta description. Change them on purpose, not as a side effect of the layout.

Internal links change in the same way. A new navigation can leave pages with fewer links pointing to them, or none. Google's link guidance says every page you care about should have a link from at least one other page on your site, and that Google can generally crawl a link only if it is a real HTML link with an href attribute. Point internal links straight at the new URLs. Redirects stay in place for bookmarks and external links; your own pages should link to the final address.

Make sure search engines can render and index the new build

Modern frameworks change how pages reach a crawler. Google's JavaScript SEO guidance describes server-side rendering or pre-rendering as a great idea because it makes the site faster for users and crawlers. Whichever approach the build uses, check three things on the new templates:

  1. The main content and links are present in the HTML that is served or rendered.
  2. Missing pages return a real 404 status code, rather than a "not found" message on a page that returns 200.
  3. Once the pages are reachable without a login, the URL Inspection live test in Search Console shows the expected rendered content. Check the declared canonical in the HTML too. Google's selected canonical appears only in the indexed data; the live test cannot predict it.

For Next.js SEO the same rules apply, and the framework can produce most of the signals from the content itself.

On this site: the Insights pages are generated at build time from local files, and canonical links use our confirmed public address, cursopic.com, by default. Staging pages carry noindex, and indexing is enabled only for an explicit production deployment. The sitemap is built from the same lists as the pages, and preview routes return 404 in production. On a website development project, rules like these are agreed as part of the build.

Point every signal at the new URLs

Redirects are one signal among several. Each of the others should agree with the redirect map.

Each signal on the new site: what it should have, and a common redesign mistake
SignalWhat the new site should haveA common redesign mistake
Permanent redirectEach changed URL sends visitors to its closest new page in one hop.Many old URLs redirected to the homepage.
CanonicalA self-referencing canonical on each new page, on the production domain.Canonicals that point at the staging host or at old URLs.
Internal linksLinks that go straight to the new URLs.Navigation and body links that still pass through redirects.
XML sitemapOnly new, canonical URLs that return 200.A sitemap that still lists old or redirected URLs.
noindex and robots.txtTemporary blocks on staging only; production keeps only the rules it needs.A staging block copied to the live site.
Structured dataMarkup that describes content visible on the new template.Markup lost with the old template, or describing hidden content.
  • Permanent redirect

    What the new site should have

    Each changed URL sends visitors to its closest new page in one hop.

    A common redesign mistake

    Many old URLs redirected to the homepage.

  • Canonical

    What the new site should have

    A self-referencing canonical on each new page, on the production domain.

    A common redesign mistake

    Canonicals that point at the staging host or at old URLs.

  • Internal links

    What the new site should have

    Links that go straight to the new URLs.

    A common redesign mistake

    Navigation and body links that still pass through redirects.

  • XML sitemap

    What the new site should have

    Only new, canonical URLs that return 200.

    A common redesign mistake

    A sitemap that still lists old or redirected URLs.

  • noindex and robots.txt

    What the new site should have

    Temporary blocks on staging only; production keeps only the rules it needs.

    A common redesign mistake

    A staging block copied to the live site.

  • Structured data

    What the new site should have

    Markup that describes content visible on the new template.

    A common redesign mistake

    Markup lost with the old template, or describing hidden content.

Google's canonical documentation treats redirects and rel="canonical" annotations as strong signals and sitemap inclusion as a weak one, and recommends absolute URLs. Its structured data guidelines say markup should not describe information that is not visible to the user, so check that the new templates still show what the markup claims. If the site has language versions, update the hreflang annotations to the new URLs as well.

Keep staging out of search, then open the live site

A staging site that crawlers can reach may appear in search results before launch. Google's robots.txt documentation is explicit that robots.txt is not a mechanism for keeping a page out of Google; a blocked page can still appear in results if other pages link to it. Password protection is the dependable option for staging. A noindex rule also works, but only if crawlers are allowed to fetch the page and see it.

The opposite mistake happens on launch day. Google's troubleshooting list for site moves includes forgetting to remove the noindex rules or robots.txt blocks that were only needed during the migration. Make removing them a named step, with an owner.

Generate the sitemap from the same source as the pages, list only canonical URLs that return 200, and submit it in Search Console. Google reads sitemaps to crawl a site more efficiently, and its site move guide asks for a new sitemap that lists the new URLs.

Set a performance budget before the design is final

A redesign can make pages slower without anyone deciding it should. web.dev defines a performance budget as a set of limits on metrics that affect site performance. Agree it before design work starts, so that the design is made within it: image sizes for the first screen, the number of web fonts and the third-party scripts the new site will load.

Measure against the Core Web Vitals. Good thresholds are a Largest Contentful Paint within 2.5 seconds, an Interaction to Next Paint of 200 milliseconds or less and a Cumulative Layout Shift of 0.1 or less, measured at the 75th percentile of page loads on mobile and desktop separately. Google recommends good Core Web Vitals for success with Search and for the user experience generally. Compare the old and new templates with lab tests before launch; field data needs real visits to build up afterwards.

Launch day and the first weeks after it

Ship the redirects with the new site, not after it. Then crawl the old URL list: changed URLs should return a single permanent redirect to a relevant page that returns 200. Unchanged URLs should still return 200, and removed content without a replacement should return 404 or 410. Google says it frequently sees redirects that point to wrong or non-existent URLs on the new site. Check the live robots.txt, a sample of canonicals and the sitemap, and inspect one URL from each template.

Use the Change of Address tool in Search Console only if the domain or subdomain changes. Google's help page says not to use it for a move from http to https, between www and non-www on the same domain, or for path changes within the same domain.

In the following weeks, the Page indexing report shows why URLs are not indexed: page with redirect, not found (404), soft 404, excluded by noindex, blocked by robots.txt, or a different canonical chosen by Google. Filter it by the new sitemap to see the URLs you care about. Compare clicks and queries per page with the baseline, and check enquiries in analytics, because tracking is easy to break in a rebuild. Google says a small to medium-sized site can take a few weeks for most pages to move.

The website redesign SEO checklist

Use this list as the sign-off for a redesign, whoever does the work. The checks belong to four moments, starting before design work begins; redirect checks apply to URLs that move.

Redesign SEO checks, in order. Start before design, so the redirect map is ready on launch day.

  1. Before design

    • Inventory: Every URL with traffic, links or enquiries, plus images, PDFs and old campaign pages.
    • Baseline: Clicks, queries, visits and key events per URL before anything changes.
    • Performance budget: Limits for images, web fonts and third-party scripts, agreed before design work starts.
  2. Before launch, on staging

    • Redirect map: One-to-one 301s to the closest new page, no chains, 404 or 410 for removed content.
    • Content parity: Headings, body text, titles and descriptions kept or changed on purpose.
    • Internal links: Pointing straight at new URLs; no important page left without links.
    • Rendering: Content and links in the served or rendered HTML; real 404 status codes.
    • Signals: Self-referencing canonicals on the production domain, structured data that matches the page, updated hreflang.
    • Performance: New templates compared with the old ones in lab tests, against the budget.
    • Staging: Password protected.
  3. Launch day

    • Redirects live: Shipped with the new site; each changed URL returns one 301 to a page that returns 200.
    • Blocks removed: Temporary noindex rules and robots.txt blocks taken off the live site, by a named owner.
    • Sitemap: New canonical URLs only, submitted in Search Console.
  4. The weeks after launch

    • Monitoring: The Page indexing report, plus clicks, queries and enquiries compared with the baseline, for several weeks.
    • Upkeep: Unexpected 404s and wrong redirects fixed; redirects kept for at least a year.

If you are planning a larger change, website redesign covers the page inventory and the URL plan; development and migration are agreed separately. For an existing site with indexing or speed problems, technical SEO and SEO audits are listed under search services. You can see how we scope and agree the work on how we work.

Sources

Frequently asked questions

  • Yes. Templates, text, internal links, rendering and metadata can all change while the addresses stay the same. Everything in this checklist except the redirect checks for changed URLs still applies.

  • Google says to keep redirects for as long as possible, and generally for at least a year. Keep them longer for old URLs that still receive visits or have links from other sites.

  • Google says rankings may fluctuate while it recrawls and reindexes a moved site, and that a small to medium-sized site can take a few weeks for most pages to move. Investigate a drop that continues or affects particular pages: check for wrong redirects, leftover noindex rules, removed content and pages that no longer render. Compare those pages with the baseline, and also consider changes in demand or search competition before attributing the whole drop to the migration.

Planning a redesign?

Tell us what is changing on your site and which pages matter most to your business. We can help you map the URLs, plan the migration checks and agree the next step.

Discuss your redesign

Let’s build your next advantage

Tell us what you want to launch, improve or automate. Let’s discuss the scope and the next step.

Get in touch

Prefer email?

sales@cursopic.com

Cursopic

Tell us about your project

What would you like to launch, improve or automate? A few lines are enough to start.

We use what you send only to reply to you about your request. Privacy policy (opens in a new tab)

Prefer email?

sales@cursopic.com