Result model

Ads.txt Checker result model

A complete report checks file reachability, record syntax, and whether a Google seller line is present.

Severity ladder

Every report separates blockers, warnings, and healthy confirmations.

This is the reporting model behind the live tools, so operators know what to fix first instead of reading a flat list.

Critical

Fix these before relying on the current setup for monetization, indexing, or language targeting.

Warning

The page or file is reachable, but there is still technical risk worth reducing quickly.

Healthy

Public signals look aligned. Keep this state stable while you scale content or ads.

Signals included

  • HTTP status and content type of `/ads.txt`
  • Presence of a valid `google.com, pub-...` record
  • Empty file, HTML fallback, or malformed line warnings

Operator actions

  • Publish the file in the domain root instead of a subfolder.
  • Use the exact publisher ID from AdSense and keep the seller domain as `google.com`.
  • Wait for Google to refresh after the file becomes publicly reachable.
01

Run the public check

Use the live checker to see what is publicly reachable and technically visible today.

02

Fix the highest severity first

The result model is intentionally ordered so blockers come before informational clean-up.

03

Re-run after deployment

These tools are built for before-and-after verification, not one-time screenshots.