Skip to content 
A website redesign SEO plan protects the rankings and leads your current site already earns. The short version: crawl and benchmark the old site before anything changes, map every old URL to its new home with permanent 301 redirects, carry over the content and metadata that rank, keep the staging site out of Google, and watch Search Console closely for the first 30 days after launch.
Most ranking drops after a redesign come from a handful of avoidable mistakes, not from the new design itself. This checklist is the process our team follows on WordPress redesigns for small businesses, healthcare practices and law firms, with links to the Google documentation behind each step. If you are new to how rankings work in the first place, our guide to what SEO is and how Google ranks small business sites is a good primer.
Why a website redesign can hurt SEO
Google ranks individual URLs, not your brand. When a redesign changes those URLs, removes pages, rewrites copy or changes how pages load, Google has to work out the new site again. That is where traffic gets lost. The usual causes are:
- Changed URLs with no redirects. Old links and bookmarks hit a 404 page, and the ranking signals those pages built up are not passed on.
- Deleted or merged pages. A service page that quietly ranked for a valuable phrase gets cut because it “looked thin” in the new design.
- Lost on-page elements. Title tags, meta descriptions, headings, alt text and schema markup do not carry over automatically to a new theme.
- Weaker internal linking. A simplified menu can leave important pages with far fewer links pointing to them.
- A staging site left blocked. The “discourage search engines” setting or a noindex tag from development goes live with the new site.
- A slower build. Heavy sliders, video headers and extra plugins push page speed backwards.
None of these are design problems. They are process problems, which is why a checklist works.
Website redesign SEO checklist at a glance
Use this table as the project tracker. Each phase is explained in more detail below.
| Phase | Task | Done when |
|---|---|---|
| Before you start | Crawl the current site and export every URL | You have a full list of live URLs, status codes, titles and meta descriptions |
| Before you start | Benchmark traffic, rankings and conversions | You have a dated snapshot of Search Console, analytics and lead numbers |
| Before you start | List your top pages | You know which pages bring organic visits, links and leads |
| Planning | Build the URL map | Every old URL has a new URL, or a reason to return 404 or 410 |
| Planning | Carry over content and metadata | Top pages keep their target keywords, titles, headings and copy that ranks |
| Build | Protect staging | Staging is password protected or noindexed, and that block is on the launch checklist to remove |
| Launch day | Switch on 301 redirects and test them | Every old URL returns a single 301 to the right new page |
| Launch day | Remove staging blocks and submit the sitemap | No stray noindex tags, robots.txt allows crawling, new sitemap submitted in Search Console |
| First 30 days | Monitor and fix | 404s, crawl errors, rankings and leads are checked weekly against the benchmark |
Before you start: crawl and benchmark
You cannot protect what you have not measured. Do this before the designer opens a new file.
- Crawl the live site. Use a crawler such as Screaming Frog or Sitebulb to export every URL with its status code, title tag, meta description, H1, canonical tag and word count. Save the file with the date.
- Pull URLs from more than one source. Google suggests building your URL list from your sitemaps, analytics, server logs and CMS, so you also catch pages the crawler cannot reach. Include PDFs and images that get traffic.
- Export Search Console data. Download 12 to 16 months of queries and pages from the Performance report, plus the Page indexing report.
- Record conversions. Note monthly form fills, calls and bookings from organic search. Rankings matter, but leads are the number you actually want to protect.
- Flag your top pages. Mark every page that gets organic clicks, has backlinks from other sites, or produces leads. These pages get the most care in every step that follows.
Build your URL map and 301 redirects
The URL map is the single most important document in a redesign. Google’s site move guidance says to map each old URL to its new counterpart and use server side permanent redirects. It is a simple spreadsheet with two columns: old URL and new URL.
Rules for the redirect map
- Keep URLs the same where you can. The safest redirect is the one you do not need. If /services/roof-repair/ works fine, keep it.
- Use permanent redirects. Google treats 301 and 308 status codes as permanent moves and uses them as a signal that the new URL should be the canonical one. Temporary 302 redirects do not send that signal, according to Google’s documentation on redirects.
- Redirect one to one. Send each old page to the most relevant new page. Google specifically warns against redirecting many old URLs to an irrelevant destination such as the home page.
- Go straight to the final URL. Avoid chains where page A redirects to B, which redirects to C. Update old redirects so they point to the final destination.
- Let removed content return 404 or 410. If a page has no equivalent on the new site and no traffic or links, a clean 404 or 410 is the honest answer.
- Keep redirects for a long time. Google recommends keeping them as long as possible, and generally for at least one year.
On WordPress, redirects can live in the server config, at the host level, or in a plugin such as Redirection or Rank Math. Server or host level rules are faster, but a plugin is easier for a small team to maintain. Whatever you choose, test the full list before launch.
Carry over content, metadata and internal links
A new design is a good time to improve copy, but your top pages need extra care. If a page ranks on page one today, treat its content as an asset, not a draft.
- Keep the target keyword and topic of every ranking page. Rewrite for clarity if you like, but do not change what the page is about.
- Move title tags and meta descriptions across deliberately. Copy them from your crawl export into the new pages, then improve them where needed.
- Preserve heading structure. One H1 per page that states the topic, with H2s that cover the sections people search for.
- Keep alt text, schema and FAQs. Theme changes often drop structured data and image alt text silently.
- Rebuild internal links. Google advises updating internal links to point at the new URLs, rather than relying on redirects. Check that your top pages still get links from the menu, footer or related content.
- Set self referencing canonicals. Each new page should have a canonical tag that points to its own new URL.
Protect the staging site, then unblock it at launch
Your staging site should never appear in Google, because a duplicate copy of your site in search results competes with the real one. Password protection is the most reliable option. If you use a noindex tag instead, know that Google can only see it when the page is crawlable: Google explains that a page blocked in robots.txt can still show up in results if other sites link to it, because Googlebot never sees the noindex rule.
The bigger risk is the reverse. We regularly see new sites launch with the WordPress “Discourage search engines from indexing this site” box still ticked, or with a sitewide noindex tag from staging. If your site drops out of search entirely after launch, our guide on why a website is not showing up on Google walks through how to diagnose it.
Launch day checks
Run this list on the day the new site goes live, ideally at a low traffic time early in the week so your team is around to fix issues.
- Turn on the redirect map and test every old URL. Each should return one 301 to the correct new page, not a 404, a 302 or a chain.
- Untick “Discourage search engines” in WordPress under Settings, then Reading, and remove any staging noindex tags or password protection.
- Check robots.txt allows crawling of the pages and the CSS and JavaScript files that render them.
- Crawl the new site and compare it with your pre-launch crawl: missing titles, duplicate titles, broken internal links, missing H1s and pages with noindex.
- Submit the new XML sitemap in Google Search Console and request indexing for your most important pages.
- Test every form, click to call link, booking widget and thank you page. Confirm analytics and conversion tracking still fire.
- Spot check key pages on a phone and make sure the mobile version shows the same content, headings and links as desktop.
The first 30 days after launch
Some movement is normal. Google says to expect temporary ranking fluctuation during a move, and that a medium sized site can take a few weeks or more for most pages to be processed. Your job is to separate normal settling from real problems.
| When | What to check | What a problem looks like |
|---|---|---|
| Day 1 to 3 | Search Console Page indexing report, server logs, 404 report | A spike in 404s or “Excluded by noindex tag” pages |
| Week 1 | Top pages: rankings, clicks and indexing status | A top page missing from the index or redirecting to the wrong place |
| Week 2 | Core Web Vitals and page speed on key templates | LCP, INP or CLS worse than the old site |
| Week 4 | Organic clicks and leads compared with your benchmark | A sustained drop on specific pages rather than a sitewide wobble |
For page experience, web.dev defines “good” Core Web Vitals as Largest Contentful Paint of 2.5 seconds or less, Interaction to Next Paint of 200 milliseconds or less, and Cumulative Layout Shift of 0.1 or less, measured at the 75th percentile of page views (web.dev). Our Core Web Vitals checklist for WordPress covers how to fix each one.
If a specific page drops and stays down after a few weeks, compare it with the old version in your crawl export. In our experience the cause is usually a missing redirect, a changed title or heading, thinner content, or fewer internal links.
Common website redesign SEO mistakes
- Bringing SEO in after the design is approved. By then, URL structure and page cuts are already decided. Involve SEO at the sitemap and wireframe stage.
- Redirecting everything to the home page. It is quick, but Google advises against redirecting many old URLs to an irrelevant page, and visitors land somewhere they did not expect.
- Changing the domain, the platform and the design at once. Each change adds risk. If you can, split a domain move from a redesign so you can tell which change caused any drop.
- Deleting the old redirect list after a few months. Keep redirects for at least a year, and longer for pages with backlinks.
- Launching on a Friday afternoon. Problems found over a weekend cost leads. Launch early in the week.
- Judging success after three days. Compare like for like periods over at least a month before drawing conclusions.
Website redesign SEO FAQs
Will a website redesign affect my SEO?
It can, in either direction. A redesign that keeps URLs, content and metadata intact and improves speed and structure often helps. A redesign that changes URLs without redirects, cuts ranking pages or launches with staging blocks in place usually causes drops.
How long does it take rankings to recover after a redesign?
Google says to expect temporary fluctuation, and that a medium sized site can take a few weeks or more for most pages to be processed after URL changes. Larger sites take longer. A drop that lasts beyond that window on specific pages usually points to a fixable problem.
Should I keep the same URLs when I redesign my website?
Yes, wherever the existing URLs make sense. Keeping URLs removes the need for redirects on those pages and is the lowest risk option. Only change URLs when the old structure is genuinely confusing or full of dates, IDs or duplicates.
Do I need 301 redirects if my URLs are not changing?
Not for those pages. You still need redirects for any page that moves, merges or changes its slug, and for protocol or domain changes such as moving from http to https or from www to non-www.
How long should I keep 301 redirects after a redesign?
Google recommends keeping redirects for as long as possible, generally at least one year. There is little cost to keeping them longer, especially for pages that other websites link to.
Can I do a website redesign SEO check myself?
A small site with a few dozen pages can follow this checklist with a free crawler, Search Console and a spreadsheet. Larger sites, sites changing platform or domain, and businesses that rely on organic leads usually benefit from having an SEO and a developer working on the migration together.
Planning a redesign? Let us protect your rankings
Our team builds and redesigns WordPress sites with the URL map, redirects, metadata and launch checks handled as part of the project, not as an afterthought. See our WordPress development services or our SEO services, and get in touch if you would like a second pair of eyes on your redesign plan before launch.
