Before a redesign launches, check that every URL that earns visits stays the same or redirects permanently to its closest new match, and that staging blocks are gone. Then watch Search Console. Google’s site-move guide says to expect temporary ranking fluctuation, so plan for a dip and for the checks that limit it.
By Donnie Strompf. Updated October 2026.
Key takeaways
- List every URL that earns visits or links before design starts. The redirect map comes from that list.
- Send each changed URL to its closest match with a permanent server-side redirect. A blanket redirect to the home page loses the match.
- Remove staging noindex tags and robots.txt blocks at launch. Google’s site-move guide says to.
- Use Google’s Change of Address tool only when the site moves to a different domain or subdomain.
- After launch, compare Search Console with the numbers you saved and read the reasons in the Page indexing report.
- Keep redirects as long as possible. Google says generally at least a year.
Does a website redesign hurt SEO?
It can, because a redesign changes what Google reads: addresses, page text, templates, internal links and structured data. A new look on the same addresses carries less risk than new addresses, but both need checks.
Google’s guide to site moves with URL changes (Google Search Central, updated August 20, 2026) says: “Expect temporary fluctuation in site ranking during the move.” For medium-sized websites, it adds, “it can take a few weeks or more for Google to gradually start showing the new URLs.” A separate guide to moves without URL changes (updated December 10, 2025) covers a change of host or CDN.
Neither guide promises a recovery date. They tell you what to prepare so the dip has a known cause. The first guide also says to plan changes “one after the other, not everything at the same time,” which is the case for treating a redesign, a domain change and a full copy rewrite as separate projects.
What kind of redesign are you doing?
Changing the design without changing URLs creates different SEO risks than moving pages or domains. Find your project in the table.
| What changes | Main risk | Change of Address tool? |
|---|---|---|
| Design or CMS, same URLs | Lost titles or text | No |
| URLs change, same domain | Missing redirects | No |
| New domain or subdomain | Redirects plus a Search Console request | Yes |
| New host, same URLs | Googlebot blocked | No |
| HTTP to HTTPS | Missing redirects | No |
Google’s Change of Address help page (Search Console Help) says Google “will figure out” an HTTP to HTTPS change for you. It points www changes to canonical tags and redirects, and path changes to redirects and updated sitemaps.
What is the full redesign SEO checklist?
Ask your developer or agency for the evidence listed in the last column.
| Phase | Task | How to verify |
|---|---|---|
| Before | Save baseline numbers | Dated export of clicks by page |
| Before | List every current URL | One spreadsheet row per URL |
| Before | Map old URLs to new | No blank rows, no chains |
| Before | Keep Search Console access | Verification works on new build |
| During | Protect the staging site | Private window shows a login |
| During | Compare mobile and desktop | Same content and metadata |
| During | Test redirects | Each type returns a permanent redirect |
| Launch | Turn on redirects | Old addresses reach right pages |
| Launch | Clear noindex and robots blocks | Source and robots.txt are clean |
| Launch | Submit the new sitemap | Sitemaps report reads the file |
| After | Inspect key pages | URL Inspection says indexable |
| After | Read Page indexing report | No new noindex or blocked reasons |
| After | Compare with baseline | Same pages, same date range |
| After | Update outside links | Profiles and ads reach new pages |
What should you do before the redesign starts?
Export your data before anyone changes the site. Search Console’s Performance report shows clicks, impressions, click-through rate and average position, grouped by query or page. Record those numbers for your top pages and queries before anything changes, and do the same in analytics.
Next, list the old URLs. Google says to check your server logs or analytics software for the URLs that get the most traffic, and a crawl of the live site fills in the rest. Then decide what happens to each one: keep the address, move it, merge it into another page, or retire it.
Ask whoever builds the site for the finished redirect map as a spreadsheet before launch day. A redesign without one cannot be checked.
What should the new site keep from the old one?
Keep the text, titles, headings, internal links and structured data of every page that earns traffic, unless the change is deliberate. Redesigns often trim copy to fit a template, and a page that ranked can stop answering the query.
Check the phone version too. Google’s mobile-first indexing guide (updated December 10, 2025) says Google “uses the mobile version of a site’s content, crawled with the smartphone agent, for indexing and ranking.” It tells you to keep the same content, structured data and robots meta tags on both versions, with equivalent titles and meta descriptions. It also says not to lazy-load primary content upon user interaction.
Test the new templates for speed before launch. Google’s Core Web Vitals guidance on web.dev (last updated October 31, 2024) sets the “good” thresholds at 2.5 seconds for Largest Contentful Paint, 200 milliseconds for Interaction to Next Paint and 0.1 for Cumulative Layout Shift. For the wider crawl and index checks, see our technical SEO guide.
How do you keep staging out of Google and then switch the live site on?
A staging site is a private copy where the build is tested. Staging pages can get indexed before launch, and staging restrictions can stay on after it.
The first risk is letting staging get indexed. Google’s robots.txt introduction (updated December 10, 2025) says robots.txt is “not a mechanism for keeping a web page out of Google” and recommends you “block indexing with noindex or password-protect the page.” Password protection suits staging best, because Google’s noindex documentation says a page blocked by robots.txt never has its noindex rule seen.
The second risk is launching with the staging blocks still on. The site-move guide notes that “some site owners block all crawling while in development,” and says: “Don’t forget to remove any noindex or robots.txt blocks that were only needed for the migration.”
The noindex page warns that “it may take months for Googlebot to revisit a page,” so a leftover tag is slow to clear. On launch day, open the live robots.txt and view the page source of the home page and one page of each template. If the new robots.txt came from a template, check that it admits the crawlers you want, including AI crawlers, as our guide to AI crawlers and robots.txt explains.
How do redirects work in a redesign?
A redirect sends visitors and Google from an old address to a new one. Google’s redirects documentation (updated April 14, 2026) says permanent redirects show the new target in search results. Use server-side redirects. The same page treats JavaScript redirects as a last resort, because if rendering fails, “Google might never see it.”
Google’s site-move guide recommends direct redirects, relevant destinations and proper error codes for removed pages. Redirect to the final destination directly instead of through a chain. Do not redirect many old URLs to one unrelated page, “such as the home page of the new site.” Removed content should return an HTTP 404 or 410. It also states that “301 and other permanent redirects don’t cause a loss in PageRank.”
| Situation | Do this | Avoid this |
|---|---|---|
| Page kept, address changes | One permanent redirect | Sending it to the home page |
| Two pages merged | Both redirect to the merged page | Leaving one as an error |
| Page retired, no match | Return 404 or 410 | A blanket home page redirect |
| Old http or www versions | Redirect to one preferred version | Several hops in a row |
Test a sample of every row before launch. The guide says the URL Inspection tool can test individual URLs, and any crawler or command-line request shows the status code and final destination.
When do you need Google’s Change of Address tool?
Only when the site moves from one domain or subdomain to another. The Change of Address page requires that you own both properties in Search Console, and the tool works on domain-level properties. Set up a 301 redirect from the old homepage to the new one first, and from the canonical pages where you can.
Google says it prioritizes the new site for 180 days after you start the migration, and to keep redirects at least that long. The site-move guide gives a longer general figure: keep redirects “for as long as possible, generally at least 1 year.” Use the longer one.
What should you do on launch day?
Use this list on launch day, and keep unrelated changes out of the release.
- Turn on the redirects and spot-check them against the map.
- Remove temporary noindex tags and robots.txt blocks.
- Confirm canonical tags, internal links and the sitemap use the new addresses.
- Submit the new sitemap in Search Console.
- Inspect your most important pages with the URL Inspection tool.
Google’s sitemap guide (updated July 8, 2026) says to “use fully-qualified, absolute URLs” and to list only URLs you want in Google’s results. The URL Inspection help page says “Test live URL” examines the page as it is requested now. You can request indexing there, but Google states that submitting a request does not guarantee the page will appear in the index.
Then update the places that link to you. Google’s guide lists internal links, external sites that link to you, your own profiles and ad campaigns that point to old landing pages. It also warns that “Google will temporarily crawl your new site more heavily than usual,” so the server needs headroom.
What should you watch after launch?
Google’s guide says to expect traffic to fall on the old addresses and rise on the new ones, and that a move is complete only once Googlebot has visited every old and new URL at least once. Compare Search Console’s performance data with your saved baseline, page by page, over the same date range.
Check the Page indexing report for blocked pages, unexpected noindex tags and missing URLs.
| Reason in the report | What it points to |
|---|---|
| URL marked “noindex” | A staging tag left on a live page |
| URL blocked by robots.txt | A staging rule left in the file |
| Not found (404) | A missing redirect or a retired page |
| Page with redirect | An old address that redirects, as expected |
| Soft 404 | An empty or error-like page with a normal status |
Chase the noindex and blocked reasons on pages that should rank. Google’s HTTP status documentation (updated February 4, 2026) says indexed URLs that return a 4xx status “are removed from the index.” After a fix, use Validate fix in the report. Google says validation typically takes up to about two weeks.
Who should run these checks?
Treat the checklist as a delivery list for whoever builds the site. Ask for the URL inventory, the redirect map, the launch-day robots.txt and a post-launch report as files you can open. Keep owner access to Search Console and analytics yourself, as our guide on who owns your website and marketing accounts explains.
The SEO fundamentals guide covers what search results depend on, and the website development page describes our design and development service. SEO price ranges are on the pricing page. Our guide to how much digital marketing costs for a small business sets out the ranges.
FAQ
How long do rankings take to recover after a redesign?
Nobody can name a date. Google describes a gradual changeover in which Googlebot must revisit every old and new URL, which takes longer on larger sites. Compare each important page with your saved baseline. A page that stays low after redirects and indexing look correct needs a content or technical review.
Do I have to redirect every old URL?
No. Redirect pages that earn traffic, links or bookings to their closest replacement. Pages with no equivalent should return 404 or 410, which Google treats the same way. Redirecting every dead page to the home page sends visitors somewhere they did not ask to go.
Is a 302 redirect acceptable on a redesign?
Not for permanent changes. Google’s redirects documentation says temporary redirects keep the source page in search results, while permanent ones show the new target. Use a 301 or 308 when the old address is never coming back. A 302 fits a short test or a seasonal swap.
Should I change my domain at the same time as the redesign?
Avoid it if you can. A new domain adds a Change of Address request, redirects across two properties and a fresh check of verification and settings. Launch the redesign on the current domain first, watch Search Console, and schedule the domain move as its own project.
My redesign keeps every URL. Do I still need these checks?
Yes, a smaller set. A leftover noindex tag, a blocked robots.txt, missing mobile content or lost structured data can appear without any address changing. Run the launch-day source checks, inspect the main templates, and watch the Page indexing report for new noindex or blocked reasons.
How long should the redirects stay?
As long as you can keep them. Google’s site-move guide says generally at least a year, and the Change of Address page names 180 days as the minimum for a domain move. Removing them early strands old backlinks and bookmarks that still bring visitors.
Related reading
- 10 email marketing landing page tips to increase conversions
- WordPress vs Wix vs Squarespace vs Shopify: which fits a small business?
Next step
The free AI-visibility audit comes first, then a 15-minute call.
Get your free AI-visibility audit
Marketing that works, in your inbox
AI search & SEO news, what’s working right now, and guides we actually use with clients. A couple of emails a month, no spam.
Unsubscribe anytime. We treat your inbox the way we treat our clients’ brands.