AdSense script found
The standard public script is present. Continue checking publisher IDs, ad unit markup, account status, and policy signals.
AdSense Code Checker
Find AdSense scripts, adsbygoogle markers, and Google publisher IDs on public pages.
This checker reads public HTML. It cannot verify private account approval, ad unit status, or policy restrictions.
adsbygooglepagead scriptca-pub IDlegacy code
Overview
About this AdSense Code Checker
The AdSense Code Checker helps you verify whether a public page contains visible Google AdSense installation signals. It scans the fetched HTML for the pagead script, adsbygoogle markers, legacy google_ad_client values, and ca-pub publisher IDs.
This is useful when ads are not showing, a theme was changed, a plugin was replaced, or a page was migrated to a new platform. The checker confirms public installation signals, but it does not prove that Google has approved the site or that ads will serve.
How it works
Check a domain or URL in three steps
- 1
Enter the page URL where you expect AdSense code to appear.
- 2
The checker fetches the public HTML and searches for AdSense script and publisher ID patterns.
- 3
The result tells you whether code signals are found, missing, partial, or hard to verify.
What this checker looks for
Page code check
AdSense script
pagead2.googlesyndication.com/pagead/js/adsbygoogle.js in the public HTML.
adsbygoogle markers
AdSense ad slot markup that suggests ad units are installed on the page.
Publisher IDs
ca-pub values and older google_ad_client values that identify the publisher account.
Legacy AdSense code
Older google_ad_client code patterns found in legacy themes, copied templates, or old AdSense snippets.
Code consistency
Signals that help distinguish missing code, partial code, legacy code, or multiple publisher IDs.
What the Report Shows
AdSense Script: Found / Not Found.
Publisher ID: Found / Not Found.
Publisher ID: ca-pub-xxxxxxxxxxxxxxxx.
Use it to verify public installation
If code is missing, install the AdSense script and ad unit markup on the pages where ads should appear, then re-check the URL.
Why Use This Checker
Features
- Detects the standard AdSense pagead script.
- Finds adsbygoogle markers used by ad unit markup.
- Extracts ca-pub publisher IDs from public HTML.
- Checks legacy google_ad_client values.
- Separates reachable page issues from missing ad code issues.
Benefits
- Confirm that AdSense code is actually published on the target page.
- Catch theme, plugin, cache, or deployment changes that removed ad code.
- Compare detected IDs with your expected publisher account.
- Troubleshoot missing ads before assuming an approval or policy problem.
Use cases
- Publishers checking a page after adding AdSense code.
- Developers validating a template or CMS migration.
- Site owners investigating why ads are not visible on a specific URL.
- Operators checking whether old publisher IDs remain in copied code.
How to interpret results
How to Read the Report
Publisher ID found
A ca-pub ID appears in public HTML. Confirm it belongs to the expected account and matches ads.txt when appropriate.
Multiple publisher IDs found
More than one ca-pub value appears in the public HTML. Check whether the IDs belong to the expected account and remove old, copied, or unrelated publisher IDs when necessary.
No code signal found
The fetched HTML does not contain common AdSense markers. The code may be missing, injected after render, blocked, or deployed on a different URL.
Limitations / disclaimer
What this tool cannot confirm
- The first version checks fetched HTML, not a fully rendered browser DOM.
- Found code does not guarantee ad serving, approval, policy status, or revenue.
- Consent management, lazy loading, client-side rendering, and ad blockers can affect what users see.
Related tools
Related AdSense Checker Tools
Google Publisher ID Finder
Scan a public page for Google AdSense publisher IDs such as ca-pub values.
ads.txt Checker
Verify whether ads.txt exists and includes a valid Google seller line.
AdSense Audit
Run a page-by-page AdSense readiness audit and get a prioritized fix plan.
AdSense Ban Checker
Check public signals that may indicate AdSense ban, block, or ad serving issues.
AdSense Approval Checker
Check whether your website is ready before applying for Google AdSense.
AdSense Eligibility Checker
Check whether your website meets basic public readiness signals for Google AdSense.
AdSense Code Checker FAQ
Common questions about what this checker can verify and how to interpret the public report.
Does found code mean ads will show?
No. Code detection only confirms public installation signals. Ad serving can still be affected by account status, policy, demand, consent, crawlability, or page quality.
Why does it look for ca-pub IDs?
ca-pub IDs identify the publisher account referenced by the public code and can be compared with ads.txt values.
Can it detect code added by JavaScript after render?
The first version checks fetched public HTML. Browser-rendered network and DOM checks are planned for a later version.
What should I fix if no script is found?
Add the AdSense pagead script and ad unit markup to the target page, then confirm the code appears in the public HTML.
Can this checker verify my AdSense account approval?
No. This checker only reads public page code. It cannot access your Google AdSense account, approval status, ad unit status, policy restrictions, or payment settings. Found code means that public installation signals exist, but it does not prove that the account or site is approved.
Why is AdSense code missing from a specific page?
AdSense code may be missing if the theme, template, CMS plugin, tag manager rule, cache, or deployment process does not add the script to that URL. It may also be injected after render, blocked by consent settings, or only added to selected page types. Check the page template and compare it with a URL where ads are expected to appear.