How a subdomain works
A subdomain is a prefix on your domain — blog.example.com, shop.example.com, help.example.com. It is created by adding a record in your DNS settings and pointing it wherever you like, and that is the important part: a subdomain can live on a different server, run different software and be managed by a different team from the main site. The familiar www is itself a subdomain, which surprises most people.
Search engines can see that two hostnames share a root domain, and they often treat them as connected. They do not treat them as one site the way they treat folders on a single hostname. Strength earned by one hostname is not automatically credited to the other, and each one is verified, crawled and reported on separately.
Why subdomains matter
The decision usually arrives disguised as a technical convenience. A hosted help desk, a shop platform or a marketing tool offers you an address on their system, and the path of least resistance is to accept it. Do that for the content meant to win you search visibility — the blog especially — and your best material now sits on an address starting from a weaker position than the site it was supposed to support.
There are honest reasons to use one. Software that cannot run inside a folder of your main site, a customer login area, a staging copy, a regional section run by another team: all reasonable. The test is whether the separation is genuinely forced on you, not whether it is tidier for the people building it.
Where subdomains go wrong
Staging is the expensive one. A copy of the site on a development subdomain with no password gets crawled, indexed and shown to customers, and it competes with the pages you actually sell from. Anything not meant for the public needs authentication, not just a noindex tag, because a tag only asks nicely and only works once the page has been fetched.
Two others are common. Choosing a subdomain for the blog in the belief that search engines will merge everything anyway — they may, partly, but you are relying on a behaviour rather than designing for one. And forgetting that the www and non-www versions are different hostnames, so both must resolve, one must redirect to the other, and the one you keep is the one every report should refer to.
What to do about it
Default to a folder on the main site, and treat a subdomain as the answer only when a real constraint makes the folder impossible. Where a hosted platform cannot serve from a folder directly, a reverse proxy often can, and that is worth asking a developer about before you accept the subdomain they offer.
Where subdomains already exist, tidy them rather than fight them. Verify each in Search Console, link between them deliberately in navigation and in body copy, keep one canonical hostname for the main site, and password-protect anything not meant for customers. If you later decide to bring a subdomain into a folder, plan it as a proper site migration, with a redirect for every URL and a period of watching afterwards — it is not a settings change.
