What should you check before launching a Webflow site?
A free learning resource from Milk Moon Studio: the checks we run through before any Webflow site launches, with the how-to for each. Work through it to learn the craft. Scan a page any time to see what a machine sees, and if you'd rather we took it on, book a call.
Some of this a scanner can check and some only a person can judge. Where Bot Appétit measures an item, we say so, and link to what it measures.
After launch. SEO and AEO are ongoing, not one-time. Watch Search Console for indexing errors, keep content fresh (AI engines favour recently updated pages), publish useful new pages on a cadence, earn links and mentions, and re-run a performance check after any major design change.
How to read it
Every item carries two ratings of our own. Impact is how much it matters to how search engines and AI answer engines see the site; effort is the work to do it in Webflow. Start with high impact and low effort. They are the checklist's ratings, not Bot Appétit's scoring.
Impact: Critical
The site can drop out of search or fail to be indexed without it. Don't launch without these.
Impact: High
Meaningful, lasting gains in how the site is found and read.
Impact: Medium
Solid practice; its value builds over time.
Impact: Low
Polish and edge cases; nice to have.
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 I–II are foundation; III–V are per-page; VI is launch day; VII is AEO. For a page-by-page review, run Phases III–IV and VII against every page before you publish it.
The honest truth: a checklist gets you technically sound, not to the top. Being found and cited still needs genuinely useful content, a good page experience, and links and mentions earned over time. Everything here makes you eligible to compete; it doesn't win the race on its own.
▼
Phase I
Strategy & keyword foundation
3 items
Decide what each page is for before you build it.
Impact: High Effort: Medium
Decide what each page is trying to rank for before you write a word of copy.
How to do it
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.
Impact: High Effort: Medium
Every important page should be reachable within three clicks of the homepage.
How to do it
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.
Impact: High Effort: Medium
Confirm the page type fits what searchers actually want for that query.
How to do it
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.
Phase II
Technical foundation (site-wide)
9 items
Set up once, correctly. These gate everything else.
Impact: Critical Effort: Super easy
Stop Google from indexing the your-site.webflow.io staging subdomain.
How to do it
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.
In Webflow
Site settings → SEO tab → Indexing
Impact: High Effort: Easy
Run on your own domain and pick one canonical host.
How to do it
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.
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 shut search engines and AI crawlers out of your entire site. Double-check this before launch — it is a common catastrophic mistake.
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).
Build sections with meaningful tags instead of generic divs everywhere.
How to do it
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.
One of the highest-value, lowest-effort AEO moves you control on-page.
How to do it
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.
In Webflow
Page settings → Custom Code → Head (or an Embed)
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.
How to do it
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.
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 states the page's facts (author, date, price, stock, address) in a form a machine reads without guessing, so an AI answer engine can quote them and attribute them to you. Richer search listings are a side benefit, not the reason.
In Webflow
CMS Collection template → Embed (bind fields)
BlogPosting JSON-LD (bind the bracketed fields to CMS)
Every fact in your schema must appear in the visible page content — no exceptions.
How to do it
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) tells a machine it can't trust either version. Some AI engines read only the visible HTML, so a fact that lives only in the markup is a fact they never see. Search engines treat a mismatch as a policy breach too.
Back claims with specific numbers and consistent terminology.
How to do it
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.
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.
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.
A free scan measures what a scanner can, in about 20 seconds — no signup. The rest is judgement, and that's
where a person helps. What Bot Appétit checks →
