UA Get a quote
Get a quote

Redesign without losing rankings: 301 redirects

Redesign without losing traffic: a 301 redirect map, internal links, 404 monitoring, false 403s from anti-bot protection and stray pagination redirects.

The Dorobymo team Published 4 min read

A new design, a new structure, finally clean page URLs. And a month later search traffic is down by a third. The most common cause isn’t the design itself but changed URLs that nobody told search engines — or the site itself — about. Here’s how to avoid it and what to watch after launch.

Why rankings drop

Search engines know your pages by their addresses. If an address changes and the old one returns 404, Google sees a new page with no history, and the old one as gone. Links from other sites lead nowhere, and the accumulated weight is lost.

A 301 redirect says: “this page has moved here permanently”. The search engine transfers signals to the new address, and the visitor lands where they should.

Step 1. Build a redirect map before launch

The redirect map is built before the redesign, not after.

Collect every old URL

Sources: the sitemap, a Search Console export (pages with impressions), analytics (pages with traffic), and a crawler such as Screaming Frog. Include not just what’s in the menu but also old articles, products and filter pages that get traffic.

Match them to new URLs

A two-column table: old URL → new URL. Rules:

  • Each old page points to the closest new page by content, not to the homepage.
  • No chains: A → B → C should become A → C.
  • If a page is truly gone with no replacement, an honest 404 or 410 is better than a redirect to the homepage.

Test before the switch

Deploy the new site on a test domain and run the redirect map through a script: every old URL should return 301 and land on a page that returns 200.

Redirects save external links, but inside your own site you shouldn’t rely on them. If articles, menus, the footer or product cards still link to old slugs, every click is an extra redirect, and crawlers waste resources following them.

After launch, go through the content and replace old URLs with new ones directly. In WordPress this can be done through the admin or the REST API, even without database access.

Step 3. Monitor 404s after launch

For the first few weeks after a redesign, keep an eye on:

  • the Pages report in Google Search Console — new 404s and “Page with redirect”;
  • the 404 log in your SEO plugin (Rank Math, for example, has its own monitor);
  • a regular crawl of the site.

New 404s that have traffic or external links are candidates for extra redirects.

Trap 1: false 403s from anti-bot protection

Audit and crawler reports often show hundreds of “broken” links. Don’t rush to fix them all.

In our case with an IT company’s website, the 404 report had 285 rows. After checking every target, 237 of them turned out to be 403 responses from external sites with anti-bot protection. The target site simply blocked the crawler, while the page opened fine for people. There were 24 real broken links.

How to tell them apart:

  • Look at the status code: 403 means “access denied”, not “page not found”.
  • Open the URL in a normal browser.
  • Group errors by domain: if all the “broken” links point to one or two large sites, it’s almost certainly anti-bot protection.

Without this filter you can spend days “fixing” links that already work.

Trap 2: pagination templates

Another common source of stray redirects isn’t content but the theme. In the same case, 84 redirects came from the pagination template: the theme built links to list pages in a format that was then redirected to the correct one.

You can’t fix these by editing posts — you need to look in the template or the permalink settings. The giveaway: identical redirects repeat across every archive page, category and tag.

Trap 3: caching

If the site uses a caching plugin such as WP Rocket, clear the cache after changing links and redirects. Otherwise crawlers and visitors will keep seeing the old links for a while, and you’ll think your fixes didn’t work.

Checklist

  1. Collect all old URLs from the sitemap, Search Console, analytics and a crawl.
  2. Build an old → new map, with no chains and no mass redirects to the homepage.
  3. Test redirects on a test domain before launch.
  4. After launch, update internal links in content and menus.
  5. Watch 404s in Search Console and your SEO plugin.
  6. Filter out false 403s from anti-bot protection.
  7. Check pagination templates and clear the cache.

If the redesign has already happened

Don’t worry — most of these problems can be fixed after launch. We go through 301 and 404 reports, separate real errors from noise and fix the links, often without hosting access. You can get a rough idea of the cost with the calculator on our pricing page.