Agency relationships
Will a website redesign lose my rankings?
A redesign can affect rankings. URL changes, removed content, crawl problems and performance changes are common risks. Inventory the current pages, preserve useful content, map changed URLs and test the new site before launch. Monitor indexing and enquiries afterwards. Planning reduces avoidable risks, but neither a checklist nor a fixed waiting period guarantees that positions will be preserved.
Why the fear is justified
This is not an imaginary risk. Sites do lose traffic after redesigns, sometimes badly and sometimes permanently.
A redesign can change more than appearance: content, URLs, links, performance and crawl settings can all change. A migration plan makes those changes reviewable. Search demand, competitors and search systems can also change, so outcomes are not entirely within an agency’s control.
Cause 1: URLs change without redirects
A common, avoidable migration problem.
Your old page lives at /services/roof-repair.html. The new site puts it at /roof-repair/. Nobody sets up a redirect.
Now every link pointing at the old address (from Google’s index, from directories, from a customer’s bookmark, from another site that linked to you) hits a 404. The ranking that page had accumulated has nowhere to go.
Crawl the existing site before anything is built. You need a complete list of every URL, which of them rank, and which get traffic. Screaming Frog does this free up to 500 URLs, which covers most local business sites.
Keep URLs that are working. A URL that ranks is an asset. Do not rename it because the new structure is tidier. Tidiness is worth less than the ranking.
Where a URL must change, redirect it one-to-one. Old page to the equivalent new page, with a 301. Not a bulk redirect of everything to the homepage: Google’s site move documentation warns that this can be treated as a soft 404, and it passes almost nothing.
Check it after launch. Crawl the old URL list and confirm every one lands where it should.
Cause 2: Content gets thinner
The quiet one.
The old service page had 900 words. The new design is cleaner, so it has a nice photo and two sentences.
It looks better. It ranks worse, because the page no longer answers what it used to answer, and the relevance that earned the ranking went with the text.
Record the word count and topics covered on every page that currently ranks, before rebuilding. Preserve or expand. If the old copy was genuinely bad, rewrite it, but rewrite it to be better and at least as complete, not shorter.
Design pressure is the usual culprit. A layout that looks best with two sentences will get two sentences. Design around the content the page needs, not the other way round.
Cause 3: The new site is slower
Redesigns frequently ship a heavier theme, a slider, a chat widget and six tracking scripts that were not there before.
Page experience is a ranking input, and speed affects conversion and Google Ads costs regardless of ranking. A prettier, slower site can lose on all three.
Measure before and after. Record the old site’s Lighthouse and Core Web Vitals numbers before it is replaced. Once it is gone you cannot. If the new one is slower, that is a defect to fix before launch, not a trade-off to accept.
What doesn’t cause ranking loss
Worth stating, because these come up constantly:
Changing how the site looks. Search engines do not rank aesthetics. A visual redesign with the same URLs and content is close to invisible to them.
Changing platform. Moving from WordPress to something else does not affect rankings by itself (see Astro vs WordPress for when to move). The URL structure and content are what matter.
Losing your Google reviews. Reviews live on your Google Business Profile, not your website.
Your domain age resetting. It does not. Same domain, same history.
What to check after launch
| When | What to check |
|---|---|
| Launch | Old URLs, direct redirects, indexability, internal links, forms and campaign attribution |
| First review | Crawl errors, unexpected canonical choices and pages missing from the sitemap |
| Following reviews | Query and landing-page trends against the baseline, demand and seasonal context |
| If enquiries fall | Check measurement and delivery as well as search traffic; investigate specific failures |
Google describes temporary fluctuation during a site move and variable processing time. It does not promise that every site will recover by a particular week.
Fix confirmed errors promptly. Keep a change log and avoid unrelated edits in reaction to a small daily movement, because extra variables make the cause harder to assess.
The migration checklist
Before
- Full crawl of the existing site: every URL
- Record which pages rank and which get traffic
- Record current Lighthouse and Core Web Vitals
- Record word count and topics on ranking pages
- Confirm access to domain, hosting, analytics, Search Console
- Take full-page screenshots of the current site. You cannot get them back later
At launch
- 301 redirects live and tested, one-to-one
- Old URLs crawled to confirm they resolve correctly
- Sitemap submitted in Search Console
- Analytics on the same property. Do not create a new one
- Tracking verified before, not after
- Speed measured and compared
After
- Search Console checked for crawl errors, weekly for a month
- Coverage report checked for pages dropping out
- Investigate confirmed errors; record fixes and avoid unrelated reactive changes
If you don’t have your logins
This stops more redesigns than budget does, and it is usually solvable. Start by checking who owns the domain, hosting and analytics.
The domain can be recovered through the registrar with proof of business ownership. Hosting can be identified from DNS records. Analytics can sometimes be reclaimed and, worst case, restarted, losing history but not rankings. Search Console can be re-verified through DNS or a file on the site.
It takes paperwork and time. Start it before any design work, because there is no point building a site you cannot deploy. Our website redesign and migration service starts with exactly that.
A migration plan you can review
Keep an inventory with the old URL, its traffic and enquiry baseline when available, intended destination, useful content to preserve and launch checks. If a kitchen-remodelling page keeps serving the same need, keeping its address may avoid an unnecessary move. If it must move, map it directly to the equivalent page. This is a planning example, not a claim about a client’s ranking results.
Review titles, canonical, language alternates, indexability, internal links and the sitemap. Test forms, phone links and campaign attribution too: keeping visibility is not enough if an enquiry can no longer arrive. Search Console’s selected canonical and indexing results still need a live check after release.
Request a redesign assessment with your current site. We can define the migration scope and the record of checks in writing before changing the pages.