Disclaimer
Last updated 5 November 2026
In short
This summary isn't part of the policy.
- pubsleuth isn't affiliated with, endorsed by or sponsored by Google, Amazon, or any ad network or affiliate program it reports on.
- Which IDs, networks and programs a site uses is found in public evidence.
- Traffic and revenue figures are estimates and can be wrong by a wide margin.
- Listings show what we found when we last checked a site, which may have changed since.
- Nothing on pubsleuth is financial, investment or legal advice; decisions you make with it are yours.
- The terms of service set out our liability; this page restates what they and our pages already say.
This page sets out in one place what our terms of service and our pages say about the data. The terms are the binding text.
pubsleuth is a research tool that shows how websites make money. Some of what it shows is found: the evidence is there in public for anyone to check. Some of it is estimated, and an estimate can be a long way off. Knowing which is which is most of what you need to use it well.
1. No affiliation
pubsleuth is not affiliated with, endorsed by or sponsored by Google, Amazon, or any ad network or affiliate program it reports on. AdSense and Google are trademarks of Google LLC. Ad network and affiliate program names and logos are trademarks of their owners. We show them only to identify the services a site uses (what is often called nominative fair use), and showing them does not imply any affiliation or endorsement.
If you own a name, logo or site shown here and want it removed, write to hello@pubsleuth.com.
The same goes for the websites we list. A site's name, and the small icon we show beside it so you can recognise it at a glance, belong to that site. Seeing a site, network or program on pubsleuth doesn't mean it works with us, approves of us or knows we exist.
2. The data and its limits
The data is provided “as is”. It comes from public sources: what websites and ad networks publish, and public popularity data. Traffic and revenue figures are estimates from public signals and can be wrong by a wide margin: revenue is shown as a range, and visits from our model carry a tilde (~). Listings reflect what we found when we last checked a site.
The index will also miss sites, and some of the sites it holds will have changed since they were last checked. Treat any single row as a lead to verify, not as a fact to quote.
3. What is found and what is estimated
Which sites carry which publisher IDs, which ad networks they run and which affiliate programs they link to are findings. The evidence is in the page code or in public files such as ads.txt and sellers.json, and the index records how each finding was confirmed.
Traffic and revenue are different. They are estimates, and they can be wrong by a wide margin for any one site: revenue is shown as a range, and visits from our model carry a tilde (~). Use them to compare sites and niches against each other, which they do well, rather than to state what a particular site earned. For affiliate sites the revenue band is deliberately rough and is meant only to rank sites against each other.
| What you see | Kind | Where it comes from |
|---|---|---|
| Publisher ID on a site | Found | The site's own page code, or Google's sellers.json naming the site |
| Ad network on a site | Found | The network's line in the site's ads.txt, its tag on the page, or its sellers.json |
| Affiliate program on a site | Found | Links on the site's pages and where they lead |
| Monthly visits | Measured or estimated | Public rankings and measured panels where they exist; our own model otherwise, marked with a tilde |
| Revenue and page RPM | Estimated | Worked out from visits, pages per visit and typical page RPM for the niche and audience country |
A finding is still only as strong as its evidence, which is why the strength is shown. A site counts as verified on an ad network when its own ads.txt carries the network's direct line or its pages load the network's tag; a site that only appears in the network's sellers.json is shown as listed, not verified. Affiliate sites are marked confirmed, likely or candidate by the same logic. Where the tool is unsure, for example an ads.txt line that doesn't by itself tie a site to an account, it says so, and it leaves the ambiguous cases out rather than guess.
4. Why an estimate can be wrong
A revenue estimate is a chain of other estimates, and each link can be off:
- Visits. Public rankings are coarse, especially for smaller sites, and panels measure a sample of people, not everyone. Where neither exists, the figure comes from our own model, which is why it carries a tilde.
- Pages per visit. A recipe reader may look at one page and leave; a forum reader may look at twenty. A typical figure can be far from a particular site's.
- Page RPM. What a thousand page views earn depends on the niche and on where the visitors are. We use a typical figure for the site's niche and audience country, but one site can earn much more or much less than its niche because of its ad layout, how many ads it shows, or the season.
Multiply three numbers that are each a little off, and the result can be a lot off. That is why revenue is shown with a low and a high end instead of a single figure.
5. Reading a revenue range: an example
The figures here are made up to show the reasoning. Say you are looking at a site you might buy, and pubsleuth shows its estimated AdSense revenue as $1,500 to $4,500 a month.
Read that as: on what public signals show, a site of this size, in this niche, with this audience, would usually earn somewhere in that band. It isn't a statement of what this site earned last month. The revenue filter and sort use the middle of the range, $3,000 here, which is fine for ranking it against other sites. It isn't a number to put in a valuation.
A sensible next step: compare it with two or three similar sites, check whether it is actually serving ads (see below), and if you go ahead, ask the seller for their own AdSense reports and analytics. If the seller says the site earns $9,000 a month, the range doesn't prove them wrong; it tells you what to ask about. If a site shows zero revenue because it isn't serving ads, the index shows what the same traffic could earn instead. That is a what-if, not a forecast.
6. What “serving ads” means
Carrying AdSense code doesn't mean ads are shown. pubsleuth checks the publisher ID against Google's sellers.json, the public file in which Google lists the sellers it pays. If no ID on the page is listed there, the code almost never gets an ad, so the site is marked as not serving and its estimated revenue is zero.
The check has limits. It tells you whether the account is one Google lists, not how many ads the site shows or how much they earn. A site can also change between our checks. And sellers.json can mark a seller confidential, without a name or a domain; we don't show the names of individual account holders from these files, only company names.
7. A shared ID is a clue, not proof
Two sites on the same AdSense publisher ID are run through the same AdSense account, which usually means the same publisher. Usually is not always. An agency may run many clients' sites on one account, and a theme can copy an analytics ID onto thousands of unrelated sites. We ignore IDs shared by very many sites as templates, ignore the well-known placeholder IDs copied from tutorials, and show how each site was confirmed, so you can judge each link yourself.
An ads.txt line alone never ties a site to an AdSense account in our lookups, because ad networks list their own accounts in the ads.txt files of the sites they serve.
8. How fresh the data is
A crawler reads the public files and pages, and each service's findings reach the website once a day. Each load is dated, and the home page says on what date its counts were taken. Even so, what you see for a site is what we found when we last checked it, so a site that joined a network yesterday, or dropped AdSense last week, may not show it yet.
9. What pubsleuth doesn't hold
- No email addresses, phone numbers or other contact details, and no outreach, emailing or scraping tools.
- No Domain Authority or other third-party SEO scores.
- No keyword search volumes or rank tracking.
If you need those, other tools provide them. What pubsleuth shows instead is how a site makes money and roughly how much.
10. Not advice
Nothing in the service is financial, investment or legal advice. Decisions you make with it, such as buying a website or choosing an ad network, are yours.
If a decision matters, treat the estimate as a place to start and check the site's own numbers. If you are paying real money for a site, or signing a contract with a network, get the seller's or the network's own figures in writing, and take professional advice where you would normally need it.
11. Links to other websites
pubsleuth links to the sites it lists, and to public files such as a site's ads.txt, so that you can check the evidence yourself. We don't run those sites. What they show, and what they do with your visit, is up to their owners and their own policies.
12. Availability
The data is provided “as is”, and we don't promise that the service will always be available or free of errors. As the terms say, we are not responsible for delays or failures caused by events outside our reasonable control, such as an outage at our hosting or network providers.
13. Liability
Our liability is set out in the terms of service, which limit it to the extent the law allows, without limiting rights you have as a consumer.
14. Telling us about an error
If something on pubsleuth is wrong, for example a site tied to the wrong publisher ID, a network a site left long ago, or a site you run that we describe wrongly, tell us through the contact page or at hello@pubsleuth.com. Give us the page and what the problem is. We review every complaint and reply within 30 days, as the terms say.
Who we are and how to reach us
pubsleuth is operated by Advanced Micro Tools, India (“we”, “us”). Questions about this page: hello@pubsleuth.com