How to Redesign a Website Without Losing SEO: A Checklist

To redesign a website without losing SEO, keep your existing URLs wherever you can, 301-redirect every URL that does change to its closest new equivalent, and carry over the titles, headings, content, internal links and structured data that earned your rankings. Then remove any staging blocks at launch and watch Google Search Console closely for the next 30 to 90 days.

Most traffic losses after a redesign come from a short list of avoidable mistakes, not from the redesign itself. This checklist walks through what to do before, during and after launch, with a dedicated section for Shopify stores.

Why redesigns lose rankings

Rankings drop after a redesign for predictable reasons:

1. URLs change without redirects. Google and your backlinks point to pages that now return 404.
2. Redirects point to the wrong place. Sending everything to the homepage throws away the relevance of each old page.
3. Content gets cut. A cleaner design often means shorter pages, and the paragraphs that ranked disappear.
4. On-page elements get overwritten. Titles, meta descriptions, H1s and image alt text revert to template defaults.
5. Staging blocks go live. A leftover noindex tag or robots.txt rule tells Google to drop the whole site.
6. Internal links break or thin out. New navigation stops linking to pages that used to get internal authority.

Everything below is designed to prevent one of these six.

Pre-launch: website redesign SEO checklist

1. Crawl the current site

Run a full crawl with a tool like Screaming Frog or Sitebulb and export every URL with its status code, title, meta description, H1, canonical tag, word count and structured data. This file is your reference point. You'll compare the new site against it before and after launch.

2. Benchmark performance

Export the following before anything changes:

• Search Console: clicks, impressions and average position by page and by query, for at least the last 12 months
• Analytics: organic sessions and conversions by landing page
• Backlinks: the pages with the most external links, from Ahrefs, Semrush or Search Console's Links report
• Rank snapshot: positions for the 20 to 50 queries that matter most to your business

3. Flag your high-value pages

Combine those exports into one list and mark each URL that gets organic traffic, has backlinks, or converts. These are the pages that must arrive on the new site intact: same URL if possible, same core content, same or better internal linking.

4. Build the URL map

Google's own migration guidance says "it's important to map your old site's URLs to the URLs for the new site," starting from your sitemaps, server logs and analytics (Google Search Central). Use a spreadsheet:

Old URL	New URL	Action	Priority	Notes
/services/web	/web-design	301	High	Has backlinks
/blog/old-post	/blog/old-post	Keep	Medium	No change
/promo-2023	/sale	301	Low	Closest equivalent

Every old URL gets a row. The best redirect is to the page that answers the same intent. If a page is truly gone with no equivalent, letting it return a 404 is honest, but do that on purpose, not by accident.

5. Set up redirects properly

• Use permanent redirects. Google treats 301 and 308 redirects as a signal that the target should be canonical; 302 and 307 are not treated that way (Google Search Central).
• Redirect server-side. Google recommends JavaScript redirects only when server-side or meta refresh redirects aren't possible (Google Search Central).
• Avoid chains. If old URLs already redirect somewhere, point them straight at the final new URL.
• Keep them. Google advises keeping redirects "for as long as possible, generally at least 1 year" (Google Search Central).

6. Preserve what earned the rankings

For every high-value page, check the new version keeps:

• Title tag and meta description (improve them if you like, but on purpose)
• One clear H1 matching the page's topic
• The body content that ranks, including FAQs and specs that might be tucked into tabs or removed in the new design
• Image alt text
• Internal links to and from the page, including footer and navigation links
• Structured data (Product, Breadcrumb, FAQ, Organization and so on)
• A self-referencing canonical tag, which Google recommends for each new URL, plus updated hreflang tags if you run multiple languages (Google Search Central)

7. Protect the staging site, carefully

Your staging site shouldn't be indexed, but the way you block it can hurt you at launch. Password protection is the safest option because nothing needs to be removed from the code. If you use noindex, Google recommends preparing a list of the URLs you'll remove the rules from when the move starts (Google Search Central). Put "remove noindex and robots.txt blocks" on the launch checklist with a named owner.

8. Crawl staging and compare

Crawl the staging site and compare it to your original crawl. Look for missing pages, changed titles, missing H1s, thin pages and broken internal links. Test page speed and mobile layout on the key templates. Fix all of it before launch, when it's cheap.

Launch day checklist

Work through this in order on the day the new site goes live:

1. Remove noindex tags, password protection and robots.txt blocks used for staging.
2. Open /robots.txt on the live domain and confirm it isn't blocking important sections.
3. Deploy redirects, then crawl your full list of old URLs and confirm each returns a single 301 to a live 200 page.
4. Check canonical tags point to the live domain, not staging.
5. Confirm analytics and Search Console verification are still in place.
6. Submit the new XML sitemap in Search Console.
7. Use Search Console's URL Inspection tool on your top 10 to 20 pages and request indexing.

If you're also moving to a new domain, use Search Console's Change of Address tool. Google notes you only need it when moving from one domain or subdomain to another, not for path changes on the same domain (Google Search Central).

Post-launch: monitoring the first 30 to 90 days

Week 1: check daily.

• Search Console Page indexing report for spikes in "Not found (404)" or "Excluded by noindex"
• Crawl errors and server errors
• Organic traffic and conversions to your top landing pages
• Fix any 404 on a URL that had traffic or backlinks right away

Weeks 2 to 4: check twice a week.

• Compare clicks and impressions by page against your benchmark
• Watch Google swap old URLs for new ones in search results
• Re-crawl the site to catch new broken links from content edits

Months 2 and 3: check weekly.

• Compare rankings for your priority queries against your snapshot
• Review pages that lost the most clicks and compare the old and new versions line by line
• Look for slow pages or layout problems on mobile

Google's guidance is to "check regularly for any unexpected crawl errors" and to watch for an unusually high number of "Not found" errors (Google Search Central).

What a normal temporary dip looks like

Some movement is expected. Google says you "may experience ranking fluctuations while Google recrawls and reindexes your site," and that for medium-sized sites "it can take a few weeks or more" for the new URLs to replace the old ones in results (Google Search Central).

Full domain migrations are riskier than redesigns on the same domain. A 2026 study of 1,052 domain migrations by SALT.agency found that roughly one in four (22.8%) recovered pre-migration traffic within 90 days, with a median recovery time of 304 days (SALT.agency). An earlier version of the study, covering 892 domain migrations, reported an average of 523 days (Search Engine Journal). Keep the domain and the URLs and you avoid most of that risk.

How to tell normal from a problem:

Probably normal	Probably a problem
Small position swings across many pages	Specific pages drop out of the index entirely
Old URLs gradually replaced by new ones	Old URLs still ranking but returning 404
Impressions steady, clicks wobble briefly	Impressions fall sharply site-wide
Recovers week over week	Keeps declining after several weeks

If you see the right-hand column, go back to your crawl and URL map. The cause is almost always a missing redirect, a leftover noindex, or content that didn't make it across.

Shopify: redesigning without losing SEO

Shopify handles some of this for you and restricts other parts.

Shopify's URL structure is fixed

Shopify uses set prefixes: /products/, /collections/, /pages/ and /blogs/. You can't change the prefix, only the handle at the end (Meetanshi). That limits how much a redesign can break.

Theme change vs platform migration

• Changing themes on the same store doesn't change product or collection URLs. Titles, meta descriptions and product descriptions are stored in the admin, so they carry over. The risks are theme-level: different heading structure, missing structured data, removed content sections, fewer internal links and slower pages. Compare crawls before and after.
• Migrating from another platform to Shopify almost always changes URLs, because Shopify's prefixes won't match your old structure. For example, a WooCommerce product at /product/blue-mug/ becomes /products/blue-mug on Shopify. Every product, category, page and blog post needs a row in your URL map.

Setting up redirects in Shopify admin

• Create redirects in Content > Menus > URL redirects, or import them in bulk from a CSV (Shopify Help Center).
• Stores can hold up to 100,000 redirects, and Plus stores up to 20,000,000 (same source).
• Shopify redirects only work from broken URLs. If a live page still exists at the old address, the redirect won't fire, so delete or rename the old page first.
• Some reserved paths, like /cart, /apps and the bare /products and /collections paths, can't be redirected from.
• When you edit a product's URL handle, keep the "Create a URL redirect" option checked so Shopify redirects the old URL (Meetanshi).

Sitemap and password page

Shopify generates sitemap.xml automatically and updates it when you add products, collections and posts (Shopify Help Center). If you're launching a new store behind a password, Google can't read the sitemap until you remove the password, so remove it on launch day and then submit the sitemap in Search Console.

For the commercial side of a Shopify project, see our guides to Shopify website redesign and Shopify website cost, or how we approach web design projects.

FAQ

Does redesigning a website affect SEO?

It can, in either direction. A redesign that keeps URLs and content and improves speed and structure can help rankings. One that changes URLs without redirects, cuts content or leaves staging blocks in place can cause serious traffic losses.

How long does it take for SEO to recover after a redesign?

Google says that for medium-sized sites it can take a few weeks or more for new URLs to replace old ones in search results, and longer for large sites (Google Search Central). Same-domain redesigns that keep URLs usually see less disruption than domain changes. If traffic keeps falling after several weeks, look for a technical cause.

Should I change my URLs during a redesign?

Only if you have a clear reason, such as URLs that are confusing or don't match a new site structure. Every changed URL needs a permanent redirect and a short period of reprocessing by Google. If a URL ranks and makes sense, keep it.

How long should I keep 301 redirects after a redesign?

Google recommends keeping redirects for as long as possible, generally at least one year (Google Search Central). Keeping them longer costs little, and it keeps old links from other websites working.

Does changing my Shopify theme hurt SEO?

A theme change on its own doesn't change your Shopify URLs, and titles and meta descriptions carry over from the admin. Rankings can still drop if the new theme removes content, changes headings, drops structured data or loads more slowly. Crawl the store before and after to catch those differences.