Technical SEO and AI visibility

Words matter.

A calm, read-only audit of the pages search engines and AI answer tools can actually fetch. You get a short list of what to fix first, with evidence and plain-English steps.

Example
72

example.com

Example audit · 3 things to fix first

  • P0
    Pricing page has no titleSearch results show the raw URL instead.
  • P1
    AI crawlers are blockedrobots.txt disallows them for the whole site.
  • P2
    No /llms.txt fileOptional. The audit notes that it is missing.
Illustration with example data. Not a measurement of any real site.

What it audits

Two lenses on every page

Technical SEO

Status codes, redirect chains, HTTP to HTTPS, titles and meta descriptions, headings, canonicals, robots.txt, sitemaps, broken internal links, JSON-LD, Open Graph, image alt text, noindex on important pages, mixed content, and response-time and HTML-size hints.

AI visibility

AI crawler rules in robots.txt, and /llms.txt: whether the file exists, is plain text, and is allowed. Blocking a crawler can be the right choice. The audit makes that choice visible.

Length cutoffs and the performance hints are product heuristics. They are not ranking scores and they are not Core Web Vitals.

How it works

Point, wait a few minutes, fix

  1. Point it at a public URL

    The crawl accepts one http or https URL. Private hosts and URLs with a username or password are refused before any request.

  2. It fetches slowly, on purpose

    About one URL per second. It respects robots.txt for its own user agent and stops at the plan’s page cap.

  3. You get findings, not noise

    Each finding has a priority (P0, P1, or P2), an evidence URL, and a plain-English fix guide. A short summary puts the most important fixes first.

See what search engines and AI tools see

Plans start with 20 audits a month. Checkout is in test mode during early access.