Keep Webflow CMS pages structured, crawlable and consistent.
Audit collection templates, metadata, canonicals, sitemap settings, localization and custom schema without turning every page into a custom-code project.
Five checks before content optimization begins.
Fix access, duplication and rendering problems before interpreting weak AI visibility as a content-only issue.
How these things actually work on Webflow
Generic advice stops being useful at the point where you have to click something. Each row below is the mechanism on this platform, linked to the vendor documentation it came from.
| robots.txt | Edited as a setting rather than a file, under Site settings, SEO, Indexing. Webflow adds the Sitemap line automatically and offers traffic-control toggles that generate rules for known bot categories including AI crawlers. Read the generated rules rather than assuming the default posture allows AI agents. Platform documentation · help centre blocks our fetcher; read from the linked article rather than tested by us |
|---|---|
| Rendering | Webflow publishes pages as static HTML served from its CDN, so page copy and CMS collection content bound in the Designer are in the source without JavaScript. Three things are not: site search result pages, anything an Embed builds at runtime, and content loaded by third-party scripts. Platform documentation · help centre blocks our fetcher; read from the linked article rather than tested by us |
| Structured data | Webflow documents no automatic schema.org output. JSON-LD goes in through custom code in the head, either site-wide in Site settings or per page in Page settings, or via an Embed on a collection page template where CMS field values are interpolated so one template emits per-item markup. Both custom-code fields require a paid Site plan, which is the usual reason a JSON-LD block will not save. Platform documentation · help centre blocks our fetcher; read from the linked article rather than tested by us |
| /llms.txt | Webflow’s help centre documents a dedicated llms.txt upload that serves the file from the domain root on a custom domain. Other arbitrary root-level filenames remain unsupported, because page slugs cannot contain a dot and assets are served from Webflow’s asset CDN rather than the root. Platform documentation · help centre blocks our fetcher; read from the linked article rather than tested by us |
| Sitemap | Auto-generated at /sitemap.xml once enabled in Site settings, regenerated on every publish, and it includes every live page unless that page’s sitemap indexing toggle is switched off. Each URL carries a lastmod, and sites using Localize get hreflang alternates. You can paste a hand-written sitemap instead, but not both, or robots.txt ends up advertising two. Platform documentation · help centre blocks our fetcher; read from the linked article rather than tested by us |
| The gotcha | Disabling subdomain indexing publishes a different, blocking robots.txt on the webflow.io staging subdomain. Auditing robots rules against the staging URL therefore gives the wrong answer every time: what you see there is not what your custom domain serves. Platform documentation |
Do these three first
- Open Site settings, SEO, Indexing and read the generated robots rules per AI bot category instead of trusting the default. ↗
- Audit robots.txt and llms.txt on the custom domain, never on the webflow.io subdomain — the two serve different files. ↗
- On each collection page template, add an Embed in the head that emits JSON-LD from collection fields, so every item gets item-specific markup from one edit. ↗
Check implementation decisions against current Webflow documentation.
Webflow SEO documentation ↗A practical Webflow GEO workflow.
Separate technical readiness, content evidence and continuous measurement.
Start with checks that do not consume AI tokens.
Questions teams ask before they start
Does a platform page mean InsightWonder edits the site automatically?
No. The page explains platform-specific checks and implementation paths. Write-back or app-based changes should be described only where a verified integration exists.
Are robots.txt and llms.txt enough for GEO?
No. They help with access and orientation, but useful answers still depend on clear content, structured evidence and credible external signals.
Should platform pages be published before examples exist?
No. Publish only after the page has platform-specific checks, executable steps and a real or complete example.
Does InsightWonder modify theme or template code?
No. Platform integrations use supported extension points rather than editing theme files directly.
Is a technical fix enough to get recommended?
Rarely. Access checks remove blockers, but whether a model names you still depends on clear content, structured evidence and credible external signals.
Can more than one site be connected?
Yes. Sites are separate measurement scopes under one account, so results stay comparable instead of being mixed together.
Turn AI visibility into a repeatable growth system.
Create a project, confirm your market and start measuring the questions that matter.