Adding a site to AdSense: root domain, subdomain or subdirectory?
Key takeaways
- Ads only appear on sites that are in your AdSense sites list and have passed review with a "Ready" status; ad code placed on a site not in the list does not show ads.
- AdSense verifies ownership through the ad code, the ads.txt file or a meta tag, and the ads.txt file must sit in the root directory of the domain.
- Google's AdSense crawler treats example.com and www.example.com as separate URLs, but not example.com and example.com/#anchor.
- Blogger and other host partner sites are added through the host partner, and a site on a platform-owned domain such as example.blogspot.com cannot be unlinked from the platform.
- Platform domains such as github.io, netlify.app, blogspot.com and appspot.com are on the Public Suffix List, which makes each customer subdomain behave like its own registrable domain.

In AdSense, a “site” is what you add under “Sites” and get reviewed; ads only serve on sites with a “Ready” status. In practice you add the domain your content lives on (one canonical version, with or without www), and subdirectories are covered by that domain. Blogger and other host partner sites are added through the host. Hosted subdomains on public-suffix platforms behave like separate domains.
What counts as a site in AdSense?
Google’s site management page sets the frame:
- You must add a site to your sites list before showing ads on it or setting site-level blocking rules.
- AdSense verifies you own it “either via your ad code, your ads.txt file, or a meta tag on your site.”
- “You can only serve ads on a site after it has passed our review and it has a ‘Ready’ status.”
- Google’s new-site page adds: “If you place your ad code on a site that’s not in your sites list, ads won’t appear on that site.”
Two of the ownership methods are domain-level by nature: ads.txt lives “in your site’s root directory”, and the review looks at “your entire site”. That is why the choice between root domain, subdomain and subdirectory matters.
Root domain, subdomain or subdirectory: which applies to you?
| Your setup | Example | How it relates to AdSense |
|---|---|---|
| Root domain | example.com |
The standard case: add it, verify, get reviewed |
www variant |
www.example.com |
Same site for visitors, but the crawler fetches it separately; choose one canonical host and redirect the other |
| Subdirectory | example.com/blog/ |
Shares the domain root, so it shares ads.txt and is part of the domain’s review |
| Your own subdomain | blog.example.com |
A separate hostname with its own pages; ads.txt questions are handled with the parent domain’s file (see below) |
| Host partner site | name.blogspot.com |
Added through the host partner (Blogger), not through “+New site” |
| Platform subdomain | name.github.io, name.netlify.app |
On the Public Suffix List, so it behaves like its own domain; a custom domain is the cleaner option |
The www question
Google’s crawler documentation is precise: “Our crawler will access site.com and www.site.com separately. However, our crawler won’t count site.com and site.com/#anchor separately.” Practical rules:
- Decide on one canonical host.
- Redirect the other with a single permanent redirect.
- Add the canonical host to AdSense.
- Serve
ads.txtat the root of the canonical host, and make sure the other host redirects to it rather than returning an error.
Subdirectories
A path like /blog/ or /fr/ is not a separate origin: it has no root of its own, cannot hold its own ads.txt, and shares the review with everything else on the domain. Google’s unapproved-account page notes the review “may review all pages of your site, not just the sign-up URL”. If the main domain hosts content that would fail the review, isolating your content in a subdirectory does not shield it.
If two parts of a domain are genuinely different projects (for example a shop and a magazine), that is a business decision, not an AdSense trick: both parts are still on one domain and one review.
Subdomains you own
A subdomain such as blog.example.com is a different hostname with its own pages and its own robots.txt. For ads.txt, the IAB Tech Lab ads.txt specification added a SUBDOMAIN variable in August 2017 for declaring subdomains in the root domain’s file; the details and how Google’s crawler reads them are in ads.txt and subdomains. When you add a hostname, read what the “+New site” form accepts and the status it shows afterwards: the Sites page is the authority on how AdSense treats that entry for your account.
Hosted platforms: Blogger, YouTube and platform partners
Blogger and other host partners
Google’s add-site page says: “If your site is on one of our host partner sites (like Blogger), you’ll need to go to your host partner to add your site to AdSense.” The eligibility page says the same and adds that YouTube creators sign up for AdSense for YouTube in YouTube Studio.
Platform partners and shared traffic
Some platforms are AdSense platform partners. Google treats your ad requests as “shared traffic” when your ad code contains the data-ad-host parameter or your page has the google-adsense-platform-account meta tag. The platform may then control ad settings and ads.txt, can view policy violations, and can take a share of revenue.
Google also notes: “If your site is part of a platform-owned domain (e.g,. example.blogspot.com), then you can’t unlink your site.” On your own domain, you can unlink by removing the data-ad-host parameter and the platform meta tag, then waiting for a recrawl or removing and re-adding the site.
Free platform subdomains (github.io, netlify.app and similar)
The Public Suffix List, “an initiative of Mozilla” maintained as a community resource and originally created for browser makers, includes github.io, netlify.app, vercel.app, pages.dev, web.app, firebaseapp.com, appspot.com and blogspot.com, among many others. A public suffix is one under which people can register names directly, so a name under one of these suffixes is treated by software that uses the list (browsers, for cookies and site grouping) as its own site: you.netlify.app and someone-else.netlify.app are separate sites, not subdomains of one site you control.
Two consequences for AdSense:
- You control the root of your own platform subdomain (for example, the root of
you.netlify.app), so you can usually serve ads.txt there. Project sites under a path (such asowner.github.io/project) do not control the root. - Your site is tied to the platform’s domain. If you later move to a custom domain, that is a new site to add and review. Starting with a custom domain avoids repeating the process; see AdSense on static and Jamstack sites.
How do I add a new site, subdomain or domain?
- Sign in to AdSense and click “Sites”.
- Click “+New site” and enter the URL of the site.
- Click “Save”. The site appears with the status “Requires review”.
- Connect it with the AdSense code snippet, an ads.txt snippet or the meta tag, click “Verify”, then “Request review”. See how to connect a site.
Google says the checks “usually take a few days, but in some cases can take 2-4 weeks.” The meaning of each status is in AdSense site statuses explained.
Common mistakes
- Adding the non-canonical host (for example
wwwwhen the site redirects to the bare domain). - Expecting a new subdirectory to get its own approval. It is part of the domain.
- Moving a site to a new domain and copying the ad code without adding the domain. Google says to add the new site first, before placing the ad code; ads won’t appear on sites missing from the list.
- Placing ads.txt in a subdirectory or only on a subdomain without checking how the root domain’s file declares it.
- Applying with a Blogger blog through “+New site” instead of through Blogger.
- Hosting low-quality content elsewhere on the same domain, assuming the reviewer only checks the section you care about.
Frequently asked questions
Do I need to add www and non-www versions separately?
Pick one canonical version and redirect the other to it with a single permanent redirect. Google's crawler page says the AdSense crawler accesses example.com and www.example.com separately, so a missing redirect or a version that does not resolve can create crawl and verification problems. Add the canonical domain to AdSense and serve ads.txt at its root.
Can I add example.com/blog as a separate AdSense site?
A subdirectory shares its domain's root, so it shares the ads.txt location and the domain-level ownership checks AdSense uses. In practice you add the domain and place the code on the subdirectory's pages. Remember that the review can cover all pages on the domain, so the rest of the domain must also comply with the policies.
Can I put ads on a Blogger blog with my own AdSense account?
Yes, but through Blogger. Google says sites on host partners like Blogger are added to AdSense from the host partner, not from the Sites page. A blogspot.com address is a platform-owned domain, which Google says cannot be unlinked from the platform; you can only remove it from AdSense.
What happens if my ad code appears on a domain I never added?
No ads are shown there. Google states that if you place ad code on a site that is not in your sites list, ads won't appear, and that you can only serve ads on a site that passed review with a "Ready" status. Google presents this as a protection: other publishers cannot use your code on their sites.
Sources
- Add a new site to your AdSense sites list · Google AdSense Help
- AdSense site management · Google AdSense Help
- About the AdSense ads crawler · Google AdSense Help
- Your site is linked to a platform partner · Google AdSense Help
- Show ads on a new site · Google AdSense Help
- Public Suffix List · Public Suffix List (a Mozilla initiative)
Related guides
- ads.txt and subdomains: which file the crawler reads and when to use subdomain=
Which ads.txt file governs a subdomain, when you need subdomain= in the root file, and the configurations that silently make a subdomain Unauthorized in AdSense.
- How to connect your site to AdSense: the three verification methods compared
Compare the three AdSense site verification methods (code snippet, ads.txt, meta tag), copy the exact snippets, and fix "code missing" or "unreachable" errors.
- Getting a static or Jamstack site approved for AdSense
Getting a static or Jamstack site approved for AdSense: where the code and ads.txt go, why platform subdomains and previews trip reviews, and what stays the same.
- AdSense site statuses explained: what each status on the Sites page means and what to do
What "Requires review", "Getting ready", "Needs attention" and "Ready" mean on the AdSense Sites page, plus the ads.txt column, and the exact next step for each.