About pubsleuth
pubsleuth is a research tool that shows how websites make money: which AdSense accounts, ad networks and affiliate programs they use, with estimates of their traffic and revenue.
The problem: how a site makes money is public, but slow to find
Say you come across a recipe site that clearly does well, and you want to know how it earns. Nothing about that is secret. The answer is written down in public, in several places, by several parties. Finding it by hand goes something like this.
- You open the site's ads.txt file and find a long list of ad companies, each with an account number. One line starts with google.com and carries a publisher ID. That looks like an answer, but it may not be the site's own account: ad networks list their own accounts in the ads.txt files of every site they serve.
- So you view the page source and search for ca-pub-, which is how the ID appears in the AdSense script. Then you check Google's sellers.json, the file in which Google names the accounts it sells ads for, to see whether that ID is really live.
- The ads.txt also mentions a managed ad network. To know whether the site really works with it, you open that network's own sellers.json and look for the domain, then go back to the site's pages to see whether the network's tag loads.
- The reviews on the site link to shops through short links. You follow each one to see where it lands and whether it carries an affiliate tag.
- Now you want the other sites behind the same publisher ID or the same affiliate tag. There's no simple way to search the web for pages whose code carries a given ID, so this is where most people stop.
And at the end you still don't know how many people visit the site or what it might earn. That's an afternoon of detective work for one site. pubsleuth does the reading across the sites we track, applies the same rules every time, and puts the answers on one page.
Why it exists
The answers to “how does this site make money, and which other sites share its IDs?” are public, but scattered across ads.txt files, ad networks' sellers.json files and the pages of millions of sites. pubsleuth reads them and puts the answers in one place.
What it is: three products on one index
pubsleuth has three products. Each starts from a different way a website earns, and each answers its own kind of question.
AdSense Lookup, and the AdSense Index behind it
The AdSense Lookup is the front door. Paste a publisher ID, a website, an Amazon tag or an analytics ID, and it shows the sites behind it. Behind the box sits an index of AdSense sites, each described the same way: its niche and sub-niche, its type (blog, tool, news site, game portal and so on), its language, its audience countries, its monthly visits and three-month trend, its estimated revenue as a range, its page RPM, whether it is really serving ads, and the other sites on its publisher ID. The AdSense Explorer opens that index for browsing, so you can start from a question rather than an ID.
A question it answers: “This unit converter is doing well. What else does the account behind it run, in which niches, and how large are those sites?”
Network Scout
Network Scout does for ad networks what the lookup does for AdSense. It shows which sites run Mediavine, Raptive, Ezoic and the other networks we track, checked against each site's own ads.txt and page code, with the tools each site uses and when it joined or left a network. Its lookup box takes a Google Analytics or Tag Manager ID.
A question it answers: “Which travel sites joined Raptive recently, and how big are they?”
Affiliate Scout
Affiliate Scout finds the sites earning from affiliate programs such as Amazon Associates, Awin, Impact and CJ, by reading the links on their own pages. It shows the programs, merchants and products a site links to, and the other sites that carry the same affiliate tag.
A question it answers: “Which programs do kitchen-gear review sites lean on, and which other sites carry this Amazon tag?”
Who uses it, and for what
The same facts serve different jobs. These are the ones we built it for, with an honest note on where each one stops.
Competitor research
If you run a site, look it up, open the cluster of similar sites it sits in and sort by visits. You get a ranked view of your neighbours: how big the leaders are, where their readers live, roughly what each earns, who is growing and who is serving ads at all. It's research into what your competitors have published, not access to anything private. The figures are estimates, so they're for comparing, not quoting.
Niche research before you build
Before you spend a year on a site, you want to know whether the niche pays. The niche counts show how crowded it is, page RPM and the audience-country filter show what a visit is worth, and the trend shows whether the niche is rising or fading. pubsleuth isn't a keyword tool and shows no search volumes; what it shows is which topics have already supported earning sites.
Portfolio research
Many publishers run several sites under one publisher ID. The lookup shows them all, and a filter finds the accounts that run five, ten or more. A handful of sites in one niche is a focused business; dozens across unrelated niches is a different model. Seeing both is how you compare strategies rather than single sites.
Ad-network and affiliate research
Network Scout tells you which sites run which managed network, in which niches, and who joined or left. That helps if you're choosing a network, selling to publishers on one, or studying how the networks differ. Affiliate Scout shows which niches depend on which programs and which sites use several. Both look at sites and the programs they join, never at individuals.
Due diligence on a site you might buy
A seller sends you a traffic screenshot and a revenue figure. pubsleuth gives you an independent view to set beside them: the traffic trend, the audience countries, what the niche typically earns per visit, and whether the ads are really serving. It can't replace the seller's own analytics. But if the seller's figures and our estimates are far apart, that's a good reason to ask more questions.
Agencies, consultants and researchers
If you advise publishers or study the advertising business, you need the whole market, not one site at a time. The API looks up one domain, publisher ID or tag at a time from your own tools (an API plan is coming soon), and a plan's CSV download lets you take results away for your own analysis, within the monthly limits on the pricing page.
How to read what you see
Everything pubsleuth shows is one of two kinds of thing, and the difference matters more than anything else on this page.
Findings: what we saw
Which sites carry which publisher IDs, which networks they run and which affiliate programs they link to are findings. The evidence is in the page code or in a public file, and pubsleuth records how each one was confirmed. Each product has its own words for how strong the evidence is:
- AdSense: an ID is tied to a site only when the site's own page code carries it, when a browser check saw the page ask for ads with it. An ads.txt line or a sellers.json listing alone never counts, and an ad network's own ID is never a site's owner. A site whose ID isn't in sellers.json is marked as not serving ads, because such code almost never gets an ad.
- Network Scout: verified means the site's ads.txt carries the network's direct line or its pages load the network's tag, so the site and the network confirm each other. Listed means the site appears only in the network's sellers.json, which is a weaker claim.
- Affiliate Scout: confirmed means one proven link, such as an Amazon link with a real tag. Likely means two strong signals agree. Candidate means a single strong signal or only commercial markers appeared.
Estimates: what we worked out
Traffic and revenue are estimates. Traffic comes from public rankings and measured panels where they exist, and from our own model otherwise. A figure from the model has a tilde (~) in front of it, so you can always tell a modelled number from a measured one. Revenue is worked out from the visits, the pages per visit and the typical page RPM for the site's niche and audience country. Because every input is itself an estimate, revenue is shown as a range with a low and a high end.
Read a range as “probably somewhere in here”. If a site shows, say, four hundred to nine hundred dollars a month, the honest statement is that range, not the number in the middle. Ranges are good for comparing: which of two niches pays better, which of fifty sites is growing. For one site, the figure can be wrong by a wide margin. On Affiliate Scout the revenue band is rougher still and is meant only to rank sites against each other.
A shared ID is a clue, not proof
Two sites on the same publisher ID are paid through the same AdSense account. That usually means the same publisher, but 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. pubsleuth ignores IDs shared by very many sites as templates and tells you how each site was confirmed. Treat a shared ID as a strong lead, then look at the sites yourself.
Every finding has a date
Each service's findings reach the website once a day, and the counts on the home page say on which date they were taken. A single site may have been checked earlier than that, and sites change: ads come off, domains are sold, networks are switched. If something matters, check it at the source before you rely on it.
What it isn't, and the rules we keep
These are the lines we drew when we built it. They shape what you will and won't find.
- Public sources only. It reads only public sources, and never logs in to anything. Nothing in the index came from behind a login, and nothing in it is private.
- Evidence before claims. Where the evidence is ambiguous, such as an ads.txt line that doesn't by itself tie a site to an account, we leave the case out rather than guess. That costs a few results and prevents a great many wrong ones.
- Estimates are labelled. It doesn't measure traffic or revenue: those figures are estimates, labelled as such, and revenue is shown as a range.
- No contact data. It holds no email addresses, phone numbers or other contact details for the people who run websites, and has no outreach or emailing tools.
- Not a list product. It isn't a lead list or a data-resale product. It's for research and analysis: a plan's CSV download is for your own analysis, under our Acceptable use policy, which forbids spam, harassing site owners, trying to identify the private individuals behind a website, and reselling the data in bulk. The monthly limits on each plan exist so that no one account can copy a service in a month.
- Independent. It isn't affiliated with Google, any ad network or any affiliate program. AdSense is a trademark of Google LLC, and the names of networks and programs belong to their owners.
Some things we leave out on purpose. We don't show the names of individual account holders from sellers.json files; only company names appear. Links in comments never count as affiliate evidence, because anyone can post them. And we don't show Domain Authority or other third-party SEO scores: pubsleuth shows traffic, trend, audience, estimated earnings and how a site is monetized, which describe what a site is worth to its publisher rather than how it scores with a link tool.
How the data is made
Our crawlers read the files and pages sites publish for the ad industry and for every visitor: the ads.txt files sites publish, the sellers.json files ad networks publish, and the code and links on the pages themselves. For affiliate links, the crawler reads a site's home page and the commercial pages its sitemap points to, and follows short and cloaked links to where they lead. For the AdSense index, HTTP Archive's browser crawl shows the ads a page asks for when a script adds the ad code, and Google's sellers.json shows whether the account is serving, because code that is present isn't the same as ads that are shown. Traffic comes from public popularity data and, for some sites, third-party traffic estimates. Each service's findings reach the website once a day.
The index will miss sites, and some of what it holds will have changed since it was last checked. For how much we hold in each service, and how we work to improve it, see Our data.
If you run a site we read
If you saw our crawler in your logs, here's what it is and what you can do about it.
Every request carries the User-Agent PubSleuthBot. It reads what your site already shows the ad industry and every visitor, such as your ads.txt and your public pages, and nothing behind a login.
To stop the ad-network and affiliate checks reading your pages, block PubSleuthBot in your robots.txt, for example:
User-agent: PubSleuthBot
Disallow: /That stops them reading your pages. Network Scout still reads your ads.txt and app-ads.txt files.
The AdSense checks don't read robots.txt. They read a site's ads.txt, its home page and up to two linked pages, and, to check that a site really shows AdSense ads, open the home page and at most one article in a browser that runs the page's own scripts and loads no images. That browser stops every ad request before it reaches Google, so no ad is shown or counted.
For anything else, a site owner can write to us about it through Contact: choose “Our crawler” and give the domain, and the time and address of the requests if you have them. If you object to how we process data about your site, the privacy policy explains how: email hello@pubsleuth.com from an address at that domain, or say how you're connected to it. The policy also says how soon we reply.
How pubsleuth is paid for
You can use pubsleuth without paying. Without an account you can run a few lookups a day and see the first sites on an ID, with a count of the rest. A free account raises the daily lookups and gives you a preview of each service.
Beyond that there are three monthly plans, each adding a service to the one below it:
- AdSense Explorer opens AdSense Index in full.
- Premium Ad Network Explorer adds Network Scout.
- Affiliate Program Explorer adds Affiliate Scout.
A plan opens the traffic, revenue and publisher details within monthly limits, and a CSV download for your own analysis. The pricing page lists each plan's price and limits exactly.
pubsleuth carries no advertising, and we don't sell personal data about the people who use it. What we sell is access to the research, on the plans above.
Paid plans are sold through Dodo Payments as merchant of record: Dodo Payments takes the payment, charges the tax and issues the invoice, and card details never reach us. Prices are in US dollars. You can cancel at any time and keep the plan to the end of the period you paid for, and refunds follow our refund policy. The site uses no advertising cookies. It counts visits with Google Analytics, which asks visitors in the EU, the UK and Switzerland first; the cookie policy has the details.
Where to go next
- Our data: how much we hold in each service, and how we improve it.
- Glossary: publisher ID, ads.txt, sellers.json, page RPM and the other terms on this page, explained.
- FAQs: the questions people ask most, from estimates to downloads.
- API docs: looking up a domain, publisher ID or tag from your own tools.
- Pricing: what a free account and each plan include.
- Contact: questions, crawler reports, objections and anything else.
Who runs it
The business that operates pubsleuth is named on our legal pages. To reach us, see Contact.