Does a website redesign affect SEO, and what actually changes?
It can, but not through the design. Google cares about the address of each page, the words on it, and the links that lead to it, and new colours and fonts aren't what it ranks. What it notices is a page answering at a new URL, a page that's been cut, or copy that no longer says what it used to. Every changed address needs a 301 to the page that replaced it, which is the core of my redesign and migration SEO service. Without one, its rankings stay attached to a URL that now returns a 404.
I'll be plain about where a website redesign and SEO split, because it decides who does what. I don't design or build the new site. That's your designer's or developer's job, and it stays with them. My part is the search side: the benchmark before work starts, the SEO brief the designer works from, the redirect map, the staging review and the Search Console checks in the weeks after launch.
The risk sits in four places, and none of them is visual.
| What changed | What Google sees | What protects it |
|---|---|---|
| URLs renamed or restructured | The old address returns a 404, and the rankings attached to it fade | A one to one 301 map, decided before launch |
| Pages cut or merged | The queries that page answered lose their answer | A decision per page that earns clicks, made before the new sitemap's final |
| Copy rewritten or hidden | The new page no longer matches the query it ranked for | Checking new copy against each page's top queries |
| Settings carried over from staging | A noindex or a staging canonical tells Google to drop the page | A launch check of the live HTML, not the dashboard |
What's on my website redesign SEO checklist?
Four stages, in this order. Each one links to the part of this post that explains it.
- i.
Before the build
Benchmark every page that earns clicks, then give the designer an SEO brief with a keep, change, merge or remove decision per URL and the redirect map started.
- ii.
On staging
Crawl the build against the benchmark, run the redirect map against it, read the protected pages against their queries and check the mobile render.
- iii.
Launch day
Clear the staging settings, re-run every redirect on the live domain within the hour and submit the new sitemap in Search Console.
- iv.
After launch
Compare clicks by page with the benchmark and add a redirect for every old URL that turns up as Not found.
Which pages do I benchmark before the designer starts?
Before the designer drafts a page list, I record what the current site earns, page by page. Without that snapshot, a drop after launch turns into a guess about which pages changed.
The core of it is Search Console's Performance report grouped by page. Search Console truncates any export to 1,000 rows, so a bigger site needs several exports or the API. I take the last three months, and the same window a year earlier if the business is seasonal.
| What I record | Where it comes from | What it's for after launch |
|---|---|---|
| Clicks, impressions and top queries per page | Search Console's Performance report, by page | Spotting which pages lost clicks, and which queries they lost |
| Title, meta description, H1 and canonical per URL | A crawl of the live site | Checking the new build carried them across, or improved them |
| Pages other sites link to | A backlink export | Making sure every linked address gets a redirect |
| Pages that bring enquiries or sales | Analytics landing pages with conversions | Knowing which pages can't be cut on looks alone |
| Structured data and index status | The live HTML and Search Console's Pages report | Catching markup or index states the redesign dropped |
The output is one spreadsheet sorted by clicks. The top of it is the part of the site that pays for itself. Pages at the bottom with no clicks, no links and no conversions are the ones the designer can merge or drop with the least risk, and I say so in writing.
Rather have me do this? One person, whole job.
Book a call on UpworkWhat goes into the SEO brief I give the designer?
The brief is short on purpose, because a long SEO document won't get read. Each point is tied to the URLs it applies to.
- i.
The URL list, with a decision per URL
Every URL from the benchmark gets keep, change, merge or remove. Keeping an address is the cheapest protection there is. When one does change, the brief names its new home, so the redirect map is half written before the build starts.
- ii.
The pages that don't get cut without a conversation
The top of the clicks list is marked. If the new sitemap drops or merges one of those pages, we agree on it with the numbers in front of both of us.
- iii.
The copy that's earning the queries
For each protected page I list the queries it ranks for and the passages that answer them. New copy can be shorter or better, but the words that match a query have to survive.
- iv.
Titles, meta descriptions and H1s
They come across or get rewritten on purpose, never left blank by a new theme. Google lists the title element and headings like the H1 among the sources it uses for a page's title link.
- v.
Internal links and navigation
Pages the current menu links to stay reachable from the new one, and internal links point straight at new URLs, not through redirects.
- vi.
Structured data and canonicals
Whatever markup the old pages carry gets rebuilt on the new templates, and each new URL gets a self-referencing canonical, as Google's guidance for moves with URL changes asks.
- vii.
How staging stays out of Google
A password on staging is the cleanest option. If it's blocked with noindex or robots.txt instead, the brief says how that comes off at launch. Google notes that noindex only works when robots.txt doesn't block the page.
The brief works best before the designer drafts the new sitemap. Changing a slug in a spreadsheet costs nothing. Changing it after the pages are laid out costs rework.
How do I review the staging site before launch?
Staging is where the brief gets checked against what was actually built. I run this once the build's called finished, and again after late changes.
- Step 01
Crawl staging and compare it with the benchmark
Same crawler, same settings. I line up titles, H1s, canonicals and word counts URL by URL, and flag anything that went blank or shrank sharply.
- Step 02
Run the redirect map against staging
Every old URL should land on its new page in one hop, with a 200 at the end. Chains, loops and 404s get fixed here.
- Step 03
Read the protected pages against their queries
If a query has lost its answer, I send the designer the missing passage rather than a vague note.
- Step 04
Check the mobile render
The main copy, headings and structured data on phones have to match the desktop version, since that's the version Google indexes.
- Step 05
List the settings that change at launch
WordPress's Discourage search engines box adds a noindex, nofollow robots meta tag to every page. That box, any robots.txt Disallow and any canonical naming the staging hostname go on a short list for the day.
- Step 06
Agree the launch-hour checks
The developer does the switch. I re-run the redirect list and the live HTML checks on the real domain within the first hour.
WordPress's own documentation says the Discourage search engines box doesn't block access to a site. It only asks search engines not to index it, and it's up to them to honour that. A staging site anyone can open needs a password as well.
Which website redesign SEO mistakes cost the most rankings?
The same six turn up again and again, and each one maps to a row in the risk table above.
- i.
Changing URLs that didn't need to change
A new structure looks tidier, but every changed address needs a redirect and a recrawl. If the old URL was fine, keeping it costs nothing.
- ii.
Cutting pages that earn clicks
A page that looks thin can still answer a search nobody else on the site answers. Cut it without a redirect to its closest match and those queries lose their answer.
- iii.
Rewriting the copy that matched the queries
Shorter copy is often better copy, until the sentence that answered the search disappears. That's why the brief lists the passages to keep.
- iv.
Hiding copy on phones or behind a click
Google says it uses the mobile version of a site for indexing and ranking, and won't load content that needs a click, a swipe or typing to appear. Copy trimmed on phones is copy Google no longer sees.
- v.
Redirecting everything to the homepage
It's quick, and it throws away the match. Google says sending many old URLs to one irrelevant page like the homepage might be treated as a soft 404.
- vi.
Shipping staging settings
A noindex, a Disallow or a canonical naming the staging address looks fine in a browser and tells Google to drop the page. I read them in the live source.
What happens if traffic drops after launch anyway?
Some movement is normal. Google's site move guidance warns that rankings may fluctuate while it recrawls and reindexes, and that on a medium-sized site the new URLs can take a few weeks or more to replace the old ones in results. I won't put a date on when things settle.
What I do is compare clicks by page against the benchmark. In the Pages report, old URLs listed as Page with redirect mean Google has found the 301s, while old URLs showing as Not found (404) are gaps in the map, and each one gets added the day it shows up. A page that kept its URL but lost clicks usually has a changed title, missing copy or a staging tag that shipped. New URLs that stay out of the index for weeks are a separate problem with its own diagnosis.
What a missing map costs is on record. On one WooCommerce store, a redesign that shipped without a redirect map took daily clicks from 162 to 49 between 12 and 15 June 2026.
If the drop started before launch, or doesn't line up with any page the redesign touched, it may not be the redesign at all, and that's what tracing a drop back to its real cause covers.
If a redesign's on the calendar and you'd like one person owning the search side, the benchmark, the brief, the staging review and the weeks after launch, that's the work I do alongside your designer. The build stays with them.
Book a call on Upwork
