One AdSense account can host an unlimited number of sites, but the workflow for adding the second site is not the same as the first. The per-site review, the verification step, and the payment-vs-policy split surprise almost everyone the first time. This article walks through the real flow as it works in June 2026, the typical timeline, and the limits that matter once you scale past 3 properties.
TL;DR
- One AdSense account, unlimited sites. Google’s policy is one account per publisher; never open a second account to “keep things separate.”
- Each new site goes through its own review (status moves from Requires review to Ready). It usually takes a few days, sometimes 2-4 weeks.
- Earnings are pooled: one $100 payment threshold (US), one tax form, one bank account across the whole portfolio.
- Policy is scoped per site first. One flagged site rarely sinks the account unless violations repeat or invalid-traffic spikes.
- The real 2026 risk is not site count: it is scaled content abuse. Networks of thin, AI-generated pages get demonetized together.
Background
AdSense is an account-level product with site-level approval. Your account is approved once, but every new domain you add goes through its own review before ads can serve on it. The earnings pool is shared across all sites (one payment threshold, one tax form, one bank account), but policy violations are scoped to the offending site first and only escalate to account-level if the same issue repeats. This split is why some publishers think their whole account is broken when really only one site is stuck.
Most ad networks share this architecture: identity-level account, asset-level review. The reason it confuses indie publishers is that the first site approval and account approval happen at the same time, so the per-site step is invisible. The second site is when the two layers separate, and the workflow looks different. Once you have run through it once, every subsequent addition follows the same pattern.
How to tell
- You already have one approved AdSense site and want to add a second, third, or tenth.
- You are about to launch a sister site and are deciding between adding it under the existing account or opening a new one.
- One of your sites was flagged but the others are fine, and you want to know whether the whole account is at risk.
- You want to consolidate revenue and tax forms across a portfolio.
Quick verdict
Run everything under one account unless a site is in a banned category (gambling, adult, weapons) or targets a sanctioned country. Per-site review is usually faster than the first account approval. Keep each site policy-clean on its own: one bad site can put the whole account on a watchlist, and a network of thin sites can take all of them down at once.
Adding a second site
- In AdSense, go to Sites then click +New site. Enter the bare domain (
example.com, nothttps://www.example.com/). - Pick a verification method (see the table below), confirm completion, click Verify, then click Request review.
- The site starts at Requires review and moves to Ready once it passes. During review, the verification stays live and the site must remain crawlable. Do not
noindexthe site or block Googlebot. - Once Ready, create ad units scoped to that site, or reuse Auto Ads if your account-level setting is on. Manual units created for site A still serve on site B; there is no per-site lockdown, the snippet just has to match a verified domain you control.
- Add the new site to
ads.txt. Each domain serves its ownads.txtat the root, with the samegoogle.com, pub-XXXXXXXXXXXXXXXX, DIRECT, f08c47fec0942fa0line.
Verification methods compared
| Method | Where it goes | Speed | Best for |
|---|---|---|---|
| AdSense code snippet | <head> on every page | Fastest, most reliable | Sites where you control the template |
ads.txt snippet | /ads.txt at domain root | Slower to pick up | CMS that blocks head edits; also required anyway |
| Meta tag | <head> of the homepage only | Moderate | When you cannot inject site-wide code |
The snippet method does double duty: it both verifies ownership and serves ads, so it is the default for most indie setups. You still need ads.txt regardless of which verification you pick, because it is what authorizes programmatic demand.
Per-site review vs account review
- Account review (first time): evaluates publisher identity, payment readiness, and the first site as a sample. This is the slow one.
- Per-site review (every subsequent site): Google states it “usually takes a few days, but in some cases can take 2-4 weeks,” and it evaluates only the new site for policy and content quality.
- Per-site review can still reject, usually for thin content, a missing privacy policy, or a domain that already had AdSense history. The rest of your account keeps earning.
- If a per-site review stalls past two weeks, the site is in a deeper manual queue. Continue publishing real content normally; do not remove the verification.
Limits that actually matter
- No hard cap on number of sites under one account. Publishers run 50+ sites under one ID without issue, as long as each site is policy-compliant.
- One payment profile and one tax form per account. Your portfolio earnings sum into a single threshold (US$100 minimum payout, paid around the 21st-26th once your balance clears it on the 20th) and a single payout.
- Country and currency are set at the account level on signup. If you move countries you cannot switch in place; you have to close the account and open a new one in the new country.
- Subdomain ads: a verified domain (
example.com) covers all its subdomains automatically. You do not need to verifyblog.example.comseparately. - Bilingual / multi-region sites: still one site if they share a domain.
example.com/en/andexample.com/zh/count as one verified property. - Invalid traffic detection runs at both account and site level. A spike on one site can temporarily limit serving across the whole account if the traffic looks artificial enough.
- Per-site reporting granularity is good: impressions, RPM, CTR, page views, and coverage per site, per ad unit, per country, per day. Export to CSV monthly for portfolio analysis.
Operating a portfolio
- Standardize the AdSense snippet placement across all sites (same template helper, same head injection). Drift between sites makes debugging slow.
- Keep
ads.txtin version control. One file per site repo, updated when you add networks. - Run a monthly portfolio review: total revenue, per-site RPM trend, any sites trending down, any policy notifications.
- Tag each site with a category (content type, audience, geography) so when one site dips, you can spot whether the dip is site-specific or category-wide.
When a portfolio gets big
- At 5 sites: manageable manually. One dashboard view per site, monthly export.
- At 10 sites: build a small internal dashboard that pulls from the AdSense Management API. Manual review starts missing patterns.
- At 25+ sites: treat the portfolio like a small product company. Quarterly OKRs per site, content roadmap, retention metrics. Skip this and most sites stagnate.
- At 50+ sites: most indie publishers consolidate or sell. Diminishing returns on author time per site.
Common mistakes
- Opening a second AdSense account “to keep books separate”. This violates policy — one person, one account. Consolidate into one.
- Adding a site that still has Google Analytics blocked or noindex on. Reviewers cannot evaluate what they cannot crawl.
- Forgetting to update
ads.txtfor the new site. Without it, programmatic demand drops and RPM craters on the new site even after approval. - Pasting the snippet only on the homepage. The snippet must be on every page that should serve ads, ideally injected by the site template.
- Running a policy-borderline site alongside compliant ones. One repeated violation can put the whole account in limited-ads mode.
FAQ
- Can I split earnings by site for accounting?: Yes. AdSense reports break revenue down per site, ad unit, and country. Export monthly CSVs and tag by site for bookkeeping.
- What if my new site gets rejected?: The rejection is site-scoped. Fix the reason (usually content or policy), wait 30 days, and resubmit that site from the Sites panel. Your existing approved sites keep earning.
- Do I need a separate ads.txt per site?: Yes. Each domain serves its own
ads.txtat/ads.txt. Same publisher ID line on each. - Can my AdSense account survive a single-site policy ban?: Usually yes, if you remove ads from the offending site within the warning window. Repeat violations on the same site, or a sudden invalid-traffic spike, can escalate to account-level action.
- Should I run a network of low-quality sites?: No. Google’s “scaled content abuse” policy (defined in 2024, heavily enforced in the March 2026 core update) targets exactly this: networks of thin, templated, AI-mass-produced pages with no human editorial review. Sites hit in that wave saw 50-80% traffic drops, and a publisher’s whole portfolio can be demonetized together. AI assistance is fine; AI slop at scale is not.
- What if I want to sell one of my sites?: Remove the site from your AdSense account before transferring ownership. The buyer must add it to their own AdSense account and re-verify. AdSense association does not transfer with the domain.
- Can I share the AdSense ID across a business partner’s site?: Only if the partner is operationally part of your business. Putting your publisher ID on a separate person’s site to “help them monetize” is account-sharing and a policy violation.
- What about Manager accounts?: AdSense Manager accounts exist for agencies and larger publishers running ads on behalf of others. For solo indie publishers managing your own sites, a single regular account is the right tool. Manager accounts add overhead without benefit at portfolio sizes under 20 sites.
- Do I need separate Search Console properties per site?: Yes. Each site has its own Search Console property. Link each to your AdSense account so the integrations (top-search-queries, page-level ad reports) light up per site.
- Will adding a new low-traffic site dilute my account?: No. Account-level signals are aggregated, but low-traffic sites neither help nor hurt the high-traffic ones in terms of policy or RPM. They just sit there earning their own slice.
- What if one site is in a different language than the rest of my portfolio?: Fine. AdSense supports the same set of languages across all sites under one account; ad demand for each language is matched per site. Earnings reporting per site still breaks out cleanly.