01

Method

We fetched robots.txt, sitemap.xml, and ads.txt directly and recorded status, content type, body size, non-empty line count, and cache headers. We did not treat the presence of any file as proof of indexing or AdSense approval.

The analysis keeps responsibilities separate: robots controls crawl directives, the sitemap suggests canonical URLs, and ads.txt declares authorized advertising sellers.

Measurement recordHostinger VPS in Europe; one cold request per URLCollector version 1.0.0Raw JSON ↗
02

Observed evidence

SignalObservedWhy it matters
robots.txtHTTP 200 · 5 linesAvailable as text/plain and references the site origin.
sitemap.xmlHTTP 200 · 6379 bytesAvailable, but its URL set required editorial pruning.
ads.txtHTTP 200 · 1 linePublisher declaration was reachable.
03

Findings

  • All three files returned HTTP 200.
  • The sitemap included generic and automated pages that were not ready to be the site's quality core.
  • ads.txt availability did not resolve the low-value-content assessment.
04

Decision and resulting changes

Keep robots.txt and ads.txt stable, rebuild the sitemap around indexable field studies and trust pages, and never present technical availability as an approval signal.

  • Pruned sitemap membership based on editorial status.
  • Added tests that noindex pages cannot appear in the sitemap.
  • Kept the publisher ID declaration unchanged.
05

Limits and reproduction

Re-run automation/evidence_collector.py against the public origin and compare the resulting JSON fields. A difference is evidence of a changed response, not automatically an improvement.

  • The check does not read Google's internal crawl state.
  • AdSense review outcome cannot be inferred from ads.txt.

Primary references

Release record

— Baseline captured from the public site, limitations documented, and remediation decision published.

Prepared by SiteSignal Hub Field Lab. Evidence collection and structural checks are automated; no personal use, customer result, or human test is claimed.