Marketing owns the website
Landing pages, case studies and posts are published by the people writing them, with no developer in the loop.
Webflow design and development
Webflow suits a marketing team that wants to change the site without filing a ticket. Designers get real control over layout, editors get a CMS for posts and case studies, and hosting, security and updates come with the plan. Its weak points are the ones a visual tool encourages: classes named "div-block-47", animations that slow a phone down, and CMS collections set up in a way that is hard to change later.
96 to 99 out of 100 for mobile speed
PageSpeed Insights on the home pages of the 7 sites we link as our work, 14 Oct 2026.
We build Webflow sites with a class naming system, a component library your team can reuse, CMS collections planned from the content you will actually publish, and the SEO settings filled in on every template rather than left to whoever publishes the first post.
When Webflow is the right choice
Design matters and changes often
Webflow builds from real HTML and CSS, so a designed page can be built as it was designed.
You would rather not run a server
Hosting, SSL, backups and updates are part of Webflow, so there are no plugins to keep current.
When it is not
Large catalogues, complex memberships or heavy integrations usually fit Shopify, WordPress or a custom build better. Webflow’s plans also step up with CMS items and traffic, which is worth checking before you commit.
What we build on Webflow
-
New Webflow sites
From a page map and a component library, so new pages are assembled from parts your team already has.
-
CMS structure
Collections for posts, case studies, team, locations or products, with fields planned from what you will publish and the SEO fields mapped on each template.
-
Moves to Webflow
From WordPress, Wix or Squarespace, with content imported, every old URL given a 301 in Webflow’s redirect settings, and the redirects tested before launch.
-
Fixes on an existing Webflow site
Class clean-up, slow interactions, CMS templates missing their titles and descriptions, and accessibility faults in custom components.
How the SEO and the build work together
Webflow gives you control over titles, descriptions, Open Graph images, canonical tags, the sitemap and 301 redirects, and almost none of it is filled in until somebody fills it in. On a site we build, every CMS template takes its title and description from the collection’s fields, headings follow the structure of the page rather than the font size somebody liked, and alt text is written for every image.
Schema is added in custom code where Webflow does not write it. Interactions are kept for where they help the reader, because each one adds script a phone has to run.
Built in from the start
- A class naming system and a component library your team can reuse
- CMS collections planned from your real content, with SEO fields on every template
- Schema added in custom code where Webflow does not write it
- Interactions measured on a phone, and kept only where they help
- A 301 redirect for every old URL, tested before launch
- Editor roles set up so your team can publish without touching the design
On top of the speed, accessibility, SEO, hosting handover and training that come with every build.
Examples
We have no Webflow site to link as an example yet. The sites we have built are on the web design services page, and a Webflow build follows the same process.
Usually considered alongside
How a build runs, from brief to launch
Six stages on every site, whichever platform it is built on. The scope and the quote are agreed in writing after the first call, before any design starts.
-
01
The brief, on a call
What the site has to do, who it is for and what exists today. If there is a site already, we read its Search Console first, because the pages earning impressions decide what the new one must keep.
-
02
A page map before any design
Every page listed with the search it answers and the action it asks for. On a redesign, every old URL is written beside its new home. You sign the map off before design starts.
-
03
Design on real content
Pages designed with your actual words and pictures, at phone width first. You review in the browser, on a staging address search engines are told to ignore.
-
04
Build, with the SEO written in
Titles, descriptions, headings, schema and internal links are written as each page is built, so nothing is added at the end by somebody who never saw the page map.
-
05
Checks before launch
Speed measured on a phone, every page at 320px wide and at 200 percent text, keyboard and screen reader checks, forms sent and received, redirects tested against the new build.
-
06
Launch, handover and training
The switch, then Search Console read daily for two weeks. The domain, hosting and logins stay in your name, with a written note of how the site is built and a recorded session on editing it.
What every build includes
-
Speed
Measured in PageSpeed Insights on a phone before launch. Images sized for the slots they fill, fonts that do not block the page, no script a page does not use.
-
Accessibility
Colour contrast, keyboard use, visible focus, alt text written for each picture, 44px tap targets on phones, and every page readable at 200 percent text.
-
SEO foundations
One title, description and H1 per page, schema, a sitemap that matches the site, clean URLs, redirects from every old address, and Search Console set up in your name.
-
Hosting handover
The domain, the hosting and every login in your name. We set the site up on your host, recommend one, or host it for you; either way you can move it.
-
Training
A recorded call showing whoever edits the site how to change a page, add a post and swap a picture, and a short written guide to keep beside it.
-
Two weeks after launch
Search Console, forms and errors checked daily for the first fortnight, and anything the launch broke fixed straight away.
Questions about Webflow builds
Is Webflow good for SEO?
Yes. It writes clean HTML, gives you control over every setting that matters and hosts the site on a fast network. What it does not do is fill those settings in, which is where most Webflow sites fall down: CMS pages with no description, headings chosen for their size, and images with no alt text.
Can we edit the site ourselves?
Yes. Editors publish posts and update content in the Webflow Editor without touching the layout, and designers build new pages from the component library. The handover includes a recorded session on both.
Can you move our WordPress site to Webflow?
Yes. Content is imported into CMS collections, every old URL gets a 301 in Webflow’s redirect settings, and the redirects are tested before the switch. If Webflow would be a step backwards for how you publish, we say so on the first call.
Do you have Webflow sites to show?
Not yet. The sites we link as examples are WordPress rebuilds and custom builds, on the web design services page. The structure, the SEO and the checks before launch are the same on Webflow.
Book a call with us
A 30-minute call in your working hours. Tell us what you sell and where, and we will tell you what we would do first and what it involves. Prefer email? Send your website through the form and the Passieon Team will reply within two working days.