Unknown Site in Your AdSense Report? What a Cloned Site Means

By Idea to Traffic Editorial Team · Published October 30, 2026 · Last updated October 30, 2026

You open AdSense, filter a report by site, and there it is: a domain you have never owned. Sometimes it is an unrelated shop. Sometimes it is a page-for-page copy of your own site, logo and all. The first reaction is panic about your account. The good news is that, under how AdSense works today, a stranger's domain cannot earn money with your publisher ID, and it does not put your account at risk on its own. The copied content is the real problem, and that one you can act on.

Why a domain you do not own shows up in AdSense

Your AdSense ad code carries your publisher ID, which looks like ca-pub-1234567890123456. Any page that loads that code sends ad requests tagged with your ID. When someone copies your HTML wholesale, scrapes your pages with a tool, or runs a proxy that mirrors your site live on their own domain, your ad code comes along for the ride. Google sees ad requests with your ID coming from a hostname it has not seen before, and that hostname starts appearing in your data.

There are three common causes, roughly in order of how often they happen:

• A scraper or cloned copy. Someone saved your pages and republished them on a new domain, often to collect search traffic or to sell the domain later. They did not bother to strip your ad code.
• A live mirror or proxy. The other domain fetches your pages in real time and serves them under its own name. These copies update when you update, which is the easiest way to spot them.
• A harmless leftover. A translation proxy, a web archive, a staging copy you forgot about, or a developer who used your site as a template. These usually show tiny numbers.

Can that site earn money or get your account banned?

Google's AdSense site management help page is direct about this: you can only serve ads on a site after it has passed review and shows a Ready status in your account, and Google says this means other publishers cannot maliciously use your ad code on other sites. A domain you never added, never verified and never got approved will not have Ready status, so ad requests from it are not filled. No ads show, no money moves, and the clicks that might happen there are not clicks on your ads.

That matters for two reasons. First, the copy is not stealing ad revenue from you through your own code. Second, because no ads serve there, the copy is not a realistic source of invalid traffic on your account. In older years, before site approval existed, publishers worried that a hostile copy could generate fake clicks on their ad units. With the Ready requirement in place, that path is closed.

The status names you will see on the Sites page are Requires review, Needs attention, Getting ready and Ready. The only status that serves ads is Ready.

What to check in AdSense today (10 minutes)

1. Sign in to AdSense and click Sites. Look at every domain in the list. Your own domains should be Ready. If the strange domain appears here, it should not be Ready.
2. If the strange domain is in the list, do not click to request review for it. A review request is you asking Google to approve that site under your account. Leave it alone or remove it if the option is offered.
3. Check the ads.txt column for your real domains. You want Authorized. Open https://yourdomain.com/ads.txt in a browser and confirm it contains your line, which looks like google.com, pub-1234567890123456, DIRECT, f08c47fec0942fa0. Google recommends ads.txt specifically to keep your inventory from being sold through accounts you do not own.
4. Run a report for the last 28 days, broken down by site. Note the impressions and earnings for the strange domain. If earnings show zero, that confirms ads are not filling there. Screenshot this; it is useful if you contact AdSense support or file a complaint later.

Find out what kind of copy it is

Before you file anything, spend five minutes learning what you are dealing with. Open the strange domain in a private browser window and compare it to your site.

• Is it live? Publish a small, unique change on one of your pages, for example a sentence with a made-up word like quorbelsnap. Wait a few minutes and load the same page on the copy. If the word appears there, it is a live proxy, not a one-time scrape.
• Where is it hosted? Run dig +short copydomain.com to get its IP address, then curl -s https://rdap.org/domain/copydomain.com to see the registrar and, often, an abuse contact. If the IP belongs to Cloudflare, the real host is hidden, but Cloudflare accepts abuse reports at abuse.cloudflare.com and forwards them to the hosting provider.
• Is Google indexing it? Search Google for site:copydomain.com. Then search for a unique sentence from one of your posts in quotes. If the copy ranks for your sentence and you do not, that is the case that needs action first.
• Does it point back to you? View the copy's source and search for rel="canonical". If your pages use absolute canonical URLs (https://yourdomain.com/page, not /page), a lazy scraper often keeps them, which tells Google your page is the original. If the copy rewrote them to its own domain, it was done on purpose.

If you want a quick read on whether your own pages have the basics that help Google pick the original, like self-referencing canonical tags, a working sitemap and indexable pages, the free site checker covers those in one pass.

How to get the copy taken down

AdSense is not the place to fix copied content. Search and hosting are. Work through these in order and stop when the problem is gone.

1. Copyright removal from Google Search. Google accepts copyright removal requests for Search results through its legal help forms. You list the copy's URLs and the matching original URLs on your site. When a request is accepted, those URLs are removed from Google's results. This is the single most effective step because the copy loses the search traffic it was built to collect. Send one request per batch of matching pages and keep a record of what you sent.
2. Abuse report to the host or proxy provider. Use the abuse contact from the RDAP lookup, or the Cloudflare abuse form if the IP is Cloudflare's. Include your original URLs, the copy's URLs and the date your content was first published. Hosts act faster on clear, specific reports.
3. Block a live proxy at your end. If the copy fetches your pages live, it has to request them from your server. On Cloudflare, open your domain's Security settings and add a WAF custom rule that blocks requests from the proxy's IP range once you have found it in your logs. You can also turn on Hotlink Protection (search the dashboard for it; Cloudflare has moved it between menus) so the copy cannot pull your images.
4. Do not disavow, do not panic-edit. A copy does not need a disavow file, and rewriting your own pages to make them different from the copy can hurt your rankings more than the copy does.

Protect your site going forward

You cannot stop every scraper, but you can make copies less useful and easier to spot:

• Use absolute, self-referencing canonical tags on every page.
• Keep an XML sitemap submitted in Search Console so Google discovers your pages first, ideally within hours of publishing.
• Keep ads.txt current on every domain you run ads on, and recheck it whenever you add an ad network.
• Once a month, filter your AdSense reports by site and search Google for one quoted sentence from your newest post. Five minutes a month catches most copies early.

A strange domain in your AdSense report looks alarming, but the money side is protected by the Ready requirement. Spend your energy on the search side: confirm your original is indexed, file the copyright request if the copy ranks, and move on.

Where this question came from

• r/Adsense: Cloned Site (unknown domains in AdSense reports)
• Google AdSense Help: AdSense site management
• Google: Search removals due to copyright infringement FAQs

Questions about cloned sites in AdSense reports