Hiring a Webflow developer is a bit like hiring a builder. Every portfolio looks lovely, everyone "does SEO", and the problems show up after you've paid: a site you don't actually own, a blog where every post has the same page title, or a CMS so fiddly your team quietly stops using it.
You can spot most of those problems before you sign, if you ask the right questions. We're Digital Mast, a Webflow agency building websites for businesses around the world, and these are the questions we'd want a client to ask us. (They do. We like it.) They work for a landing page or a five-page site as well as a big rebuild, whether you're working out how to choose a Webflow agency or vetting a freelancer.
Earlier in the process? Start with our guide on how to hire a Webflow expert. This post is the detailed Webflow developer checklist for once you have a shortlist.
Why Webflow-specific questions matter
Webflow is a professional visual development platform. Sites are built from real HTML and CSS structure, with classes, breakpoints, a CMS, interactions, SEO controls and hosting. It has a genuine learning curve, which is why you're hiring someone. (If you'd rather build a simple site yourself, Squarespace and Wix are designed for that.)
It's also why generic "questions to ask a web designer" lists only get you halfway. Much of what makes a Webflow site good or bad sits under the bonnet: which Workspace it lives in, how the CMS Collections are set up, whether SEO fields are bound on the templates, how classes are named and what your team can edit. None of that shows up in a screenshot.
So for each question we've added why it matters and what a good answer sounds like. You don't need every technical detail. Just notice whether the answer is clear and specific, or vague and a bit wriggly.
Ownership and portfolio
1. Will the site live in our Webflow Workspace (or be transferred to us), and who pays the Site plan?
Why it matters: every Webflow site sits inside a Workspace. If yours stays in your developer's Workspace, you're relying on them to keep it there and paid for. Webflow lets developers on its Freelancer or Agency Workspace plans transfer a site to a client's Workspace, along with its paid Site plan and custom domain, with no downtime. There's also a client payments option, where the site stays in the developer's Workspace but you're billed for the Site plan.
A good answer: "We'll transfer it to your Workspace at launch", or "It stays with us on client payments, and we'll transfer it whenever you ask." Either way, in writing.
2. Can we see three live Webflow sites similar to ours?
Live sites, not screenshots. A screenshot shows taste. A live site shows whether it actually works.
Your quick Webflow portfolio review:
- Open each one on your phone and click past the homepage into inner pages, blog posts and the contact form.
- Check it really is Webflow: view the page source and look for "data-wf-site" near the top.
- Ask what they did on each: design, build, copy and SEO, or just part of it?
- Ask whether the client now edits the site themselves. That's a very good sign.
There are more checks in our hire guide.
3. Who designs, builds, writes the copy and handles SEO? One person or a team?
Why it matters: "Webflow developer" can mean a designer, a developer or both, and none of those titles promises copywriting, SEO or project management. You need to know who does each job, and whether any of it is quietly left to you.
A good answer: names or roles for strategy, design, build, SEO, copy, testing and project management, plus who picks up the work when someone's on holiday. If you hear "we handle all that", ask "who, exactly?" Our Webflow freelancer vs agency guide explains what each set-up gives you, and why the difference is what you get, not the size of your project.
4. Will the site be custom designed from scratch for our brand?
Why it matters: you should know whether you're paying for a custom design or a template with your logo on it. A template also arrives with a class structure and CMS set up for somebody else's content.
A good answer: a straight yes or no, and how they'll get there: goals, sitemap and wireframes first, then visual design, then the build. Ask how many feedback rounds are included, too.
Build quality: CMS, SEO and structure
5. How will you structure the CMS so our team can add content?
Why it matters: Webflow's CMS stores content in Collections, such as blog posts, case studies, team members or locations. Each has its own fields and template page, and reference fields link Collections, such as a post to its author. Get the structure right and adding a case study takes minutes. Get it wrong and every new page needs a developer.
A good answer: they'll ask what you publish now and plan to publish, then sketch the Collections and fields before building. Bonus points for help text and required fields, so nobody publishes a post without a summary. Webflow's Premium plan allows up to 20,000 CMS items and 40 Collections, which is plenty for most businesses.
6. How are SEO titles, meta descriptions and Open Graph fields bound on the CMS templates?
Our favourite question, because it's where plenty of otherwise lovely sites fall down.
Why it matters: on a Collection template page, Webflow lets you build the SEO title, meta description and Open Graph settings from CMS fields, so every blog post or case study gets its own. If nobody sets this up, every item can share one generic title, which doesn't help anyone find you.
A good answer: "We add SEO title, meta description and social image fields to each Collection and bind them on the template." Then test it on their portfolio: open three blog posts in separate tabs and check that each tab shows a different title. For the wider picture, see our guides to on-page optimisation and schema markup.
7. If we're moving from an existing site, what happens to our Google rankings?
Why it matters: if your current site brings in traffic and enquiries, a rebuild can lose them when URLs change and nothing points visitors (or Google) to the new pages.
A good answer: a Google Search Console baseline before anything changes, a full inventory of existing URLs, a 301 redirect for every URL that changes (Webflow can import these in bulk from a CSV file), titles and descriptions carried over deliberately, and checks after launch. Ideally it starts with a technical SEO audit. Still choosing a platform? See our Webflow vs WordPress comparison.
8. How do you name classes and organise the style system so another developer could take over?
Why it matters: styling in Webflow is built on classes. A tidy system keeps changes quick and consistent, so another Webflow developer can pick the site up later. A messy one, full of vague names like "div-block-27" and one-off tweaks, makes every change slower and riskier.
A good answer: a naming convention they can explain in a sentence (a published system or their own documented one), components for repeated sections, variables for brand colours and fonts, and a style guide page. Ask them to walk you through a past build on screen.
9. How do you handle accessibility basics?
Why it matters: an accessible site works for more people, including screen reader and keyboard users, and the basics overlap nicely with good SEO.
A good answer: headings in a logical order, meaningful alt text, visible focus states for keyboard users, readable colour contrast and properly labelled forms. Webflow's Audit panel flags issues such as missing alt text and skipped heading levels, but it doesn't check alt text on CMS images, so ask how they handle those. (Ideally, an alt text field in the Collection, bound to the image.)
Launch and handover
10. What testing do you do before launch?
Why it matters: the small things are the embarrassing ones, like a form that sends enquiries to nobody.
A good answer: a written checklist covering real phones, tablets and browsers, every form (including where notification emails go), links, redirects, the 404 page, page titles and descriptions, the sitemap, and a crawl of the site the way Google sees it. Ideally you'll review it all on Webflow's staging domain first.
11. Which Webflow Site plan and Workspace seats will we need, and what do they cost?
Why it matters: the build fee isn't the only cost. You pay Webflow for the Site plan, not your developer.
A good answer: a named plan and a yearly figure. As of October 2026, Webflow's Basic plan, for sites that don't need a CMS, is $15 a month billed yearly or $25 billed monthly. Premium, which most business sites with a blog need, is $25 a month billed yearly or $39 billed monthly. Prices are in USD, per site, plus applicable taxes. Then ask about seats: Webflow's Freelancer and Agency Workspace plans include one and three free client seats per site respectively, so check how your team will log in. For build fees and running costs in full, see how much a Webflow expert costs.
12. What training do we get for the content editor role at handover?
Why it matters: the point of a CMS is that you don't need your developer to fix a typo.
A good answer: a proper session with whoever will edit the site, plus notes or videos to keep. Webflow's content editor role lets your team edit text, links and images, create CMS items such as blog posts, manage SEO titles, meta descriptions and Open Graph settings, and publish if given permission, all without touching the design. They can't change the layout, edit page slugs, add custom code or create Collections, so ask what happens when you need one of those.
13. Who owns the design files, the custom code and the third-party accounts?
Why it matters: a Webflow site rarely runs alone. There may be analytics, a booking tool, form integrations, fonts, a domain registrar and custom code. When a site is transferred, Webflow resets some account-specific settings, such as form notifications and reCAPTCHA keys, and connected apps need re-authorising.
A good answer: design files handed over, a written inventory of every custom code embed (what it does and where it lives), and every third-party account in your name, with logins you control.
Support and exit
14. What support is available after launch, and how is it charged?
Why it matters: launch is the start. You'll want new pages, campaign landing pages, SEO improvements and the odd "quick change" that isn't.
A good answer: what happens after launch (a support window, a retainer or work quoted as needed), who you contact and how quickly they reply. Get it in writing.
15. What happens if we want to leave you, or leave Webflow, later?
Why it matters: nobody plans a break-up on the first date, which is exactly why you should ask.
A good answer: if the site is in your Workspace and the classes are tidy, changing developer is simple. If your developer still holds the site, they should happily transfer it. Leaving Webflow is a bigger job, as on any platform. Webflow can export a site's HTML and CSS, though CMS items and pages aren't included in that export, and Collection items can be exported separately as CSV files. Forms and hosting run on Webflow, so they'd need replacing. A good developer explains this calmly, not defensively.
Red flags to listen for
- Only images of past work, no live sites.
- The site stays in their Workspace, with no plan to transfer it.
- "SEO is included", with no detail.
- No clear answer on who writes the copy.
- Portfolio blog posts that all share one page title.
- Support is "just give us a shout", with nothing written down.
Webflow's directory of Certified Partners, vetted by the Webflow team, is another useful shortlisting signal, but not a substitute for these questions.
How we'd answer these at Digital Mast
We'd rather you ask than wonder. Our team covers design, the Webflow build, SEO and copywriting. Every site is built from scratch and custom designed for your audience, keyword research shapes the sitemap, and we'll brief you on the copy we need or write it for you. Before launch we test, crawl the site the way Google would and submit it for indexing. Then we hand over with access and CMS training, and stay on for ongoing support and improvement. Our website design process walks through each stage.
That's the same for a landing page or a five-page site as for a larger build. Small projects get the whole team, and we're very happy to take them on.
See it in practice in our work for Habello, a fast house-buying brand that needed a full website build and a scalable blog to support its SEO, and Experience Charters, a boat charter company whose redesign brought in online booking.
Bring all 15 questions to the first call. We'll answer every one, then quote for your project.
You can also read more about how we design and build websites and our SEO services.
Frequently asked questions
What should I ask a Webflow developer before hiring them?
Ask who will own the site and its Webflow Workspace, to see live sites similar to yours, and who handles design, build, copy and SEO. Then ask how the CMS and SEO fields will be set up, how your rankings will be protected if you're migrating, which Webflow plans you'll need, what training and support you'll get, and what happens if you want to leave. Clear, specific answers are a good sign; vague ones are worth probing.
How can I tell if a website was built in Webflow?
Open the site, view the page source and look near the top for an attribute called data-wf-site, which Webflow-built pages include. Then ask the developer what they did on that site, because seeing Webflow in the code doesn't tell you who designed or built it.
How many Webflow developers should I speak to before choosing?
Two or three is usually enough to compare answers properly. Send each the same brief, ask them the same questions, and compare how clearly they answer as well as the price. If one quote is much lower than the others, check what's missing from the scope, such as SEO, copy, testing or training.
Will a Webflow agency take on a small website or landing page?
We certainly will. At Digital Mast, a single landing page or a five-page site gets the same team as a larger build: strategy, design, the Webflow build, SEO set up properly from day one, copywriting if you need it, testing, CMS training and support after launch. Get in touch for a quote.
Do I need my own Webflow account to hire a Webflow developer?
It's a good idea. Having the site in your own Workspace, or transferred there at launch, means you're in control of it. Webflow lets developers on Freelancer or Agency Workspace plans transfer a site to you along with its paid Site plan and custom domain, and you can add them back as a guest if they're still working on it.
Does a Webflow Certified Partner badge mean I don't need to ask these questions?
No. Webflow's Certified Partners are vetted by the Webflow team, which is a useful signal when you're shortlisting. But a badge can't tell you who will own your site, how your CMS will be set up or what support you'll get, so ask the questions whoever you're talking to.
Header photo by Markus Spiske on Pexels
