AEOCheck
Blog

By Ummar Ahmed

AEO Checklist for Webflow Developers: 12-Point Guide (2025)

The complete AEO checklist for Webflow developers. Covers schema markup, structured data, content structure, and technical signals that get Webflow sites cited in ChatGPT and Perplexity.

aeowebflowchecklistai-search
AEO checklist for Webflow developers - 10-step guide for AI search visibility

Webflow sites have a natural AEO advantage that most developers do not realize: the platform generates clean, semantic HTML with proper heading hierarchy and well-structured markup out of the box. That is more than many WordPress themes or custom builds can claim. AI engines can read Webflow pages clearly.

The gaps are not in the HTML. They are in three areas: missing structured data, content that is not formatted for AI extraction, and robots.txt settings that may be blocking AI crawlers. All three are fixable in an afternoon.

This checklist covers every change a Webflow developer needs to make - in order of impact - to go from invisible in AI search to reliably cited. Run a free AEO scan on your Webflow site first to see your current score and understand which items matter most for your specific site.

Not familiar with AEO yet? Read what is AEO and how it works before starting the checklist.

1. Fix Your robots.txt - Stop Blocking AI Crawlers

This is the most common mistake. Many Webflow sites accidentally block GPTBot, ClaudeBot, and PerplexityBot - the crawlers that power AI search results.

Check your robots.txt at yourdomain.com/robots.txt

You want to allow AI retrieval bots while optionally blocking training bots:

# Allow AI retrieval bots (these cite you in answers)
User-agent: ChatGPT-User
User-agent: PerplexityBot
User-agent: Applebot-Extended
Allow: /

# Optional: block training crawlers
User-agent: GPTBot
User-agent: CCBot
Disallow: /

Sitemap: https://yourdomain.com/sitemap.xml

In Webflow, go to Site Settings > SEO > Custom robots.txt and paste your updated rules.

What to check:

  • [ ] PerplexityBot is not blocked
  • [ ] ChatGPT-User is not blocked
  • [ ] ClaudeBot is not blocked (unless you want to block training)
  • [ ] Sitemap URL is included

2. Add an llms.txt File

llms.txt is a plain text file at your domain root that tells AI systems what your site does, who it is for, and where to find key pages. Think of it as a robots.txt for large language models.

Create a file at yourdomain.com/llms.txt with content like this:

# YourBrand

> One sentence describing what you do and who you help.

## What we do
2-3 sentences in plain English. No marketing speak.

## Who this is for
Specific user type - not a vague persona.

## Key pages
- https://yourdomain.com
- https://yourdomain.com/about
- https://yourdomain.com/pricing
- https://yourdomain.com/blog

Webflow-specific note: Webflow does not allow arbitrary file uploads at your domain root. The most reliable approach is to host the file at any public URL (a GitHub Gist, your own CDN, or an S3 bucket), then add a 301 redirect in Site Settings > Hosting > 301 Redirects pointing /llms.txt to that URL. Alternatively, create a Webflow page at /llms-txt with the content as plain text and redirect /llms.txt to it.

What to check:

  • [ ] /llms.txt exists and returns 200
  • [ ] Description is plain English, not marketing copy
  • [ ] Key pages are listed with full URLs

3. Add JSON-LD Schema Markup

AI engines use structured data to understand what your page is, who wrote it, and what it is about. Without schema, they are guessing - and guessing wrong hurts your citation chances.

Priority schema types for Webflow sites:

| Page type | Schema to add | |---|---| | Homepage | Organization, WebSite | | Blog post | Article, BreadcrumbList | | Service/product page | WebPage, FAQPage | | About page | Person or Organization |

Organization schema belongs in Site Settings: Unlike page-specific schema, your Organization block should load on every page. Add it to Site Settings > Custom Code > Head Code so it runs site-wide:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Your Brand",
  "url": "https://yourdomain.com",
  "description": "What you do in one sentence.",
  "logo": "https://yourdomain.com/logo.png"
}
</script>

For page-specific schema (Article, FAQPage, WebPage): go to Page Settings > Custom Code > Head Code and add the relevant block to each page type.

What to check:

  • [ ] Organization or WebSite schema on homepage
  • [ ] Article schema on all blog posts (with datePublished and dateModified)
  • [ ] FAQPage schema on any page with Q&A content
  • [ ] Validate using Google's Rich Results Test

4. Fix Your Meta Title and Description

AI engines read your meta title and description to understand what a page is about before crawling its full content. Short, vague titles hurt your AI visibility score significantly.

Targets:

  • Title: 30-60 characters, describes the page clearly
  • Description: 120-160 characters, answers "what will I find here?"

In Webflow: Page Settings > SEO Settings > Title Tag and Meta Description.

What to check:

  • [ ] Every page has a unique title
  • [ ] Title is 30-60 characters
  • [ ] Meta description is set (not left blank)
  • [ ] Description answers the page's core question

5. Add One H1 Tag Per Page

AI systems use heading structure to understand content hierarchy. Multiple H1s confuse the hierarchy. Missing H1s mean the page has no declared topic.

Webflow sometimes generates extra H1s when you use heading elements in multiple sections. Check your published page source.

What to check:

  • [ ] Exactly one H1 per page
  • [ ] H1 includes your primary topic keyword
  • [ ] H2s and H3s follow a logical hierarchy

6. Structure Content for Answer Extraction

AI engines extract 40-75 word chunks from pages to use as answers. If your content is written in long unbroken paragraphs, AI systems struggle to cite it accurately.

Answer-first format:

  • Open each section with a direct one-sentence answer
  • Follow with supporting detail
  • Use H2/H3 questions as section headers (e.g. "What is AEO?")
  • Add FAQ sections to any page that answers common questions

What to check:

  • [ ] Key pages open sections with direct answers
  • [ ] FAQ content exists on relevant pages
  • [ ] Content uses question-format headings where appropriate

7. Set Up Author and About Signals (E-E-A-T)

ChatGPT and Perplexity weigh trust signals heavily. Named authorship, About pages, and Contact pages all signal that a real entity stands behind the content.

What to check:

  • [ ] Blog posts have a named author with a bio
  • [ ] An About page exists and links from the main nav
  • [ ] A Contact page exists
  • [ ] Author pages include credentials or experience signals
  • [ ] datePublished and dateModified are set in Article schema

8. Add Open Graph Tags

OG tags are not just for social sharing - AI systems use them to extract page identity, images, and descriptions when structured data is missing.

In Webflow: Page Settings > Open Graph - set OG Title, OG Description, and OG Image for every key page.

What to check:

  • [ ] OG Title is set
  • [ ] OG Description is set
  • [ ] OG Image is set (1200x630px recommended)

9. Submit Your Sitemap

AI crawlers use your sitemap to discover pages efficiently. Webflow generates a sitemap automatically at yourdomain.com/sitemap.xml - but you need to make sure it is submitted and up to date.

What to check:

  • [ ] Sitemap exists at /sitemap.xml
  • [ ] Sitemap is referenced in robots.txt
  • [ ] Sitemap is submitted to Google Search Console
  • [ ] Sitemap is submitted to Bing Webmaster Tools (ChatGPT Search uses Bing's index)

10. Improve Core Web Vitals

AI engines and Google AI Overviews deprioritize slow pages. Page speed is a trust signal - if your site loads slowly, AI systems are less likely to cite it.

Targets:

  • LCP (Largest Contentful Paint): under 2.5s
  • CLS (Cumulative Layout Shift): under 0.1
  • TBT (Total Blocking Time): under 200ms

Common Webflow fixes:

  • Replace heavy Lottie animations with CSS or lightweight SVG
  • Use Webflow's built-in lazy loading on images
  • Avoid loading large third-party scripts in the <head>
  • Use system fonts or preload custom fonts

What to check:

  • [ ] LCP under 2.5s (test with PageSpeed Insights)
  • [ ] CLS under 0.1
  • [ ] No render-blocking scripts in <head>

11. Add FAQ Schema to Key Webflow Pages

FAQPage schema is the single highest-returning AEO fix for most Webflow sites. AI engines specifically parse FAQ structured data when selecting answer sources, and pages with FAQ schema are cited at significantly higher rates than equivalent pages without it.

In Webflow, add a Custom Code Embed component directly on the page in the Designer, or use Page Settings > Custom Code > Before </body>. Paste this JSON-LD and replace the placeholder questions with your actual content:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "What is [your topic]?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "A direct 2-3 sentence answer. Write it as a self-contained response that makes sense without any surrounding context."
      }
    },
    {
      "@type": "Question",
      "name": "How do I [common task your customers ask about]?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Your answer here. Keep it direct and specific."
      }
    },
    {
      "@type": "Question",
      "name": "What is the difference between [option A] and [option B]?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Your answer here."
      }
    }
  ]
}
</script>

Target your most important landing page, your pricing page, and any page that already has FAQ-style content. Aim for 3-7 question/answer pairs. Write each answer as a complete standalone response - a paragraph that only makes sense if you read the one above it is a paragraph that cannot be cited.

What to check:

  • [ ] FAQPage schema added to homepage, pricing page, and key service pages
  • [ ] Each answer is 2-4 sentences and self-contained
  • [ ] Questions match what customers actually search for
  • [ ] Validates cleanly in Google's Rich Results Test

12. Structure Webflow CMS Collections for AEO

Webflow's CMS gives you more AEO control than most platforms if you configure it correctly from the start.

Dynamic meta titles: In Page Settings for your CMS Collection template, reference the CMS item name or title field rather than using a static title. This ensures every blog post and collection item has a unique, specific title - a basic requirement that is frequently missed on Webflow CMS builds.

Rich text field structure: Inside your main rich text fields, apply the same answer-first structure used for static pages. Each major section should open with an H2 framed as a question, followed immediately by a direct 1-2 sentence answer, then supporting detail. AI engines extract from CMS rich text exactly as they do from any HTML page.

Dynamic Article schema on CMS templates: Use a custom code embed on your CMS Collection page template to inject dynamic Article schema. Webflow allows you to reference CMS fields inside embed code blocks:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "BlogPosting",
  "headline": "{{wf {\"path\":\"name\"} }}",
  "datePublished": "{{wf {\"path\":\"published-on\",\"type\":\"Date\",\"format\":\"YYYY-MM-DD\"} }}",
  "description": "{{wf {\"path\":\"post-summary\"} }}",
  "author": {
    "@type": "Person",
    "name": "{{wf {\"path\":\"author-name\"} }}"
  },
  "publisher": {
    "@type": "Organization",
    "name": "Your Brand"
  }
}
</script>

Replace post-summary and author-name with your actual CMS field slugs. This ensures every CMS page has properly attributed Article schema without manual per-page editing.

What to check:

  • [ ] CMS Collection templates have dynamic, unique meta titles using field references
  • [ ] Article schema on blog template references CMS field values
  • [ ] Rich text content uses H2 headings framed as questions
  • [ ] A summary or description field exists and is used in schema markup

Check Everything at Once

Going through this checklist manually takes hours. AEOCheck scans your Webflow site against all 25 AEO checks in under 60 seconds - including robots.txt, llms.txt, schema markup, meta tags, heading structure, E-E-A-T signals, and Core Web Vitals.

You get a prioritized action plan showing exactly what to fix first for the fastest improvement in AI visibility.

Run a free AEO scan on your Webflow site - no account required.

Once you have made these fixes, check if your site appears in ChatGPT and Perplexity to validate the results directly.

Quick Reference Checklist

Technical (do these first)

  • [ ] robots.txt allows PerplexityBot and ChatGPT-User
  • [ ] llms.txt exists at domain root
  • [ ] Organization schema in Site Settings > Custom Code
  • [ ] JSON-LD schema on all key pages
  • [ ] Sitemap submitted to Google and Bing

On-page

  • [ ] Meta title 30-60 characters on every page
  • [ ] Meta description set on every page
  • [ ] Exactly one H1 per page
  • [ ] OG tags set on key pages

Content and schema

  • [ ] Answer-first section structure
  • [ ] FAQ schema on homepage, pricing, and key service pages
  • [ ] Named author with bio on blog posts
  • [ ] About and Contact pages exist
  • [ ] CMS templates use dynamic Article schema

Performance

  • [ ] LCP under 2.5s
  • [ ] CLS under 0.1
  • [ ] No render-blocking scripts

Frequently Asked Questions

Can Webflow sites rank in AI search engines?

Yes - Webflow's clean semantic HTML is actually an advantage for AEO. The main gaps are usually missing structured data and content that is not structured as direct answers. Both are fixable with Webflow's custom code embeds.

How do I add schema markup to a Webflow site?

Use Webflow's custom code embed component (available on paid plans) to add JSON-LD script tags directly to any page. For site-wide schema like Organization, add it in Site Settings > Custom Code > Head Code. For page-specific schema, use Page Settings > Custom Code > Head Code.

Does Webflow automatically add structured data?

Webflow adds some basic meta tags but does not automatically generate JSON-LD structured data. FAQ schema, Article schema, and Organization schema all need to be added manually via custom code embeds or the Site Settings head code section.

What is the fastest AEO win for a Webflow site?

Adding FAQ schema to your most important pages. Create a JSON-LD script block in a custom code embed with your top 3-7 questions and answers. This alone can significantly improve AI citation rates, and it takes under an hour to implement on a live Webflow site.

How do I check my Webflow site's AEO score?

Run a free AEO scan on AEOCheck - paste your Webflow site URL and get a full AI visibility score with a prioritized list of issues in under 60 seconds. No account required for the baseline scan.