Guide
How to redesign your website without losing your Google rankings
The short answer: keep every page that ranks reachable at the same address, or permanently redirect it (a 301 redirect) to its closest new equivalent, and carry over the content and page titles that earned those rankings. Most traffic lost in a redesign comes from broken or missing redirects and deleted content, not from the new design itself.
Search engines rank individual pages, not websites. When a redesign changes or removes the pages Google already trusts, the trust doesn't automatically transfer. Here's the process we follow so it does.
Step 1: Benchmark before you touch anything
Record where you stand. In Google Search Console, export your top pages and queries for the last three to six months. In your analytics, note which pages bring in visitors and enquiries. You can't protect what you haven't measured, and you'll need this baseline to judge the launch.
Step 2: Inventory every URL
Crawl the current site with a tool such as Screaming Frog, or pull the list from your sitemap and Search Console, to get every live URL. Include blog posts, old landing pages and PDFs. Pages you forgot about are often the ones still quietly ranking.
Step 3: Keep URLs where you can, redirect the rest
The safest URL is one that doesn't change. Where a URL must change, or a page is merged or retired, map it to the most relevant new page with a 301 redirect. Avoid sending everything to the homepage; Google may treat that as a missing page. Avoid chains where one redirect points to another.
Step 4: Protect the content that ranks
If a page ranks for valuable searches, keep its substance. Improve it, restructure it, make it clearer, but don't cut the sections that answer what people searched for. Carry over or improve page titles, meta descriptions, headings, image alt text and any structured data.
Step 5: Check the launch details
Staging sites are usually blocked from search engines. Make sure that block is removed at launch, a surprisingly common mistake. Confirm robots.txt allows crawling, the XML sitemap lists the new URLs, canonical tags point to the right pages, internal links use new URLs instead of relying on redirects, and the site is fast on mobile.
Step 6: Submit and monitor
Submit the new sitemap in Search Console, then watch the coverage and performance reports for four to eight weeks. Fix any 404 errors with redirects as they appear. Some ranking movement in the first few weeks is normal while Google recrawls. A steady decline after that points to a missed redirect or lost content worth investigating.
At Pacific Standards, reviewing current page URLs and including redirects for the agreed pages is part of every rebuild, and the old site stays live until the new one is approved. Larger migrations with hundreds of pages are scoped separately, because they deserve the extra care.