What Are WordPress Permalinks?
A WordPress permalink is the permanent URL for a post, page, or other content, the web address people bookmark, share, and click from search results. WordPress lets you choose a permalink structure in Settings, from ugly numeric URLs like /?p=123 to clean, readable ones like /blog/my-post/. The recommended Post name structure produces short, keyword-friendly links that help both readers and search engines understand a page. Because links are how the web references your pages, changing an established permalink can break inbound links and rankings unless you set up redirects.
- Definition
- The permanent URL used to link to a specific piece of content (WordPress Documentation)
- Where set
- Settings, then Permalinks, offers preset structures plus a custom option (WordPress Documentation)
- Recommended
- The Post name structure (/sample-post/) is the common SEO-friendly default
- Stored in
- Structure rules generate rewrite rules; each post's slug lives in the wp_posts table
- Change risk
- Altering an existing permalink breaks old links unless you add a 301 redirect (Google Search Central)
What a permalink really is #
A permalink, short for permanent link, is the full web address of an individual page or post on your WordPress site. It is what appears in the browser bar, what someone copies to share on social media, and what Google displays and links in search results. Because so much of the web depends on stable addresses, permalinks are meant to stay fixed once published, hence the name. WordPress gives you control over how these addresses are formed through a setting called the permalink structure, which turns your chosen pattern into readable URLs. A good permalink is short, human-readable, and hints at the page's topic, such as /services/local-seo rather than a string of numbers. This clarity helps visitors trust a link before clicking and helps search engines understand context. Getting permalinks right early is a small decision with long consequences, because every link, bookmark, and ranking your site earns is tied to the exact URL you chose at the start.
The available permalink structures #
In Settings, then Permalinks, WordPress offers several preset structures plus a custom field. Plain uses query strings like /?p=123, which work but look cryptic and reveal nothing about the content. Day and name, and Month and name, embed the publish date, which suits news sites but makes URLs long and can look dated for evergreen content. Numeric uses the post ID. Post name, generally the recommended choice, produces clean links like /how-to-choose-a-host/ using the post's slug. You can also build a custom structure with tags such as %category% and %postname% to nest posts under sections. Each choice affects readability, length, and how tidily your site is organized. For most small businesses, Post name strikes the best balance of brevity and clarity, and it pairs well with strong /services/seo-services. The key is choosing deliberately before you publish widely, because switching structures later changes every URL on the site at once. Whatever you decide, document the choice so future editors keep new URLs consistent with the pattern already in use.
How WordPress turns structures into URLs #
Behind the scenes, WordPress converts your chosen permalink structure into rewrite rules that map a clean URL back to the right content. When you save the Permalinks screen, WordPress regenerates these rules and typically writes matching directives into the site's .htaccess file on Apache servers, or relies on equivalent handling on Nginx. A visitor requesting /how-to-choose-a-host/ is silently matched to the correct post ID, so the pretty URL and the database lookup stay in sync. Each post's slug, the last readable segment, is stored with the post and can be edited per item in the editor. The example below shows the kind of rewrite directive WordPress manages for you. Understanding this helps explain why clean permalinks sometimes return 404 errors right after a server move: the rewrite rules did not carry over. That is a routine fix in /services/website-migrations, usually solved by re-saving permalinks so WordPress rebuilds the rules for the new environment.
# Simplified .htaccess block WordPress manages for pretty permalinks
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# Fix for 404s after a move: Settings > Permalinks > Save (regenerates rules)Why permalinks matter for SEO #
Permalinks are a modest but real SEO factor and, more importantly, a usability one. A clean URL containing relevant words, like /web-design-for-dentists rather than /?p=482, gives readers and search engines an instant clue about the page's subject before they even load it. Descriptive URLs appear as blue link text in some search layouts and are easier to read aloud, remember, and trust. They also tend to earn more clicks when shared, because a human-readable link looks safer than a cryptic one. That said, the effect is supporting, not decisive; content quality, page speed, and relevance matter far more, and stuffing keywords into URLs backfires. The practical advice is simple: use short, lowercase, hyphenated slugs that reflect the page topic, and avoid dates on evergreen pages. Businesses investing in /services/local-seo benefit from consistent, tidy URLs across their whole site, since clarity compounds when every page follows the same sensible, readable pattern. Keeping URLs consistent sitewide also makes analytics cleaner, since tidy, predictable paths are easier to group and interpret in reports.
The danger of changing permalinks #
Changing an established permalink is one of the most damaging mistakes a WordPress owner can make without realizing it. Every existing link to that page, from other websites, social shares, bookmarks, and Google's index, points at the old URL. Change the slug or the whole structure and those links suddenly land on a 404 error, losing traffic and the SEO value that inbound links passed along. If you must change a URL, the fix is a 301 redirect from the old address to the new one, which tells browsers and search engines the page moved permanently and forwards both visitors and ranking signals. On a large site, switching the entire permalink structure means hundreds of redirects, which is a real project, not a casual setting flip. This is precisely the kind of work handled carefully during /services/website-redesign, where teams map old URLs to new ones before launch so nothing is silently lost and hard-won rankings survive the transition intact.
Editing individual post slugs #
Separate from the sitewide structure, you can edit the slug of any single post or page in the editor, the readable segment at the end of its URL. WordPress auto-generates a slug from the title, but the auto version is often longer than ideal, including small words that add no value. Trimming a slug from /the-ultimate-guide-to-choosing-a-web-host-in-2026/ down to /choosing-a-web-host/ makes it cleaner and more durable, since it will not look dated next year. The best time to set a good slug is before publishing, because editing it afterward requires the same 301 redirect discipline as any URL change. Keep slugs short, lowercase, and hyphen-separated, and drop stop words like the and a where they add nothing. This attention to individual URLs is a small habit that keeps a growing site tidy. When many posts accumulate messy auto-slugs, cleaning them up is a common recommendation from a thorough /free-website-audit. Building the habit of trimming slugs before publishing spares you the redirect work that fixing them afterward always requires.
Common permalink issues and fixes #
Several permalink problems recur. The classic is pretty URLs returning 404 errors after a hosting move or a plugin change, fixed by visiting Settings, then Permalinks, and clicking Save to regenerate the rewrite rules, plus confirming .htaccess is writable on Apache. Another is a category base appearing in URLs, like /category/, which some owners remove for cleaner links, though that must be done carefully to avoid conflicts. Duplicate slugs get an automatic numeric suffix, such as -2, which looks awkward and signals a naming clash worth resolving. Switching structures on an indexed site without redirects tanks traffic overnight. Trailing-slash inconsistencies can create duplicate-URL confusion for crawlers. Each of these is manageable with care, and none should be tackled casually on a live business site. When permalinks break widely and links stop resolving, it is often bundled into a /services/website-rescue effort, where restoring correct URL routing and adding the right redirects gets traffic flowing to the proper pages again.
Best practices for lasting URLs #
The safest permalink strategy is to decide early and rarely change. On a new WordPress site, set the structure to Post name before you publish much, keep slugs short and descriptive, and standardize on lowercase with hyphens. Avoid dates in URLs unless you truly run a news site, since dated links make evergreen content look stale. Resist restructuring URLs on a whim; if a change is genuinely necessary, plan the 301 redirects first and test them before and after launch. Treat your URLs as long-term assets, because every link and ranking your site earns attaches to a specific address. This forward-looking discipline is a hallmark of solid /services/wordpress-development and pays dividends for years. If you are unsure whether your current structure is helping or quietly hurting you, or you inherited a messy set of URLs, a quick review through /contact can flag the changes worth making and the ones best left alone. When in doubt, leave a working URL alone; stability is almost always worth more than a marginally prettier address.
FAQ
What is the best permalink structure for SEO?
The Post name structure, which produces clean URLs like /my-post/, is the common recommendation. It is short, readable, and can include topic keywords without dates that age content. For most business sites it beats date-based or numeric structures. Whatever you choose, set it before publishing widely, because changing it later rewrites every URL on the site.
Will changing my permalinks hurt my rankings?
It can, badly, if you do not add redirects. Every old link and search-engine entry points at the previous URL, so without a 301 redirect those become 404 errors and you lose traffic and ranking value. If you must change URLs, map old to new and set up redirects before launching the change.
Why are my pretty permalinks showing 404 errors?
Usually the rewrite rules did not regenerate, often after a server move or plugin change. Go to Settings, then Permalinks, and click Save without changing anything to rebuild them. On Apache, also confirm the .htaccess file exists and is writable. This simple re-save fixes the majority of sudden permalink 404 problems.
Can I change the URL of a single post?
Yes. In the editor, edit the slug, the readable end of the URL, for that post. It is best done before publishing. If the post is already live and indexed, changing its slug requires a 301 redirect from the old URL to the new one so existing links and rankings are not lost.
Where are permalinks stored in WordPress?
The sitewide structure lives in your options settings, while each post's individual slug is stored with the post in the database. WordPress converts the structure into rewrite rules, typically written to .htaccess on Apache servers, that map clean URLs to the correct content. That is why re-saving permalinks regenerates those rules.
Should I include the date in my URLs?
Generally no, unless you run a genuine news site. Dates make URLs longer and cause evergreen content to look outdated a year later, which can reduce clicks. The Post name structure without a date keeps links timeless and short. Reserve date-based structures for time-sensitive publications where the publish date genuinely matters to readers.
How Local Web Advisor checks this for you
Is your own website getting web dev right?
Our free AI audit scans your site and tells you — in plain English — exactly what to fix for web dev and seven other areas, with the business impact and the fix for each. No login needed to start.
Run my free website audit →Was this helpful?