Documentation

AEO Spotlight answers one question with evidence: when people ask AI about your category, how is your brand represented? It monitors the answers, shows who AI names instead of you and which sources it cites, and turns the gaps it finds into content you publish on your site or CMS. These guides show you how to wire that into your site, CMS, and data stack.

What the platform covers

These guides are about wiring AEO Spotlight into your stack. The product itself is broader than the content pipeline they describe:

• Monitoring — real queries run on a schedule across 8 AI answer engines; every answer is scanned for your brand, your competitors and the sources cited. → AI visibility monitoring
• Competitors — who AI recommends instead of you, per platform, with share of voice. → Competitor intelligence
• AEO Score — a four-factor score tracked over time, so you see direction rather than a one-off snapshot. → AEO Score
• Content Studio — turns a gap (or a topic you bring) into a brief and a GEO-optimized draft, gated by an AI fact-check before anything publishes, then tracked to citation and refreshed in place if AI still ignores the page. Suggestions are labelled with the evidence behind them, and an empty queue explains what the engine had to work with. → Content Studio
• Content library & brand voice — your own documents, split into sections and searched so a draft uses the sections relevant to the piece (never the whole file), plus a brand voice that shapes how it reads. → Content library and brand voice
• Site Audits — scores a single page for the signals that make it retrievable and quotable, or crawls the whole site for grouped quick wins (the crawl is deliberately unscored). → Site audits
• Content Gaps — where Google already ranks you but AI does not cite you, and where AI names a competitor instead. It lives inside Content Studio. → Content Gaps
• Agent Control & the Public API — permissioned automation with an audit trail on every action. → Agent control

The content pipeline these guides cover

Every piece of content that AEO Spotlight publishes flows through the same pipeline. You plug into it at the point that matters to you:

1. Choose a destination (where it goes). Before anything can publish, the workspace needs a publish destination — the endpoint Content Studio delivers to. Add one per site, CMS or client under the account menu → Publish destinations. → Create a publish destination
2. Publish (you receive it). When the Content Studio publishes to a webhook destination, the platform POSTs a signed, versioned JSON document — the PublishPayload — to your endpoint. You upsert it by slug and return the live URL. → Receive content via webhook
3. Index (get crawled now). Right after a successful publish the platform pings IndexNow, so Bing, Yandex, Seznam, Naver and other participating engines crawl the fresh URL immediately. → Set up IndexNow
4. Google demand (find what to write). Connect your Google Search Console property to import real queries with impressions but no ranking page, which are classified into content gaps, on-page lifts and title fixes and appear in Content Studio's review list alongside your other suggestions.
5. Verify & automate. Read mentions, citations, the AEO score and every gap's status over the public API, or subscribe to events (content.published, content.cited, …). → Public API quickstart

Guides

Who each guide is for

More resources

• Full machine-readable API reference: /openapi.json (interactive: /swagger).
• Agent-native index: /llms.txt and /llms-full.txt.
• Ready-made calls: the Postman collection.
• The product's API landing page: aeospotlight.com/developers.