Question 1

Webflow vs WordPress for marketing — which makes sense now?

Accepted Answer

Honest answer: Webflow wins for almost every marketing site under 1,000 pages where the marketing team owns the lifecycle. WordPress still makes sense if you have a big publishing operation (50+ editors, 10k+ posts, multi-author workflows), or if your stack is deeply WordPress-coupled (WooCommerce inventory, BuddyPress, custom plugin investments).

For the typical SaaS / B2B / DTC marketing site — Home, About, Pricing, Blog, Cases, Contact — Webflow is faster to ship, easier to edit, cheaper to host, and the Core Web Vitals come in the box. We've migrated 14 WordPress sites to Webflow in the last 18 months; zero have asked to go back. If your site is mostly conversion pages rather than a full marketing system, see our Landing Page Design service instead.

Question 2

Will my SEO survive the WordPress → Webflow migration?

Accepted Answer

Yes — if the migration is done right. The risk in any CMS migration is broken URLs, missing meta tags, lost schema markup, and 404s where search engines have indexed pages for years. We protect against all four:

(1) Every old URL gets a 301 redirect mapped before launch and tested in staging. (2) Title tags, meta descriptions, OG tags, canonicals all ported page-by-page. (3) Schema markup rebuilt (Article, Product, Organization, FAQPage). (4) sitemap.xml and robots.txt verified, then submitted to GSC the day we publish.

Question 3

What's the catch on Webflow's 100 static-page limit?

Accepted Answer

The '100 static pages' is a per-site limit on individually-designed pages — but it doesn't include CMS Collection pages, which can scale to 10,000 items per Collection and 20 Collections per site. So the real ceiling is closer to 200,000+ pages on the Business plan, just structured through Collections instead of one-off layouts. In practice: marketing sites need 10-30 static pages (Home, About, Pricing, etc.) and use Collections for everything that repeats (Blog, Cases, Team, Changelog, Help articles). We've never hit the static-page limit on a marketing site. If you're worried about it, send a sitemap on Day 0 — we'll model it before we start.

Question 4

Can our marketing team edit without breaking the site?

Accepted Answer

That's the whole point of how we build. Marketing uses the Editor — a content-only view that lets them edit copy, swap images, add CMS items, schedule posts, and publish. They cannot touch layout, classes, or interactions, so they literally can't break the design.

For advanced edits such as new sections or hero tests, reusable components with content properties keep updates consistent. A one-day handover helps your team take ownership when ready.

Question 5

Do you handle hosting setup — custom domain, SSL, CDN?

Accepted Answer

Yes — included on every tier. Webflow hosting comes with AWS-backed CDN, free SSL via Let's Encrypt, automatic asset optimization, and 100GB bandwidth on the Basic Site plan. We configure your custom domain (CNAME + A records), set up the SSL handshake, verify it propagates globally, and confirm Core Web Vitals before we hand over.

One thing to flag: Webflow hosting is a separate monthly bill from Webflow itself — $14-49/mo per site depending on plan. That's your cost, not ours. We help you pick the right plan during the brief audit (CMS plan for most marketing sites, Business for high-traffic or 10k+ CMS items).

Question 6

Can you really publish a site in 7 days?

Accepted Answer

For a Site Build on a defined scope (6-10 pages, our design or yours, your content brief in by Day 0) — yes, and the 7-day milestone is when we hit the Publish button. For a Page Build it's 5 days. For a Migration with content port + 301 redirects + IA rework, it's 4 weeks.

The same senior stays from brief to Publish, with components and CMS structure decided on Day 1. Async Slack reviews keep feedback focused and reduce unnecessary meetings.

Question 7

I already have a Figma — do you just build it?

Accepted Answer

Yes — that's exactly what the Page Build tier ($1,400) is for. You ship the Figma, we build it in Webflow pixel-faithful: type ramp, spacing, motion, hover states, breakpoints (1440/991/767/479), interactions, form wiring, SEO, all preserved. 5 days. One page.

For a full site from an approved Figma file, the Site Build tier covers 6–10 pages with CMS Collections, reusable components, and native interactions. Design changes are scoped separately as a UI/UX engagement.

Question 8

Webflow's own subscription cost — who pays?

Accepted Answer

You pay Webflow directly — they're a separate vendor. Our pricing covers design + build + handover. Webflow's monthly bill (workspace + per-site hosting plan) is yours, in your account, on your card. We help you size it right on Day 0 so you don't overpay or hit a limit.

Typical costs: Workspace — Core plan $19/mo (1 designer seat). Site hosting — Basic $14/mo or CMS $23/mo for most marketing sites, Business $39/mo if you need 10k+ CMS items or staging environments. E-commerce add-on — Standard $29/mo or Plus $74/mo if you have a storefront. We work within whatever you're on.

Question 9

Does Webflow Localization actually work for EN+AR?

Accepted Answer

Yes — and we've shipped 9 bilingual EN+AR sites on it. Webflow Localization (launched 2023) handles per-locale URLs (e.g. /en/pricing + /ar/الأسعار), hreflang tags, locale-aware CMS Collections, language switcher components, and dir="rtl" attribute switching. The tricky part is RTL design discipline — most agencies translate copy and call it bilingual; we rebuild the visual hierarchy in both directions.

We work in IBM Plex Arabic, GE SS, 29LT, and bespoke Arabic typefaces. Arabic numerals in SAR/USD pricing, GCC trust signals (CMA, SAMA, SDAIA logos), Hijri-aware date pickers, and currency switchers that respect locale. Both directions reviewed daily and shipped together. For full bilingual brand work (logo lockup, type ramp, color tokens across both directions), pair this with our Brand Identity service.