What happens to rankings when you change a URL slug?
- Published November 6, 2026
- Linked from 2 answers
- In a cluster of 51
The page moves to a new address, and Google has to find out. Until it recrawls the old URL, sees the redirect and processes the new one, the old URL keeps its place in the index; the new one may be found sooner through your internal links and sitemap, but it does not take over the old page’s standing until the redirect is seen. With a permanent redirect in place the page’s standing follows it to the new URL, but not on the day you make the change, and the rankings can move while Google catches up. Without a redirect, the old URL returns an error, the links pointing to it lead nowhere, and the page starts again as a new URL.
A slug change, step by step
| Stage | What happens | What you control |
|---|---|---|
| You change the slug | The old URL stops serving the page | Add a 301 from the old URL to the new one in the same release |
| Google recrawls the old URL | It sees the redirect and starts treating the new URL as the replacement | Keep the redirect live; do not chain it through other redirects |
| Google crawls the new URL | It indexes the page at its new address | Make sure the new URL returns 200 and is not blocked or set to noindex |
| Signals move to the new URL | Links that point to the old URL count for the new one through the redirect | Update your own internal links so they point to the new URL directly |
| Rankings settle | The new URL holds the position the page's content earns | Watch the affected queries, not the site total |
For a single page, this can pass quickly if Google crawls the page often, and slowly if it does not. There is no fixed timeline. A slug change is one kind of 301, and the general sequence is traced in what happens to rankings when you 301 a URL.
When a slug change is worth it
- The slug is wrong: it names a different topic, a discontinued product or a misspelling.
- The slug contains a date or number that the content has outgrown.
- Two pages are being merged, and one URL has to go.
A slug that is merely long or not keyword-matched is not worth the change. The gain from a better slug is small, and the change brings a redirect to maintain and a period of uncertainty on a page that already ranks.
Doing it cleanly
- Change the slug and add the 301 in the same release.
- Update internal links, the sitemap and any canonical tags to the new URL.
- Request indexing for the new URL in URL Inspection once.
- Keep the redirect in place. Google’s site move guidance asks for at least a year and suggests keeping redirects indefinitely for users, since links to the old URL on other sites do not update themselves.
Change a slug only when the old one is wrong, and when you do, make the redirect part of the same change.
Add a comment