Webflow Gets the Output Right. The Constraints Are the Problem
Webflow ships clean, semantic HTML on fast hosting, and it does not invent a single URL you did not ask for — which puts it ahead of most of what we are handed. What it does instead is refuse you some of the URLs you will eventually want, and the refusals are almost all decided at build time. That is a very different job from cleaning up after a CMS, and it has to happen earlier.
No credit card required · 30-minute call · No obligation to sign up
Six constraints, and most are permanent by launch
None of these is a bug and none is a reason to avoid Webflow. They are design decisions in the platform, and every one of them is far cheaper to plan around before the build than to work around afterwards.
- Collection URLs are one level deep
/collection/item· you cannot nest a third level - The collection slug governs every itemChange it and every URL in that collection changes at once
- An item cannot live at the rootEvery CMS page sits under its collection, always
- Redirects are plan-boundA finite list in site settings · not a config file you own
- No server-side layerNo .htaccess, no custom headers, no server logic
- Content is published, not servedA CMS change is live only after a publish · plan for it
The first three are the ones that decide your architecture, and they are the reason a URL plan on Webflow is a build-time decision rather than an SEO task. A structure like /services/audits/uk/london/ is simply not expressible in a Webflow Collection — and finding that out after 200 items exist means renaming a collection slug and redirecting every one of them.
The opposite problem to the one WordPress has
It is worth stating the comparison directly, because the two platforms fail in mirror-image ways and the advice for one is close to useless for the other. A WordPress site arrives with hundreds of URLs nobody wrote — attachment pages, tag archives, duplicate slugs — and the work is deciding what to remove. A Webflow site arrives with exactly the URLs you built and no more, and the work is that some of the ones you now want cannot be built at all.
That trade is mostly a good one. Webflow’s output is semantic, its hosting is fast, and the whole category of index bloat that dominates WordPress audits simply does not occur. On Core Web Vitals a competently built Webflow site starts ahead, and stays ahead unless somebody adds interactions that move the layout after paint.
Where it costs you is depth and control. Collection items live one level under their collection and nowhere else, so a topical architecture more than two levels deep has to be built as static pages instead — which works, and which means losing the CMS for exactly the section most likely to grow. Redirects live in a settings panel with a plan-dependent limit rather than in a file you control, which matters most in the migration you have not planned yet.
And there is no server layer at all. Nothing you would ordinarily solve with a rewrite rule, a custom header or conditional logic is available. Most sites never need any of it. The ones that do usually discover the need at the worst possible moment, which is why we would rather raise it before a build than during one.
- ✓No index bloat — Webflow does not generate URLs you did not create. The entire WordPress cleanup category is absent here.
- ✓Fast by default — Clean markup on a global CDN. A competent Webflow build starts ahead on Core Web Vitals.
- ✓Two levels, not four — Collection items sit one level under their collection. Deeper architecture means static pages and no CMS.
- ✓Redirects are a list, not a file — Plan-bound and managed in settings. Fine until a migration needs a few hundred of them.
- ✓No server layer at all — No rewrite rules, no custom headers, no conditional logic. Usually irrelevant, occasionally decisive.
On WordPress the question is which of these thousand URLs should exist. On Webflow it is why the URL you need cannot. Same discipline, opposite conversation.
What we do on a Webflow site
Six pieces. The first two are build-time decisions, which is why we would rather be asked early than well.
Collection & URL Architecture
Which content becomes a Collection and which becomes static pages, decided against the URL structure you will need in two years rather than the one you need this month. The single most consequential Webflow decision and the hardest to reverse.
Internal Linking & Topical Depth
With only two URL levels available, hierarchy has to be carried by links rather than by paths. That is how search engines read it anyway, and on Webflow it stops being optional.
Collection List Indexation
Filtered and sorted views of the same Collection can produce several addresses for one set of content. Deciding which are indexable, and keeping the canonicals honest, before the collection grows.
Interactions & Layout Stability
The one place a Webflow build reliably loses Core Web Vitals. Animations that move content after paint cost you CLS, and they are added visually by people who cannot see the metric.
Redirects & Migration Planning
Mapping what the redirect list actually has to hold before you need it, and consolidating where the plan limit is going to bind. This is the constraint that turns a routine migration into a problem.
Content Fields & Metadata
Title and description as real Collection fields with sensible fallbacks, so a new item cannot publish with an empty snippet. Our own site once ranked 24 pages with none at all, at 0.13% click-through.
The constraints bind differently by build
How much of the above matters depends on what you are asking Webflow to be. These are the four we see.
Marketing site, static pages
Where Webflow is at its best and almost none of this applies. Fast, clean, and no CMS constraints because there is no Collection doing the work.
Content-led site with a blog
One Collection, one level, entirely comfortable. The decisions that matter are which taxonomy views are indexable and whether metadata fields have fallbacks.
Programmatic or multi-market pages
Where the two-level limit bites hardest. A structure that wants discipline, then country, then city cannot be a single Collection, and the answer is usually static pages for the upper levels.
Ecommerce
Webflow Ecommerce is workable at modest catalogue sizes. Above that, the same faceted-navigation arithmetic that troubles every platform arrives, with fewer levers to answer it.
Post-migration onto Webflow
The moment the redirect list matters most, and the moment people discover it is a settings panel rather than a file. Plan the map before the move, not after.
When Webflow is the right choice
We build in Webflow, so this is a view from inside rather than a comparison written to sell something else.
Design-led marketing sites
Where the site is a brand asset that changes often and a designer needs to ship without a developer in the loop. Webflow is genuinely excellent at this and the SEO baseline comes free.
Startups and SaaS
Fast to launch, fast to change, and clean enough that technical SEO is not a rescue job later. The thing to decide early is what happens when the content section grows past two levels.
Teams without a developer
The strongest argument for the platform. A site that can be updated by the people who know the business beats a faster site nobody can change.
When we would suggest WordPress instead
Heavy editorial operations with many authors, complex taxonomies and thousands of posts. WordPress’s defaults are a liability, but its editorial depth is real.
When we would suggest static or custom
Deep topical architecture, unusual URL requirements, or anything needing a server layer. This site is static PHP for precisely those reasons.
Sites already on Webflow
Most of our Webflow SEO work. The constraints are already set, so the job is getting the most out of them and planning the one migration that will eventually test the redirect list.
What clients say
Real clients, quoted in their own words — published with their permission.
“We’re very thankful to Ghalib and his team for building a fully-functioning website for our business.”
“Highly professional and dedicated to achieving results.”
“Ghalib’s clear guidance has helped improve our website’s SEO performance.”
“It was a pleasure working with Ghalib and his team.”
More of them, in full, on our reviews page.
— Our Proprietary Methodology —
The Visibility Framework™, applied to Webflow
The method is the same one every engagement here runs on. On Webflow, step one asks what the URL structure needs to be in two years, because that is the question the platform will not let you revisit cheaply.
Visibility Score
We baseline your index coverage and Core Web Vitals from your own data, then map your Collections against the URL structure the content will actually need — because that is the constraint everything else on Webflow is downstream of.
Custom Strategy
A keyword and content roadmap scoped to your niche and budget — which pages to fix, which to build, and which terms are worth the money here.
Execution
Senior strategists implement technical fixes, content and links as one roadmap — no juniors, no outsourcing, no handoffs between departments.
Track & Improve
Monthly reporting and continuous optimization — we re-test what’s working, cut what isn’t, and adjust as the market moves.
Honest, No-Nonsense Commitment
No one controls Google or AI search — so we'll never guarantee a #1 ranking. What we do guarantee: we baseline your visibility at the start — where you rank on Google and whether AI answers cite you — and if that baseline has not moved in 90 days, the next 60 days are free.
Webflow SEO pricing
Scoped by how much of the structure is still changeable rather than by page count. A site pre-build costs less to get right than one with 300 Collection items already published. Prices below are USD; UK clients are quoted in GBP and Pakistani clients in PKR.
Starter
A low-risk way to test SEO with us on a single site.
- Collection & URL structure review
- Metadata fields and fallbacks
- Monthly reporting
Growth
For Webflow sites growing past their original structure.
- Everything in Starter, deeper execution
- Internal linking & topical depth
- Interaction and Core Web Vitals work
- Bi-weekly reporting calls
Enterprise
Multi-market Webflow builds and migrations.
- Dedicated senior strategist
- Redirect strategy within plan limits
- Static-plus-CMS hybrid architecture
- Custom reporting dashboard
Webflow engagements are frequently shorter than WordPress ones, because there is less to undo. What replaces the cleanup is planning — and planning is cheaper.
What you’re actually committing to
Most agencies keep this in a contract you only see after the sales call. We would rather you knew now, because it is the question everyone asks second — right after the price.
- A 3-month initial term, then month to monthLong enough for the 90-day guarantee above to mean something, short enough that you are not trapped if it doesn’t work out. The wider industry standard is 6 to 12 months.
- 30 days’ notice to stopNo exit fee and no buy-out of the months you haven’t used. You leave when you decide to, not when the contract lets you.
- No setup or onboarding feeThe audit is free, and month one costs exactly what month two costs. Nothing is front-loaded.
- You own everythingAnalytics, Search Console, content, accounts and any tooling set up for you — all in your name from day one, and all still yours if we part ways.
- One fixed monthly feeAnything outside the agreed scope is quoted and approved by you before it starts. It never appears on an invoice as a surprise.
- Reporting written to be readWhat changed, what it moved and what is next — in plain English, at the cadence set out in your plan, not a 40-page export nobody opens.
These are the terms as they appear in the agreement itself — nothing here is softened for the website. The full wording lives in our terms and conditions, and you get the agreement to read before anything is signed or invoiced.
What we will tell you before you build
We will ask what the URL structure needs to look like in two years, and we will keep asking until there is an answer. It is the only Webflow question that is genuinely expensive to get wrong, because the platform will not let you revisit it cheaply once a Collection has items in it.
We will not tell you to leave Webflow because of anything on this page. Every constraint listed here has a workable answer — static pages for depth, links for hierarchy, planning for redirects — and replatforming to escape a two-level URL limit costs far more than designing around it. We build in Webflow ourselves; this is a view from inside it.
What we will say plainly is when it is the wrong tool. If your content genuinely needs four levels of hierarchy, thousands of items and a server layer, Webflow will fight you for years and you will win none of it. That conversation is much cheaper before the build than after 300 items exist.
And the ordinary limits apply as everywhere else here: no bought links, no doorway pages, no invented reviews. A clean platform does not make a spam tactic safe.
- Structure first, always. The URL question is the one Webflow decision that is expensive to revisit.
- We build in it. Webflow Development is a named service here. This is a view from inside, not a comparison to sell something else.
- Constraints have answers. Static pages for depth, links for hierarchy, planning for redirects. None of them requires leaving.
- We will say when it is wrong. Four levels, thousands of items and server logic mean a different platform. Better said before the build.
- No shortcuts on a clean platform. Good output does not make a doorway page safe.
Webflow SEO questions, answered
/collection-slug/item-slug — you cannot nest a third level, and you cannot put an item at the root. The collection slug governs every item in it, so changing it rewrites every URL at once. Redirects are a finite list in site settings, with the ceiling depending on your plan. And there is no server-side layer at all: no .htaccess, no custom headers, no conditional logic. Plan limits on item counts also exist and change over time, so check them against your own plan rather than against an article./collection/item has to be built as static pages, which works perfectly well but means the section loses the CMS — exactly the section most likely to grow. The usual answer is a hybrid: static pages for the upper levels of the hierarchy, a Collection for the layer that repeats. Deciding that before the build is cheap. Deciding it after 200 items exist means a collection rename and a redirect for every one of them.Related SEO pages
Same service, different angle — by market, by discipline and by platform.
Building in Webflow? Decide the URLs first.
Free 30-minute audit · No obligation · Response within 24 hours
Get in touch with Ghalib Ashrafi HQ
Ghalib Ashrafi takes on work for brands in six markets — the UK, USA, UAE, Saudi Arabia, Australia and Pakistan. Every enquiry gets a reply within 24 hours.