What can go wrong when you redirect a high-traffic page?
- Published November 6, 2026
- Linked from 1 answer
- In a cluster of 3
The redirect itself is routine; what goes wrong is the target, the setup, or the wait. On a page that earns real traffic, each of those mistakes costs more, so the move deserves the same planning as a small site migration. Google’s site move guidance warns that with any significant change “you may experience ranking fluctuations while Google recrawls and reindexes your site”, and a high-traffic URL is where that fluctuation costs the most.
The four failure points
| Failure | What happens | Prevention |
|---|---|---|
| The target is not a true replacement | Google may treat the redirect as a soft 404, and visitors land on something they did not ask for | Redirect to a page that covers everything the old page did, or improve the target first |
| The redirect is temporary or client-side | Google's indexing pipeline does not use a temporary redirect as a signal that the target should be canonical, so the old URL can hold its place | Use a server-side permanent redirect, the method Google's redirect documentation favors |
| The redirect joins a chain or loop | Each extra hop adds latency, a loop never loads, and a broken hop ends in a 404 | Send the old URL in one hop to a target that returns 200 |
| The redirect is removed too soon | Old links and bookmarks stop reaching the page | Keep it in place for at least a year, longer if old links still bring visits |
Chains need their own rules; for those, see when a redirect chain is harmless and when it is a real problem.
What happens to existing links
External links and bookmarks keep working as long as the redirect is in place; they simply pass through one hop. The risk lies on your own site. Menus, body links, and the sitemap that still point at the old URL send every visitor and every crawl through the redirect. Update them on the day of the change so the target is the only URL your site presents.
Before and after the switch
Before:
- Export the old page’s queries, clicks, and top landing traffic from Search Console so you have a baseline.
- Check the old page’s external links in the Links report and confirm the target can satisfy the visitors those links send.
- Compare the target’s content against the old page and add anything the old page answered that the target does not.
After:
- Request the old URL and confirm a single permanent redirect to a 200 page.
- Inspect the target in URL Inspection and request indexing.
- Track the target’s queries against your baseline. A short dip during reprocessing is expected. If queries never return once Google has recrawled both URLs, recheck steps 1 and 2 first, including the target’s Google-selected canonical and any noindex, and look at whether competitors moved in the meantime; a content gap in the target is the next suspect, not the only one, and no redirect guarantees the old position.
If the page is high-traffic because it ranks well and converts, also ask whether it should move at all. A redirect is the right tool when the old URL has to go; it is not a ranking upgrade on its own.
Add a comment