Report · Pre-launch reference · Updated 22 June 2026

The Ultimate Webflow SEO & AEO Checklist

Q: What is the difference between SEO and AEO?

SEO (Search Engine Optimization) gets your pages to rank in a list of blue links on Google. AEO (Answer Engine Optimization) gets your content selected and cited inside an AI-generated answer in ChatGPT, Perplexity, or Google AI Overviews. They overlap heavily — nearly every AEO practice also improves classic SEO — but AEO shifts the unit of optimisation from the page to the individual, independently-citable fact.

Q: What is the most important Webflow SEO setting before launch?

Disabling Webflow subdomain (staging) indexing. In Site settings → SEO → Indexing, toggle it on so the your-site.webflow.io staging copy is not indexed as duplicate content competing with your live domain. It is one switch and the single most-missed Webflow launch step.

Q: How do I get my Webflow site cited by AI like ChatGPT and Perplexity?

Write answer-first content, structure it in self-contained chunks with question-style headings, and add schema — especially FAQPage and Organization JSON-LD with sameAs links. FAQ and Q&A markup is among the highest-value schema types for AI answer engines because it hands them a ready-made question-and-answer pair. Keep every schema fact visible on the page, and remember authority and links still matter more than markup alone.

Q: Does Webflow handle SEO automatically?

Partly. Webflow auto-generates a sitemap and self-referencing canonicals, serves responsive images and SSL, and gives you fields for titles, meta descriptions, slugs, and Open Graph. But the high-impact work — keyword mapping, one H1 per page, clean heading hierarchy, internal linking, performance, and schema — is on you. This checklist covers all of it.

Q: How long does it take to see SEO results from a new Webflow site?

Typically three to six months for a new site to build enough trust and indexing history to rank for competitive terms, though AEO citations and long-tail rankings can come sooner. A checklist makes you technically eligible to compete quickly; durable rankings still need useful content, internal links, and earned mentions over time.

Q: Is FAQ schema still worth adding in 2026?

Yes — but for AEO rather than classic rich results. Google reduced FAQ rich snippets in regular search, but FAQPage markup remains one of the strongest on-page signals for AI answer engines: it hands them a ready-made question-and-answer pair in their native format, which is easy to extract and cite. The magnitude varies by study, but the direction is consistent across the research.

Ship a site that ranks on Google and gets cited by AI. This is a page-by-page pre-launch checklist for a Webflow project, organised into seven phases and ordered roughly by when you do the work. Every item is rated by impact (how much it moves rankings and visibility) and effort (how hard it is in Webflow) — and for each you get the what, the how on Webflow, and the why. The final phase covers AEO: the structural and schema work that gets you surfaced in ChatGPT, Perplexity, and Google AI Overviews.

7: Phases, strategy through AEO
52: Items, rated by impact & effort
82%: Higher click-through for pages that win rich results Google case study (Nestlé)
58%: Lower click-through at position 1 when an AI Overview shows Ahrefs, 2025

Mindset

How to use this checklist

Impact is the ranking and visibility payoff. Effort is the work to implement it in Webflow. Chase the top-left quadrant first: high impact, low effort. Check items off as you go — your progress is saved in this browser, so you can close the tab and pick up where you left off.

Effort scale — Super easy (a toggle) · Easy (a few minutes per page) · Medium (setup and judgement) · High (ongoing or design-wide).

Work the phases in order. Phases 1–2 are foundation; 3–5 are per-page; 6 is launch day; 7 is AEO. For a page-by-page review, run Phases 3–4 (on-page and content) and 7 (AEO) against every page before you publish.

The honest truth: a checklist gets you technically sound, not to #1. Ranking still needs genuinely useful content, good page experience, and links and mentions earned over time. Two factors carry outsized weight — relevant internal linking and full page renderability. Everything here makes you eligible to compete; it does not win the race on its own.

Critical — Site can lose rankings or fail to index without it. Do not launch without these.
High — Meaningful, durable ranking and visibility gains.
Medium — Solid best practice; compounding value over time.
Low — Polish and edge-case coverage; nice to have.

Strategy & Keyword Foundation

Decide what each page is for before you build it.

Decide what each page is trying to rank for before you write a word of copy.

What: A spreadsheet of target terms, each assigned to exactly one page, prioritised by search volume versus keyword difficulty. Keywords are the bridge between what users type and what your page is about.
How: Brainstorm money keywords (commercial and transactional intent), check volume in Google Keyword Planner, Ahrefs, or Semrush, then assign one primary keyword per URL plus a few secondary variations.
Why: Mapping one keyword per page prevents keyword cannibalisation, where two of your own pages compete for the same term and split their ranking strength.

Every important page should be reachable within three clicks of the homepage.

What: A flat hierarchy — Home → Category → Page — with clear parent/child relationships and a primary nav of only the 6–7 most important destinations.
How: Sketch the sitemap before building. Group pages into logical folders and CMS Collections in Webflow, and keep the primary nav tight; push everything else into the footer.
Why: Shallow structures spread link equity efficiently and let crawlers find and index every page. Deep, buried pages get crawled less and rank worse.

Confirm the page type fits what searchers actually want for that query.

What: The right format for the query: informational queries → guide or blog; commercial → comparison or landing page; transactional → product or pricing.
How: Google your target keyword and look at what already ranks. If the top 10 are all how-to guides, a sales page will not break in — build the format that is winning.
Why: Intent mismatch is the most common reason good content never ranks. Search engines reward the format that satisfies the query.

Technical Foundation (Site-Wide)

Set up once, correctly. These gate everything else.

Stop Google from indexing the your-site.webflow.io staging subdomain.

What: A noindex rule on the Webflow subdomain so only your real domain gets indexed.
How: Site settings → SEO tab → under Indexing, toggle Disable Webflow subdomain indexing to ON, then publish.
Why: If the staging copy is indexed you create duplicate content competing with your live site, diluting rankings. This is the single most-missed Webflow launch step.

Run on your own domain and pick one canonical host.

What: A custom domain connected, with one version (e.g. www) set as the default and the other redirecting to it.
How: Site settings → Publishing → add your domain, point the DNS records as instructed, then set the default domain — Webflow auto-redirects the other.
Why: Serving the same content at both www and non-www splits authority. Consolidating to one preserves it and prevents duplicate-content signals.

Serve every page over an encrypted HTTPS connection.

What: A valid SSL certificate so the browser shows the padlock and never a Not Secure warning.
How: On Webflow-hosted sites SSL is on by default — just confirm Enable SSL is checked in Publishing settings.
Why: HTTPS is a confirmed ranking signal, and browsers actively warn users away from insecure pages, killing trust before the page even loads.

Give crawlers a machine-readable map of every page.

What: A /sitemap.xml file listing all indexable URLs.
How: Site settings → SEO → Sitemap → toggle Auto-generate sitemap ON, save, publish. Verify it loads at yourdomain.com/sitemap.xml.
Why: Sitemaps speed up discovery and indexing, especially for a brand-new site with no backlinks pointing crawlers to your pages yet.

Tell crawlers what they may and may not crawl.

What: A robots.txt file allowing your public pages and (optionally) blocking utility pages, with a link to your sitemap.
How: Site settings → SEO → Robots.txt. To allow everything, use User-agent star on one line and an empty Disallow on the next.
Why: A misconfigured Disallow can de-index your entire site. Double-check this before launch — it is a common catastrophic mistake.

robots.txt — allow all, point to sitemap

User-agent: *
Disallow:

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

Declare the official version of each URL.

What: A canonical link tag pointing to the preferred URL when similar content could exist at multiple addresses.
How: Webflow auto-adds self-referencing canonicals; for custom needs add a global canonical in Site settings → SEO, or a per-page custom canonical in page settings.
Why: Canonicals consolidate ranking signals onto one URL and resolve duplicate-content ambiguity (e.g. URL parameters or paginated CMS pages).

Self-referencing canonical in the page head

<link rel="canonical" href="https://yourdomain.com/page" />

Declare the human language of your content.

What: The lang attribute on the html element (e.g. lang="en").
How: Site settings → General → Localization → enter your 2-letter language code, save, publish.
Why: It tells search engines, browsers, and screen readers what language to expect, improving accessibility and right-region targeting.

Give your site a recognisable browser-tab and bookmark icon.

What: A 32×32px favicon and a 256×256px webclip (touch) icon.
How: Site settings → General → Icons → upload both, publish, and hard-refresh to see it.
Why: Favicons appear next to your title in search results and tabs, reinforcing brand recognition and click-through.

Catch broken links with a helpful, navigable error page.

What: A branded 404 page with search, primary nav, and links back to key pages.
How: Webflow has a built-in 404 template — design it like any other page under the special Utility pages section.
Why: Good 404s keep users on-site instead of bouncing, and stop dead ends from wasting crawl budget.

On-Page SEO (Run Per Page)

Repeat these for every page before you publish it.

Every page needs its own keyword-led title under ~60 characters.

What: The title tag — the clickable blue line in search results.
How: Page settings → SEO settings → Title Tag. Lead with the primary keyword, keep it under 60 characters so it does not truncate.
Why: The title is the strongest on-page relevance signal and the biggest driver of click-through from the results page.

Summarise the page in 150–160 characters with the keyword and a reason to click.

What: The meta description snippet shown under the title in results.
How: Page settings → SEO settings → Meta Description. Make each one unique; use action-oriented language.
Why: It does not directly rank you, but a strong description lifts CTR — and higher CTR is itself a positive signal.

One clear H1 that states the page's topic and includes the primary keyword.

What: The H1 heading — the main on-page title.
How: In Webflow, select your main heading element and set its tag to H1 in the element settings. Use H1 only once.
Why: The H1 confirms the page topic to crawlers. Multiple H1s or a missing one muddies the relevance signal.

Nest headings in order — never skip levels or use a heading just for big text.

What: H1 → H2 (sections) → H3 (subsections), with keyword variations in your H2s.
How: Set the correct tag on each heading element via the tag dropdown; never style a paragraph to look like a heading.
Why: The hierarchy is how crawlers and screen readers understand your content's structure — and it is a major input for AEO chunking (Phase VII).

Short, descriptive, hyphenated slugs that include the keyword.

What: A slug like /webflow-seo-checklist — 3–5 words, hyphens not underscores, no stop words, under ~75 characters.
How: Page settings → edit the Slug field. For CMS items, set a clean slug pattern in the Collection.
Why: Keyword-rich URLs reinforce relevance and read more clearly in results, lifting CTR. If you change a slug later, always add a 301.

Get the primary keyword into the first 100–150 characters of body copy.

What: A natural, early mention of the term in the intro.
How: Write the first sentence to directly state what the page is about, keyword included — no throat-clearing windup.
Why: Both search crawlers and AI answer engines weight the opening heavily when judging relevance and extracting answers.

Describe the image's purpose in ≤125 characters, with keywords where natural.

What: The alt attribute — e.g. "Webflow SEO settings panel showing the sitemap toggle," not "screenshot."
How: Select the image → Settings → Alt Text. For bulk CMS work, an app like FlowSEO can generate alt text at scale.
Why: Alt text powers image search, gives screen-reader users context, and provides fallback text if an image fails to load.

Control how each page looks when shared on social and in chat apps.

What: OG tags that drive the preview card on LinkedIn, X, Facebook, Slack, and iMessage.
How: Page settings → Open Graph settings. Set a unique title, description, and a 1200×630px image per page (OG cannot be set globally).
Why: Polished share previews lift click-throughs on social, an increasingly important discovery and link-earning channel.

Build sections with meaningful tags instead of generic divs everywhere.

What: Real landmarks instead of div soup — header (intro/logo/nav area), nav (menus), main (the one unique body), article (a blog post or CMS item), section (each thematic block), aside (sidebars, related links), and footer (legal, sitemap).
How: Select a Section, Container, or Div Block → in element settings use the Tag dropdown to assign the correct HTML5 tag. No code required.
Why: Semantic tags tell crawlers and screen readers what each region is (versus an undifferentiated soup of divs), which improves accessibility, indexing, and — critically — how cleanly AI engines parse and cite your page.

What clean semantic structure looks like

<header> … logo + nav … </header>
<main>
  <article>
    <h1>Page title</h1>
    <section> … </section>
    <section> … </section>
  </article>
  <aside> … related links … </aside>
</main>
<footer> … legal + sitemap … </footer>

Link each page to related pages using keyword-rich, descriptive anchors.

What: Contextual links like "see our Webflow SEO checklist" — never "click here."
How: Add text links in rich-text and link blocks; deliberately point to your most important money pages.
Why: Internal linking is one of the two highest-leverage technical SEO factors — it spreads authority and tells engines which pages matter most.

Keep your site open when sending users to third-party pages.

What: target="_blank" on outbound links (Webflow adds rel="noopener" automatically).
How: Select the link → Settings → check Open in new tab.
Why: It preserves the session and engagement on your page; also review outbound links periodically so you are not linking to sites that have gone bad.

Performance & Core Web Vitals

Fast pages rank better and convert better.

Ship the smallest possible image files in modern formats.

What: Compressed images served as WebP or AVIF instead of heavy JPEG/PNG.
How: Pre-compress with TinyPNG or ImageOptim, then use Webflow's built-in image conversion tool to convert assets (and CMS images) to WebP/AVIF in bulk.
Why: Images are usually the heaviest thing on a page; shrinking them is the fastest win for load speed and the LCP metric.

Defer off-screen images; load the above-the-fold hero immediately.

What: loading="lazy" on below-fold images, loading="eager" on the hero.
How: Webflow lazy-loads by default; for your main hero image, switch the loading setting to Eager in image settings.
Why: Lazy-loading cuts initial page weight; eager-loading the hero prevents a slow, janky LCP for the first thing users see.

Strip whitespace and comments from your code on publish.

What: Minified asset files that download faster.
How: Site settings → Publishing → toggle on minification for HTML, CSS, and JavaScript. Three switches, done.
Why: Smaller files mean faster render and better Core Web Vitals — essentially free performance.

Don't let third-party scripts block the page from rendering.

What: defer or async on custom and embed scripts (analytics, chat widgets, and the like).
How: Add defer to script tags in custom code; load non-essential widgets after the main content.
Why: Render-blocking scripts delay both LCP and INP. Deferring them keeps the page interactive faster.

Defer a non-critical script

<script src="/widget.js" defer></script>

Limit custom font weights and serve them efficiently.

What: A small set of font weights with sensible fallback behaviour (font-display: swap).
How: Use only the weights you actually need; host fonts via Webflow; avoid loading many custom families.
Why: Heavy or render-blocking fonts cause layout shift (CLS) and slow text paint.

Give images, embeds, and ads explicit dimensions so the page doesn't jump.

What: Defined width/height (or aspect ratio) on media; no content injected above existing content after load.
How: Set sizing on image and embed elements; size background images appropriately; avoid late-loading banners that push content down.
Why: Cumulative Layout Shift under 0.1 is a Core Web Vital; jumpy layouts frustrate users and hurt the score.

Serve appropriately-sized images per device.

What: srcset / sizes so phones get small images and desktops get large ones.
How: Webflow generates responsive variants automatically on upload — nothing to do, just verify in dev tools that variants are being served.
Why: It can make mobile pages load several times faster by not shipping desktop-size images to phones.

Clean out orphaned styles before launch.

What: Removal of classes no element uses anymore.
How: In the Style Selectors panel, click the broom icon → Remove unused classes.
Why: Less CSS means a lighter, faster-parsing stylesheet.

Launch Day & Verification

The pre-publish pass that catches ranking-killers.

Catch missing titles, alt text, and structure issues before publishing.

What: A pre-publish audit pass on every page.
How: Use Webflow's Audit panel in the Designer (and/or an app like AI SEO Copilot or FlowSEO) → review → fix → re-run.
Why: It is the cheapest way to catch the silly, ranking-killing omissions a human reviewer misses.

No broken links, no dead ends.

What: Confirmation that all internal links point to live pages.
How: Crawl with Screaming Frog (or a sitemap-based URL checker) and fix any 404s before launch.
Why: Broken links waste crawl budget, leak authority, and frustrate users.

Permanently redirect old URLs to new ones if you're migrating or changed slugs.

What: 301 redirect rules from every old URL to its new equivalent.
How: List old URLs (Screaming Frog), list new URLs, then add rules in Site settings → Publishing → 301 Redirects.
Why: 301s carry over the link equity of old pages and stop visitors hitting 404s — essential on any migration.

Claim your site so you can monitor indexing and performance.

What: A verified property in GSC and Bing Webmaster Tools.
How: Add the verification meta into Site settings → SEO → head code (or use the built-in GSC field), publish, then verify. Repeat for Bing.
Why: Search Console is your direct line to Google — index status, errors, queries, and AI/search performance all live here.

Tell the engines exactly where your sitemap lives.

What: Sitemap URL submitted in both consoles.
How: GSC → Sitemaps → enter sitemap.xml → Submit. Same in Bing Webmaster Tools.
Why: It triggers faster crawling and indexing of a brand-new site that has no inbound links yet.

Start collecting behaviour data from day one.

What: GA4 (and optionally a cookieless tool like Plausible or Cloudflare Web Analytics) tracking installed — often via Google Tag Manager.
How: Paste the tracking or GTM snippet into Site settings → Custom Code → Head, save, publish.
Why: You cannot improve what you do not measure — and you will want a baseline before traffic arrives.

Benchmark Core Web Vitals on key pages and fix the worst offenders.

What: Lighthouse/PageSpeed Insights scores for LCP (<2.5s), INP (low), CLS (<0.1).
How: Run pagespeed.web.dev on your homepage and top templates; act on the flagged opportunities.
Why: Core Web Vitals are a confirmed ranking input and a direct proxy for user experience.

Disambiguate similar pages and language variants.

What: Canonical tags for near-duplicates; hreflang tags for language/region variants.
How: Use Webflow Localization for multilingual sites (it handles hreflang); add canonicals where content overlaps across subdomains.
Why: Duplicate content splits and confuses ranking signals; hreflang serves the right language version to the right audience.

AEO — Get Cited by AI Answer Engines

Optimise so ChatGPT, Perplexity, and Google AI Overviews select and cite you.

Lead every section with a direct, 40–60 word answer to the question its heading implies.

What: The inverted pyramid — answer first, supporting detail after. Definitions in extractable form: "[Term] is [clear definition]."
How: Write each H2 so its first sentence answers the heading; cut windup intros like "In today's landscape…".
Why: AI engines extract the first 1–2 sentences of a section to decide if it answers the query. Vague openings get skipped for a competitor's.

One concept per section, 200–400 words, with descriptive question-style headings.

What: Semantic chunking — do not mix a definition with a how-to in the same block; give each fact its own structural home.
How: Use clear H2/H3s (questions work well), bullets and numbered lists for processes, comparison tables for evaluations, and a table of contents.
Why: Answer engines parse by section, not by page. Self-contained sections are far more likely to be lifted and cited.

One of the highest-value, lowest-effort AEO moves you control on-page.

What: A visible FAQ on the page, mirrored in FAQPage JSON-LD. Phrase questions the way people ask an assistant ("how much", "how long", "can I"); keep each answer 40–70 words. FAQ and Q&A markup is consistently ranked among the highest-value schema types for AI answer engines, and an empirical cross-platform study found structured data is associated with higher AI-citation rates (Fischman, 2025) — though, in honesty, domain authority and links still matter more than markup alone.
How: Build the visible FAQ as content, then paste the JSON-LD into Page settings → Custom Code → Head (or an Embed).
Why: FAQ pairs map exactly to how people query AI. The markup hands the engine a ready-made question-and-answer in its native format — minimal interpretation, maximum citation odds.

FAQPage JSON-LD

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [{
    "@type": "Question",
    "name": "How do I improve SEO on a Webflow site?",
    "acceptedAnswer": {
      "@type": "Answer",
      "text": "Set unique meta titles and descriptions, one keyword-led H1 per page, clean semantic structure, fast images, and add FAQPage schema."
    }
  }]
}
</script>

Define your business as a single, verifiable entity.

What: Organization JSON-LD on the homepage with name, url, logo, contactPoint, and a sameAs array linking your LinkedIn, Crunchbase, Wikidata, and social profiles.
How: Paste the JSON-LD into Site settings → Custom Code → Head (so it loads site-wide).
Why: sameAs lets engines confirm you are one real entity across independent sources — the foundation of entity clarity that makes AI confident enough to name you.

Organization JSON-LD

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Your Studio",
  "url": "https://yourdomain.com",
  "logo": "https://yourdomain.com/logo.png",
  "sameAs": [
    "https://www.linkedin.com/company/your-studio",
    "https://www.instagram.com/your-studio"
  ]
}
</script>

Match schema type to page type.

What: Article or BlogPosting on posts, Product + Offer on shop pages, BreadcrumbList for hierarchy, LocalBusiness on contact/location pages.
How: For CMS Collections, build the JSON-LD in an Embed inside the template and bind fields to CMS values so each item gets correct markup automatically.
Why: Typed markup makes facts (author, date, price, stock, address) machine-readable and unlocks rich results — and Google's own case studies report higher click-through for rich-result pages (Nestlé measured an 82% higher CTR; Rotten Tomatoes, 25%).

BlogPosting JSON-LD (bind the bracketed fields to CMS)

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "BlogPosting",
  "headline": "[Post title]",
  "datePublished": "[Published date]",
  "author": { "@type": "Person", "name": "[Author]" }
}
</script>

Every fact in your schema must appear in the visible page content — no exceptions.

What: An exact match between JSON-LD and on-page content (founding date, price, FAQ answers, and so on).
How: Validate with Google's Rich Results Test and the Schema.org validator before publishing; re-check after CMS edits.
Why: Mismatched schema (a price not on the page, an FAQ answer that differs) is a Google policy risk and erodes machine trust — and some AI engines read only the visible HTML anyway.

Back claims with specific numbers and consistent terminology.

What: A concrete statistic every ~150–200 words, linked to the original source; consistent naming of your brand and key terms; mentions of related entities (e.g. Google, ChatGPT, Perplexity) for semantic context.
How: Cite .gov/.edu/industry sources, use exact figures not "significant growth," and keep your terminology consistent throughout.
Why: AI engines favour specific, well-sourced, entity-clear content and recently-updated pages — they cite content that is easy to trust and attribute.

Priority

The Do-First Shortlist

If you only do ten things, these are the highest impact-to-effort moves across the whole list. Knock these out first, then work the rest by phase.

Disable Webflow subdomain indexing (#4) — critical, one toggle.
Unique meta title + description per page (#13, #14).
One keyword-led H1 + logical heading hierarchy (#15, #16).
Keyword-rich slugs (#17).
Enable sitemap + submit to Search Console (#7, #42).
Compress images to WebP/AVIF + minify code (#24, #26).
Mobile-test every page (#32).
Internal links with descriptive anchors (#22).
FAQ section with FAQPage schema (#48) — your top AEO lever.
Organization schema with sameAs (#49).

After launch

SEO and AEO are ongoing, not one-time. Monitor Search Console weekly for index/coverage errors, keep content fresh (AI engines favour recently-updated pages), publish useful new pages on a cadence, earn backlinks and third-party mentions, and re-run Lighthouse after any major design change.

Questions

Frequently asked questions

What is the difference between SEO and AEO?

SEO (Search Engine Optimization) gets your pages to rank in a list of blue links on Google. AEO (Answer Engine Optimization) gets your content selected and cited inside an AI-generated answer in ChatGPT, Perplexity, or Google AI Overviews. They overlap heavily — nearly every AEO practice also improves classic SEO — but AEO shifts the unit of optimisation from the page to the individual, independently-citable fact.

What is the most important Webflow SEO setting before launch?

Disabling Webflow subdomain (staging) indexing. In Site settings → SEO → Indexing, toggle it on so the your-site.webflow.io staging copy is not indexed as duplicate content competing with your live domain. It is one switch and the single most-missed Webflow launch step.

How do I get my Webflow site cited by AI like ChatGPT and Perplexity?

Write answer-first content, structure it in self-contained chunks with question-style headings, and add schema — especially FAQPage and Organization JSON-LD with sameAs links. FAQ and Q&A markup is among the highest-value schema types for AI answer engines because it hands them a ready-made question-and-answer pair. Keep every schema fact visible on the page, and remember authority and links still matter more than markup alone.

Does Webflow handle SEO automatically?

Partly. Webflow auto-generates a sitemap and self-referencing canonicals, serves responsive images and SSL, and gives you fields for titles, meta descriptions, slugs, and Open Graph. But the high-impact work — keyword mapping, one H1 per page, clean heading hierarchy, internal linking, performance, and schema — is on you. This checklist covers all of it.

How long does it take to see SEO results from a new Webflow site?

Typically three to six months for a new site to build enough trust and indexing history to rank for competitive terms, though AEO citations and long-tail rankings can come sooner. A checklist makes you technically eligible to compete quickly; durable rankings still need useful content, internal links, and earned mentions over time.

Is FAQ schema still worth adding in 2026?

Yes — but for AEO rather than classic rich results. Google reduced FAQ rich snippets in regular search, but FAQPage markup remains one of the strongest on-page signals for AI answer engines: it hands them a ready-made question-and-answer pair in their native format, which is easy to extract and cite. The magnitude varies by study, but the direction is consistent across the research.

Why we made this

About this checklist

We build Webflow sites at Milk Moon Studio, and we run this list against every project before it goes live. It started as our internal pre-launch QA — so it is opinionated, Webflow-specific, and ordered the way we actually work, rather than a generic list of tags.

It is a synthesis, not a scoop. We pulled together Webflow's own SEO guidance, well-established technical-SEO practice, and current AEO research, then reorganised it into a prioritised, page-by-page workflow you can tick off. The references below are credited in full — the parts worth reading in their original form are linked, and where we quote a statistic we link the primary source.

A note on honesty: much of AEO is still new and the numbers move. Where a figure is well-evidenced we cite it; where the field is genuinely uncertain, we say so rather than dress a blog estimate up as fact. If you spot something out of date, tell us — this is a living document.

Credited in full

References & further reading

The research behind the numbers

Ahrefs — AI Overviews reduce clicks by 58% (2025 update) Source for the 58% lower CTR at position 1 when an AI Overview appears (300k-keyword study).
Google Search Central — Intro to structured data (case studies) Google's own case studies: Nestlé 82% higher CTR and Rotten Tomatoes 25% higher CTR for rich-result pages.
Fischman — Does schema markup predict AI citation? (SSRN, 2025) Cross-platform empirical study associating structured data with higher AI-citation rates.
Pew Research Center — Google users click less with AI summaries Corroborates the AI-Overview click decline (8% click-through with an AI summary vs 15% without).

Webflow & SEO references

Webflow University — SEO checklist Webflow's official SEO guidance and settings reference.
Webflow Blog — Technical SEO
Webflow Blog — SEO checklist for site migration
Sofian Bettayeb — Webflow SEO Checklist A thorough community Webflow SEO reference.
Semrush — Technical SEO checklist
DashThis — Technical SEO checklist

The Ultimate Webflow SEO & AEO Checklist

How to use this checklist

Build a keyword list and map one primary keyword per page

Plan a shallow, logical site structure

Match each page to search intent

Disable Webflow subdomain (staging) indexing

Connect a custom domain and set the www / non-www default

Confirm HTTPS / SSL is enabled

Enable the auto-generated XML sitemap

Configure robots.txt

Set a global canonical URL strategy

Set the site language code (ISO)

Add a favicon and webclip (touch) icon

Set up a useful custom 404 page

Write a unique meta title with the keyword

Write a compelling meta description

Use exactly one H1 per page, containing the keyword

Build a logical heading hierarchy (H1–H6)

Put the keyword in the URL slug

Front-load the keyword in the opening paragraph

Add descriptive alt text to every meaningful image

Set Open Graph title, description, and image per page

Use HTML5 semantic tags for page structure

Add internal links with descriptive anchor text

Set external links to open in a new tab where appropriate

Compress images and convert to WebP / AVIF

Lazy-load below-the-fold media, eager-load the hero

Enable CSS, JS, and HTML minification

Defer / async non-critical JavaScript

Optimise fonts and reduce font-loading time

Reserve space for media to prevent layout shift (CLS)

Confirm responsive images (srcset) are working

Delete unused CSS classes and interactions

Make the site fully responsive and mobile-tested

Use touch-friendly tap targets

Design clear, simple navigation

Ensure sufficient colour contrast (WCAG AA)

Support keyboard navigation and ARIA landmarks

Keep animations simple and respect reduced-motion

Run Webflow's built-in SEO & accessibility audit

Verify every internal link resolves

Map 301 redirects for any changed URLs

Verify in Google Search Console & Bing Webmaster Tools

Submit your sitemap to Google and Bing

Install analytics (GA4 and/or a privacy-first tool)

Run a Lighthouse / PageSpeed pass

Handle duplicate content & hreflang (if multilingual)

Write answer-first content

Structure content in self-contained chunks

Add an FAQ section with FAQPage schema

Add Organization schema with sameAs links

Add Article, Product, BreadcrumbList & LocalBusiness schema where relevant

Enforce schema-content parity and validate