Should WordPress post URLs start with /blog/?
It is a structural choice, not a ranking one. A /blog/ prefix helps when posts share a site with product or service pages, because reports and rules can treat articles as a group. On a site that is only a blog it adds nothing. Either way, choose before you publish and then leave it.
What the prefix changes in WordPress
You add it under Settings → Permalinks → Custom Structure by entering /blog/%postname%/. The fixed text before the first tag is what core calls the front, and it is applied to more than posts:
| URL type | Without prefix | With /blog/%postname%/ |
|---|---|---|
| Post | /espresso-grind-size/ | /blog/espresso-grind-size/ |
| Category archive | /category/brewing/ | /blog/category/brewing/ |
| Tag archive | /tag/espresso/ | /blog/tag/espresso/ |
| Author archive | /author/sam/ | /blog/author/sam/ |
| Page | /pricing/ | /pricing/ (unchanged) |
| Custom post type | /recipes/flat-white/ | /blog/recipes/flat-white/, unless registered otherwise |
The last row catches people out. A custom post type inherits the front unless whoever registered it set with_front to false in its rewrite settings. If your products or case studies suddenly appear under /blog/, that is why, and it is fixed in the code or plugin that registers the type.
Categories and tags behave slightly differently if you have typed your own Category base or Tag base on the same screen: a custom base is used as written, without the front.
Does the folder help rankings?
Google has not said that a path segment such as /blog/ improves or harms ranking, and a post one folder deeper is not "further from the root" in any way that matters. Crawlers measure distance in clicks, not slashes.
What the folder gives you is organisation:
- Reporting. In Search Console and analytics you can filter by "URLs containing /blog/" and see article performance apart from commercial pages.
- Rules. Redirects, caching, robots rules and schema defaults can be written once for the whole section.
- Clarity for visitors. The address tells them they are reading an article. Paired with breadcrumbs, the trail is Home, Blog, post.
And one cost: every post URL is five characters longer.
Which sites should use it
Use a prefix on a company site, shop or SaaS site where the blog is one section among several. Group separation is useful there, and a slug like /pricing-guide/ will not be mistaken for the /pricing/ page.
Skip it on a publication where posts are the site. /blog/ in front of everything says nothing, and the shorter address is cleaner.
Do not switch an established site just to get one or lose one. Changing the structure changes every post URL together with category, tag and author archives. Core does not create redirects for a structure change; you must add a pattern redirect and then wait while search engines reprocess everything. The gain is organisational only, so on a site that already ranks it rarely justifies the move. If you go ahead anyway, follow changing permalinks without losing SEO.
Setting it up cleanly on a new site
- Create a page called Blog and set it as the Posts page under Settings → Reading, so
/blog/itself is the article index. Without this, the folder in your URLs has no page at its root. - Enter
/blog/%postname%/as the Custom Structure and save. - Open a category archive and confirm where it lives. If you would rather keep
/category/brewing/at the top level, typecategoryinto the Category base field; a custom base drops the front. - Check any custom post types. Each should sit where you expect.
- Publish, then test a post, a category, a tag and a page.
After that, treat the structure as permanent.
Common questions
Is a blog on a subfolder better than no folder?
Neither ranks better. The folder is a way to group posts for reporting and rules, which matters on mixed sites and not on pure blogs.
Why did my category URLs change when I added /blog/?
Because WordPress prepends the fixed start of your permalink structure to category, tag and author archives as well. Setting a custom Category base keeps them out of the folder.
Can posts be under /blog/ and pages stay at the root?
Yes. Pages never take the prefix, so `/about/` and `/pricing/` remain top-level while posts move under `/blog/`.
Does the Blog page need the same slug as the prefix?
It should. If the Posts page is at `/news/` while posts live under `/blog/`, the `/blog/` address has no index page and returns a 404.