Quick answer:
Put your blog in a subfolder such as yoursite.com/blog unless the section is a genuinely separate product, platform or regional site run by its own team.Key Takeaways
- Google can crawl and rank blogs in subdomains and subfolders, so neither address carries a built-in penalty.
- A subfolder blog shares the main site's CMS and Search Console property, which keeps linking and maintenance in one place.
- A subdomain fits a separate application, a help centre hosted on another platform, or a regional site with its own team.
- Moving a blog into a subfolder is a full site move that needs page-level permanent redirects and a traffic benchmark first.
- A subdomain blog that already performs well is usually better improved in place than migrated.
A company blog can live at blog.yoursite.com or at yoursite.com/blog. The address looks like a small technical detail, but it shapes how the blog is linked, maintained and measured for years.
Google can work with either structure, so the choice comes down to how your team runs the site. This guide explains where each option fits and what a move between them involves.
What Google says about the two structures
Google's documentation does not rank one structure above the other. Its SEO starter guide keeps its URL advice to descriptive, organised addresses and says nothing about where a blog should sit.
The guidance for site owners is to pick the structure that is easier to maintain.
Crawling and indexing work in both setups. The differences that matter appear later, in how teams run the blog day to day.
Why subfolders work better in practice
A blog at yoursite.com/blog runs in the same CMS as the rest of the site. Writers can link each post to a service page without leaving the editor, so a blog with hundreds of posts ends up with hundreds of links pointing at the pages that sell.
A subdomain blog usually sits in its own CMS. Those links still help, but adding one means logging in to the main site to copy the address, so in practice most posts go out without them.
Reporting is simpler in one place too. A single Search Console property shows blog pages and service pages side by side, so you can tell whether blog readers end up contacting you.
The blog also inherits the main site’s technical foundations. Page speed improvements, structured data and security updates cover every section at once.
A separate blog also doubles the housekeeping. Updates, sitemaps, redirects and structured data all need doing twice, and the copy nobody owns falls behind.
None of this shows up as a penalty in Search Console. It shows up as a blog that slowly stops getting maintained, and our comparison of content, backlinks and technical work makes the same point about routine upkeep.
When a subdomain is the right tool
A subdomain makes sense when the section really is a separate system. These situations come up most often:
- An application interface such as app.yoursite.com, which should have its own system and release cycle.
- A help centre or online store on a hosted platform such as Zendesk or Shopify, which usually connects to your domain only as a subdomain like help.yoursite.com.
- A regional or language site run by its own team, where Google's international guidance treats country subdomains and country subdirectories as equally valid.
None of these reasons have anything to do with rankings. Each one is a case where the technology or the team genuinely needs its own space.
Which structure fits your situation
| Your situation | Suggested structure | Why |
|---|---|---|
| New blog for an existing site | Subfolder | Shared CMS, shared reporting and natural internal links. |
| Application interface | Subdomain | A product interface needs its own system and release cycle. |
| Help centre or store on an outside platform | Subdomain | Hosted tools usually only connect as a subdomain such as help.yoursite.com. |
| Regional site with its own team | Either | Both are valid for country targeting, so decide on operations. |
| Subdomain blog that already performs | Keep the subdomain | Improving links and content in place avoids migration risk. |
If none of the subdomain cases apply, the subfolder is the safer default. The order of decisions matters too, and choosing a domain extension comes before the structure.
Plan the move before you start
Moving a blog from a subdomain into a subfolder gives every post a new address. Most of the work is redirecting each old address to its new one, so set aside real time for that step.
Benchmark rankings, sessions and top landing pages before touching anything. Without a before, recovery and decline look the same.
Google's site move documentation is direct about the method:
"Use server side permanent redirects if technically possible."
Redirect every old URL to its matching new URL rather than sending everything to the blog homepage. Leave the redirects up for good, since other sites will keep linking to the old addresses for years.
Update internal links so they point at the new addresses, and move everything in one go. Rankings usually dip and settle over a few weeks while Google recrawls the moved pages.
If the blog already gets steady traffic where it is, a move can cost more than it returns. Keep it in place and add more links between the blog and the main site instead.
The bottom line
For a new blog, use a subfolder and spend the saved effort on the content itself. What gets published matters more than the address, and our comparison of AI drafts and human writing covers that work.
Structure reviews are part of our SEO services. The same clear organisation helps AI assistants cite a site, which is where a GEO agency in Singapore looks first.
An SEO consultant can put a number on the effort and the risk of a move before you commit to it. As a Singapore SEO firm, we will tell you plainly when a move is worth making.
Tell us where your blog lives and what it needs to do. We will recommend the structure, or the fix, that fits.
