Docs / AEO Ultimate for Webflow

AEO Ultimate for Webflow

AEO signals for Webflow

Reads your Webflow site and publishes answer-engine signals through Webflow’s own Data API — JSON-LD, Open Graph, llms.txt and sitemaps — so your CMS collections are legible to ChatGPT, Perplexity, Claude and Google’s AI.

How it connects

Everything runs through Webflow’s Data API after an OAuth install against your account. Nothing is injected into your site’s custom code, and no script is added to your published pages — the app reads and writes CMS fields the same way you would in the Webflow interface.

That has one consequence worth knowing up front: what the app can publish is bounded by what Webflow’s API exposes. Where the API does not allow writing a signal, the app detects and reports rather than pretending to have set it.

What it does today

• AI-readiness scan — point it at a URL and see what an answer engine can and cannot read.
• Signal bundle — generate the missing signals for a page and apply them to the CMS item.
• Meta titles and descriptions — written from the content you already have, using your own AI key.
• Sitemaps — standard and Google News.
• IndexNow — tell engines a page changed rather than waiting to be recrawled.
• Citation directories — where your brand should be listed to be verifiable.
• Agency hub connector — keyed, for managing several sites from one place.

AI features use your own key

As with every edition, AI features run on a key you supply and control, billed to you by the provider at their rate with nothing added on top. Fewer providers are wired up here than in the WordPress and WooCommerce editions — selecting one that is not yet implemented returns “Unsupported AI provider”.

The app is usable with no AI configured at all; the AI features are for generating copy, not for publishing signals.

Known gaps

Being honest about an unfinished product is more useful than a feature list:

• Some errors surface as technical messages rather than written explanations. Being replaced; report any you hit and they get prioritised.
• Schema publishing is detection-only in places, where Webflow’s API does not permit the write.
• Pricing is not set. See the terms for how the other editions work; Webflow’s will be decided before launch.

If you build on Webflow and want to shape this before it ships, tell me what you need. Early input on an unreleased product carries more weight than a feature request after launch.