AdSense With Multiple Sites: Why Extra Accounts Get Disabled and What Google Allows

Picture a publisher running AdSense with multiple sites — seven niche ones. A recipe blog, a home improvement guide, a personal finance site, four more. Different writers on each. At some point she decided every site deserved its own AdSense account: cleaner books, less exposure if one site had a bad month, easier to sell later.

Then one morning every account is disabled at once.

That publisher is a composite, not a customer story. But the shape of it turns up again and again in publisher forums, and the usual post-mortem gets it wrong. People conclude the mistake was letting Google see the accounts were connected. The actual mistake came earlier. She was running seven accounts on a program built around one.

So this post covers four things: what AdSense allows for multi-site publishers and agencies, how platforms connect accounts (and why they bother), what it really costs to try to get around that, and the official route if an account has already been disabled. We make an antidetect browser, so we'll also be specific about where one fits for publishers. And where it doesn't.

Short version: one account, as many sites as you like.

AdSense is designed around a single account per publisher. You don't open a new account for each site. You add each site on the Sites page of the account you already have, and Google reviews it before ads serve there. Multiple sites on one account — seven of them, or seventy — is the normal, supported case.

Inside that one account you still get plenty of separation:

Per-site reporting. Reports break down by site, so you can see which property earns what.
Custom and URL channels for tracking specific ad units or sections across sites.
Per-site ad settings, including Auto ads, configured site by site.
User management. You can invite other people to the account with Administrator or Standard user access, so a site manager or your accountant gets in with a Google login of their own instead of yours. One catch: AdSense requires that login not already be linked to another active or closed AdSense account, so check Google's current help article on adding users before you invite someone who runs AdSense themselves.

Edge cases do exist. Separate legal entities, a company that bought another publisher, business versus individual accounts. The rules for those are specific and Google changes them, so read the current AdSense Help Center articles on multiple accounts and account ownership before you act. Don't take a forum post's word for it. Ours included.

Which is the part that irritates me. The edge cases are what people actually need, and they're the rules most likely to have moved since whatever article they're reading went up. This one included.

How Platforms Connect Accounts (and Why They Bother)

Google doesn't publish exactly how it decides two AdSense accounts belong to the same publisher, and we're not going to pretend we know. But the general toolkit large platforms use is no secret, and it helps to understand it.

Account data. Names, addresses, tax details, payment information, phone numbers, the sites claimed. A lot of connections are made right here, before anything technical comes into it.

Network signals. IP addresses and the networks behind them. Weak on their own (plenty of strangers share an IP at a coworking space or on a mobile network), but useful in combination.

Browser and device signals. This is browser fingerprinting. A site can ask your browser to draw a hidden canvas image, and the exact pixels depend on your GPU, driver, operating system and font rendering. It can read the WebGL renderer string, which names your graphics hardware. It can check which fonts are installed, process a short audio sample, and read User-Agent Client Hints. One signal says little. Together they describe a machine closely enough to recognise it across sessions, and clearing cookies or opening an incognito window doesn't change them. Our comparison of incognito vs separate profiles goes deeper, as do the posts on WebGL and GPU detection and audio and font fingerprinting.

Behaviour. When and how accounts are used, and whether traffic across sites looks alike. The dullest signal on the list, and I'd bet it's the one that does the most work.

Why does Google care this much? Because advertisers pay for real people seeing and clicking real ads. Invalid traffic, meaning bots, click schemes and publishers clicking their own ads, takes money straight out of their budgets. If a publisher disabled for that could reopen under a new name the next morning, enforcement would mean nothing. So ad networks connect accounts, and they act on the whole group when one is caught. (If you want to see how this looks from the detection side, here's how bot detection works at the fingerprint level.)

Here's the take most "AdSense multiple accounts" advice gets backwards. It treats Google's ability to connect accounts as the problem. It isn't. The rule is about how many accounts you hold, not whether Google can see them. An extra account kept perfectly hidden is still an extra account, and every hour spent hiding it is an hour spent on a terms violation that does nothing to protect your revenue.

What It Costs to Work Around Enforcement

Some publishers respond to a disabled account by opening another one under different details. We're not going to describe how people try that. It breaks the AdSense terms, and it usually makes the situation worse. Here's what's actually at stake.

The account and any future one. Google's help pages say a publisher whose account has been disabled generally isn't eligible to take part in AdSense again. A new account opened after that is a violation in its own right, and when it's connected to the old one, it's disabled too. Usually for good.
Unpaid earnings. When an account is disabled for invalid traffic, Google can refund affected earnings to advertisers instead of paying them out. Every month a workaround runs is more revenue that may never reach you.
Resale value. Buyers of content sites look at monetisation history. A site with disabled accounts in its past is a harder sale and a weaker price.
Other people's money. For an agency, any workaround on a client's account gambles the client's revenue without their consent. That's a contract problem on top of a policy one.
Your options elsewhere. Other ad networks run their own invalid-traffic checks and tend to look at a publisher's history. A pattern of disabled accounts follows you.

If Your Account Has Already Been Disabled

Use the official route. It's slow and there's no guarantee, but it's the only path that can actually restore the account.

Read the notice. Policy violations and invalid traffic are separate cases with separate processes. The email and the Policy center in your account tell you which one you're facing.
For policy violations, fix the flagged pages or sites, then request a review from the Policy center.
For invalid traffic, Google provides an appeal form for disabled accounts. Before you file, find the source. Check your analytics for referral spikes, traffic you paid for, auto-refreshing pages, ad units placed right next to buttons or menus, and anyone with access to your sites who might have clicked ads. Say what you found and what you changed.
Write it carefully the first time. Specific and factual beats long and emotional. Don't paste a template.
Don't open another account while you wait. It turns a case Google can review into a clear violation.

Step four is the one people skip, and it decides the case. A reviewer reading "I have no idea how this happened, please help" has nothing to act on. One reading "a referral spike from one domain sent most of last month's sessions, I blocked it and moved the ad unit away from the menu" has something to check.

If the appeal fails, the honest options are other ad networks that accept you on their own terms, affiliate programs, direct-sold sponsorships, or subscriptions. None of them involve a new AdSense account.

Running Multiple Sites the Legitimate Way

Back to our seven-site publisher. Here's her setup done properly:

Every site in one AdSense account. Each one added and approved on the Sites page. The ads.txt file on each domain lists the same publisher ID.

Separation through reporting, not accounts. Per-site reports and channels give each brand its own revenue line. Per-site profit and loss comes from those reports and her own bookkeeping.

People, not passwords. Writers and managers who need access are invited as users at the right level. Nobody logs in as her.

Selling a site. She removes it from her account, the buyer adds it to theirs and swaps the ads.txt entry for their own publisher ID. A clean handover, and nobody needed a second account.

Honestly, I don't think the seven-account plan was ever about Google. It was about bookkeeping — wanting each brand's earnings in its own tidy column. Which is a spreadsheet problem. Solving it with seven ad accounts is like buying seven cars to avoid keeping a mileage log.

Traffic analytics across the whole portfolio. Many publishers want one place to see visitors and errors for every property, separate from ad revenue. A tool like JustAnalytics can sit across all the sites for that. It changes nothing about AdSense's rules. It just keeps the reporting in one place.

Is one account less flexible than seven? A little. But that flexibility was never on offer.

For Agencies and Multi-Client Operators

Agencies managing monetisation for clients have a simple rule to build on: the client owns the account. The client invites your staff as users. AdSense won't link one Google Account to more than one AdSense account, so a staffer working on several clients typically needs a separate Google login for each one. Check Google's current user-access help before you set this up. You never open an AdSense account in the agency's name for a client's site.

If you manage ad inventory on behalf of other publishers at real scale, Google Ad Manager's Multiple Customer Management (MCM) program is the official structure for it. It has its own eligibility requirements and application process, so check the Ad Manager help pages for the current criteria.

What trips agencies up day to day usually isn't the policy. It's logistics. One person juggling a dozen client Google logins in a single browser will eventually change a setting in the wrong account. Sessions overlap. Someone gets logged out mid-task. Which client is this tab again? (Every agency has a story about that last one.)

Where an Antidetect Browser Fits, and Where It Doesn't

The "doesn't" first. An antidetect browser doesn't make a second AdSense account acceptable. If the goal is to keep accounts hidden from Google, no browser fixes that, because it's a terms problem, not a tooling problem. That isn't a use we want, and it isn't what JustBrowser is for.

Awkward paragraph to write when the browser is the thing we sell, I know. Writing it still beats taking someone's money for a policy fix we can't deliver.

Where it does help publishers and agencies:

Separate sessions per client. Each client gets its own browser profile with its own cookies and storage, so a staffer working in Client A's account can't accidentally act in Client B's. This is about not making mistakes in accounts you're authorised to use.

Shared access without shared passwords. JustBrowser team seats are free, and you can share a profile with view-only or launch permission. A seat can run the profiles shared with it but can't create its own or use the API. So a contractor gets exactly what you shared, and you remove access by unsharing it. We cover more of this in the teams and agencies FAQ.

Seeing your sites the way visitors in other countries see them. Consent messages for EU visitors, regional layouts, how a page renders on a Windows laptop versus a Mac. A profile with a matching proxy, timezone and locale shows you what a reader there gets. One firm rule: never click your own ads, from any profile. To review which ads are serving on your pages, use the Ad review center inside AdSense. Our ad verification workflow shows how verification teams set up this kind of geo check, and the same no-clicking rule applies.

Automation for QA. A local REST API plus CDP lets you drive profiles from Playwright, Puppeteer or Selenium, which is handy for scripted screenshot checks across a whole portfolio after a template change.

Under the hood: a custom Chromium engine with native C++ integration, patched on every upstream release, with 40+ identity parameters per profile. It runs on Windows x64 and macOS (Apple Silicon). No Linux build, and none coming that anyone here can point to, so if your portfolio QA lives on a box in a data centre this isn't your tool. Proxies aren't included either — you bring your own. (I've buried that line at the bottom of enough posts to admit it deserves a sentence of its own.)

Frequently Asked Questions

Generally, no. AdSense is designed around one account per publisher, and you add every site you own to that account. There are specific rules for edge cases such as separate legal entities or acquired businesses, and Google updates them, so check the current AdSense Help Center articles on multiple accounts before you act.

Yes. That's the normal, supported setup. Add each site on the Sites page of your account, wait for Google to review it, and use per-site reports and channels to see what each property earns.

Why were all my sites disabled at the same time?

Google can act on a single page or site, but disabling an account (for invalid traffic, for example) applies to the whole account. If every site sits in one account, a disabled account stops ads on all of them. If you held several accounts that Google connected to the same publisher, the outcome is the same, because holding the extra accounts was itself against the rules.

That isn't a use we support, and it wouldn't fix the real problem. The rule is about how many accounts you hold, not whether Google can see them, so a hidden second account is still a terms violation. Use browser profiles for legitimate separation: keeping client sessions apart, sharing access with your team, and checking how your sites render in other countries.

Read the notice first, because policy violations and invalid traffic follow different processes. For policy issues, fix the flagged pages and request a review from the Policy center. For invalid traffic, use Google's appeal form for disabled accounts and explain what caused the traffic and what you changed. Don't open a new account while you wait.

Is it safe to look at my own site with ads on it?

Viewing your own pages is normal. Clicking your own ads is not, from any browser or device. To check which ads are serving on your sites, use the Ad review center inside AdSense rather than repeatedly loading pages yourself.

Try JustBrowser

Native Chromium antidetect browser with native C++ integration, not extension-based. Separate profiles with their own cookies and storage, team sharing without shared passwords, and a local REST API + CDP for Playwright, Puppeteer and Selenium.

$9.99/month or $99.99/year. 7-day free trial, card required — cancel any time in the seven days and you are not charged. Unlimited profiles, unlimited cloud sync, unlimited team seats.

Get started → · How it differs from Multilogin / GoLogin / AdsPower