Skip to content
FixAEO
User-Agent · single-fetch-per-scan · robots.txt respected

FixAEOBot

The User-Agent our scanner sends when fetching a page on behalf of a fixaeo.com user. Honest identifier, single fetch per scan, respects robots.txt. Allow or block as you like.

The exact User-Agent
Mozilla/5.0 (compatible; FixAEOBot/1.0; +https://fixaeo.com/bot)

Same shape as Googlebot/2.1 and Bingbot/2.0. The Mozilla/5.0 (compatible; …) prefix is the conventional “named bot” format. The +URL link points back here.

Allow FixAEOBot

Most sites don't need anything special — our UA passes the default Cloudflare and Akamai bot heuristics. If you want to explicitly whitelist us:

User-agent: FixAEOBot
Allow: /
Block FixAEOBot

If you'd rather we didn't scan your site, add this to your robots.txt. Our scanner reads /robots.txt before fetching anything and will respect it.

User-agent: FixAEOBot
Disallow: /

What the scanner actually does

When a user types a URL into fixaeo.com and clicks scan, FixAEOBot makes one GET request to that URL. The HTML response is parsed for AEO-relevant signals:

  • Schema.org JSON-LD presence and completeness
  • Canonical tag, viewport meta, robots meta
  • Title and meta description length / structure
  • Heading hierarchy (H1 → H2 → H3)
  • FAQ section + FAQPage schema
  • llms.txt presence at your root
  • robots.txt rules for major AI crawlers
  • Freshness signals (lastmod, dateModified)

We do notcrawl. We don't fetch internal links, images, or assets. We don't recur. We don't republish your content. We don't train models on it. We don't share the HTML with third parties.

Scan results go back to the user who initiated the scan as a private 10-check report. The full source code path is documented in our public about page.

FAQ

How often does FixAEOBot fetch my site?
Once per scan request a user makes. We don't crawl. The scanner makes a single GET to the URL the user typed (usually the homepage), reads the HTML, parses schema / canonical / meta tags / FAQ structure, and exits. No follow-on requests to internal links. No recurring fetches. If 1,000 of our users each scan your site, that's at most 1,000 single-page fetches across however long that takes — almost certainly less than one fetch per minute on average.
Does FixAEOBot respect robots.txt?
Yes — and we eat our own dog food. If your robots.txt disallows our user-agent, we don't fetch. Our scanner reads /robots.txt before any other request. If you want to specifically block us while allowing other AI crawlers, add `User-agent: FixAEOBot` followed by `Disallow: /` to your robots.txt.
Why does the User-Agent start with Mozilla/5.0?
Same convention Googlebot, Bingbot, and most respectable named crawlers use. The Mozilla/5.0 prefix is historical — sites that gate content behind 'is this a real browser?' heuristics check for it. Without that prefix, even named bots get 403'd at the edge by Cloudflare / Akamai / similar WAFs. We chose honesty (`compatible; FixAEOBot/1.0`) over pretending to be Chrome — same shape Google chose for Googlebot.
How do I block FixAEOBot specifically?
Two ways. (1) In robots.txt, add `User-agent: FixAEOBot` then `Disallow: /` on the next line. (2) At your WAF layer (Cloudflare, Akamai, etc.), block the user-agent string `FixAEOBot/1.0`. We'll see the 403 and surface a friendly error to whoever asked us to scan your site — they'll know it was you, not a fluke.
How do I explicitly allow it (e.g. for sites with otherwise strict bot WAFs)?
Most sites don't need to do anything — our UA looks browser-like enough to pass typical Cloudflare bot fight modes. If you're running an aggressive WAF (DataDome, PerimeterX, Akamai Bot Manager) and want to specifically whitelist us: allow the User-Agent substring `FixAEOBot/1.0` and source IPs originating from our scanner. The IPs are not fixed (we're running on Oracle Cloud) so the UA whitelist is the durable signal.
What does the scanner do with the page content?
Parses it for AEO-relevant signals: schema markup completeness, canonical tag presence, meta description length + keyword fit, heading hierarchy, FAQ structure, llms.txt at root, structured data freshness. The parsed result is sent back to the user who asked for the scan as a 10-check report. We don't republish your content. We don't train models on it. We don't share the HTML with third parties.
Where do scan requests originate from?
An anonymous user types your URL into fixaeo.com (or one of our free tools at fixaeo.com/aeo-tools/) and clicks scan. They're usually a marketer or SEO checking AEO health — either yours, theirs, or a competitor's. We never scan a site uninvited.
I have a complaint about a scan
Email [email protected] with the URL + approximate time. We can confirm whether the scan happened, by what hashed visitor ID, and which signals were extracted. We retain scan records but do not share them publicly without consent.

Questions? Concerns?

Email [email protected] — we'll respond within 24 hours. Block requests, scan complaints, anything.

Run a free AEO audit