SEO & AI search · Guide
How to Change Permalinks Without Breaking SEO
Short answer
To change WordPress permalinks without breaking SEO, pick the new structure under Settings then Permalinks, add a 301 redirect from every old URL to its new URL, and submit your updated sitemap in Google Search Console. WordPress redirects a changed post slug on its own, but a full structure change still needs manual redirects.
Key takeaways
- Changing a permalink breaks the old URL, so every changed address needs a 301 redirect to its new address.
- Post name is the best permalink structure for most sites because it gives short, readable URLs.
- WordPress redirects a changed post slug to the new URL on its own, but that does not cover a full structure change.
- Google shows the new URL in search results when it sees a permanent 301 redirect.
- Submit your updated sitemap in Search Console after a permalink change so Google finds the new URLs sooner.
What happens when you change a permalink?
Changing a permalink changes the address of a page, so the old address stops working unless you redirect it.
A permalink is the permanent URL of a post, page or archive, and WordPress.org's docs say these URLs should never be changed. That is the ideal, but sites still change them when they clean up dates in URLs or move from plain links to readable ones.
When an old URL has no redirect, visitors and search engines get a 404 error. Links from other sites, bookmarks and social shares all point at the dead address. Google drops the old URL from its index over time, and the new URL starts with no ranking history of its own.
The damage is fixable. A 301 redirect tells Google the page moved for good, and Google's own redirects guide says a permanent redirect makes the new target the one shown in search results.
Which permalink structure is best for SEO?
Post name is the best choice for most sites, because it gives short, readable URLs built from the post title.
Google's URL structure guide recommends descriptive words instead of long ID numbers, and hyphens instead of underscores to separate words. A URL like example.com/change-permalinks/ tells a reader and a search engine what the page is about before it loads.
Date-based structures suit news sites where the date matters. For guides and articles that stay useful for years, a date in the URL makes the content look old and adds nothing. Keep the structure short and stable, and avoid changing it again later.
| Structure | Example URL | Best for |
|---|---|---|
| Plain | example.com/?p=123 | Nothing; this is the install default |
| Day and name | example.com/2026/11/20/post-name/ | News sites |
| Month and name | example.com/2026/11/post-name/ | Dated blogs |
| Numeric | example.com/archives/123 | Sites that never use words in URLs |
| Post name | example.com/post-name/ | Most blogs and business sites |
| Custom structure | example.com/blog/%postname%/ | Sites that want a fixed prefix |
WordPress offers six permalink options in total, and Post name is the one most SEO guides point to. The Plain setting, with its ?p=123 address, is the default on a fresh install, and WordPress.org's docs call it neither user-friendly nor search friendly.
How do you change the permalink structure?
Change the structure under Settings, then Permalinks, pick your new option and save, then add redirects for every old URL.
- Back up your site, including the database, so you can undo the change.
- Go to Settings, then Permalinks in your WordPress dashboard.
- Under Common Settings, pick Post name or your custom structure.
- Click Save Changes, even if you only want to refresh the rewrite rules.
- Open a few posts and pages to check the new URLs load.
- Add 301 redirects from the old URLs to the new ones before you do anything else.
If a post shows a 404 after the change, the rewrite rules may not have saved. Saving the Permalinks screen again usually fixes it, and our fix permalinks not working guide walks through the other causes.
Custom structures use tags such as %year%, %monthnum%, %postname% and %category%. WordPress.org's docs say to end a custom structure with %post_id% or %postname%, so each post still gets its own address.
How do you change one post's slug?
Open the post, click the URL field in the sidebar, type a short slug with hyphens, and click Update.
The slug is the last part of the URL, made from the post title with spaces turned into hyphens. Short slugs read better and are easier to share, so trim filler words and keep only the words that describe the topic.
WordPress builds the slug from the title when you first save a post. Changing the title later does not change the slug, which is why the slug field exists as a separate control. Use lower-case letters only, since Google treats /Apple and /apple as different URLs.
You can also set a category base and tag base on the same Permalinks screen. WordPress.org's docs note the defaults are “category” and “tag”, and you can change the words but cannot remove the base from the URL through settings alone.
Does WordPress redirect the old URL by itself?
Yes, for posts: WordPress keeps the old slug and sends visitors from the old address to the new one with a 301 redirect.
This built-in redirect lives in a core function called wp_old_slug_redirect(), listed in the WordPress developer reference. It runs when a post URL returns a 404 and the old slug is still on file.
It has limits. The function skips hierarchical post types, so it does not redirect a page whose slug changed. It also only matches the old slug, so a full structure change from dated URLs to plain post names still needs redirects you add yourself.
Do not rely on it as your only safety net. Check a few old URLs by hand after any change, and add manual redirects for any that do not land on the right page.
How do you add 301 redirects for changed URLs?
Add a 301 redirect from each old URL to its new URL, using a plugin like Redirection or your SEO plugin's redirect tool.
Redirection is a free plugin that manages 301 redirects, tracks 404 errors and watches for permalink changes so it can create redirects on its own. Its WordPress.org page notes it has been around for over 10 years and works with PHP 7.4 to 8.5.
To add a redirect by hand in Redirection, go to Tools, then Redirection, type the old address in the Source URL box and the new address in the Target URL box, then save. Repeat the step for each changed URL, or import a list in bulk.
If you use Yoast SEO or Rank Math, both offer redirect tools as well. Our Yoast redirects guide shows the steps for that plugin.
Keep the redirect list short and direct, and avoid chains where one redirect points to another redirect. Our too many redirects guide explains how chains cause errors.
How do you update your sitemap and Search Console?
Open your sitemap, check the new URLs appear there, then submit it again in Google Search Console so Google finds the new addresses sooner.
WordPress builds its own sitemap at /wp-sitemap.xml, and SEO plugins replace it with their own index. Either way, the sitemap updates itself when content changes, so the new URLs should appear without any work from you.
Google's sitemap guide says a single sitemap holds up to 50,000 URLs or 50 MB uncompressed, which covers most small and mid-size sites. It also says submitting a sitemap is only a hint, and Google may or may not download it or use it for crawling.
In Search Console, open the Sitemaps report and submit your sitemap URL again. Then open the Pages report over the next days to watch the new URLs get indexed and the old ones drop away.
How long before Google shows the new URLs?
Google switches to the new URLs after it re-crawls them, and a 301 redirect is the signal that tells it which address to show.
There is no fixed timetable. Google re-crawls popular pages fast and quiet pages slowly, so some URLs change in days and others take longer. The 301 keeps visitors and ranking signals moving to the new address while Google catches up.
Watch the change in Search Console rather than guessing. The Pages report shows which URLs are indexed, and the Sitemaps report shows when Google last read your sitemap. If an old URL still shows in results after a few weeks, check that its redirect is a 301 and not a 302.
A 302 is a temporary redirect, and Google's redirects guide says it keeps showing the source page in results. That is the wrong signal for a permanent permalink change.
What mistakes should you avoid?
The biggest mistake is changing the structure and forgetting the redirects, which leaves every old URL returning a 404.
- Do not change slugs on high-traffic posts for cosmetic reasons alone.
- Do not use underscores or capital letters in slugs.
- Do not redirect every old URL to the homepage; send each one to its matching new page.
- Do not stack redirects into chains, where one redirect points to another.
- Do not forget your own internal links, which still point at old URLs until you update them.
- Do not skip the sitemap resubmission in Search Console.
If a 404 keeps appearing after the change, our 404 causes guide lists the usual reasons, from a missed redirect to a rewrite rule that did not save.
Frequently asked questions
Will changing permalinks hurt my SEO?
It can, but only if the old URLs are left without redirects. Add a 301 redirect from each old URL to its new URL, update your sitemap, and resubmit it in Search Console. With redirects in place, Google moves the ranking signals to the new addresses.
Can I change the permalink structure on a live site?
Yes, but do it with care. Back up first, make the change when traffic is low, add the 301 redirects right away, and check several old URLs by hand. On a large site, change the structure in stages or get help, since hundreds of URLs change at once.
Should I remove the date from my post URLs?
For guides and articles that stay useful for years, yes. A date in the URL makes the content look old even when it is current. News sites are the exception, since the date is part of the story there.
What is the difference between a 301 and a 302 redirect?
A 301 means the page moved permanently, and Google shows the new URL in search results. A 302 means the move is temporary, and Google keeps showing the old URL. Use a 301 for every permalink change.
Do I need to update internal links after changing permalinks?
Yes. WordPress does not rewrite links inside your post content when the structure changes. Update menu links, links between posts and any hard-coded links, or they will keep sending visitors through a redirect instead of straight to the page.
Sources
- Customize permalinks WordPress.org Documentation
- Managing Settings: Permalinks Learn WordPress
- URL Structure Best Practices for Google Search Google Search Central
- Redirects and Google Search Google Search Central
- wp_old_slug_redirect() WordPress Developer Resources
- Redirection WordPress.org Plugin Directory
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
