Run a Technical GEO Audit | Make your site readable by AI crawlers

Technical GEO Audit

A page can be perfectly written and still be unreadable to an AI crawler

Gumshoe fetches your page, runs its coded assessments against it, and hands you the specific changes that make it readable.

See the audit

What the Technical GEO Audit assesses

Crawlability

Can AI crawlers reach your pages? robots.txt checked against named AI and search agents, plus meta robots and X-Robots-Tag noindex, plus the HTTP status.

robots.txt

Fetch health

If your page can't be fetched cleanly, that's the finding. A bot wall, an error response, a redirect to the homepage, or a near-empty body stops the audit and gets reported instead of a score.

Structured Data

Is there JSON-LD, and does every block parse? Plus the metadata a model reads to classify your page: canonical, title, OpenGraph, Twitter card, published date.

<script type="application/ld+json">
{ "@context": "https://schema.org", ... }
</script>
<script type="application/ld+json">
{ "name": "Acme", "url": , }
</script>

Every block has to parse. One broken block is a finding.

Page Structure

Is your content easy to lift into an answer? One h1 and no skipped heading levels, main content volume against the markup around it, and a main or article landmark.

What the audit gives you

  1. Summary Score

  1. Component Breakdown

Every assessment grouped into its category, each with a score and a pass or fail count.

  1. Assessments

Open an assessment and it shows what it looked for, how to fix it, and the evidence.

How you use it

  1. Point it at a page

    • Paste a URL and the audit runs against that one page. Start with the pages AI is most likely to draw on when it describes you: home, pricing, product, comparisons.
    • acme.com/pricing
    • Run
  2. Assessments run in code

    • Every assessment runs against the fetched page in code, so the score is repeatable rather than a model's opinion. The written summary sitting on top of it is AI-generated.
    • robots and status
    • structured data
    • headings and content
  3. Findings with evidence

    • Each finding names what the assessment looked for, what it found, and the change that fixes it. The evidence is what the fetch actually returned, so nothing rests on taking the score at its word.
    • Open Graph essentials evidence
    • Text to markup ratio evidence
    • Publish date evidence
  4. Fix, then run it again

    • Ship the change and re-run the audit. The score moves with the page, and the audit carries the latest run and the date it ran, so progress is easy to track.
      • 71 before
      • 84 after the fix
      • 1234 on a cadence

Questions about the Technical GEO Audit

Find out what AI can't see.

Run the Technical GEO Audit on your most important page and get every finding back with the evidence behind it.

Run a Technical GEO Audit