CueScout

Use this when someone asks why their site never shows up in AI answers, or whether GPTBot, ClaudeBot, PerplexityBot or Google-Extended can crawl it. Reads the site's robots.txt and reports which of those crawlers are blocked, including by a blanket rule the owner may not have meant. One fetch, no AI.

Use this when someone asks whether AI engines can read, crawl or quote their website, or wants an AI-readiness audit of a site. Runs eight checks: AI crawler access in robots.txt, llms.txt, Organization and FAQ schema, canonical and meta tags, server-rendered copy, and whether an about page and a pricing page exist. It does not measure whether any engine actually cites the site; check_ai_visibility does that. No AI call, nothing stored.

Use this when someone asks whether an AI answer engine names or cites a brand for a buying question, or which other brands it names. Sends one question to one search-grounded engine through its API and returns whether the brand was named, whether its domain was cited, which of the listed competitors were named, and the pages the answer cited. Each call is a fresh API request with no account history or personalization, and one question is one datapoint, not an overall visibility score.

Use this when someone wants their XML sitemap checked. Reports whether a site's sitemap is reachable, parses, is declared in robots.txt, and is free of cross-host entries a crawler discards. A handful of fetches, no AI.

Use this when someone asks how visible their brand is in AI answers, what their share of AI voice is, or how they compare with competitors. Reads the results CueScout already collected for the brand: how often AI answers named it, its share of voice, how often its site was cited, and the same for each competitor, over the last 7, 28 or 90 days. It does not run new checks.

Use this when someone asks which CueScout account is connected. Returns the account name and email.

Use this when someone wants to read what the AI engines actually answered to one of their tracked prompts. Returns the most recent answer from each engine, whether the brand was named or cited, which brands were named, and the pages each answer cited. Take the prompt id from list_prompts.

Use this when someone asks whether AI engines can read their own brand's site, based on CueScout's last audit of it: crawler access, llms.txt, schema, meta tags, server-rendered copy, and about and pricing pages. Reads the stored result; it does not re-run the audit. For a site that is not in the account, use check_ai_readiness instead.

Use this when someone wants the details of one To-do: why it matters, the steps to do it, and the evidence behind it. Take the id from list_todos.

Use this to see which brands the connected CueScout account tracks, with their sites and the competitors set for each. The other account tools take one of these brands.

Use this when someone asks which websites or pages AI answers rely on in their brand's category, or where they should try to get mentioned. Returns the pages cited most often across the brand's tracked prompts, with how many times each was cited, by which engines, and which brands each page names.

Use this when someone asks which questions CueScout tracks for their brand, which ones the brand is missing from, or who gets named instead. Returns each tracked prompt with the latest verdict per engine (named and cited, named, or not named), the brand's mention and citation rate over the window, and the brands named instead.

Use this when someone asks what they should do next to show up in AI answers. Returns CueScout's To-dos for the brand in priority order: the action, why it matters and its priority. Filter by status: todo (default), suggested, done or dismissed.

Use this when someone wants their schema markup or JSON-LD checked on a specific page. Reports which schema types the page declares, which blocks fail to parse, and whether the fields that help an engine attribute a claim (sameAs, Organization identity, FAQ answers) are filled in. One fetch, no AI.