Entry page structure
Title, meta description, canonical, H1 count, and homepage-level entity signals.
Methodology
How mygeo verifies a site.
mygeo only reports what it can fetch, parse, and point back to. The system is built to answer whether a public website exposes the signals that crawler-facing GEO checks can verify today.
Artifacts first
Homepage HTML, robots.txt, sitemap.xml, llms.txt, and sampled pages are captured before checks run.
Checks stay deterministic
No traffic forecasts, no made-up readiness scores, and no hidden confidence math.
Evidence stays visible
Every finding ties back to explicit evidence lines so another operator can review it quickly.
Current verification lanes
Crawler access
robots.txt presence plus explicit GPTBot and ClaudeBot blocking directives.
Discovery assets
sitemap.xml and llms.txt are checked as root assets, not inferred from UI state.
Sampled pages
When the sitemap exposes internal URLs, mygeo fetches them directly and verifies their signals independently.
What mygeo does not claim
- It does not predict traffic uplift or AI referral revenue.
- It does not infer platform rankings from a checklist.
- It does not treat unknowns as hidden passes.