Does a redesign hurt SEO?
A redesign only hurts SEO when it changes the things search engines were rewarding without redirecting or replacing them: URLs, page content, internal links, headings and technical signals. Change the look and keep those, and rankings usually hold or improve because the new site is faster and clearer. Change them without a plan and traffic can drop the week you launch and take months to recover.
The work below is not optional extra polish. It is the difference between a redesign that pays for itself and one that quietly costs you the leads the old site was bringing in. It also fits inside a normal project timeline if it starts at the beginning rather than the week before launch. For the wider process, see our guide to redesigning a website without losing traffic.
Before: benchmark what you have
Before anyone designs anything, record what the current site ranks for and which pages earn it. You cannot protect what you have not measured, and after launch this record is the only way to tell a real problem from normal noise.
| What to record | Where to get it | Why it matters |
|---|---|---|
| Every indexed URL | A crawl of the live site plus the sitemap and Search Console's pages report | This is the list you must redirect or keep |
| Top pages by clicks and impressions | Search Console, last 12 months | These pages need the most care |
| Top queries per page | Search Console, filtered by page | Tells you which words on the page are doing the work |
| Pages with backlinks | Search Console links report or a backlink tool | Losing these URLs loses authority you cannot easily rebuild |
| Current titles, descriptions and H1s | The crawl export | So the new site keeps what worked |
| Speed and Core Web Vitals | PageSpeed Insights and the Search Console report | The new site should beat these numbers |
| Conversion sources | Analytics: which landing pages produce enquiries or sales | These are the pages you protect first |
Export all of it to a spreadsheet dated the day you took it. Take a second snapshot the week before launch, because the numbers will have moved.
URL mapping and redirects
Every old URL needs one of three fates: it stays the same, it redirects permanently to the best matching new page, or it is deliberately retired. The URL map is the document that records that decision for each one, and it should be finished and reviewed before the new site goes live.
- Keep URLs where you can. The cheapest redirect is the one you do not need. If the page's job has not changed, keep its address.
- Redirect one to one. Point each retired URL at the page that best answers the same need, not the home page. A blanket redirect to the home page is treated much like a page that no longer exists.
- Use permanent (301) redirects. They tell search engines the move is final and carry ranking signals across.
- Avoid chains. If the old site already redirected A to B, point A straight at the new C rather than A to B to C.
- Include everything. Images, PDFs and old campaign URLs with backlinks count too.
- Test on staging. Run the whole list through a redirect checker before launch, then again after.
| Old URL pattern | New URL | Action |
|---|---|---|
| /services/web-design-services.html | /services/website-design | 301 redirect |
| /blog/2019/03/why-speed-matters | /blog/why-website-speed-matters | 301 redirect |
| /about-us | /about-us | Keep, no change |
| /promo-2021 | /services | 301 to closest page, then retire |
What to keep on each page
For every page that ranks, carry across the elements that earned the ranking, even if the design around them changes completely. Designers often see body copy as placeholder text; on a ranking page it is the asset.
- The title tag and meta description, unless you are improving them on purpose.
- The H1 and the subheadings, which tell search engines what the page covers.
- The body content, especially the sections that match the page's top queries. Trim and improve, but do not delete the substance.
- Internal links to and from the page. A redesigned navigation often removes links that were passing authority to deep pages.
- Image file names and alt text where images rank in image search.
- Structured data, such as FAQ, product or article markup.
- Any content in tabs or accordions that the old site loaded in the HTML. Make sure the new build still renders it in the page source, not only after a click.
Technical checks on the new build
Run these on the staging site before launch. Each one is a common cause of a post-launch drop.
- Staging is blocked from indexing with a password or a noindex rule, and that rule is removed at launch.
- Every page has one canonical tag pointing at its own final URL, not at staging.
- The robots.txt file does not block CSS, JavaScript or whole sections by mistake.
- An XML sitemap lists only final, indexable URLs and is referenced in robots.txt.
- The site is served over HTTPS only, with HTTP redirecting. Our guide to HTTP vs HTTPS explains why this matters for rankings.
- Page speed and Core Web Vitals match or beat the old benchmark. See website speed optimization for what to fix.
- Mobile layouts show the same content as desktop, not a cut-down version.
- Analytics and Search Console tags are present on every template.
- Custom 404 page returns a real 404 status, not a 200.
- Pagination, filters and search pages are either indexable on purpose or excluded on purpose.
Launch day
Launch on a day when someone can watch the site for the next 48 hours, and work through this list in order.
- Remove the staging block and confirm the home page and three deep pages are indexable.
- Test the full redirect list against the live domain.
- Submit the new sitemap in Search Console and request indexing for the top pages.
- If the domain changed, use the change of address tool in Search Console.
- Crawl the live site and fix any 404s, redirect chains or missing canonicals.
- Check that forms, tracking and conversion events fire.
- Update links you control elsewhere: social profiles, directories, email signatures, ad campaigns.
The 30 days after
Expect some movement in rankings for two to four weeks while search engines recrawl. What you are watching for is a sustained drop on specific pages, which almost always points at a missed redirect, a removed section of content or a technical block.
- Daily for the first week: Search Console coverage and 404 reports. Fix new errors the same day.
- Weekly: compare clicks and impressions per page with your benchmark. Investigate any page down sharply.
- Weekly: Core Web Vitals report, to catch a template that is slower than the rest.
- At 30 days: a full comparison against the benchmark and a list of pages that need content restored or improved.
The website redesign checklist covers the non-SEO tasks for the same period.
When you need a developer
You need a developer for the redirects, the technical checks and the crawl comparison. Marketing teams can and should own the benchmark, the content decisions and the URL map, but implementing redirects at the server level, fixing canonical and rendering issues, and diagnosing a post-launch drop are development tasks. If your redesign is being handled by a design-only team, ask who is responsible for this list before the project starts. The cost of doing it properly is covered in our guide to website redesign costs.
Next step
If you are planning a redesign and want the rankings to survive it, send us the site address and your Search Console access. We will benchmark it, produce the URL map, and give you a fixed-scope quote that includes the SEO work rather than treating it as an extra. See our website redesign service or start on the contact page.