How a redesign quietly loses Google

A print shop in Oradea stood first on Google for its main searches, and its website needed a rebuild from scratch. Before the switch, I checked every old address from Google's index against the live preview of the new site: 25 of 39 would have died quietly. No warning, no message in any dashboard. Just visitors and rankings arriving at a 404 page.

That is how a redesign loses Google. Not by changing the look — by losing the addresses. The rebuild itself is a separate note; this one is about the move.

A trailing slash is a different address

On Cloudflare, redirects live in a plain text file called _redirects: one line per rule — old address, new address, status code. The semantics look obvious and are not.

An exact rule for /produse/ does not match /produse. A splat rule /produse/* matches /produse/, but still not /produse. The old WordPress site had served both shapes for years, and Google's index remembers both.

That is why the map is built in pairs, with extra lines for addresses WordPress invented on its own:

/produse           /produse/   301

/oferta            /produse/   301
/oferta/*          /produse/   301
/oferta-*          /produse/   301
/bwg_gallery/*     /lucrari/   301

The first line closes the no-slash gap. /bwg_gallery/ is a leftover of a WordPress gallery plugin: the plugin was long gone, its addresses had lived in the index for years.

There was a second surprise, in October 2026. A specific splat placed above a general one kept losing to it on the live host, while wrangler dev matched the same file in order. The lesson stuck: the only behaviour that counts is the live one.

75 rules, tested like code

The final map is 75 rules: 55 exact, 18 splats, 2 placeholder rules. The pairs make the file longer than feels necessary. That redundancy is the cheapest part of the whole project.

Nobody holds 75 rules in their head, so every change triggers a regression run: 103 addresses, requested on the live host, not in a local simulation. The script follows each redirect chain to its end. A 301 that lands in a void counts as a failure:

if (isRedirect(r.expect)) {
  if (r.status !== r.expect && !hostHop) return false;
  if ((r.effective_location ?? r.location) !== r.location_expected) return false;
  return r.final_status === 200;   // a redirect must land on a live page
}

The script runs before every push; one failed address blocks the deploy. None of this is visible in the design, and all of it decides whether the redesign keeps its positions.

The preview stays out of the index

Until the switch, the new site lived on a workers.dev preview address, fully public. If Google had indexed it, the launch would have started life as a duplicate of itself. One rule in the _headers file closes the preview, keyed to the host name. The rule is straight from Cloudflare's docs:

https://:version.:subdomain.workers.dev/*
  X-Robots-Tag: noindex

The :version and :subdomain placeholders match every preview host and cannot match a custom domain, so the noindex cannot leak into production. The regression run checks the live side too: the production host must answer without X-Robots-Tag.

The switch

The new site also ships a second sitemap, sitemap-old.xml, listing the old addresses: it helps Google find and revisit them, and follow the 301s, instead of stumbling on redirects one by one.

The DNS switch happened on the night of 20 October 2026 and took about 15 minutes, with no downtime. Email moved two days later, on purpose. One change at a time: when something breaks, you want to know which change broke it.

What Google did

Eleven searches were tracked before and after, checked the same way on 20 October and on 3 November 2026. The rows below show six of them: nothing fell, and the weakest position rose. The searches are public — run them yourself:

Search20 Oct (old site)3 Nov (new site)
tipografie oradea / tipografie in oradea1 / 11 / 1
tipar oradea21
formulare tipizate oradea — the key B2B search71
eleron com / eleron oradea — brand searches1 / 11 / 1

Search Console showed no spike of 404s after the move — not a single one. Indexed pages went from 21 to 29, among them the new English pages the old site never had.

Clicks in the first week ran at three and a half times the old rate: 5.7 a day against 1.6. That window flatters a launch. The honest comparison is two windows of equal length. The old site's last 28 days of September, 3–30: 47 clicks. The first 28 days after the switch, 20 October to 16 November: 64. Plus 36 percent, with impressions up by a fifth. Seventeen extra clicks in four weeks: small numbers.

Within two weeks Google rebuilt the sitelinks under the new page structure. The 404s that did arrive came from bots probing for WordPress paths — a story of its own.

A snapshot, not a promise. Google decides rankings, and no one can honestly guarantee a position after a move. What the map controls is narrower and real: no old address leads into a void.

One question before a redesign

If your site ranks and a redesign is coming, ask the developer one question first: where will the old addresses lead? Not the new pages — the old addresses, each one Google has already indexed.

The list is not hard to get. Search Console shows the addresses Google knows about your site, and checking them costs an afternoon, not a position.

← All notes

mihai@papush.ro