Because nobody filled in the per-page SEO fields. Webflow gives every page its own title tag and meta description, but they start empty. When they are empty, search engines fall back to whatever text they can find, which is usually your site name repeated on every result.
This is the single most common thing we fix on Webflow sites we inherit. The build is beautiful, the structure is sound, and every page in the search results looks identical. It takes an afternoon to correct and it is usually the highest value afternoon in the whole project.
The good news is that Webflow makes this genuinely easy, including for CMS pages where you would otherwise be writing hundreds of titles by hand. Here is how we set it up on every build.
Page settings is the panel where each page holds its own SEO and social information. Webflow University states that every page in Webflow has SEO settings where you can set the page title, which appears in the browser tab and in search results, and the meta description, which is the snippet shown beneath the title in search results.
You reach it from the Pages panel in the Webflow Designer, by opening the settings for the page you want. Static pages have their own settings. CMS collection template pages have settings that apply to every item in that collection, which is where the dynamic fields come in.
Treat this panel as part of building the page, not as a cleanup task before launch. Every page we build gets its title and description written at the same time as its content. Left to the end, it becomes a spreadsheet nobody wants to fill in, and it gets skipped.
Lead with the thing people search for, keep it under about sixty characters so it does not get cut off, and make it different from every other page on the site. The page title is the biggest text in a search result, so it does most of the work of earning the click.
Our working format is the specific thing first, then the brand. A services page is better as the service name followed by the business name than as the business name followed by the word Services. Search engines truncate from the end, so anything generic should sit at the back where losing it costs nothing.
Resist the urge to write the same title with a keyword swapped in fifteen times. That produces a set of pages that compete with each other rather than covering different ground. If two pages want the same title, you probably have one page too many.
We covered the writing side of this in more depth in our guide to how to write title tags and meta descriptions. The Webflow part is just where you put them.
Write it as ad copy for the page, not as a summary of the page. Around 150 to 160 characters is the useful range. Say what the reader will get and why it is worth their click. Google will sometimes rewrite it anyway, which is a reason to write it well rather than a reason to skip it.
The description does not directly move rankings, and we tell clients that plainly. What it moves is click-through rate, and click-through rate is what turns a ranking into traffic. A page sitting at position four with a compelling description often outperforms a lazy result at position three.
One habit that helps is writing the description before the page. If you cannot describe the value of the page in a sentence and a half, the page is not focused enough yet. We have killed a few planned pages at exactly this step, which is a cheap place to kill them.
You bind them to Collection fields instead of typing them. Webflow University states that for CMS collection pages you can make title tags and meta descriptions dynamic, pulling from CMS fields so each page in the collection gets its own unique title and description automatically. You do this by adding a field inside the SEO settings on the collection template page.
The mechanics are simple. Open the collection template page settings, click into the SEO title field, and insert the field you want, such as the item name. You can mix dynamic fields with static text, so a pattern like the item name followed by a category and your brand works well and stays unique across every item.
Webflow University demonstrates exactly this kind of combination, building a title from several Collection fields so that each item produces its own natural sounding title. That is the behaviour you want. One template, hundreds of distinct titles, no manual work.
For descriptions we prefer a dedicated CMS field over reusing the post summary. A summary written for a card on a listing page is rarely the sentence you want in a search result. An extra plain text field in the collection costs nothing and gives you control. If you are building a blog on Webflow CMS, our guide to building a blog in Webflow using the CMS walks through how we structure those collections.
Open Graph controls how your page looks when someone shares it, covering the image, title, and description in the link preview. Webflow University describes it as controlling how your pages appear when shared on social media. It does not affect rankings directly, but it affects whether a shared link gets clicked.
Webflow gives you a shortcut here. According to Webflow University, you can check an option marked same as SEO tag to sync your SEO values into the Open Graph fields, or uncheck it and write something custom. For most pages, syncing is fine. For pages you actively promote, custom is better, because the tone that works in a search result is not the tone that works in a social feed.
The image is the part that gets neglected. A link with no Open Graph image shows up as a bare text row in most feeds and messaging apps, and it looks broken next to competitors. Set a default image site wide, then override it on the pages that matter. On CMS pages you can bind the image dynamically, which Webflow University also demonstrates by pulling the main project image in from the collection.
Yes. Webflow University states that Webflow supports automatic sitemap generation, and that your sitemap.xml is created and updated automatically as you add and publish pages. For most sites, that is one entire task you can stop thinking about.
The automatic sitemap is a real advantage over stacks where the sitemap drifts out of date silently. The trade is that it includes what you publish, so an unfinished page that goes live is a page in the sitemap. Publishing discipline matters more when the sitemap keeps up with you.
Check it after launch anyway. Open the sitemap in a browser and read it. We do this on every project because it takes two minutes and occasionally reveals a page nobody meant to ship. If you want to understand what a good sitemap looks like beyond Webflow, we covered it in our piece on what an XML sitemap is and how to get it right.
It surfaces the mistakes that are easy to make and easy to miss. Webflow University states that the Designer audit feature surfaces common SEO issues like missing alt text, missing meta titles, and skipped heading levels. It is a built-in checklist that costs you nothing to run.
Skipped heading levels is the one that surprises people. A page that jumps from a heading one straight to a heading three reads fine visually and reads badly to a crawler or a screen reader. The audit catches it before anyone else has to.
We run the audit before every handover, alongside a manual pass. Automated checks find missing things. They do not find a title that is technically present and completely useless. Both passes matter, and the manual one is where the judgement lives.
Four things, over and over. Leaving CMS template SEO fields static so every item shares one title. Writing titles longer than the space available. Forgetting Open Graph images entirely. And filling everything in beautifully in the Designer, then never publishing, so none of it is live.
The static CMS template mistake is the most damaging by volume. One unbound title on a collection template can mean two hundred pages sharing an identical title. Search engines treat that as a signal that the pages are interchangeable, and they respond accordingly.
The publishing mistake sounds silly until it happens to you. Webflow separates the Designer from the live site, so SEO settings only exist to Google once the site is published. We have been called in to diagnose invisible pages that were simply never pushed live.
If you want a wider pass over everything technical on a Webflow build, our technical SEO checklist for Webflow websites covers the items outside the page settings panel.
Publish, then verify from the outside. Search for a few of your own pages, look at what actually appears, and compare it to what you wrote. Then connect Google Search Console and watch which pages get indexed. Setting the fields is the work. Confirming they took effect is what tells you it worked.
Give it time before you judge the result. Search engines re-crawl on their own schedule, so a title you fixed today may show the old version for a while. That is normal, and it is not a reason to change it again next week.
If you have a Webflow site with a few hundred CMS items and you are not sure whether the titles are doing anything useful, we are happy to take a look. Send us the URL over at phoenix.studio. It is usually a quick diagnosis, and the fix is often one afternoon of work in the collection template.
Tell us where you want to go. We'll tell you how we'd get you there.