Subdomains, Folders and What Google Sees

The two arrangements

A subdomain sits before your name: shop.example.com or blog.example.com. A folder sits after it: example.com/shop or example.com/blog.

To a visitor there is little difference. Both work, both look reasonable, and most people would not notice which they were using.

To a search engine there is a real one. A folder is unambiguously part of the same site. A subdomain is treated as related but distinct, and how much credit passes between them is not something you control.

Why it matters for a small business

Because you have one site's worth of reputation and dividing it is expensive.

Search visibility accumulates. Links, mentions, and the general sense that a site is established build up over years and apply across the site they belong to.

Put the blog on a subdomain and it is building its own reputation from zero, separately, while the main site builds its own. Two small piles instead of one larger one.

For a large organisation with resources to build both, that separation is sometimes deliberate. For a small business with one site and no spare capacity, it is a self-inflicted disadvantage.

When a subdomain is right

Because it is not always wrong, and the honest answer matters.

• The technology demands it. Some hosted platforms only offer a subdomain.
• It is genuinely a different thing, serving a different audience, that you would happily separate entirely.
• You need different infrastructure, such as a shop on a separate server.
• It is not meant to be found, such as a staging site or a client portal.
• You are running different languages or regions as distinct properties.

The first is the most common reason in practice, and it is a constraint rather than a choice. It is worth knowing you are accepting a cost rather than making a neutral decision.

The cases that come up

Three, and the answer is the same for all three.

A blog. Put it in a folder. Its whole purpose is to build visibility for the business, and on a subdomain it builds visibility for itself.

A shop. Folder if the platform allows it. This is where the platform constraint bites most often.

Location or service pages. Folders, always. A subdomain per town is a pattern that used to be common and produces several thin sites instead of one substantial one.

The staging site nobody blocked

A specific subdomain problem worth naming separately.

Development copies frequently live on a subdomain, and they are frequently left open to search engines.

The result is a complete duplicate of your site in the index, competing with the real one, sometimes ranking instead of it, and occasionally showing visitors an unfinished version with placeholder content.

It is fixed by blocking it properly and adding a password. Both take minutes and neither happens by default.

If you have ever had a site built or redesigned, it is worth checking whether the staging copy is still there and still visible.

A worked example

An equipment hire business that put its blog on a subdomain in 2017, on the advice of the platform's setup guide.

Over two years they published around forty articles answering practical questions about the equipment they hired out. The articles were good and several ranked well.

None of that visibility reached the main site. Somebody searching a question found the article, read it, and left, because the blog was effectively a separate property with its own weak navigation back.

Moving the blog into a folder took a day, plus redirects from every old address. Within a few months the main site was ranking for terms it had never appeared for, because two years of accumulated credit now applied to it.

The work was small. The two years of separation were the expensive part, and nobody had made a decision at all: they had followed a setup guide.

Changing it later

Possible, and it is a proper migration rather than a setting.

Every existing address has to be mapped to its new equivalent and redirected permanently. Internal links need updating. Anything pointing at the old addresses from outside continues to work through the redirect, which must then be maintained indefinitely.

Done properly it is a day or two of work and the accumulated value transfers. Done carelessly it loses whatever the old addresses had earned.

Which is the argument for getting it right at the start, when it costs nothing, rather than correcting it in year three.

What about www

A related question that causes needless worry.

Technically www is a subdomain. Practically it is a convention and search engines treat it as the same site either way.

What matters is picking one and redirecting the other to it, so the site exists at one address rather than two. Both versions resolving independently is a genuine duplicate problem and a common one.

Which you choose is a matter of preference. That you choose is not, and it is worth confirming rather than assuming somebody handled it during setup.

What to check on your own site

1. Type your address with and without www and confirm one redirects to the other.
2. Look for anything on a subdomain that was meant to be part of the main site.
3. Search for your domain and see whether a staging copy appears.
4. Check the blog address, since setup guides frequently default to a subdomain.
5. Check the shop address if you have one.

The third is worth doing even if you are confident. Staging sites are created by suppliers rather than owners, and the owner is rarely told one exists, still less told when it is finished with.

The decision, in one line

Unless something forces a subdomain, use a folder.

That covers the blog, the shop, the service pages, the location pages and almost everything else a small business adds to its site over time.

And when a platform tells you a subdomain is required, treat it as a factor in choosing the platform rather than a detail to accept without noticing. It is a real cost, paid slowly, and it is easiest to avoid before you have published anything.

How the address itself resolves to a server in the first place is covered in domains and hosting, explained once.

Frequently asked questions

West Coast Media Solutions Inc. provides web design, web development, hosting, digital marketing, and business consulting to organisations across Canada, drawing on more than twenty-five years in the field.