Press slash to focus this field, or Escape to return home.
How do you use Webflow?
ToolsWebflow is where the client's site lives: the build platform, the CMS, and the thing a team has to be able to run after I leave.
It is the primary platform for one reason before any other: it puts the content in the server response. A Webflow page ships its text, its headings and its Collection List items as HTML, so the crawlers that only fetch raw HTML still read them. That single property rules out most of the alternatives before the design conversation even starts.
The work inside it is mostly modelling and structure. Every meaningful entity gets its own indexable URL. Components get built where the team will reuse them, named the way the rest of the project is named. The class system is the deliverable as much as the pages are, because it is what decides whether the site is still coherent a year after handover.
Webflow has a boundary, and I name it. A product UI or an application surface belongs on a different stack, and I say so.
The rules I hold
A project is a site ID
I resolve a build to its site ID before touching anything. The account behind this practice held 258 sites with heavy name collision on 29 July 2026: several near-identical names, multiple copies of the same starter. Writing to the wrong site is not recoverable by undo.
The existing system wins
New work has to be indistinguishable in idiom from what is already there: class grammar, naming, component structure. Imposing Client-First on a project that already has its own consistent system is a defect.
Nothing is published without the owner saying so
Every domain, staging included. The owner raises it in their own words, and then I publish.
Content ships in the HTML
Anything a script writes into the page after load is invisible to OpenAI's, Anthropic's and Perplexity's crawlers, which fetch raw HTML and stop there.
Every entity gets a URL
If a piece of content exists only inside a tab, an accordion or a filter state, it does not exist to a search engine, however good it looks.
Embeds get verified on a rendered page
Script and CSS inside an embed do not execute on the Webflow canvas. That is normal platform behaviour, and I confirm the embed works by loading the real page it ships on.
A failed check stays open
When a read errors, times out or comes back empty, I open the Designer and look at the page myself. Unchecked is a status I am willing to report.
Built with it
Every client build on this site is Webflow. Three of them:
Möbeldesignmuseum
Museum site with a structured CMS for exhibitions, built for multilingual search visibility.
PastaHR
Content architecture rebuilt so every job and location page is independently indexable.
Origin Executives
Executive search site with a structured candidate and role CMS.