Website Redesign SEO Checklist: How to Keep Your Rankings
Use this website redesign SEO checklist to keep rankings: URL inventory, 301 redirect maps, metadata parity, sitemaps and post-launch Search Console checks.
By Devma Team · · 10 min read

A website redesign SEO checklist protects your rankings by making sure every old URL, page, title, internal link and piece of structured data has a clear home on the new site before it goes live. Most traffic losses after a redesign come from a few preventable problems: changed URLs without proper 301 redirects, thinner content, and staging settings like noindex that ship to production. Follow the pre-launch, launch-day and post-launch steps below and your redesign can protect, and sometimes improve, your organic and AI search visibility.
Key takeaways
- Google treats a redesign that changes URLs as a site move and processes it page by page, so a temporary ranking wobble is normal even when the migration is done right.
- Map every old URL to its most relevant new URL with server-side 301 or 308 redirects, and keep those redirects for at least one year.
- Permanent redirects do not cause a loss in PageRank, but redirect chains, 302s and mass redirects to the homepage weaken or confuse the signal.
- The most damaging launch mistake is shipping a staging
Disallow: /in robots.txt or a site-widenoindextag to the live site. - Google's AI Overviews and AI Mode rely on normal indexing and snippet eligibility, so a clean SEO migration also protects your AI search visibility.
Why can a website redesign hurt SEO?
Search engines rank individual URLs, not your website as a whole. Each URL has built up signals over time: links from other sites, internal links, topical relevance from its content, and a history in search results.
When a redesign changes slugs, folder structures or the domain, Google's site move guidance counts it as a site move. Googlebot has to crawl every URL on both the old and new versions at least once before the move is complete, and Google's own advice is to be patient and give it time.
Rankings usually drop for one of four reasons:
- URLs changed with no redirect, or with a redirect to the wrong page.
- Content was cut, merged or rewritten so it no longer answers the same search.
- Titles, headings, canonical tags or structured data were lost in the new templates.
- Crawling or indexing was blocked by accident.
If your redesign keeps every URL exactly the same, Google has a separate, simpler guide for moving a site without URL changes. The content, metadata and indexing checks below still apply.
Website redesign SEO checklist: before launch
Most of the work happens before the new site goes live. Put these tasks in the project plan from the start, not in the final week.
1. Build a complete URL inventory
You can't redirect URLs you don't know about. Combine at least three sources:
- A full crawl of the current site with a desktop SEO crawler.
- Landing pages from GA4 and Search Console over the last 12 to 16 months. These catch pages that get traffic but are poorly linked internally.
- Pages with backlinks from your backlink tool, plus server logs if you have access to them.
Merge everything into one spreadsheet with columns for old URL, status code, organic clicks, backlinks, title tag and H1. This becomes both your redirect map and your parity checklist. If you want a structured review, an SEO audit before design work begins is the cheapest point to catch problems.
2. Map every old URL to its best new match
Every old URL that returns a 200 status today needs a decision: keep, redirect or retire. Google recommends server-side permanent redirects (301 or 308) for URLs that have moved for good. It also warns against irrelevant redirects, such as pointing many old URLs at the homepage.
| Old URL | New URL | Reason |
|---|---|---|
| /services/web-design.html | /website-design/ | Same topic, new slug |
| /blog/2021/seo-tips/ | /blog/seo-tips/ | Date folder removed |
| /glendale-plumbing-services/ | /locations/glendale/ | Duplicate location pages merged |
| /summer-promo-2022/ | No redirect (404 or 410) | Expired offer, no equivalent page |
A few rules keep the map clean:
- Match by relevance, one to one wherever possible. The new page should satisfy the same search intent as the old one.
- Redirect straight to the final URL. According to Google's HTTP status code documentation, Googlebot follows up to 10 redirect hops, but Google advises avoiding chains. If one is unavoidable, keep it short: ideally no more than 3 hops and fewer than 5.
- Collapse old chains. Fold redirects from previous migrations into your new map so each old URL resolves in a single hop.
- Retire honestly. If nothing on the new site covers a topic, a 404 or 410 is better than a redirect to an unrelated page.
3. Keep content and metadata parity
Designers often trim copy to make layouts cleaner. That can quietly remove the text a page was ranking for. Compare old and new versions of each important page and template for:
- Title tag and meta description
- H1 and main subheadings
- Body content depth and the questions it answers
- Image alt text
- Canonical tag (it should point to the new live URL, never the staging domain)
- Hreflang tags, if you run multiple languages or regions
If you also plan a major content rewrite, consider doing it in a separate phase after launch. Changing URLs, design and content all at once makes it much harder to diagnose any drop.
4. Plan internal links
Redirects catch outside links, but your own links should point directly at the new final URLs. Update navigation, footers, breadcrumbs, in-content links and buttons. Keep your most important service and product pages reachable within a few clicks of the homepage, and make sure no high-value page ends up orphaned with no internal links at all.
5. Carry over structured data
New themes and page builders often drop schema that the old site had. List every type you use today, such as Organization, LocalBusiness, Product, Article or BreadcrumbList, and confirm the new templates output it.
Before you rebuild anything, check Google's search gallery for the features it still supports. Google has restricted or retired several rich result types in recent years, including the 2023 changes to FAQ and HowTo results, so carry over markup that is valid and still useful rather than everything you once had. Test templates with the Rich Results Test (paste the code if staging is password protected). Our Schema Markup Generator can help you rebuild missing markup.
6. Prepare robots.txt and noindex settings for production
Staging sites are usually blocked from search engines, and those blocks sometimes go live with the new site. Know the difference before launch:
- robots.txt controls crawling, not indexing. A blocked URL can still appear in results if other pages link to it.
- A
noindextag only works if Google can crawl the page. As Google's guide to blocking indexing explains, a page blocked in robots.txt can't have its noindex seen. - Password protection is the safest way to hide staging. It doesn't depend on files you might forget to change.
# Staging robots.txt (must NOT go live)
User-agent: *
Disallow: /
# Example production robots.txt for WordPress
User-agent: *
Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.php
Sitemap: https://www.example.com/sitemap_index.xml
On WordPress, also confirm the "Discourage search engines from indexing this site" box under Settings, Reading is unchecked on production. Our Robots.txt Generator is handy for drafting a clean production file.
7. Build the new XML sitemap
Include only canonical, indexable new URLs that return a 200 status. Per Google's sitemap documentation, one sitemap can hold up to 50MB uncompressed or 50,000 URLs; split larger sites and use a sitemap index. Separate sitemaps for sections like products, blog posts and locations make indexing easier to track.
Google ignores <priority> and <changefreq> and only uses <lastmod> when it is consistently and verifiably accurate. A common mistake is stamping every URL with the launch date. Use the date each page's content actually changed.
8. Verify Search Console and record a baseline
In Google Search Console, verify every variant of your site (www and non-www, HTTP and HTTPS) or use a domain property. Check that verification still works with the new templates, and clear any leftover URL removal requests, especially a site-wide one.
Then capture a baseline you can compare against later:
- Search Console clicks and impressions by page and by query, for the last 3 and 12 months
- GA4 organic landing pages, sessions and conversions
- Positions for your priority keywords
- Your current Page indexing report numbers
Make sure conversions are tracked the same way on old and new templates, or your comparison won't be fair. Our guide to GA4 form conversion tracking for lead forms covers that setup.
Launch day: what to check when the new site goes live
Launch day is about deploying carefully and confirming nothing slipped through.
- Deploy redirects at the server level. Avoid JavaScript or meta refresh redirects for permanent moves.
- Test redirects in bulk. Crawl your full old URL list in list mode and confirm each returns a single 301 or 308 to a live 200 page. Spot-check top pages with the URL Inspection tool in Search Console.
- Check indexing controls on the live site. Review robots.txt, meta robots tags,
X-Robots-Tagheaders and canonical tags on every template. - Submit the new XML sitemap in Search Console and Bing Webmaster Tools.
- Use Change of Address only if the domain changed. Google updated its guidance in June 2026 to say you should submit it for every variant, including www and non-www (Google Search Central updates).
- Annotate the launch. Add a dated note to your GA4 report charts and Search Console Performance report where annotation features are available. If you don't see the option, keep a dated change log instead.
- Tell Bing. Use Bing Webmaster Tools (including its site move tool if your domain changed) and consider IndexNow to request faster recrawling. Bing's index also feeds Microsoft Copilot.
- Confirm tracking fires. Check GA4, conversion events and any Google Ads conversion tags in real time.
Here is what single-hop server redirects look like on Apache and nginx:
# Apache (.htaccess)
Redirect 301 /services/web-design.html https://www.example.com/website-design/
Redirect 301 /blog/2021/seo-tips/ https://www.example.com/blog/seo-tips/
# nginx
location = /services/web-design.html {
return 301 https://www.example.com/website-design/;
}
After launch: what to monitor in the first 12 weeks
Don't treat launch as the finish line. Google needs time to recrawl both versions, and that is when hidden problems show up.
| Timeframe | What to check | Where |
|---|---|---|
| First 48 hours | 404s from old URLs, redirect errors, robots and noindex, tracking | Crawler, URL Inspection, GA4 realtime |
| Weeks 1 to 2 | New URLs being indexed, old URLs moving to "Page with redirect" | Search Console Page indexing |
| Weeks 1 to 4 | Spikes in server errors or not-found responses | Search Console Crawl Stats |
| Weeks 2 to 8 | Clicks and impressions by page versus your baseline, soft 404s | Search Console Performance |
| Weeks 6 to 12 | Redirect chains, internal links still pointing to redirected URLs | Site recrawl |
| Ongoing | Ask sites linking to your top old URLs to update their links | Backlink tool, outreach |
Some fluctuation is normal. Google's guide notes that even well-run moves take time: a few weeks or more for a medium-sized site. Don't roll back the launch over a few days of movement. Instead, group pages by section and look for patterns. If one section dropped and hasn't recovered, compare those URLs against your redirect map and parity checklist first.
Finally, keep your redirects for as long as possible. Google's guidance is generally at least one year, which gives it time to pass signals, including links from other sites, to the new URLs. Many sites simply leave them in place permanently.
How do you protect AI search visibility during a redesign?
Google's AI features documentation says AI Overviews and AI Mode don't require any special markup or file. Pages need to be indexed and eligible to show a snippet. That means a clean migration is your AI visibility plan, with a few extra checks:
- Watch snippet controls. A new template that adds
nosnippetor a very lowmax-snippetvalue limits how your content can appear in Google's AI features. - Don't over-block crawlers. Blocking Google-Extended doesn't affect Google Search, but a careless robots.txt rule can block crawlers used by other assistants, such as Bingbot or OpenAI's OAI-SearchBot. Our AI Crawler Checker shows what your live robots.txt allows.
- Keep answers intact. Clear headings, concise definitions and factual detail make your content easier to understand and quote. Don't strip them out for a minimal design.
- Treat llms.txt as optional. Many SEO blogs recommend it, but Google representatives have said Google doesn't use it.
For more on the AI side, see our guides to optimizing for Google AI Overviews and the Generative AI report in Search Console. If AI answers are a major traffic source for you, generative engine and LLM SEO work is worth folding into the redesign plan.
Common redesign SEO mistakes to avoid
Most failed migrations repeat the same errors:
- Building the redirect map from a crawl alone and missing pages that only have backlinks or analytics traffic
- Redirecting everything retired to the homepage
- Using 302, JavaScript or meta refresh redirects instead of server-side 301s or 308s
- Leaving old redirect chains in place and linking internally to redirected URLs
- Losing titles, H1s, canonicals or schema in new templates
- Listing redirected or noindexed URLs in the new sitemap
- Removing redirects after a few months to tidy the server config
- Not marking the launch date, which makes later traffic changes hard to explain
Planning a redesign? Start with the SEO map
A redesign is the best chance you'll get to fix structure, speed and content, as long as you protect what already ranks. If you'd like help building the URL inventory, redirect map and launch plan alongside the new design, Devma Agency's website redesign service treats SEO migration as part of the project from day one, not an afterthought.
Frequently asked questions
How long does it take rankings to recover after a website redesign?
It depends on site size and how cleanly the move was handled. Google processes a site move page by page, and its guidance says a medium-sized site can take a few weeks or more before new URLs replace old ones in results. If a specific group of pages has not recovered after a couple of months, audit those URLs against your redirect map rather than waiting longer.
Do I need the Search Console Change of Address tool for a redesign?
Only if your domain changes. A redesign on the same domain, even with new URL paths, does not use it, and it is not meant for HTTP to HTTPS moves. If you are changing domains, Google updated its guidance in June 2026 to say you should submit Change of Address for every variant, including www and non-www.
Should I redirect deleted pages to my homepage?
No. Google specifically advises against redirecting many old URLs to one irrelevant page such as the homepage. Redirect each old URL to the closest relevant new page, and if nothing on the new site covers the same topic, let it return a 404 or 410.
Is a 302 redirect okay during a website redesign?
For permanent URL changes, use a server-side 301 or 308 instead. Google treats a 302 as a weak signal and may keep showing the old URL in results, while a 301 or 308 is a strong signal that the new URL should be indexed. Permanent redirects also do not cause a loss in PageRank.
Do I need an llms.txt file to stay visible in AI search after a redesign?
No. Google says its AI features, such as AI Overviews and AI Mode, need no special file or markup, only normal indexing and snippet eligibility, and Google representatives have said Google does not use llms.txt. You can add one as an optional extra, but crawlability, indexing and content quality matter far more.








