Audit methodology
How SenseApproval gathers evidence, assigns severity and calculates readiness scores.
Observable evidence, not approval predictions
SenseApproval requests public pages and technical files, evaluates response headers and markup, samples internal pages and assets, inventories structured data, and groups findings by severity. It cannot see Google’s private review systems and never presents a score as approval odds.
Purpose-aware page analysis
Pages are classified as homepage, article, tool, About, Contact, Privacy, Terms, publisher policy, private application route, or general content. Each type is reviewed against signals appropriate to its purpose. A short Contact page is not penalized merely for its word count when it provides a usable form or email address; an article is reviewed for depth, authorship and dates; a tool page is reviewed for instructions, controls, methodology and limitations.
Current audit coverage
- Availability, HTTPS, canonical URLs, indexing directives and robots rules.
- XML sitemap integrity, sampled sitemap URLs and crawl-to-sitemap comparison.
- AdSense publisher IDs, connection script placement, account meta tags and ads.txt consistency.
- Publisher identity, About and Contact discovery, legal and advertising disclosures.
- Title, descriptions, H1 headings, duplicate metadata and navigation structure.
- JSON-LD syntax and structured-data type inventory.
- Broken internal pages, homepage assets, mixed content and redirect behavior.
- Security-header coverage, response time, image layout-shift risks and static performance indicators.
- Public RDAP registration and Internet Archive signals when available.
Weighted scoring
Only findings with a direct, observable relationship to availability, indexing, content usefulness, publisher trust, AdSense configuration, navigation or technical reliability affect the score. Informational observations—such as domain age, social profiles, Analytics, CSP, RSS or optional discovery assets—do not reduce readiness by themselves. Warnings receive a smaller deduction than verified failures, and critical blockers remain visible regardless of the numeric score.
Confidence and limitations
Direct response codes, headers and markup are verified observations. Content completeness, page purpose and ad-to-content balance are automated heuristics that require human review. Static scanning cannot validate AdSense account ownership, Policy Center messages, manual Search actions, real-time Analytics collection, consent transitions, field Core Web Vitals or Google’s final decision. Those require authenticated product access, browser testing or manual review.
Domain-history context
SenseApproval may show registration and archive dates when public sources respond. These signals are context only. A new domain is not automatically low quality, and SenseApproval does not use an arbitrary minimum domain age as an AdSense requirement.
Verified readiness, public quality, and audit coverage
Version 19 no longer allows a limited public sample to appear fully verified. The public-site score measures observed pages and files. The overall score is capped while private account, traffic-quality, rendered ad-placement, consent-runtime, copyright, originality, and full-site review requirements remain unresolved. Audit coverage shows how much of the applicable matrix was actually examined.
Six possible outcomes
- Pass: direct evidence supports compliance.
- Fail: direct evidence shows a correctable defect.
- Warning: a strong risk indicator needs review.
- Informational: useful context that does not reduce the score.
- Account access required: only AdSense, Search Console, Analytics, or account records can verify it.
- Human review required: originality, copyright, traffic quality, consent behavior, rendered placement, or complete-site judgment is needed.