Website Redesign Checklist: Keep Rankings and Win AI Search

A website redesign only hurts SEO when URLs, content or internal links change without a plan. This website redesign checklist walks you through what to do before, during and after launch — crawl and benchmark the old site, map every URL to a 301 redirect, keep the content that ranks, fix technical signals, and monitor Search Console for 60 days — so you keep your Google rankings and become easier for AI assistants to cite.

Use it as a working document with your designer, developer and whoever owns marketing. Every step below is something we do on our own redesign and migration projects.

Why redesigns lose traffic

Traffic drops after a redesign almost always come from one of a handful of causes:

• Changed URLs with no redirects. Old pages return 404, and the links and rankings they earned disappear with them.
• Removed or thinned content. A “cleaner” design often cuts the paragraphs, FAQs and product details that were answering search queries.
• Broken internal linking. New navigation hides pages that used to be one click from the homepage, so they get crawled and valued less.
• Technical regressions. A staging noindex tag left in place, a blocked robots.txt, missing canonical tags, heavier pages or JavaScript that search engines render poorly.
• Lost structured data and metadata. Titles, meta descriptions and schema markup that were tuned over years get replaced by template defaults.
• Too many changes at once. New domain, new platform, new content and new structure in one release — when traffic moves, nobody can tell why.

The good news: every one of these is preventable.

Before: crawl, benchmark, export Search Console data

Do this at least two to four weeks before launch, before anyone deletes or renames a page.

Crawl the current site. Use a crawler such as Screaming Frog (or any equivalent) to export every URL with its status code, title, meta description, H1, canonical, word count and inbound internal links. This is your source of truth.

Export Google Search Console data. From the Performance report, export pages and queries for the longest window available (Search Console keeps 16 months). Note which pages bring clicks, which queries they rank for and their average position.

Export analytics. From GA4 (or your analytics tool), export landing pages by sessions and conversions for the last 12 months. Some pages matter because they convert, not because they rank.

Record backlinks. Export the pages that other websites link to. Those URLs must never 404.

Benchmark performance. Record Core Web Vitals and page speed for your key templates, so you can prove the new site is faster rather than hope it is.

Checklist:

• Full crawl exported (URLs, status, titles, metas, H1s, canonicals)
• Search Console pages and queries exported (16 months)
• Analytics landing pages and conversions exported (12 months)
• Pages with backlinks listed
• Core Web Vitals baseline recorded
• List of “must-keep” pages agreed (top traffic, top conversions, top links)

URL mapping and 301 redirects

This is the single most important step of any website migration SEO checklist.

1. Keep URLs where you can. The safest redirect is the one you never need. If the old structure is clean, reuse it.
2. Build a redirect map. A spreadsheet with two columns — old URL, new URL — covering every URL from your crawl, Search Console export and backlink list.
3. Redirect one-to-one to the closest equivalent. Old service page → new service page, not → homepage. Mass-redirecting everything to the homepage is treated much like a 404.
4. Use 301 (permanent) redirects, implemented on the server or edge (for example in your hosting or Cloudflare rules), not with JavaScript or meta refresh.
5. Avoid chains. If A already redirects to B and B now moves to C, point A directly to C.
6. Handle parameters, trailing slashes, HTTP/HTTPS and www/non-www consistently.
7. Keep the redirects for the long term. Google advises keeping them for at least a year; we leave them in place indefinitely because old links keep sending visitors.
8. Changing domain? Use the Change of Address tool in Search Console after the redirects are live.

Test the redirect map on staging by running your old URL list through a crawler and confirming every line returns a single 301 to a 200 page.

Content: keep what ranks, rewrite what doesn’t, add answer-first FAQs

Sort every page from your crawl into three groups:

Group	Criteria	Action
Keep	Brings clicks, ranks top 10, or converts	Migrate content almost as-is; improve formatting only
Improve	Has impressions but low clicks or rank 11–30	Rewrite to answer the query directly, add depth and FAQs
Merge or retire	No traffic, no links, duplicates another page	Merge into a stronger page and 301 it, or retire it

For pages you rewrite, write answer-first: the first two or three sentences should answer the question the page targets, followed by detail, examples, tables and a short FAQ. This structure helps classic rankings and makes the page easier for AI assistants — ChatGPT, Gemini, Perplexity, Google AI Overviews — to quote. We explain that side in depth in how to get recommended by ChatGPT.

Also preserve the details designers tend to cut: specifications, prices or price ranges, locations, opening hours, author names and dates. They are exactly what search engines and AI systems use to decide whether a page is trustworthy.

Technical: speed, structured data, hreflang for multilingual sites

Speed and Core Web Vitals. Aim for “good” on all three metrics: Largest Contentful Paint at or under 2.5 seconds, Interaction to Next Paint at or under 200 milliseconds, and Cumulative Layout Shift at or under 0.1. In practice that means compressed modern image formats with explicit sizes, minimal third-party scripts, server-rendered or static HTML, and a CDN. A redesign is the cheapest moment to fix Core Web Vitals, because you are rebuilding templates anyway.

Structured data. Add schema markup that matches what is on the page: Organization and LocalBusiness for your business details, Service or Product for offerings, BreadcrumbList, FAQPage where you have a real FAQ, and Article for blog posts. Note that Google stopped showing FAQ rich results in May 2026; FAQPage markup is still valid Schema.org and harmless, but the visible FAQ text on the page is what now does the work. Validate your markup with Google’s Rich Results Test or the Schema.org validator.

Hreflang for multilingual sites. If you publish in several languages, every language version needs hreflang annotations pointing to all its alternates (including itself), plus an x-default. The links must be reciprocal, and each version should have its own URL — for example /az/, /ru/ subfolders — not a language switcher that swaps text on the same URL.

Indexing hygiene. Self-referencing canonicals, a fresh XML sitemap containing only 200-status canonical URLs, a robots.txt that allows crawling, and no leftover noindex from staging.

Launch day checks

Run this list in the first hours after the new site goes live:

• robots.txt allows crawling; no noindex on production pages
• Redirect map tested against production: every old URL returns one 301 to a 200 page
• Top 50 pages (by traffic and conversions) load, render and show correct titles and metas
• Canonical tags point to the new, final URLs
• New XML sitemap submitted in Search Console
• Hreflang and schema validated on key templates
• Analytics and Search Console verification working; conversion events firing
• Forms, booking, phone and WhatsApp links tested end to end
• 404 page is helpful and logged, so you can catch missed redirects
• Internal links updated to new URLs (do not rely on redirects inside your own site)

First 60 days: what to monitor in Search Console

Days 1–14 (daily):

• Page indexing report — are new URLs being indexed, and are old URLs moving to “Page with redirect”?
• Crawl errors and 404s — fix any missing redirect the same day.
• Performance → Pages and Queries — compare your top 20 pages and queries with the baseline you exported.
• URL Inspection — request indexing for your most important new pages.

Days 15–60 (weekly):

• Clicks and impressions versus the same period before launch (and year-on-year if you are seasonal).
• Core Web Vitals report for the new templates.
• Enhancement reports (breadcrumbs, products and other supported types) for schema errors.
• Queries that dropped: check that the matching page still answers them, and restore content if needed.

Some fluctuation in the first weeks is normal while Google recrawls. A sustained drop on specific pages almost always traces back to a redirect, content or indexing problem on those pages — which is why the benchmark you took before launch matters.

How Racool Studio can help

We design and build websites with SEO and AEO in from the first wireframe, not added after launch. For Shukurlu Design, an architecture and interior studio, we organised 200+ project renders by project, deployed on Cloudflare for speed and set up analytics plus SEO/AEO. For Magna, a glass manufacturer, we built a corporate site and a 7-product catalogue in Azerbaijani, English and Russian, with specs, an FAQ and schema on every product — a textbook case for hreflang and structured data.

If you are planning a redesign, start with a free pre-migration SEO snapshot before you touch a single URL: we review your current rankings, the pages you cannot afford to lose and the risks in your plan. See our website design and redesign and SEO & AEO services, check what a website costs, or request your snapshot.