Webflow SEO Expert for Marketing Sites That Need to Rank

Webflow has no site-wide default title or description. So every static page needs its own, and every Collection template needs a pattern (Webflow docs). Build that pattern from the Name field alone and you get titles with no qualifier and no brand. A description pulled from a summary field is worse: it comes out blank on any item where nobody filled that field in. I check the pattern first. Then the output, on 20 or so real items.

The Sitemap indexing toggle adds a noindex tag and drops the page from the sitemap, but only when the auto-generated sitemap is on. Use a robots.txt disallow, or paste a noindex into custom code, and the page stays in your sitemap anyway (Webflow docs). Per-item noindex on CMS items needs a paid Site plan. Then there’s the sneaky one. Collections built only to feed other pages (testimonials, team members, FAQ entries) can end up with a live URL for every item if their template page is published. You don’t want those thin pages in the index.

Webflow builds each canonical by joining the global canonical tag URL to the page’s slug. Its docs say that URL needs https (and www, if your default domain uses it) and no trailing slash. Get the slash wrong and every subpage canonical picks up a double slash, like //contact (Webflow docs). Inject another canonical through Google Tag Manager and you’ve got two, and search engines may ignore both. Page-level overrides exist. The doc only covers them for static pages, though.

There’s no hard cap, but Webflow recommends 1,000 redirects at most, because every rule goes into a manifest file that visitors’ browsers download (Webflow docs). Rules run oldest first. So a broad wildcard you added early will catch URLs before a specific rule added later. Locale paths need their own rules too: /old-url and /es/old-url are two redirects. And an old path written with a slash right before a query string never matches. For a relaunch I build the map first with my redirect map builder, then collapse patterns into wildcards.

Every Webflow site can publish to a yoursite.webflow.io staging subdomain as well as your domain. Unless Staging indexing is switched off, that’s a second copy of your whole site open to crawlers. The switch needs a Site plan or paid Workspace, and it works by publishing a robots.txt on the subdomain only (Webflow docs). Webflow’s own doc warns that blocked content can stay indexed if it was found earlier. So if staging URLs already show up in Google, the switch alone won’t clear them. I check it two ways: a site: search, then Search Console. Enterprise plans can also make staging private (Webflow docs).

Alt text set in the Assets panel follows a static image around the site. CMS images don’t work that way. You need a plain text field in the Collection, filled in on each item and bound to the image’s alt setting on the template (Webflow docs). Images inside a rich text field take their alt text from that field, item by item. Webflow AI can bulk-generate alt text from the Audit panel. Read what it writes before you accept it.

Collection templates can pull the Open Graph title, description and image from each item. The image has to come from an Image field, and every Open Graph image in a Collection must share the same dimensions (Webflow docs). One more catch. Webflow can bulk-compress CMS images to AVIF, and its own doc says AVIF isn’t widely supported for Open Graph images, so pick WebP for those (Webflow docs).

Webflow’s speed guide blames the usual suspects: large images, third-party scripts, excess transitions and excess interactions (Webflow docs). Run Classic interactions and the newer Interactions with GSAP on one site and you load both engines, which Webflow ranks as the slowest option (Webflow docs). Responsive variants aren’t created for images added by CSV import or the API, for background images, or for images in rich text (Webflow docs). That’s where I’d look for an oversized file. The optional async JavaScript setting? It can speed up rendering. It can also break custom code, so test it on staging first.

Webflow now has a Schema markup field in Page settings, and Webflow AI can draft the markup (Webflow docs). On Collection pages, bind CMS fields so each item gets its own data. Reference, Multi-reference and Multi-image fields can’t be used, so an author or location held in a reference field needs a workaround. Older sites usually carry schema in custom code embeds instead. Webflow advises against keeping it in both places, so pick one. For a local business, my LocalBusiness schema generator writes valid JSON-LD you can paste straight into the field.

Webflow Localize sets the HTML lang attribute and adds hreflang tags automatically, in the page head, the sitemap or both (Webflow docs). The gaps are elsewhere. Webflow’s pricing page lists localized URLs and automatic visitor routing only on Localize Advanced (Webflow pricing). Locale routing uses 302 redirects with no native override. Webflow AI can’t write metadata in secondary locales, so translated titles and descriptions are a manual job (localized page settings). And your 301s won’t cover locale paths unless you add them.

The blog, resources or case study Collections went from 20 items to several hundred, and the templates were designed for the first 20.

You’re moving from WordPress, Squarespace or an older Webflow build, and the redirect map, staging checks and launch QA need doing before the switch so rankings carry over.

You’ve turned on Webflow Localize, or you’re about to, and want hreflang, locale URLs and redirects checked by someone who’s run international SEO across 11 countries.

You own the build. You just want an SEO specialist to sign off templates and settings before handover, without taking over the project.

I crawl your live domain and your webflow.io subdomain, pull Search Console and GA4, and list which URLs Google actually indexes.

Every row in the settings table above, plus each Collection template’s SEO, Open Graph and schema patterns, checked against what real items output.

Title patterns, alt text fields, canonicals, noindex toggles and schema. I make the changes in the Designer with the access you give me, or write them up for your developer to ship.

For relaunches and migrations: a full redirect map, wildcard rules in the right order, and a staging check before cutover. After launch I watch Search Console for 404 spikes and dropped pages.

Monthly reporting on non-branded clicks and organic leads. Once the foundation is clean, the work moves to new pages and content that win buying searches.

A 40-page brochure site and a site with 2,000 blog and resource items aren’t the same audit, mostly because of how many templates need checking.

Each Localize locale adds its own slugs, metadata, redirects and hreflang to verify.

A move onto Webflow means a full redirect map, launch QA and post-launch monitoring on top of the audit.

Whether I make the changes in the Designer, or brief and review the work of your developer or agency.