Every agency and hosting provider gets asked the same question sooner or later: where should the client’s blog live?
The usual answer stops at SEO, comparing a subdirectory against a subdomain and calling it done. But that only covers half the decision. The other half is what each option actually costs to run: the DNS records, the certificate, the mail setup, the renewal exposure three years from now.
This article walks through both sides, plus a migration path for when a client outgrows their first choice.
Key takeaways
- A subdirectory inherits the main domain’s authority. A subdomain usually counts as part of the same site, but consolidation is less consistent. A separate domain starts from zero and has to earn its own authority.
- Each option has a different operational cost: DNS zones, certificate scope, mail authentication, and provisioning steps all change depending on where the blog sits.
- Short, brandable .blog names are often premium-tier, which means a higher renewal price every year, not just at signup.
- Moving a client between options is a manageable migration with a redirect map and a Search Console change of address, not a reason to avoid the right long-term choice.
Subdirectory, subdomain, or .blog: what you’re actually choosing between
Each of the three options puts the blog in a different place technically, and that difference is what drives everything else in this article.
A subdirectory puts the blog at a path under the main domain, like yoursite.com/blog. It lives on the same server or the same hosting account as the rest of the site, under the same certificate and DNS zone.
A subdomain puts the blog at blog.yoursite.com. It’s a separate hostname under the same root domain, which can point to different hosting, a different platform, or a different team, while still carrying the yoursite.com name.
A separate domain, such as client.blog, is its own registration entirely. It needs its own DNS zone, its own certificate, and its own mail setup if the client sends anything from it.
Is .blog better than .com for a company blog? Neither extension is inherently better. What matters is what the client needs the hub to do, covered in the decision framework below.
What each option does to your client’s search rankings
When a client asks where their blog should live, SEO is usually the first thing on the table.
A subdirectory carries a real advantage here: because it lives under the same domain, search engines treat it as part of the same site from day one, inheriting the domain’s existing authority and crawl budget (the number of pages a search engine is willing to crawl, in order to index them on a given site in a given window). A subdomain gets treated as part of the same site too, most of the time, but the signals don’t consolidate as cleanly. Google can, in some contexts, read a subdomain as a separate entity, and that inconsistency is exactly why agencies hesitate before recommending one.
A separate domain is a different proposition entirely. It won’t drag down the main site’s rankings, but it also inherits nothing. Every ranking signal has to be built from zero, on its own timeline.
What doesn’t factor into any of this is the TLD itself. A .blog domain ranks no better and no worse than a .com purely because of the extension – the part after the dot doesn’t affect ranking. Treating it like it does is a common mistake. We’ve made that case in full in why resellers should revisit .blog in 2026, so it’s worth a read if you want the deeper argument.
What each option actually costs to run
In reality, cost is where the three options diverge, and it’s the part most SEO comparisons skip.
Here’s what each one actually costs, starting with the cheapest to run:
Subdirectory: no new DNS zone, since it sits inside the existing one. The main site’s SSL certificate already covers it, no separate issuance needed. Mail authentication (SPF, DKIM, DMARC) stays exactly as it is, since there’s no new sending domain. Provisioning is whatever the client’s existing hosting plan already does. No separate billing line, no separate renewal date to track.
Subdomain: it needs one new DNS record inside the existing zone, usually a CNAME or A record pointing to wherever it’s hosted, plus an MX record if it sends its own mail. Zone management stays light. The certificate is the one thing to watch: a standard single-domain certificate won’t cover it, so it needs either a new certificate or a SAN (Subject Alternative Name) added to the existing one. If the client sends a newsletter from the subdomain, that hostname needs its own SPF, DKIM, and DMARC records – the authentication that proves mail from it is legitimate. Provisioning in WHMCS or HostBill is usually a quick manual addition rather than a full new product.
Separate domain: this is the full setup – its own registration, its own DNS zone, its own certificate, and its own SPF, DKIM, and DMARC records if it sends mail. Yes, it can send email exactly like any other TLD, as long as those records are configured. Most registrar modules let you provision it as a standalone product tied to the client’s existing account, so it lands on their usual invoice rather than as a new customer record. That’s also where the ongoing cost sits: a second domain means a second renewal date and a second line item on the bill, for as long as it stays active. Beyond the registration fee, budget for one certificate, a handful of DNS records, and the time to set it up properly the first time. After that, it runs itself.
The premium renewal trap that erodes your margin
Many of the best short, brandable .blog names sit in the registry’s premium tier, which means they renew at a premium price every single year, not just at first purchase. A reseller who prices year one off a promotional rate and lets the domain auto-renew at list price can get squeezed hard on renewal, especially if the client only budgeted for the promo price. Before quoting a .blog name to a client, check its tier in the registry’s premium list so the renewal cost is part of the conversation from day one, not a surprise twelve months later.
Registry rules that protect you before you commit a client
With Openprovider, .blog domains carry a six-day transfer window rather than the more typical 5, so factor that into any migration timeline. If a domain lapses, it moves through a series of stages: a free-restore soft quarantine, then a paid-restore quarantine, and finally a five-day PendingDelete period where restoring it is no longer possible. After that, the domain becomes available for anyone to register. For the full technical detail on transfer windows and lifecycle stages, see our .blog registry knowledge base article.
The five questions that decide the right option for your client
When deciding whether a separate domain is worth it for a blog, run through these five questions with the client before recommending an option:
- Does the hub need its own brand, separate from the main site?
- Does it need its own analytics baseline, tracked independently?
- Will it send its own newsletter, with its own sending reputation?
- Does it need its own team or workflow, separate from whoever runs the main site?
- Will the client still be running this hub in three years, or is this a shorter-term push?
If you answer yes to most of these, a separate domain is usually the right call. A no across the board usually means a subdirectory is the simpler, cheaper option. A subdomain sits in between: useful when the client wants some separation without the full cost of a second domain.
How to migrate a client without losing their traffic or their trust
Clients often change their minds, and moving from a subdirectory to a separate domain, or the other way round, is a manageable project rather than a reason to avoid the right long-term choice. The key is doing it properly: start with a full redirect map, giving every existing URL a 301 redirect to its new equivalent rather than a blanket redirect to the homepage. Set canonical tags on the new domain so they point to themselves, update internal links across the main site to the new location, and file a change of address in Google Search Console once the redirects are live.
Done this way, most migrations see rankings and traffic largely recover within a few weeks to a couple of months. It’s worth setting that expectation with the client up front rather than promising an instant transition.
How Openprovider keeps all three options cheap to run
Whichever option a client lands on, the operational side runs through one platform. Openprovider handles the domain, Premium DNS, SSL certificates, business email, and DMARC setup from a single account, so provisioning a subdomain or a separate domain doesn’t mean juggling four different vendors.
For resellers managing this across a client portfolio, bulk actions, the WHMCS module, and the API handle provisioning at scale, and a Membership subscription offers Openprovider-accredited TLDs at cost price.
Create your free Openprovider account to start registering .blog domains today.
FAQ
Do .blog domains renew at the same price every year?
Not always. Standard .blog names renew at the standard rate, but premium-tier names renew at a premium price every year, not just at initial registration.
What is a premium .blog domain?
A premium .blog domain is a name the registry has priced above the standard rate, usually because it’s short or highly brandable. The premium applies to every renewal, not just the first purchase.
How long does a .blog transfer take?
A .blog transfer runs through a 6-day transfer window before completing, slightly longer than the more common 5-day window on many other TLDs.
What happens if a .blog domain expires?
An expired .blog domain moves through a free-restore soft quarantine, then a paid-restore quarantine, before entering a five-day PendingDelete period. After PendingDelete, it becomes available for anyone to register.
Who runs the .blog registry?
.blog is operated by Knock Knock WHOIS There, LLC – a subsidiary of Automattic, the company behind WordPress.com.
How long does traffic take to recover after a blog migration?
Most migrations done with proper 301 redirects and a Search Console change of address see traffic largely recover within a few weeks to a couple of months.
