How to set up SEO friendly URLs in WordPress

A fresh WordPress install gives posts addresses like example.com/?p=123. WordPress’s own documentation calls this Plain structure reliable on any server but not user-friendly or optimized for search. Fixing it takes one setting and about ten seconds, as long as you do it before the site has a few hundred indexed pages.

That timing is the whole story. Choosing a good URL structure is a one-time decision with almost no risk. Changing an existing structure is a migration: every old address needs to send people and search engines to its new one. URLs are one item on a longer list. The rest is in our guide to doing SEO on WordPress.

What makes a URL SEO friendly, and what doesn’t

An SEO friendly URL tells a person and a crawler what the page is about before they open it. /services/web-design/ does that. /page?id=8472 doesn’t. Google’s URL structure guidance asks for descriptive words instead of long IDs, hyphens between words, as few unnecessary parameters as possible, and consistent casing. Google treats /APPLE and /apple as two different URLs.

Google does not set a character limit. It does not say that shorter URLs, extra keywords or a missing /category/ segment rank better. Rank Math, which sells a feature for removing the category base, says in its own documentation that doing so is not guaranteed to improve rankings. Clean URLs are hygiene. They help people read and trust a link, and they keep your site consistent. They will not lift a weak page.

What does hurt is instability. Practitioner threads on Reddit and X rarely report a URL cleanup that boosted traffic. They often report a relaunch where addresses quietly changed and pages started returning 404s.

Which permalink structure should a new site use?

Post name, for nearly every site. It produces example.com/your-post-title/ and stays accurate however your categories change later. To set it:

1. In the dashboard, go to Settings > Permalinks.
2. Under Permalink structure, select Post name. The custom field shows /%postname%/.
3. Click Save Changes.
4. Open any post on the front end and check that the address now ends in its slug, not ?p=.

If you write a custom structure, use structure tags such as %postname% and leave the domain out of the field. WordPress adds it. The same screen holds the Category base and Tag base fields. Leave them empty unless you have a reason to change them.

When category or date in the URL makes sense

Category plus post name (/%category%/%postname%/) works when your categories are few, short and unlikely to change. The cost: moving a post to another category changes its URL, and that needs a redirect. Dates suit news sites, where readers care when a story was published. On evergreen guides, a date keeps showing the original year long after you’ve updated the article.

How to write slugs that hold up

The slug is the last part of the URL, and it is separate from the title. WordPress builds it from the title when you first save. You can edit it in the post’s settings panel before you publish. Our explainer on what a WordPress slug is covers where to find it. Rules that work in practice:

• Describe the page in a few words: /small-business-accounting/, not /accounting-services-for-every-small-business-owner-2026/.
• Use lowercase and hyphens. Google recommends hyphens over underscores.
• Include the main term once if it describes the page naturally. Don’t repeat it.
• Don’t strip every stop word by reflex. /how-to-fix-a-leaking-tap/ reads better than /fix-leaking-tap/, and WPBeginner notes that keeping stop words can help readability.
• Get the slug right before you share the post. Rewriting a title later doesn’t change the URL, and it shouldn’t.

The common “under 60 characters” or “three to five words” rules are editorial habits, not Google requirements. A slug that could be shorter but is accurate is fine. Leave it alone.

Why changing URLs on a live site is a migration

Each changed URL is a new address. That applies whether you switch the permalink structure, rename a WooCommerce base, drop trailing slashes in a redesign, or lowercase addresses during a move. Unless each old URL redirects to its new one, links, bookmarks and search results all lead to 404s. WP Engine’s support docs warn that changing an established site’s structure can cause widespread 404s and affect SEO. WordPress.com notes that posts may not redirect automatically when the structure changes.

A common mistake: people assume Save Changes on the Permalinks screen handles this. It doesn’t. Saving rebuilds WordPress’s rewrite rules, which fixes stale routing. It creates no redirects for addresses that have actually moved.

Before changing an established structure, ask whether you have a concrete reason. One example from Reddit: a long-running news site wanted category data in its URLs for analytics. Commenters suggested tracking the category in GA4 instead of moving thousands of articles. If the change is still worth it, Google’s site move documentation describes the method:

1. Export every current URL from a crawl, your sitemap or Search Console.
2. Map each old URL to its closest new equivalent. Don’t send unrelated pages to the homepage. Google may treat those as soft 404s.
3. Add server-side 301 or 308 redirects that go straight to the final URL, with no chains.
4. Test the map on staging, then on the live site with a sample of old URLs.
5. Update internal links, the XML sitemap and canonical tags to the new addresses.
6. Keep the redirects for at least a year, and watch 404 reports and Search Console after launch.

Even a clean migration can cause rankings to move for a while as Google recrawls. Use one redirect layer, either a plugin, server rules or your host’s tool, not several. Overlapping layers are how sites end up with ERR_TOO_MANY_REDIRECTS. For single pages, see how to redirect a WordPress page. For server rules, see htaccess 301 redirects in WordPress. If you would rather hand off the redirect map and the checking, SiteSelf handles 301 redirects and SEO settings through chat. Plugin-level redirects need the connector plugin, and rules in .htaccess need hosting access.

On redirect plugins: Yoast’s redirect manager, including automatic redirects when a slug changes, is part of Yoast SEO Premium, not the free plugin. It uses PHP redirects by default. Whichever tool creates the redirects, open a few old URLs yourself and confirm where they land.

WooCommerce: product and category bases

WooCommerce adds its own fields under Settings > Permalinks. Product URLs can use /product/name, /shop/name, /shop/category/name or a custom base, and category and tag bases are set separately. WooCommerce’s permalink documentation makes three points worth knowing before you touch them:

• Don’t use the same base, such as shop, for products and product categories. WordPress may no longer be able to tell them apart.
• If you change product URLs, old product links return 404 unless you redirect them.
• Attribute archive URLs only work if Enable archives is turned on for that attribute.

Putting the category in product URLs looks tidy until a product sits in two categories. Then it can have two addresses, and you have to manage canonicals for both. On an existing store, the safest choice is usually to keep the defaults.

Should you strip the category base?

Only if you understand the trade. Rank Math’s Strip Category Base setting (Rank Math SEO > General Settings > Links, visible in Advanced mode) removes /category/ and redirects existing category URLs. Rank Math warns that a category slug matching a post, page or product slug can cause unexpected results. WooCommerce support has advised against removing the product category base for the same reason. A middle path Reddit store owners suggest is a short, unique base like /c/, which keeps the URL short without the collision risk.

Why pretty permalinks return 404s, and how to fix them

The classic symptom is that the homepage loads but every post and page returns 404. Work through these causes, most frequent first:

1. Stale rewrite rules. These are common after a migration, an update or a new custom post type. Go to Settings > Permalinks and click Save Changes without changing anything. If that fails, switch to another structure, save, switch back and save again.
2. An .htaccess file WordPress can’t write to. On Apache, the Permalinks screen then shows “You should update your .htaccess file now.” along with the rules to add. Back up the file first, then paste the rules into the # BEGIN WordPress block, keeping your own custom rules above it.
3. A server that doesn’t route requests to WordPress. Apache needs mod_rewrite and permission for .htaccess overrides. Nginx ignores .htaccess completely and needs its server block configured. Resaving can’t fix either problem. Your host has to.
4. A plugin conflict. A WordPress.org support thread documents TranslatePress 2.8.3 breaking WooCommerce product category pagination on several client sites. If resaving helps only until the next page load or update, a plugin is probably rewriting the rules. Deactivate plugins one at a time on staging until the 404s stop.
5. A slug collision. A page and a category, or a page and a plugin route, share the same path. WordPress’s Common Errors handbook lists renaming the conflicting slug as the remedy. Rename it, then resave permalinks.

Stop and get help when inner pages still return 404 after a resave and a clean .htaccess, when you’re on Nginx and don’t have access to the server config, or when the 404s started right after a URL change and you have no list of the old addresses. The first two are hosting problems. The third needs someone to rebuild the redirect map from crawl data and Search Console before more traffic leaks away.

What to do about duplicate URLs from filters and parameters

Store filters, sort orders, tracking tags and variant parameters can give one page dozens of addresses. Google’s guidance on consolidating duplicate URLs treats redirects and rel="canonical" as strong signals and sitemap inclusion as a weaker one. A canonical is a signal Google weighs, not an order it must follow. In practice: redirect when an old URL is gone for good, use a canonical when both versions have to stay live, and link to the same preferred URL everywhere, in menus, internal links and the sitemap. For product variants passed as optional parameters, point the canonical at the clean product URL.