Technical SEO for Webflow.

Crawlability is upstream of everything else — if Googlebot can't reach a page or render it correctly, none of the on-page work matters. On Webflow, the failure modes are usually around robots.txt overrides, JavaScript-gated content, or password-protected staging environments accidentally pushed live.

User-agent: *
Allow: /

# Block utility paths
Disallow: /thank-you
Disallow: /admin

# Surface the sitemap
Sitemap: https://www.example.com/sitemap.xml

We audit the rendered HTML — not the source — because Webflow's interactions can hide content from crawlers if wired through display:none transitions instead of opacity or transform.

Webflow lets you set noindex at the page level via Page Settings, and at the collection-template level via the page-specific SEO tab. The trap is forgetting the project-level setting in Site Settings → SEO → Indexing that disables search engine indexing globally — typically left on during build and forgotten at launch.

Webflow injects a self-referencing canonical by default. This is correct most of the time. The cases where you need to override:

• — Paginated CMS lists where /page-2, /page-3 should canonicalize back to the primary list view.
• — URL parameters from filters or campaigns (utm_source, fbclid) — these are fine in practice but worth tracking in Search Console for parameter-driven duplication.
• — Duplicate or near-duplicate content across two collections (e.g., a service appears under both /service/* and /las-vegas/*) — pick the canonical and override on the secondary.
• — Migrations where old URLs need to canonicalize forward during a transition window before the 301s settle.

The most common mistake on Webflow projects is hand-pasted JSON-LD in the page's custom-code embed. It works once, then breaks the moment the title or description changes in the CMS. We build schema as Webflow components driven by CMS fields — so the schema regenerates with the content.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Service",
  "name": "{{wf {"path":"name"} }}"}",
  "description": "{{wf {"path":"summary"} }}"}",
  "provider": { "@type": "LocalBusiness", "name": "WFpulse" }
}
</script>

CMS-bound fields inside an embed mean the editorial team can update content normally and the structured data follows along — without touching code.

Webflow's hosting handles TTFB and HTTP/2 well. The work is at the template level: image sizing, font loading, hero composition, and how interactions are wired. We set budgets per template type and audit against them.

Webflow generates /sitemap.xml automatically when auto-generation is enabled in Site Settings. For most sites under a few hundred pages, this is sufficient. Above that — or when you need fine-grained control over which CMS items are included, lastmod accuracy, or multiple sitemap files — we override with a custom sitemap.

The sitemap should always be referenced in robots.txt and submitted in Search Console. We monitor sitemap submission status weekly during the first month after launch, then monthly thereafter.

Slug changes are unavoidable. The discipline is mapping them. Every slug change gets a 301 in Webflow's Hosting → 301 Redirects panel, and we keep a tracked log alongside it — what changed, when, and why — so redirect chains can be pruned over time and the next agency or in-house team understands the history.

For migrations, we build the redirect map URL-by-URL before launch, validate it in staging, and run a crawl post-launch to confirm every legacy URL resolves with a 301 and no 404s slip through.

Webflow's CMS makes programmatic SEO accessible without a developer. Two collections, a reference field, and a template page can produce hundreds of intent-matched pages. The work isn't the build — it's the data model.

Programmatic pages fail when the variants are too thin to stand on their own. Each page needs genuinely distinct, useful content — not just a headline swap. We design the data model so every field carries information specific to that page, and we set a quality floor below which a page doesn't publish.