SEO · Webflow
Webflow SEO onthe CMS you have.
Titles bound on the collection template, a closed staging site, and a redirect list. We are not redrawing the layout.
The short answer
Fields, slugs, and the staging copy.
Webflow SEO is the CMS template and the hosting settings, not a new visual design. If the SEO title on a collection is a static string, every item shares it. If the staging subdomain is public, you have two copies of the site. We bind titles and descriptions to fields, block staging, and put redirects in the project when slugs change. Exporting the site to static files is not an SEO tactic. It removes the editor that makes the next title possible.
CMS fields
The project stays in Webflow. The metadata does not.
This fits a marketing site that is staying on Webflow. Collection items are the pages you want found: articles, case studies, locations, jobs. The template exists. The failure is that the title, the description, or the Open Graph image was designed once and never bound to the item.
It is the wrong fit when the site is a set of absolute-positioned posters with no collection, and every new page is a duplicate of the last drawing. We can still fix a title on a static page. We cannot invent a scalable SEO model without a CMS structure. That structure is a build.
- You are staying on Webflow hosting so editors remain.
- Repeating pages already live in a CMS collection.
- Staging, slugs, or shared titles are the actual problem.
Bindings and redirects
A field on the item, a redirect when the slug moves.
On each collection template we bind the title, the meta description, and the main heading to fields the editor fills in. A new case study cannot publish with the homepage's title. Static pages that are truly one of a kind get their own fields too. The sitemap should list those templates and not a discarded staging path.
Slug changes get a redirect in the project at the time of the change, not a month later when someone notices a 404. The webflow.io staging host is blocked from indexing. Alt text lives on the image field in the CMS so it is not a one-time pass over the Designer. Heading levels inside components get a check so a hero does not ship three H1s.
- SEO title and description bound to CMS fields on templates.
- Redirects added in the project when a slug changes.
- Staging host blocked. One production host is the canonical site.
Mistakes
A static title on a dynamic template.
The common miss is a collection template with the SEO title typed in as plain text. Every item inherits it. The pages look unique in the Designer preview of the layout and identical in the search result. Editors are not at fault. The field was never there for them to fill.
The second miss is a public staging project, or a redirect list that was never entered because Webflow has no server file to hide the chore in. There is no htaccess to discover later. If the redirect was not added in the project, it does not exist. We also do not export to static hosting and leave the CMS behind as an 'SEO improvement.'
- No shared static SEO title across a collection.
- No public staging subdomain.
- No static export that abandons the CMS and the redirect tool.
What changed
Items have distinct titles. Staging is gone from the index.
We sample new CMS items and confirm the rendered title and description match that item, not the template default. Search Console should stop listing the staging host. When a slug changes, the old URL should resolve on the production domain.
A topic should land on the article or the service page you named, not on a utility page or the staging copy. We are not grading this on a visual refresh. Layout complaints go to the web project. Index and title complaints stay here.
- Rendered titles checked on new CMS items, not only the homepage.
- Staging host absent from coverage.
- Old slugs redirect, tested from the change list.
Example engagement
A B2B software company with one title on every story.
B2B software company, marketing site in Webflow, product app elsewhere. Case studies were a CMS collection. The SEO title on the template was a sentence about the company, typed once. Every story shared it. The staging subdomain was indexed. Two renamed landing pages 404ed because the slug edit never got a redirect.
We bound the title and description to fields on the case study and article templates. Editors filled the fields on the existing items. Staging was blocked. The two renamed pages got redirects in the project. We did not redraw the components or move the site off Webflow. The product app was out of scope. Later items published with their own titles because the template required the field.
Bound
Titles and descriptions came from CMS fields, not one static string
Staging
Staging host blocked so only production stayed indexable
The example uses anonymized results from a Quorum engagement. It is one account, not a benchmark you should budget against.
Questions
Webflow questions.
Can you do this without a Designer seat?
Binding a field on a template is Designer work. Filling the field afterward can be an Editor. If nobody on your side should touch the Designer, we do the binding and hand the fields back. We do not need to restyle the page to bind a title.
Will you improve the layout while you are in there?
Not as part of SEO. If a component prevents a unique heading or hides the article text, we will name that limitation. A visual redesign is a separate web project. Mixing them is how a title fix turns into an open-ended design thread.
What if we use static pages for campaigns?
A one-off campaign page can be static, with its own title and a redirect plan for when the campaign ends. If you clone that page every month, it should be a collection item so the SEO fields travel with the template.
Do redirects survive a site export?
The project redirect list applies on Webflow hosting. An export does not take that list with it unless you rebuild the redirects on the new host. Another reason not to export as a casual SEO step.
How do you handle a localized site?
Only if the localized pages are real, maintained translations. A folder of machine-translated duplicates with the same title is not an international SEO program. We will not add locales you will not edit.
More in this lane
Other SEO platforms.
Talk through webflow.
One conversation. A diagnostic. A plan you can kill if it is not the work.