Host vs Subdomain When Adding a Site to AdSense

Host vs subdomain when adding a site to AdSense is the hostname decision: which string you type on Sites, how www relates to the apex domain, and when a true subdomain is even allowed—before you burn a review cycle on a URL AdSense will reject.

This page is hostname strategy only. It is not the full add a new site after approval verify → review → Ready walkthrough. It is not connected sites vs account status (account badge vs Sites row). Public SEO host consistency belongs with www, HTTPS, and trailing slash. First-apply readiness stays on the approval checklist.

Decision in one line: For a normal custom domain, enter the root domain AdSense accepts (for example example.com), keep one public host with redirects, and do not treat blog.example.com as a second Sites row unless you are on a host-partner / public-suffix pattern Help allows.

Disclosure: Educational overview of AdSense Sites URL rules. We do not guarantee review outcomes or ad fill. UI labels change—confirm in official Google AdSense Help. CashPilot may earn from some links at no extra cost to you.

Table of contents

1. The decision before you click + New site
2. What Google accepts as a “site” URL
3. www vs apex: SEO host vs AdSense domain
4. True subdomains and host partners
5. Scenario map
6. Mistakes that waste a Sites review
7. FAQ
8. Pick the string, then verify

The decision before you click + New site

Most second-site failures start with a typing debate, not a policy essay:

  HOSTNAME DECISION
  1. What do users type?     (www or apex — pick one)
  2. What does AdSense accept? (root domain / partner host)
  3. What do redirects do?   (301 everything else to the one host)
  4. Then verify ownership   (code / ads.txt / meta — other post)

If you skip step 2 and paste https://www.example.com/blog/?ref=adsense, you are fighting Help’s URL rules, not “AdSense hate.”

Official anchors while you decide:

• How to enter the URL of your site
• Site management is changing in AdSense
• Add a new site to your AdSense sites list
• AdSense site management

What Google accepts as a “site” URL

URL entry Help (written for account creation, still the clearest valid/invalid table) says the URL must be a standard domain without path, parameter, fragment, or port.

Valid examples Help lists: example.com, example.blogspot.com
Invalid examples Help lists: example.com/page.html, directories, query strings, and subdomain.example.com (and paths under it)

Help’s note: subdomains are only allowed on host partner sites (see Blogger / partner flow). That is the core strategy rule for custom domains.

Site management changes reinforced the Sites model:

• You add domains (for example website.com)
• Or subdomains on public-suffix platforms (Help example: site.appspot.com)
• Or AdSense platform partner sites (Help example: site.blogspot.com)
• You no longer add or manage subdomains that are part of an existing site as separate Sites entities; Help says removal of those rows does not impact ad serving or earnings

So the modern mental model is: one domain row, not a Sites zoo of www, blog, and shop as separate applications—unless you are on a partner/public-suffix pattern.

www vs apex: SEO host vs AdSense domain

These are related jobs, not identical fields.

You do not solve SEO duplicates by creating two AdSense Sites rows for www and apex. You solve them with DNS + redirects so one host wins, then verify the domain AdSense lists.

Practical pattern for a typical indie blog:

1. Choose public host (many sites pick apex or www—either is fine if consistent)
2. 301 the other host and HTTP → HTTPS
3. Add example.com (or the domain form Sites accepts)
4. Place verification / ad code so ownership checks see the live host users hit
5. Continue with verify → review on the add new site guide

If Privacy & messaging needs different behavior on www vs apex, Help says publish to the more specific subsite only when you want different behavior; otherwise publish on the parent and let inheritance work. That is messaging config—not a reason to invent a second Sites application for the same blog.

True subdomains and host partners

Custom domain subdomains (blog.example.com)

For ordinary example.com properties, do not plan your monetization architecture around adding blog.example.com as its own Sites line. Help marks that pattern invalid for signup URL entry and moved Sites away from managing belonging-subdomains separately.

If content lives on a subdomain for historical reasons, your options are architectural (move content under the main domain, or treat monetization under the parent domain strategy)—not “file a second AdSense application for every subdomain.” Confirm serving and ads.txt placement against the domain you actually have in Ready status.

Host partners and public-suffix hosts

Different rules apply when the hostname is the product host:

• Blogger-style something.blogspot.com appears in Help’s valid examples
• Add through the host partner path when AdSense says Go to… / add from the host
• YouTube payments go through YouTube Studio, not a fake custom subdomain

Connected sites vs account still applies: the account can be approved while a new partner site waits on its own review.

Scenario map

Mistakes that waste a Sites review

Pasting a full article URL. Paths and query strings are invalid per URL Help.

Adding www. as if it were a different product. Fix redirects; add the domain once.

Creating a subdomain Sites row to “speed approval.” Custom-domain subdomains are the wrong lever; you risk invalid entry or outdated mental models from old screenshots.

Skipping DNS redirects. AdSense can list a domain while Search still sees soft duplicates—clean that with the one host URL checklist.

Removing the site and re-adding weekly. Connected-sites guidance warns resubmits can delay checks. Fix hostname/DNS first; then verify once.

Mixing first-apply anxiety with hostname typing. Use the approval checklist before first apply; use this page when the account is already in and you are choosing the string for Sites.

FAQ

www or non-www in the Sites box?

Enter the standard domain AdSense accepts; keep one public host with redirects. Do not treat www and apex as two applications.

Can I add a subdomain on my custom domain?

Help’s invalid list and site-management changes push you away from separate subdomain Sites rows for belonging subdomains. Partner/public-suffix hosts are the exception pattern.

Is this the add-site how-to?

No—hostname strategy only. Verify/review steps live on the add-new-site owner.

Blogger different?

Yes—partner hostname and host flow.

Do HTTPS and slash rules matter?

For SEO host consistency, yes—see the one-host URL post. AdSense still wants a clean domain entry.

Does root cover www for serving?

Sites is domain-centric; www is often a subsite for messaging. Confirm live Help/UI rather than forum myths.

Wrong hostname already submitted?

Stabilize redirects, keep a valid domain row, finish verification—avoid thrash remove/re-add.

Official Help?

URL entry examples, site management changes, add a new site, site management, connect your site, and sites/subsites messaging Help.

Pick the string, then verify

Hostname strategy is boring on purpose: one public host, one AdSense domain row for a normal custom site, partner flows when you are actually on a partner host. After the string is correct, leave this page and run Site-Then-Verify—add, verify ownership, request review, wait for Ready—while connected sites vs account keeps the layers straight.