AEO for Webflow
Use Webflow’s native schema settings and CMS fields to keep each published page’s markup accurate.
Default robots.txt behavior
Site settings → SEO → Indexing has Traffic control toggles for search engine crawlers and AI bots. Both categories allow traffic by default. The same Indexing section lets you add custom robots.txt rules. Webflow adds a sitemap reference. Publish your changes for them to take effect. Staging indexing is a separate control for the webflow.io site.
Decide whether to permit search and user-fetch crawlers separately from training crawlers, within the controls your platform provides. See how AEOprobe distinguishes crawler roles.
Default structured data
Webflow has a native Schema markup field in Page settings. You can enter JSON-LD by hand or, optionally, generate it with Webflow AI.
Common AEO issues
| Issue | Impact | Fix |
|---|---|---|
| Schema repeats the same facts across Collection items | ImpactThe markup describes another item instead of the published page. | FixBind item-specific Collection fields. Then inspect two published items. |
| Native and custom-code schema overlap | ImpactDuplicated or conflicting structured data is harder to maintain. | FixKeep schema in one location. Existing custom-code markup does not have to move to the native field. |
| Staging and public-site indexing are confused | ImpactThe intended public page may be excluded, or the staging site may remain discoverable. | FixReview Staging indexing, bot Traffic control and the page’s Sitemap indexing setting separately. |
Step-by-step guide
- 1
Review the page’s native schema field
Open Pages → page settings → Schema markup. Review the manual or generated JSON-LD. Bind supported Collection fields.
- 2
Set the intended crawler and indexing policy
Open Site settings → SEO → Indexing → Traffic control. Review the search and AI categories and any custom robots.txt rules. Then open Page settings → SEO settings. Check Sitemap indexing for the public pages you want indexed.
- 3
Check sitemap and canonical settings
Under Site settings → SEO → Sitemap, enable Auto-generate sitemap if you use Webflow’s generated sitemap. Review Global canonical tag URL. Use the full default-domain base URL without a trailing slash. Check any Page canonical URL overrides.
- 4
Publish and inspect Collection items
Save and publish to the intended site. Inspect /robots.txt, /sitemap.xml and representative static and Collection pages. Confirm the JSON-LD matches the published content. Confirm canonical tags point to the preferred URLs you intend.
Official documentation
- Webflow native schema markup(opens in a new tab)
Field access, AI generation, dynamic bindings and duplicate-markup guidance.
- Webflow indexing and traffic controls(opens in a new tab)
Search and AI bot defaults, staging and page indexing.
- Webflow robots.txt rules(opens in a new tab)
Custom crawler directives and sitemap discovery.
- Webflow sitemap settings(opens in a new tab)
Auto-generation and publishing.
- Webflow canonical settings(opens in a new tab)
Global canonical URL and page overrides.
Questions
Who can use native schema markup?
You need a paid Site plan or a paid Workspace, and a role above Reviewer. Webflow AI must be enabled for generation. Reference, Multi-reference and Multi-image Collection fields are not supported.
The free audit checks up to 3 public pages with no sign-up. Structured data checks read JSON-LD only. Microdata and RDFa are not parsed. Findings do not guarantee rankings or AI citations.
A saved-site audit costs 20 credits. It covers up to 10 pages on Free, 50 on Watch and 100 on Pro. AEOprobe plans are Free at €0/month, Watch at €7/month and Pro at €21/month. Your account shows what you can buy.
Run the free audit on your site