Skip to main content
sus.botdocs
  • SEO
  • AI
  • QA
  • Privacy
  • Accessibility
  • Security
  1. Docs
  2. AI

Module

AI

17 audits · 80 checks · 29 findings

Audits

  • AI crawler access 6 checks
  • Visibility in AI answers 6 checks
  • AI Overviews for tracked keywords 2 checks
  • Traffic from AI assistants 4 checks
  • Page readiness for AI answers 6 checks
  • Checks that need judgement 5 checks
  • AI usage signals and agent files 3 checks
  • llms.txt invites what robots.txt forbids 4 checks
  • robots.txt allows a bot the server turns away 4 checks
  • AI access is blocked while AI visibility is the goal 4 checks
  • The content exists only after JavaScript runs 5 checks
  • The site gives different answers to the same question 6 checks
  • AI answers contradict the site 5 checks
  • Organisation and author markup contradicts the visible page 5 checks
  • The page has four different dates 5 checks
  • Snippet and reuse controls contradict each other 5 checks
  • Bots and people are served different content 5 checks

Findings

  • An agent file the site offers is broken
  • An AI answer states a fact about the site that the site itself does not state
  • A language model read an AI answer as describing the brand wrongly
  • A language model found no passage that answers the page's question plainly
  • AI assistants leave the brand out, cite others, or state facts the site contradicts
  • Visitors from an AI assistant convert far less often than other visitors
  • Visits from AI assistants dropped, land on a broken page, or leave at once
  • AI answers are tracked for this site while its pages are closed to AI systems
  • A crawler is served different content from a browser
  • robots.txt lets AI crawlers in, but Cloudflare turns them away
  • A language model judged a title, heading, link text, alt text or word as not fitting
  • An AI crawler cannot fetch or read the site's pages
  • A page's date moved while its text stayed the same
  • The dates a page declares contradict each other or the changes we observed
  • Author, organisation or address in the structured data differs from the visible page
  • Two pages of the site state the same fact with different values
  • The passage that answers the page's question sits inside data-nosnippet
  • llms.txt lists a URL that AI crawlers cannot fetch or should not use
  • The site has no llms.txt, or it lists no pages
  • The site gained a section after llms.txt was last changed
  • Most of the page text is missing from the HTML source
  • A Markdown version the site offers is broken
  • Google shows an AI Overview for a tracked keyword and does not cite the site
  • A page lacks what an AI assistant needs to read, trust and quote it
  • robots.txt has a group for a crawler name no crawler list knows
  • What robots.txt says about an AI crawler differs from what the server does
  • Snippet and reuse controls contradict each other or the page's own markup
  • Markup, links or key facts appear only after JavaScript has run
  • An AI usage signal contradicts the crawler rules
  • All audits
  • About sus.bot
  • Open the app
  • Contact support