AI search SEO checks

Whether AI assistants (ChatGPT, Claude, Perplexity, Gemini, Copilot) can read and quote your site: AI crawler access, llms.txt and answer-ready content.

SmooxSEO runs 18 ai search checks on every page of your site:

High High priority

A page can't be found, indexed or trusted, or search engines can't read part of the site. Fix it soon: it costs traffic.

  • AI search robots blocked

    robots.txt stops the robots that ChatGPT, Claude, Perplexity and others use to find answers. Your pages can't be quoted or linked in those answers.

  • Bingbot blocked

    Bing's robot is blocked, so the site can't appear in Bing, nor in Microsoft Copilot and the other assistants that answer with Bing results.

Medium Medium priority

The page still ranks, but less well, or a real opportunity is lost. Fix it when you can.

  • AI robots stopped by a firewall

    Asked with their real names, these robots got an error or a challenge page while a normal browser got the site. Often Cloudflare's "Block AI bots" setting or a bot-protection rule. Tested from Smoox's server: real robots come from their own addresses, so treat it as a strong hint.

  • Answer not first under a question

    The heading asks a question, but the text under it doesn't answer it in its first sentence. AI answers quote short, direct answers, and readers want them too.

  • Page hidden from some AI robots

    A rule for specific robots (<meta name="OAI-SearchBot" content="noindex"> or an X-Robots-Tag header naming them) keeps this page out of those assistants' answers.

  • Too slow for AI assistants

    Assistants that read pages live give up after a few seconds. This page took more than 5 seconds before the server started answering.

Low Low priority

Good practice with a small effect, or something that is often intentional. Nice to have.

  • AI robots that read a page for a user are blocked

    When someone pastes your link in ChatGPT, Claude or Perplexity, these robots fetch it. Blocked, the assistant can't read your page for that person.

  • AI training robots blocked

    GPTBot, ClaudeBot, Google-Extended and others can't use your text to train models. That's a legitimate choice: it doesn't stop you from being quoted in AI answers.

  • Brand not clearly described

    The home page never says plainly what the brand is ("Acme is a … that …"). Assistants describe you from sentences like this, and guess when there isn't one.

  • Comparisons not in a table

    The page compares things in sentences. Tables are much easier for assistants (and readers) to extract.

  • Consent-only HTML needs manual review

    No independent content was found outside the consent UI and navigation in the raw HTML. This does not prove a cookie wall or consent dependency.

  • llms.txt has broken links

    Pages listed in llms.txt don't load, so an assistant following it hits dead ends.

  • No FAQ

    No page answers your customers' common questions in one place. FAQs match how people ask assistants.

  • No figures in a long article

    Specific facts (numbers, prices, dates, percentages) are quoted far more often than general statements.

  • No heading phrased as a question

    People ask assistants questions. Headings that match those questions are easier to pick as an answer.

  • No llms.txt

    llms.txt is an optional map of the site for AI assistants, in plain text. No major assistant has said it uses it yet, so it's a small, cheap extra.

  • Passages that need the rest of the page

    Phrases like "as mentioned above" break when an assistant quotes the paragraph on its own.

  • Snippets limited (nosnippet or max-snippet)

    nosnippet, a small max-snippet or data-nosnippet tells Google not to quote the page: no text in search results and no use in AI Overviews.