Free Webflow SEO audit. Find dynamic page sitemap gaps, CMS thin content, missing schema, AI crawler blind spots, and FAQPage markup your embed code skips.
Run Free Audit →No credit card required · Results in under 2 minutes
Webflow's SEO panel is a clean interface for controlling titles, meta descriptions, and Open Graph images. It does not tell you whether your CMS collection pages have thin content getting indexed, whether your JavaScript-dependent navigation is actually crawlable, or whether any AI assistant on the internet can read your site. These gaps are structural — they exist at the infrastructure level, below what any in-product panel can surface.
seo.yatna.ai crawls your published Webflow site from the outside, following links, evaluating rendered HTML, parsing embed-code schema, and scoring your site across 7 categories. The result is the audit your Webflow SEO panel is unable to run on itself.
Dynamic pages not generating sitemap entries — Webflow's auto-generated sitemap includes static pages and CMS collection items — but only if the collection is published and the page template is set to "indexable." Collection items filtered out of the sitemap by Webflow's settings are also excluded from Google's discovery queue, even if they're publicly accessible.
CMS collection items with thin content indexed — Webflow CMS is commonly used for case studies, team members, and job listings. Pages with fewer than 300 words of unique content — or templates where 80% of the content is boilerplate — are treated as thin pages by Google and can drag down site-wide quality scores.
JavaScript-dependent navigation not crawlable — Webflow's interactions and animation system can hide navigation elements inside JavaScript-triggered states. If your primary navigation only appears after a scroll trigger or a mouseover event, Googlebot — which executes JavaScript but doesn't simulate user interaction — may not crawl those links.
Schema markup only via embed code — most sites skip it — Webflow has no native schema builder. Adding JSON-LD requires embedding a <script> block in the page's custom code section. The majority of Webflow sites have no schema at all, missing eligibility for FAQ rich results, breadcrumb trails, article features, and AI citation sources.
No llms.txt support out of the box — llms.txt is an emerging standard for telling AI crawlers which pages are authoritative and safe to cite. Webflow has no native mechanism to serve a file at /llms.txt. Sites that want AI visibility need to either use Webflow's file hosting or proxy the file through a CDN.
Webflow's default robots.txt doesn't address AI crawlers — The default Webflow robots.txt allows all crawlers with a wildcard User-agent: * Allow rule. While this technically permits AI crawlers, it provides no explicit guidance on which pages are high-value for AI citation, and doesn't set Crawl-delay rules for crawlers that don't respect rate limits.
Image alt text uses filename, not descriptive text — Webflow serves images in WebP format and does image CDN optimization automatically. However, if alt text is left blank in the CMS or asset manager, the rendered HTML uses the filename (IMG_4521.webp) as the alt attribute — which is meaningless to screen readers and image search crawlers.
/admin or staging paths accidentally indexed — Webflow staging URLs (yoursite.webflow.io) are supposed to be blocked by Webflow's default robots settings, but custom domain redirects configured incorrectly can sometimes expose staging content. The audit checks whether staging URLs or internal admin paths resolve publicly.
Form pages without noindex creating duplicate paths — Webflow form confirmation pages (often at /thank-you or /form-success) contain minimal content. Without a noindex directive, these pages consume crawl budget and may be indexed as thin content.
No built-in FAQPage or HowTo schema generation — FAQPage schema is among the highest-impact schema types for driving rich results in Google Search. Webflow's native accordion and FAQ components generate clean HTML but no accompanying JSON-LD. Every FAQ section on your site is invisible to rich result eligibility without custom embed code.
seo.yatna.ai scores your Webflow site across 7 weighted categories:
robots.txt AI crawler directives, llms.txt availability, schema fields eligible for AI citationA Webflow marketing site with 40 static pages and a 60-item CMS blog collection typically returns results like this:
| Category | Score | Key Finding |
|---|---|---|
| E-E-A-T | 60/100 | No Organization schema, no author schema on posts |
| Technical SEO | 66/100 | 14 CMS items below 300-word threshold |
| On-Page SEO | 72/100 | Form confirmation pages indexed (3 pages) |
| Schema | 28/100 | No JSON-LD found on any page |
| Performance | 75/100 | LCP acceptable, minor CLS from hero animation |
| AI Readiness | 35/100 | No llms.txt, robots.txt has no AI-specific rules |
| Images | 58/100 | 22 CMS images using filename as alt text |
| Overall | 59/100 | 16 actionable issues found |
Can the audit detect issues inside Webflow CMS collection templates? Yes. seo.yatna.ai crawls each published CMS collection item as a unique URL. It evaluates the rendered output of your template — not the template itself — so it catches issues that only appear on specific items (missing fields, thin content, broken embeds).
Webflow says it handles SEO automatically. What does that mean in practice? Webflow automatically generates a sitemap, sets canonical tags on static pages, serves images via CDN in WebP format, and provides an SEO settings panel per page. It does not generate schema, validate that schema is correct, check AI crawler configuration, audit CMS item content quality, or measure site-wide Core Web Vitals.
How do I add JSON-LD schema to a Webflow page?
In Webflow's Page Settings, scroll to "Custom Code" and paste your JSON-LD <script type="application/ld+json"> block in the <head> section. For CMS-driven schema, you can inject dynamic field values using Webflow's embed component inside the collection template.
Does the audit work on Webflow's webflow.io staging domain?
It works, but we recommend auditing your published custom domain. The staging domain has its own robots.txt controlled by Webflow that may noindex all pages — auditing it will show a blocked-crawl result rather than your real SEO state.
See what's below the SEO panel. Thin CMS content, missing schema, AI crawler access, and Core Web Vitals — all in one audit.
Audit My Webflow Site — Free →
Related reading:
7 AI agents. 7 audit categories. One score. Free for your first audit.
Run Free Audit →