CueScout

By Telman Gadimov

Overview

CueScout checks how AI answer engines treat a website. Ask whether an AI search engine names your brand for a question a buyer would type, and CueScout runs that question once and reports back: whether the brand was named, whether its site was cited, which of up to three competitors came up, and the pages the answer was built from. Those pages are mostly reviews, comparison posts and "best tools" lists on other people's sites, so the list tells you where the answer is coming from. Four more checks look at the site itself and use no AI. One reads robots.txt and says whether the main AI crawlers are blocked, including by a catch-all rule nobody meant to write. Another runs eight readiness checks: crawler access, llms.txt, Organization and FAQ schema, canonical and meta tags, whether the copy is in the HTML or only appears after JavaScript runs, and whether there is an about page and a pricing page. The last two validate the JSON-LD on a single page and check that the sitemap can be fetched, parses, and is listed in robots.txt. If you track brands in CueScout, you can connect your account and ask about them directly. The app then reads what CueScout has already collected: how often AI answers named your brand and each competitor, your share of voice, the prompts you're missing from and who got named instead, what each engine actually said, the pages those answers cited, your To-dos in priority order, and your last site audit. Connecting is read only. The app can't change settings, add prompts, run checks or buy anything, and you can disconnect it in CueScout's settings. It's built for marketers, founders and SEO people who want a quick read on AI search in the middle of a conversation. The five checks above work without an account. What it can't tell you: the visibility check asks an engine through its search API, not through a consumer app, so no account history, memory or location shapes the answer. One question gives one answer. A brand missing from one phrasing can show up in the next, so read a single result as one datapoint rather than a score. The site checks only read public pages and never change anything. Visibility checks have a daily limit shared by everyone using the app.

Tools

check_ai_crawler_access

ChatGPT

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.

check_ai_readiness

ChatGPT

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. No AI call, nothing stored.

check_ai_visibility

ChatGPT

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.

check_sitemap

ChatGPT

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.

get_ai_visibility

ChatGPT

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.

get_profile

ChatGPT

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

get_prompt_answers

ChatGPT

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.

get_site_audit

ChatGPT

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.

get_todo

ChatGPT

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

list_brands

ChatGPT

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.

list_citation_sources

ChatGPT

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.

list_prompts

ChatGPT

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.

list_todos

ChatGPT

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.

validate_structured_data

ChatGPT

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.