A 301 says permanently moved and a 302 says it is coming back, and an engine treats them differently for exactly that reason. Newent Nurseries in Gloucestershire rebranded in 2022 and again in 2024, and by 2026 its most linked page sat behind a four hop chain, and the crawler stopped following after the third.
The chain ran from the 2021 address to a 2022 category, to a renamed 2024 category, to the current plant guide. Every hop is a fetch, the number a crawler will follow is small and not published, and the practical consequence is that the twelve garden forums linking to the 2021 address were sending their readers and their standing into a wall.
The rule that prevents all of it
Point every old address at the final destination, not at the next redirect. That is one sentence and it is nearly the whole subject. Newent's four hops became four rules all pointing at the current address, in one afternoon, and the guide recovered its position over about ten weeks.
Redirects
The route from a 2021 link to the page it was about
Four hops, added by three people over four years, none of whom knew about the ones before them.
- 01The 2021 addressTwelve garden forums still link to this one.
- 02A 2022 categoryAdded in the first rebrand, and correct at the time.
- 03The renamed 2024 categoryAdded in the second rebrand, pointing at the hop before it.
- 04Where the crawler stoppedNot a page. The chain was abandoned around here.
- 05The plant guideReached by a person clicking, and not by much else.
The four rules now all point at the last stop, so the route is one hop. The figure draws the old route because the new one has nothing to draw.
Rewrite the old rules when you add a new one. This is the part that does not happen, because adding a rule is one line and rewriting the old ones means reading them, and the person doing the rename in 2024 had no reason to know about 2021. A rename is not finished until the older rules point at the new address.
Two ways to throw away what a page earned
Redirecting everything to the home page is the same as deleting it. It is the standard shortcut during a migration, it looks tidy, and a redirect to a page that answers something else is a soft 404: the destination does not answer what the old address answered, so nothing is carried over and the visitor is lost as well.
Mapping
How to handle each old address before switching
Sending unrelated old URLs to the home page acts like a soft 404 and wastes earned standing.
- YesMap one to onePoint the old address straight to the specific page that answers the same topic.
- Build the 340-address sheet before the switch
- Spend one day mapping to avoid months of recovery
- NoReturn 410 or 404Let discontinued addresses end cleanly instead of dumping visitors on the home page.
- Avoid soft 404 responses on irrelevant pages
- Keep the home page for home queries only
Stating upfront that retired URLs return 410 or 404 stops the home page from becoming the default catch-all.
Map old to new one address at a time before anything is switched. Newent's second rebrand had 340 addresses and the mapping took a day, which is the honest cost and is far less than the eleven months of recovery the first rebrand cost by skipping it. Addresses with no sensible destination should return a 410 or a 404 rather than a redirect to something irrelevant, and saying that out loud in a plan is what stops the home page becoming the default answer.
Where this stalls: the temporary that is not
A 302 left in place for a year is a page that never finished moving. Newent had eleven of them from a stock outage in 2025, added by somebody who intended to put the products back in a fortnight. An engine reading a 302 keeps the old address as the real one, which is correct behaviour for a temporary move and is wrong for a permanent one, and nothing about the site says which this is except the code.
Status codes
Why a 302 left in place stalls without throwing an error
Visitors reach the new page normally, while search engines keep treating the 2025 old URL as the real address.
- What visitors experienceLooks completely fine
- Lands on the new destination
- Zero broken pages or user complaints
- What search engines storeUnfinished move
- Keeps the old address as canonical
- New URL never finishes taking over
302 left for a year
A temporary 302 emits no warning; searching the rule set for 302 is the only way to catch forgotten temporary redirects.
The stall is that a 302 works. Visitors land where they should, nothing errors, and the only symptom is that the new address never quite takes over. It is a fault with no report, and the fix is a search of the rules for the number.
Checking it properly
Check the chain with curl, because a browser follows every hop silently and shows the last page as though it were the first. A single command prints each status and each location header in turn, which is the only way to see a chain as a chain, and it is free and already on the machine.
Verification
Checks that catch broken hops before and after a move
Browsers follow redirect chains silently, so verification requires inspecting raw headers and crawling the old sitemap.
Pre-launch redirect check
- YesTrace headers with curlPrints every status code and location header one hop at a time.Yes
- YesCrawl old sitemap in Screaming FrogReports hop counts and final status across lists of old URLs.Yes
- NoConfirm zero old URLs end in 404Newent uncovered 41 addresses hitting 404 that everyone assumed were redirected.No
- Not checkedKeep final destinations liveOnce an old address breaks, external forum links point at a rule instead of a page.Not checked
Unlike editing a tag, a broken redirect cannot be reversed without re-establishing the lost addresses.
Screaming Frog SEO Spider crawls a list of old addresses and reports the number of hops and the final status for each, free up to a few hundred, and it replaced checking them by hand in a browser. Feeding it the old sitemap before a migration is the whole of the verification step, and Newent's showed 41 addresses ending in a 404 that everybody had believed were redirected.
Which addresses were worth keeping in the first place is readable, stable and shallow, doing the whole exercise on a deadline is the checklist, and the traffic drops it prevents, and a duplicate that has to stay reachable wants a hint rather than a rule, which is naming the real version of a duplicated page. All three are the layer that decides whether any of the rest counts, and a redirect is the one item in it that cannot be undone by editing a tag: once an old address stops resolving, the twelve forums linking to it are pointing at a rule rather than at a page.