WordPress Permalinks Explained: The Beginner's Guide to SEO-Friendly URLs

Web Development Basics · Real Info B · Updated September 2026 · 13 min read

Getting your permalink structure right early saves a lot of SEO headaches later. Photo via Pexels.

Quick Answer

A WordPress permalink is the permanent URL structure assigned to your posts and pages. By default, WordPress uses an ugly format like example.com/?p=123, which is bad for both SEO and readability. To fix it, go to Settings → Permalinks in your dashboard, select "Post name," and click Save Changes. This gives you clean URLs like example.com/your-post-title/. If you're changing permalinks on a site that already has published content, set up 301 redirects from every old URL to its new version first, or you'll lose existing search rankings and break any links pointing to your site.

Here's something that trips up almost every new WordPress site owner: they spend hours picking a theme, writing their first few posts, tweaking colors — and never once look at the Permalinks settings tab. By default, it's sitting on the worst possible option, quietly generating URLs like example.com/?p=47 for every single page on the site. It works, technically. Visitors can still click through. But it's doing real, measurable damage to how search engines understand and rank that content, and it's one of those Web Development Basics that takes five minutes to fix and pays off for years.

This guide walks through exactly what permalinks are, why the structure you choose actually matters for SEO, how to set them up correctly whether you're starting fresh or fixing an existing site, and how to avoid the single most common mistake people make when changing this setting on a site that's already live.

Consider two nearly identical blog posts covering the same topic, published by two different sites on the same day. One lives at a URL like example.com/2026/09/19/?p=847. The other lives at example.com/wordpress-permalinks-guide/. Nothing about the actual written content differs, and yet the second URL gives a small, consistent edge in relevance signaling, click-through rate from search results, and simple shareability — three things that compound over months and years of a site's life, even though no single one of them feels dramatic in isolation.

What you'll find in this guide

1. What are WordPress permalinks?
2. Why permalink structure actually affects SEO
3. Comparing the six built-in permalink structures
4. Step-by-step: setting up SEO-friendly permalinks
5. Changing permalinks on a site that's already live
6. Common permalink mistakes to avoid
7. Troubleshooting 404 errors after a permalink change
8. Best practices for individual post URLs
9. Frequently asked questions

What Are WordPress Permalinks?

"Permalink" is short for permanent link — the full web address that points to a specific post, page, or piece of content on your site. Every time you publish something in WordPress, it automatically generates one of these URLs based on a structure you choose once, in your site settings, and which then applies to everything you publish afterward.

The word "permanent" is doing real work in that name. The whole idea is that once a URL is published and indexed by search engines, bookmarked by readers, or linked to by other websites, it should never change. Every time it does change without a proper redirect in place, something breaks: a bookmark stops working, a shared link goes dead, a search engine result points to a 404 error page instead of your content.

WordPress gives you control over this through Settings → Permalinks, a page most beginners never open, sitting on a default structure that nobody who understands SEO would actually choose on purpose.

Why Permalink Structure Actually Affects SEO

It's fair to ask why a URL format matters at all, as long as the link technically works. Here's the honest answer, broken into the parts that matter:

• Readability signals relevance. A URL like example.com/wordpress-permalinks-guide/ tells both readers and search engines what the page is about before they even click. A URL like example.com/?p=847 tells them nothing.
• Keywords in the URL carry a small but real SEO weight. It's not a massive ranking factor on its own, but it's one more relevant signal stacked on top of your title, headings, and content — and search algorithms reward relevance wherever they find it.
• Clean URLs get clicked more often in search results. When someone scans a page of search results, a readable URL underneath the blue link reads as more trustworthy and specific than a string of numbers and question marks.
• They're easier to share and remember. A URL a person can actually read is a URL they're more willing to paste into a message, mention out loud, or type from memory.
• Category and date structures create unnecessary length. Longer URLs aren't automatically bad, but stuffing in a full date or a category name adds characters that rarely help anyone and occasionally cause real problems, covered in the comparison below.

A clean permalink structure is invisible when it's working, and obvious the moment it isn't. Photo via Pexels.

Comparing the Six Built-In Permalink Structures

WordPress ships with six preset options, plus a custom field for building your own. Here's exactly what each one produces and when, if ever, you'd actually want it.

Structure	Example URL	Recommended?
Plain (default)	example.com/?p=123	No — worst option for SEO and readability
Day and name	example.com/2026/09/19/post-title/	No — unnecessarily long, dates content visibly
Month and name	example.com/2026/09/post-title/	Rarely — only for strictly date-sensitive news sites
Numeric	example.com/archives/123	No — same core problem as the plain structure
Post name	example.com/post-title/	Yes — the recommended default for almost every site
Custom structure	example.com/%category%/%postname%/	Situational — useful for large sites with stable categories

Notice the pattern: every structure that bakes in a date creates a small but real problem. If you publish an evergreen guide in 2026 and it's still accurate and ranking well in 2029, a URL that literally says /2026/ in it makes the content look outdated at a glance, even when the information inside hasn't aged a day. This alone is reason enough to avoid the date-based structures for almost any kind of content that isn't inherently time-sensitive news.

Step-by-Step: Setting Up SEO-Friendly Permalinks

1Open the Permalinks settings

From your WordPress dashboard sidebar, go to Settings, then click Permalinks. This page lists all six built-in structures as radio buttons, with the currently active one selected.

2Select "Post name"

Click the radio button next to Post name. This is the structure recommended for the overwhelming majority of blogs, business sites, and content sites, since it produces the shortest, cleanest, most keyword-relevant URL format available out of the box.

3Click Save Changes

This single click does more than update a setting — it triggers WordPress to regenerate your site's rewrite rules, which is the underlying mechanism that translates a clean URL back into something your server and database can actually process. On most hosting setups, this also updates your .htaccess file automatically.

4Test a few existing URLs

Click through to two or three published posts from your homepage or a category page. Confirm each one loads correctly with the new, cleaner URL format showing in your browser's address bar.

5Check your XML sitemap

If you're using an SEO plugin like Yoast or Rank Math, visit your sitemap URL (usually example.com/sitemap.xml) and confirm the new URL format is reflected there. Most SEO plugins regenerate this automatically, but it's worth a quick check.

Tip: If Save Changes doesn't seem to do anything visible, that's expected — there's no confirmation animation. The change is applied the moment you click it, and the real test is whether your URLs load correctly afterward.

Changing Permalinks on a Site That's Already Live

Everything above is simple and low-risk on a brand-new site with no published content or existing traffic. The moment your site already has posts that are indexed by Google, linked to from other websites, or bookmarked by readers, changing the permalink structure without a plan can quietly cost you a meaningful amount of SEO value.

Here's why: every one of those old URLs is still out there, embedded in search results, backlinks, and social shares. The instant you switch structures, every single one of them starts returning a 404 error, because the address it's pointing to no longer technically exists on your server.

The fix is 301 redirects — a permanent redirect rule that automatically sends anyone (including search engine crawlers) from the old URL to its new equivalent. Here's the safe process:

1. Export a full list of your current URLs before making any changes, either through your SEO plugin's tools or your XML sitemap.
2. Install a redirection plugin such as Redirection or the redirect manager built into your SEO plugin, if you don't already have one active.
3. Change your permalink structure following the steps above.
4. Set up a 301 redirect from every old URL to its new version. Some redirection plugins can detect and handle this pattern-matching automatically when the change is systematic (for example, removing a date prefix from every URL at once); for anything irregular, you may need to add redirects individually.
5. Resubmit your sitemap to Google Search Console so it recognizes the new URLs faster.
6. Monitor your 404 reports in Search Console over the following two to three weeks to catch anything the redirect setup missed.

Important: Never change your permalink structure on a live, indexed site without redirects in place first. Even a few days without them can mean losing backlink value that's difficult, and sometimes impossible, to fully recover.

Redirects are the safety net that makes a permalink change on a live site low-risk instead of high-risk. Photo via Pexels.

Common Permalink Mistakes to Avoid

• Changing structure on a live site with no redirect plan. Covered above, and worth repeating: this is the single costliest mistake in this entire guide.
• Including stop words and filler in individual URLs. A post titled "How to Fix a Slow WordPress Site in 2026" doesn't need every word in its URL slug. Something like fix-slow-wordpress-site is cleaner and just as clear.
• Using dates in the structure for evergreen content. As covered earlier, this makes timeless content look stale years down the line for no real benefit.
• Changing a post's individual URL slug after it's been published and indexed. This creates the exact same 404 problem as a site-wide structure change, just on a smaller scale — one broken link instead of hundreds.
• Using underscores instead of hyphens in custom slugs. Search engines read hyphens as word separators; underscores are generally treated as one continuous word, which can hurt how individual keywords in the URL are understood.
• Leaving the default Plain structure active indefinitely. Sometimes this is simply an oversight from never opening the Permalinks settings page in the first place. It's worth checking today if you haven't already.

Troubleshooting 404 Errors After a Permalink Change

If you've changed your structure and started seeing 404 errors on pages that should exist, work through these in order:

First: revisit the Permalinks settings page and click Save again

This sounds too simple to be real advice, but it resolves the majority of cases. Go to Settings → Permalinks and click Save Changes one more time, without changing the selected structure. This forces WordPress to regenerate its rewrite rules and often fixes broken URLs immediately, especially right after a structure change or a theme switch.

Second: check whether your .htaccess file is writable

On Apache-based hosting, WordPress needs to be able to write to the .htaccess file in your site's root directory for automatic rewrite rules to apply. If file permissions are too restrictive, this step silently fails. Your host's support team or File Manager tool can confirm and adjust permissions if needed.

Third: manually check your .htaccess content

If you have FTP or File Manager access, open .htaccess and confirm it contains a WordPress rewrite block that looks like this:

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress

If this block is missing entirely, copy it in manually, or trigger it to regenerate by saving the Permalinks settings page again.

Fourth: rule out a caching issue

If you're running a caching plugin or your host uses server-level caching, an old cached version of a page can keep showing a 404 even after the underlying issue is fixed. Clear all caching layers and test again in a private browser window.

Best Practices for Individual Post URLs

Getting the site-wide structure right is half the job. The other half is how you write the URL slug for each individual post going forward:

• Keep slugs short and specific. Somewhere between three and six words is usually the sweet spot — enough to be descriptive without becoming unwieldy.
• Include your primary keyword naturally. If the post targets "wordpress child theme tutorial," a slug like wordpress-child-theme-tutorial is direct and effective.
• Drop unnecessary words. Articles, conjunctions, and filler words ("a," "the," "and," "how to") rarely need to survive into the slug itself.
• Use lowercase letters and hyphens only. WordPress does this automatically in most cases, but it's worth confirming, especially if you've manually edited a slug.
• Never reuse a slug after deleting the original post. If old backlinks or search results still point to that address, reusing it for unrelated content creates a confusing experience for anyone arriving through the old link.
• Decide on a slug before publishing, not after. Editing a slug after a post has been live and indexed for a while triggers the exact redirect problem covered earlier, just at the level of a single page instead of the whole site.

A well-written slug does double duty: readable for humans, relevant for search engines. Photo via Pexels.

Frequently Asked Questions

What is the best permalink structure for SEO in WordPress?

For most sites, the Post Name structure, which looks like example.com/post-title/, is the best option. It's short, readable, keyword-friendly, and doesn't include dates or numbers that add no value for readers or search engines.

Will changing my permalink structure hurt my SEO rankings?

Changing permalinks on a brand-new site with no traffic is completely safe. On an established site, it can temporarily hurt rankings if you don't set up 301 redirects from every old URL to its new equivalent, since search engines and other sites are still linking to the old addresses.

Why do I get a 404 error after changing my permalinks?

This almost always means your server's rewrite rules haven't updated. Going to Settings, then Permalinks, and clicking Save Changes again, without changing anything, usually forces WordPress to regenerate the .htaccess file and fixes it immediately.

Should I include the category name in my post URLs?

Generally no, for most blogs. Category names in the URL make links longer, and if you ever reorganize your categories, every post in that category changes its URL. The Post Name structure avoids this problem entirely by leaving categories out of the address.

Do I need a plugin to manage WordPress permalinks?

No, changing the structure itself is a built-in WordPress feature with no plugin required. A plugin becomes useful only when you're setting up bulk 301 redirects after changing permalinks on a site that already has published content and existing backlinks.

What happens to my old URLs if I switch permalink structures?

Without redirects, the old URLs simply stop working and return a 404 error page to anyone who visits them, including search engines following old links. Setting up 301 redirects from each old URL to its new version is the only way to preserve that traffic and the SEO value built up over time.

Setting up permalinks on a new site right now?

Choose Post Name from the start — it's the one structure on this page you'll never need to migrate away from later.

How Permalinks Actually Work Behind the Scenes

It helps to understand, at least at a high level, what's happening when you click that Save button, because it demystifies why certain problems occur and why the fixes above actually work.

By default, WordPress stores every post and page in a database table, each with its own numeric ID. The plain permalink structure, example.com/?p=123, is really just a direct, literal query telling your server "go fetch database entry number 123." It's simple, and it's exactly why it works reliably even when everything else is misconfigured — but it's also why it's meaningless to a reader or a search engine glancing at the address.

When you switch to the Post Name structure, WordPress doesn't change how content is stored in the database at all. Instead, it relies on a server module, most commonly Apache's mod_rewrite or an equivalent on Nginx, to intercept a clean-looking URL request and silently translate it back into that same underlying database query before your server ever processes it. The .htaccess file mentioned in the troubleshooting section is where Apache stores the specific pattern-matching rules that make this translation possible.

This explains two things that otherwise seem mysterious. First, why clicking Save Changes on the Permalinks page — even with nothing actually changed — can fix a broken site: it forces WordPress to rewrite those translation rules from scratch, clearing out anything that had gotten corrupted or outdated. Second, why moving a WordPress site between hosts sometimes breaks permalinks entirely: the new server's mod_rewrite configuration, or the .htaccess file itself, didn't transfer correctly, and the clean URLs no longer have anything to translate them back into a valid database lookup.

On Nginx-based hosting, there's no .htaccess file at all — the equivalent rewrite rules live directly in the server's own configuration files, which is why permalink issues on Nginx hosting sometimes require a support ticket to your host rather than something fixable from inside the WordPress dashboard alone.

Permalinks for Categories, Tags, and Custom Post Types

Everything above focuses on individual posts and pages, but permalinks apply to every content type WordPress generates a URL for, and each has its own quirks worth knowing about.

• Category and tag archive pages get their own base prefix, usually /category/ and /tag/ by default. These can be customized or shortened under the same Permalinks settings page, in the "Optional" section near the bottom, which is easy to miss on a first pass.
• Custom post types, such as a portfolio, product catalog, or testimonials section added by a plugin or custom code, typically get their own slug prefix as well, defined either by the plugin itself or by whoever registered the post type. These usually don't need to be touched unless there's a specific reason to change them.
• Author archive pages use a base like /author/username/ by default, which is worth reviewing on a single-author site, since exposing a username in a public URL is a minor, commonly overlooked security consideration.

For a typical content site with just posts and pages, none of this needs active management beyond knowing it exists. It becomes relevant mainly once a site grows into e-commerce, membership content, or a custom plugin-driven structure, at which point it's worth a five-minute review of the full Permalinks settings page rather than assuming the defaults are optimal.

Wrapping Up

Permalinks are one of those Web Development Basics that sit quietly in the background for years once they're set up correctly — which is exactly why it's worth getting right the first time. Five minutes in Settings → Permalinks, choosing Post Name, and clicking Save is the entire fix for a brand-new site.

If you're working with a site that already has traffic and history, the extra step of setting up proper 301 redirects isn't optional — it's what stands between a smooth, invisible upgrade and a genuine SEO setback. Take the time to do it properly, and this becomes one more setting you never have to think about again.

This guide is provided for informational purposes based on standard WordPress documentation and common SEO practices. Always back up your site before changing structural settings.