Integrations
What CueScout works with
Three different senses of the word, and it is worth being clear about which is which. We do not have a partner directory, and nothing here is a logo waiting on a “coming soon”.
Site platforms
What your site is built on decides how you fix the things stopping an engine reading it. CueScout works out which one you are on during a scan and rewrites the fixes for it.
Webflow
The robots.txt setting that only works on a custom domain, where JSON-LD goes, and why /llms.txt needs a proxy.
WordPress
The virtual robots.txt, the Yoast and Rank Math settings that produce sameAs, and where llms.txt goes.
Shopify
The robots.txt.liquid template, Organization schema in theme.liquid, and the file Shopify will not serve.
Squarespace
Two checks Squarespace makes impossible, and the schema ones you can still pass through code injection.
Wix
The built-in robots.txt editor, the custom schema field, and the Velo-shaped rendering trap.
Framer
The robots.txt setting, custom head code on paid sites, and why /llms.txt needs a proxy.
Ghost
robots.txt lives in the theme, llms.txt goes in /public, and Ghost already writes half the schema.
Substack
Almost nothing here is yours to fix — and that changes what is worth doing instead.
HubSpot CMS
The per-domain robots.txt, Design Manager for root files, and the schema HubSpot never writes.
Mintlify
llms.txt and robots.txt are already handled. What is left is schema, and the link to your pricing.
Docusaurus
static/ handles the files, headTags handles the schema, and pre-rendering handles the rest.
Next.js
app/robots.ts, a route handler for llms.txt, JSON-LD in the layout, and the client-component trap.
AI clients
The five free tools as an MCP server, so an assistant you already use can run a visibility check without you opening a tab.
Claude Code
One `claude mcp add` line, then ask about your site's AI visibility mid-session.
Claude Desktop
Paste one block into claude_desktop_config.json and ask about your site in ordinary chat.
Cursor
One block in ~/.cursor/mcp.json, and the agent editing your site can check what engines see of it.
Windsurf
One block in mcp_config.json and Cascade can check what the engines see of your site.
VS Code
A .vscode/mcp.json block — note the key is `servers`, not `mcpServers`.
Zed
Zed calls them context servers — same block, different key, in settings.json.
ChatGPT
The MCP server will not fit — ChatGPT needs a remote one. The public API is the route that works.
Alerts and automation
Where CueScout sends a message when your share of AI answers moves, or when a page that cites you changes.
Slack
A formatted weekly message: the number, which way it moved, and who turned up where you are not.
Discord
A channel webhook and the plain JSON body, once a week.
Zapier
Catch Hook, then map visibility_pct and delta into whatever you already run.
Make
A custom webhook module, then whatever your scenario already does.
n8n
A Webhook node, and the one place signature verification is worth actually doing.
Not sure which platform you are on?
The free readiness check works it out from your homepage and gives you the fixes written for it. Eight checks, no signup, nothing stored.
Run the free check