Should You Change a Page's URL? Safe Slug Changes for SEO

A question I get a lot from business owners goes like this: “My URL has the wrong keyword in it. Should I change it?” Sometimes the slug has an old year in it, a typo, a product name that changed, or a long string of words the CMS made up from the first draft title.

Many people believe the URL is a big ranking factor, so fixing it must help. Others are so scared of losing rankings that they never touch a URL, even when it is clearly broken. Both views cost money.

Let me explain this simply. Changing a URL is not dangerous by itself. What is dangerous is changing it without a plan: no redirect, broken internal links, or a big batch of changes all at once. In this guide I will show you when a change is worth it, when to leave things alone, and exactly how to change a slug safely. If you are creating new URLs from scratch, start with our guide to SEO-friendly URLs instead. This post is about URLs that already exist and already have history.

What really happens when you change a page’s URL

To Google, a new URL is a new page. Everything the old URL built up, such as links from other sites, history in Google’s index and signals about what the page is about, is tied to the old address. A 301 redirect is a permanent forwarding instruction. It tells browsers and Google: “this page has moved for good, go here instead.” It is the bridge that carries those signals over.

Google is open about the fact that this takes time. In a January 2022 video covered by Search Engine Land, John Mueller explained that URL changes are “not that simple for search engines,” because every signal has to be moved to the new address. More important URLs get processed sooner, and less important ones can take months.

Ahrefs puts the practical side bluntly:

“There’s rarely much point changing existing URL slugs as it takes too much time.”

— Joshua Hardwick, Ahrefs, SEO-Friendly URLs

I agree with the spirit of that. But “rarely” is not “never.” There are good reasons to change a URL, and I will list them next.

When a URL change is worth the risk

Here is the simple test I use. A change is worth it when the current URL is misleading, broken or blocking a real business goal. It is usually not worth it when the only reason is “it could have a slightly better keyword.”

Situation	Change it?	Why
Slug contains an outdated year (e.g. /best-crm-2022/) and you update the post every year	Usually yes, once, to a yearless slug	A stale year in the URL can look out of date in results and forces another change next year
Product or service was renamed, or the slug names something you no longer offer	Yes	The URL now misleads people and may confuse Google about the topic
Typo or embarrassing slug	Yes, if the page is visible to customers	Trust matters, and the fix is a single redirect
URL is just an ID (/p?id=8812)	Often yes, during a planned rebuild	Google recommends readable words over long ID numbers
Merging two weak pages into one stronger page	Yes	The redirect consolidates both pages’ signals
Slug is fine but missing the “perfect” keyword	Usually no	The ranking gain is tiny; the temporary disruption is real. Fix the title and content focus instead (see choosing a primary keyword for an existing page)
Page ranks in the top 3 and earns most of your leads	No, unless there is a strong business reason	Even a short dip costs real money
Changing the folder structure of the whole site just to look tidier	Rarely	This is a migration, not a slug change, and needs its own project

The year case is very common. If you keep putting dates into URLs, read our post on dates in URLs before you publish the next one. It is cheaper to avoid the problem than to fix it later.

Google’s own SEO Starter Guide also tells site owners: “Don’t drop everything and start reorganizing your site right now though.” Good URLs help, but a tidy URL is not worth a big risk on its own.

The real risks, ranked from most to least common

Let me be specific about what actually goes wrong. In my view, these are the problems in order of how often they happen.

1. No redirect at all. Someone edits the slug in the CMS, the old URL returns a 404 error (“page not found”), and all links pointing to it go nowhere.
2. Internal links still point to the old URL. The redirect works, but every click from your own menus and articles goes through an extra hop.
3. Redirect chains. Old URL goes to a URL that goes to another URL. Each hop adds delay and risk. We explain how to fix these in our guide to redirect chains and loops.
4. Temporary redirects by mistake. A 302 tells Google the move may not be permanent. See 301 vs 302 redirects for when each one fits.
5. Changing content and URL at the same time. If rankings drop, you can’t tell which change caused it. The same goes for the title: a new slug plus a new title can also trigger Google title rewrites you didn’t expect.
6. Removing the redirect too early. Someone cleans up the redirect list six months later, and old backlinks break.

Notice that most of these are process failures, not Google penalties. That is good news. Process problems can be prevented with a checklist.

Checklist before you change a single slug

Here is how I would prepare. It takes about 30 minutes for one page.

1. Record the baseline. In Search Console, note the page’s clicks, impressions and average position for the last 28 days and the last 3 months. Export the queries list.
2. Check backlinks. In Search Console’s Links report or your SEO tool, list the sites linking to the old URL. Note any important ones you could ask to update.
3. Find internal links. Crawl your site with a tool like Screaming Frog, or search your CMS, for every link to the old URL.
4. Check for existing redirects to this URL. If older URLs already redirect here, you will need to update them too, to avoid chains.
5. Choose the final slug carefully. Short, readable, lowercase, words separated by hyphens, and no year or number you will need to change again.
6. Decide what else will change. Ideally nothing else. Keep the title, content and template the same for at least a few weeks.
7. Pick a quiet time. Avoid your peak season and known Google core update rollouts.

Google’s URL structure guide supports the slug rules in step 5. It recommends readable words over long ID numbers, hyphens to separate words, and notes that Google treats URLs as case-sensitive, so /Apple and /apple are different addresses.

Setting up the 301 redirect correctly

The redirect is the most important step. Google’s documentation on redirects and Google Search says permanent redirects show the new redirect target in search results, which is exactly what you want. The safest option is a server-side 301.

How to do it on common platforms

Platform	How the redirect is created	What to watch
WordPress	Core WordPress often redirects changed post slugs automatically; SEO plugins like Yoast Premium, Rank Math or the Redirection plugin give you a managed list	Don’t rely only on the automatic redirect. Add a manual 301 so it survives plugin or theme changes
Shopify	When you edit a product or collection URL handle, tick “Create a URL redirect.” Or add it under URL redirects in the admin	Shopify redirects only work when the old URL no longer exists as a page
Apache server	A Redirect 301 or RewriteRule line in .htaccess	Order matters; test after every edit. See our .htaccess redirects guide
Nginx server	A return 301 line in the server config	Reload Nginx after changes
Headless or JavaScript sites	Redirect at the hosting or edge level (for example in the platform’s redirect config)	Avoid JavaScript-only redirects for important pages

A simple Apache example looks like this:

Redirect 301 /blog/best-crm-2022/ https://www.example.com/blog/best-crm/

After you add it, test the old URL. It should return a 301 status and land on the new URL in one hop. You can check this with any HTTP status checker, or by inspecting the new URL in Search Console.

How long to keep the redirect

The short answer is: as long as you can. Google says so plainly.

“Keep the redirects for as long as possible, generally at least 1 year.”

— Google Search Central, Site moves with URL changes

John Mueller explained the reason in Google’s Ask Googlebot series, as reported by Search Engine Journal in December 2021: Google needs to see a redirect several times before it treats the move as permanent, and it tries to reprocess pages at least every few months. For a single slug change, I suggest you simply never remove the redirect. It costs almost nothing to keep.

Updating internal links, canonicals and sitemaps

A redirect is a safety net. It is not the finish line. Once the redirect works, clean up everything on your own site that still points to the old URL.

• Internal links: update links in menus, footers, related posts, body text and buttons so they point straight to the new URL. Our internal link audit guide shows how to find them all, and while you are there, check the anchor text too with an internal anchor text audit.
• Canonical tag: the new page’s canonical should point to the new URL, not the old one. This happens automatically in most CMSs, but check it.
• XML sitemap: it should list only the new URL. Google’s site-move guide says submitting a sitemap of new URLs helps Google learn about them. See our guide to XML sitemaps.
• Hreflang tags on multilingual sites must reference the new URL on every language version.
• Paid ads, emails and social bios: update links in Google Ads, Meta ads, email templates and profiles, so you are not paying for an extra redirect hop.
• Important backlinks: email the owners of your two or three strongest links and ask them to update the URL. Not essential, but nice.

Changing many URLs at once without losing traffic

One slug is a small job. Fifty or five hundred slugs is a project. When the number grows, the risk grows too, because mistakes multiply and it becomes hard to know what caused a drop.

Google’s site-move documentation recommends changing one thing at a time and considering moving large sites in sections. That applies to bulk slug changes too. Here is the approach I suggest.

1. Build a redirect map in a spreadsheet: one row per old URL, with the new URL beside it. Pull old URLs from your sitemap, analytics, server logs and CMS so nothing is missed.
2. Mark each row’s priority by traffic and backlinks. High-value pages get checked by hand.
3. Start with a test batch of 10 to 20 lower-value pages. Wait two to four weeks and check the results.
4. Roll out the rest in batches, keeping a log of dates for each batch.
5. Test every row with a crawler in list mode after launch: each old URL should return one 301 to the right new URL, and each new URL should return 200.

Worked example: renaming a 120-page blog section

Example (hypothetical): a software company has 120 blog posts with years in their slugs, like /blog/email-marketing-stats-2023/. Together they earn about 18,000 organic clicks a month. Twelve posts earn 70% of those clicks.

• Batch 1: 20 low-traffic posts (about 600 clicks a month combined). Changed in week 1.
• Check in week 4: clicks for the batch are back to around 580 to 620, so the process works.
• Batch 2: 88 more low and mid-traffic posts in week 5.
• Batch 3: the 12 top posts in week 9, one at a time over two weeks, each checked by hand.

If batch 1 had dropped badly instead, they would have found the problem with only 600 clicks at stake, not 18,000. That is the whole point of batching. If you are planning something bigger, like a new domain or a full site rebuild, read our Learn SEO lesson on site migrations first.

Monitoring the first 90 days after a URL change

Google warns that “the visibility of your content in Search may fluctuate temporarily during the move.” A small, short dip is normal. Here is what to watch and when.

When	What to check	What “good” looks like
Day 1	Redirect status, new URL indexing request, sitemap	Old URL returns one 301; new URL returns 200 and is listed in the sitemap
Weeks 1–2	Page indexing report and URL Inspection	Old URL shows as “Page with redirect”; new URL is indexed
Weeks 2–6	Clicks and impressions for old and new URL combined	Combined total within a normal range of the baseline, allowing for a short dip
Month 3	Combined clicks, top queries, average position	Back near the baseline, or higher if the page was also improved

For the combined view, use a Search Console page filter that matches both old and new URLs. Our post on regex filters in Search Console shows how.

Remember to compare like with like. If the change happened during a seasonal dip or a Google update, your numbers will move for reasons unrelated to the URL. Our guide on measuring on-page SEO changes covers how to separate these effects.

Rolling back a URL change that went wrong

Sometimes a change goes badly. Maybe traffic drops sharply and doesn’t recover after six weeks, or you find the redirect was broken for a month. Here is how to undo it cleanly.

1. Check the cause first. Is the redirect working? Is the new URL indexed? Did anything else change, like the title or content? Fix those before reverting.
2. If you revert, reverse the redirect: new URL now 301s back to the old URL. Remove the old-to-new rule so you don’t create a loop.
3. Update internal links and the sitemap back to the old URL.
4. Request indexing of the old URL in URL Inspection.
5. Wait again. A rollback is another URL change, so Google needs time to process it too.

In brief, a rollback is not free. That is why the preparation steps matter so much. Most of the time the answer is to fix the redirect and internal links, not to undo the change.

Questions owners ask before changing a slug

Will changing a URL slug drop my rankings?

It can cause a temporary wobble while Google processes the redirect. With a correct 301 and updated internal links, most pages recover. Without a redirect, you can lose the page’s rankings and links.

Does WordPress handle slug changes automatically?

WordPress often redirects changed post slugs on its own, but I don’t rely on it alone. Add a proper 301 through your SEO or redirect plugin so it is visible and survives future changes.

How long until Google shows the new URL?

For an important page that is crawled often, it can be days. For less important pages, it can take weeks or longer. Requesting indexing in Search Console can speed up discovery, not ranking.

Should I remove the year from my URLs?

If you update the post every year and plan to keep it, yes, change it once to a yearless slug with a 301. If the post is a one-off from a specific year, leave it alone.

Can I change the slug and the content at the same time?

You can, but it makes results hard to read. If you can, change the URL first, wait a few weeks, then improve the content. That way you know what caused any change.

How to decide on your own URL change this week

Start with one question: is this URL misleading, broken or blocking a business goal? If not, leave it and spend the time on content or links. If yes, take the baseline, set up a server-side 301, fix internal links and the sitemap, and watch the numbers for 90 days.

If you are planning to change many URLs, or you are not sure the redirects on your site are set up correctly, our SEO team can map and check them for you. Get in touch for a quote and tell us how many URLs you plan to change.

Further reading on changing url slugs

• Multiple H1 Tags: Does It Hurt SEO?
• Mobile Navigation and Hamburger Menus: SEO Best Practices
• Should You Put Your Brand Name in Title Tags?

Sources for this URL slug change guide

1. Google Search Central: Site moves with URL changes
2. Google Search Central: Redirects and Google Search
3. Google Search Central: URL structure best practices
4. Google Search Central: SEO Starter Guide
5. Search Engine Journal: Google says keep 301 redirects in place for a year (December 2021)
6. Search Engine Land: URL changes are not so simple for Google Search (January 2022)
7. Ahrefs: SEO-Friendly URLs (Joshua Hardwick)