Website Redesign SEO Checklist: Protect Search Visibility

1. Separate a visual redesign from a URL or domain migration
2. Export URLs, search data and metadata
3. Decide what to keep, improve, merge or remove
4. Use a URL mapping table
5. Protect staging and check indexing settings
6. Prelaunch checks
7. Launch with backups and a rollback plan
8. Monitor after launch
9. Frequently asked questions

First, decide what kind of change you are making, because the risk is very different.

• Visual redesign only: new design, same URLs, same domain. This is the lowest-risk change. You do not need redirects for unchanged URLs.
• Redesign with URL changes: some pages get new paths or are merged. Every changed URL needs a redirect.
• Domain move: the site moves to a new domain or subdomain. This needs the full site-move process.

Google’s site move guidance notes that the Change of Address tool is for domain or subdomain changes only. You don’t need it for an ordinary visual redesign, an HTTP-to-HTTPS move or path changes within the same domain. If you can, avoid combining a domain move with a redesign. Doing both at once makes problems harder to trace.

Before anyone touches the design, capture a baseline. You will compare against it after launch.

• Every live URL from your XML sitemap and a site crawl.
• Top landing pages by clicks and impressions from the Search Console Performance report.
• Pages that generate enquiries, from your analytics or CRM.
• Title tag, meta description, H1 and canonical for each important page.
• Pages with external links pointing at them, if you have a backlink tool.

Save this as a spreadsheet with a date. In addition, note the settings in your SEO plugin, because a new theme or plugin can quietly change them.

A redesign is a good moment to clean up. However, removing content that ranks is the most common cause of lost traffic, so decide page by page.

A URL mapping table is the single most useful redesign document. Fill it in before development finishes, then use it to test the build.

Copyable migration table

These rows are examples to show the format. Notice the first row: when a URL does not change, no redirect is needed. Adding a redirect from a URL to itself creates a loop.

Google recommends server-side permanent redirects such as 301 or 308. It also advises against sending many old URLs to one irrelevant destination like the home page. In addition, it suggests keeping chains short, ideally no more than three hops (Google Search Central).

Keep the staging site out of search results. Password protection is the safest method, because a “noindex” setting can be copied to production by mistake.

Then, on launch day, check production immediately:

• WordPress “Discourage search engines” is off (Settings → Reading).
• No unexpected noindex in page source or HTTP headers.
• robots.txt does not block the whole site or key folders.
• The sitemap lists only live, indexable, final URLs.

Before launch

• Every redirect in the mapping table returns the right status and lands on a 200 page in one hop.
• Each new page has one canonical tag pointing to itself, unless it is a deliberate duplicate.
• Titles, meta descriptions and H1s from the baseline are carried over or improved, not reset.
• Internal links point to final URLs, not to redirects or 404s.
• Important text is in the HTML, not hidden behind tabs that only load on click.
• Structured data validates and matches visible content.
• Enquiry forms and WhatsApp buttons work and still fire tracking events.

Take a full backup of files and database just before launch. Next, write a short rollback plan: who decides, how long a rollback takes, and what triggers it. After switching, clear every cache layer, including the plugin cache, server cache and CDN. Finally, check the live pages again as a logged-out visitor, because cached old pages can hide problems.

After launch (same day)

• Crawl the live site and compare with the baseline URL list.
• Test a sample of old URLs from the mapping table in a browser.
• Submit the XML sitemap in Search Console if its location changed.
• Inspect the homepage and two key service pages with URL Inspection.
• Submit a test enquiry and confirm it arrives and is tracked.

Ranking movement after a redesign is common while Google recrawls. Google says a site move can take a few weeks for most pages on a small or medium site. It also recommends keeping redirects for at least a year (source). Therefore, compare weeks, not days.

Each week for the first two months, check:

• Search Console page indexing report for new “Not found (404)” or redirect errors.
• Clicks and impressions for your top 20 baseline landing pages.
• Enquiries by landing page, compared with the same period before launch.

If a page drops sharply, compare its old and new content first. Usually the cause is missing text, a changed title or a broken redirect. For ongoing checks like these, see our website management service or our guide to website maintenance costs in India.

Before you approve a redesign, ask your developer for the URL mapping table and the prelaunch checklist above. If you would like us to review a redesign plan or build the site with SEO continuity included, see our website development service or get in touch.

• Google Search Central, Site moves with URL changes (checked 25 October 2026).
• Google Search Central, Ask Google to recrawl your URLs (checked 25 October 2026).