Honest methodology. What's real, what's approximated, what's impossible.
AdSense uses multiple specialized crawlers. Understanding which is which is the foundation of this tool.
User-agent: Googlebot
Discovers and indexes pages for regular Google Search. AdSense uses its crawl history as a signal: if Googlebot has never successfully crawled your site, AdSense won't seriously consider it.
User-agent: AdsBot-Google / AdsBot-Google-Mobile
The bot that decides if you get approved. It checks reachability (was the site down?), verifies ads.txt, evaluates pages against AdSense policies. This bot only visits during an active AdSense review.
User-agent: Mediapartners-Google
Reads page content to decide which ads to show. Only relevant after approval.
We call googleapis.com/pagespeedonline/v5/runPagespeed directly. The audits, scoring, and recommendations come straight from Google's servers — same engine they use internally.
Google's Chrome User Experience Report (CrUX) records anonymous performance data from real Chrome users. This is the closest thing that exists to Google's private telemetry — and it's the data AdSense reviewers see.
Our log parser detects zero-byte responses, 5xx errors, and slow responses — the exact patterns that trigger AdSense's "Site down or unavailable" verdict. We catch these before the next AdsBot visit, not after.
15+ classification rules identify real Googlebot (by reverse-DNS-able IP ranges and user-agent patterns), AdsBot-Google, fake Tencent bot farms, scraper tools, and brute-force probes.
Auto-checked via the Internet Archive's Wayback Machine API. Returns first-seen date and approximate age — critical for 2026's stricter domain-age preferences.
Google trained models on billions of sites to detect "low value content," AI-generated content, and scraped content. The model weights are proprietary. No public tool can replicate this.
Google has 25 years of data on every domain — previous owners, spam associations, backlink quality, ad ecosystem reputation. This database is internal.
Edge cases go to Google employees who make subjective calls. We can't predict their decisions.
Free browser-callable APIs don't exist for these. We provide one-click links to Google's official tools instead.
The site readiness score combines multiple weighted components:
If no Chrome field data is available (very new or low-traffic site), the overall score is reduced by 10% — this itself is an AdSense signal.
The server score uses log-based deductions:
Google tightened AdSense approval criteria in 2026. The unofficial benchmarks now circulating among publishers who recently got approved (or rejected):
The site is pure HTML + JavaScript with no backend. Here's what gets sent where: