What actually happens to rankings when you 301 a URL?
- Published November 6, 2026
- Linked from 5 answers
- In a cluster of 51
After a 301, Google treats the redirect as a strong hint that the target URL should replace the old one in its index. Over the following crawls the old URL drops out, the target takes its place, and the target’s position settles according to how well it answers the searches the old page used to rank for. The change is not instant, and the end position is not guaranteed to match the old one.
The sequence, step by step
- Google recrawls the old URL and sees the redirect. Until that happens, nothing changes in search. A page Google crawls infrequently takes longer to update.
- The target becomes the canonical candidate. Google’s redirects documentation describes a permanent redirect as a signal that the target should be canonical; a temporary redirect is not used that way, which is why the type of redirect matters.
- The old URL is replaced in results. Search Console’s Page indexing report lists it as “Page with redirect”, a URL that “will not be indexed”, while the target is evaluated on its own merits.
- The target settles. Google’s site move guidance warns of ranking fluctuations while it recrawls and reindexes; a single redirect goes through the same recrawl, on a smaller scale.
What decides where the target lands
The redirect carries the old page’s history to a new address, but the new address still has to deserve the rankings.
| Target | Likely outcome |
|---|---|
| Same content at a new URL, such as a renamed slug | The target can take over the old rankings once processed |
| A merged page that covers everything the old page did and more | The target can hold or gain, since it answers the old queries |
| A related page that covers only part of the old topic | The target may rank for some old queries and lose others |
| An unrelated page or the homepage | Google may treat the redirect as a soft 404 and the old rankings fall away |
How much of the old page’s value reaches the target is a separate question with its own myths, covered in how long a 301 takes to pass value and whether any leaks. Two follow-up cases have their own pages: why a redirected page can still show in search, and moving a blog between a subfolder and a subdomain.
What to do in the first weeks
Keep the redirect permanent and in place, update internal links to point at the target directly, and swap the old URL for the target in your sitemap. Watch the target’s queries in Search Console rather than the old URL’s. A dip during reprocessing is expected. If the target never picks up the old page’s main queries after it has been recrawled, check the plumbing before the content: the old URL should answer with a single 301 to the final URL, the target should return 200, carry no noindex and be its own Google-selected canonical in URL Inspection, and internal links should point at it. If all of that holds, a content gap between the two pages becomes the likelier explanation.
Add a comment