Web Development

Website Redesign Without Losing Google Rankings: What I Check Before and After Launch

What makes a redesign lose search traffic and how to avoid it: a list of old URLs, 301 redirects, checking the real HTTP status, sitemaps and Search Console. With one mistake from my own site.

RedesignSEOSite migration301 redirectsGoogle Search Console

The new site looks better, loads faster and feels modern. A month later the enquiries from Google are down by half. I have seen this often enough to know it is almost never the design.

The short answer: a redesign does not lose rankings by itself. Missing URLs, cut content and redirects that only look like redirects do. All of it can be caught with checks before and after launch.

Do you lose Google traffic when you redesign a website?

Not necessarily. Traffic goes away for three reasons:

  • The old URLs disappear. Google remembers the pages it ranked. If those addresses now return “Page not found”, their rankings drop.
  • The pages that bring visits get rewritten or trimmed, because the text “does not fit” the new layout.
  • The new site is slower or thinner on a phone, even though it looks great on the designer’s big monitor.

There is also normal turbulence. Google’s documentation on site moves with URL changes says that for a medium-sized site it can take a few weeks or more before the new URLs start showing in results. A dip in the first days is not a reason to panic. A dip after two months is.

What do I do before a redesign?

This is the part most people skip, because nobody sees it.

  1. I pull a list of every old URL. Not only the ones in the menu. I take them from the sitemap, from Search Console (the Pages and Performance reports) and from the site itself: old articles, categories, tags, PDF files, pages nothing links to anymore but Google still remembers.
  2. I check which pages bring visits and enquiries over the last 12 months. Those do not get touched without a reason: title, main text, H1. They can get a new design, not a new meaning.
  3. I build a table: old URL to new URL. Every old page goes to the closest matching new page. Not to the home page. Google explicitly advises against sending many old URLs to one unrelated page such as the home page, and it may count them as soft 404s.
  4. I save the titles and meta descriptions of the pages that bring traffic, so nobody deletes them out of habit.
  5. I note the structured data, canonical tags and hreflang if the site has more than one language.

If the URLs can stay the same, even better. Then you need almost no redirects. If the old ones look like ?p=123, change them, but with the table.

How do you set up redirects properly?

  • A permanent redirect from the server: 301 or 308. Not JavaScript, not a meta refresh, not a plugin that “redirects” after the page has loaded.
  • Straight to the final page. No chains like old URL to an intermediate URL to the new one.
  • Keep them for a long time. Google recommends at least a year. I keep them forever, because old links from other sites never fully go away.
  • Check the real HTTP status code, not what the browser shows you.

The mistake I made on my own site

When I moved tanchev.net from WordPress to Astro, I first put the redirects for the old WordPress URLs in .htaccess. It looked fine. Except that on my server OpenLiteSpeed proxies everything to the Node server that serves the site, so that .htaccess is never read by anything.

The second attempt was Astro’s built-in redirects. On a static site they generate a page that returns status 200 and sends the browser on with a meta refresh. To a person it looks like a redirect. To Google it is a separate page with a 200 status and almost no content.

The real 301s ended up in the configuration of the Node server itself, and the domain-level redirects (www to the bare domain, the old blog subdomain to the blog section, http to https) went into Cloudflare. I caught it with a script that walks the old URLs and checks the response code, not the page. Since then I do not trust a redirect until I see the 301 myself.

What do I check on launch day?

  • robots.txt and noindex. The staging version is almost always blocked from Google. If that block stays on the live site, nothing else matters.
  • The canonical tag on every page points to its own new URL.
  • A new sitemap in Search Console, and the old ones removed. On my own property there were 11 old sitemaps left over from WordPress and the old blog subdomain.
  • The dates in the sitemap. My generator stamped today’s date on every page on every build. Google only uses lastmod when it is consistently and verifiably accurate, so a fake date is useless. I removed it.
  • Internal links go straight to the new URLs instead of through a redirect. And they use one form: with a trailing slash or without, not both.
  • Speed and layout on a phone, on a real phone, not only in the browser developer tools.
  • The contact forms. I send myself a test enquiry. A new site that does not send emails is worse than the old one.

How long should you watch after launch?

For the first two weeks I look at Search Console every day: the Pages report for new 404s, and Performance by page compared with the period before launch. Then once a week for at least two months.

If an important page drops out of the results, I check its old URL first: does it return a 301, does it lead to the right page, does that page still have the text it used to have. Most of the time the answer is there.

When does a redesign not help?

Honestly: a redesign protects what the site already has. It does not create trust that is not there. If the site was not ranking before because the domain is weak, the content is thin or there is no separate page for each service, a new design will not fix that on its own. Then the work is on content and local SEO, and the design is the packaging.

Frequently asked questions

Can I change the domain and the design at the same time?

You can, but I prefer two steps. If something breaks, you know which of the two changes caused it.

Should I keep the same URLs?

If they make sense, yes. That is the safest option. If they are ugly or unclear, change them, but give every old URL a 301 to its new one.

Does this apply when moving from WordPress to another platform?

Yes, the rules are the same. Google does not care about the platform. It cares about the URLs and the content.

Can I check the redirects myself?

Yes. Any online HTTP status checker shows the code. You want a 301 or 308 and one hop to the new URL, not a 200 and not a 302.

If you are planning a website redesign, write to info@tanchev.net or call +359 896 86 3508. I look at what brings traffic today first, then we talk about design. A quote is prepared after a short conversation.

Related Articles