Frequently asked questions
Everything you need to know about FlxWoo (SaaS), FlexWoo, and FlexWP. Keep WordPress compatibility and SEO; render mapped routes with Next.js + Tailwind; and rely on instant fallback for safety.
Getting started
Do we need to migrate away from WordPress?
No. WordPress still runs first—your theme, plugins, hooks, and SEO execute as usual. FlexPlat replaces the final HTML for the routes you map (e.g.,
/shop, /product/*, or content pages).What should we roll out first?
Most teams begin with PLP (listing) and PDP (product detail) or key marketing pages. You can expand route by route, keeping instant fallback to the original WP theme for safety.
How long does a first rollout take?
With an existing design (Figma) and Tailwind tokens, initial routes are often live in days; larger rollouts land in 1–3 weeks.
Performance & Core Web Vitals
How does FlexPlat improve LCP/INP/CLS?
We render via Next.js + Tailwind with predictable image sizing, minimal client JS, and caching for content routes. Targets we design around: LCP ≤ 2.5s, INP ≤ 200ms, CLS ≤ 0.1. Actual results vary by host, media, and theme complexity.
What’s cached and what isn’t?
PLP/PDP and marketing pages can use ISR/SWR-style caching. Cart/Checkout and account pages remain no-cache by default.
Can we monitor Web Vitals?
Yes—report to GA4/BigQuery or your observability tool. Our templates integrate cleanly with common Web Vitals libraries.
SEO & URLs
Will our SEO be preserved?
Yes. We reuse output from Yoast/RankMath (titles, canonicals, JSON-LD) and keep your URLs the same for mapped routes.
Do we need to rebuild schema markup?
No—existing JSON-LD from your SEO plugin is surfaced in the rendered HTML for parity.
Does server rendering affect indexing?
Pages are server-rendered and cacheable; search engines can crawl normally. Ensure sitemaps and robots remain healthy.
Checkout & safety
Is WooCommerce Checkout safe with a headless layer?
Yes. Cart/Checkout routes are no-cache by default and honor WooCommerce security constraints.
What happens if the renderer is down?
Health checks trigger an instant fallback to the original WP theme for mapped routes, keeping the store usable.
Can we opt out specific routes?
Absolutely. Route mapping is granular—enable headless where you’re ready; keep native WP elsewhere.
Plans, pricing & white-label
How does pricing work across the suite?
FlxWoo (SaaS) is traffic-based per site. FlexWoo/FlexWP are yearly plugin licenses (Dev/Pro/Enterprise). See Pricing.
Do you offer white-label?
Yes. Branding removal + custom domain/CNAME for FlxWoo (included on Pro; add-on on lower tiers). FlexWoo/FlexWP support white-label as an add-on on Pro. See partner pages for details.
Can we start on FlxWoo and later move to FlexWoo?
Yes. Many teams start hosted for speed, then migrate to self-hosted (FlexWoo) when they want full code control.
Choosing between FlxWoo, FlexWoo, and FlexWP
When should we choose FlxWoo (SaaS)?
When you want speed without ops. No infrastructure to manage, traffic-based plans, optional white-label. Great for fast CWV wins.
When should we choose FlexWoo (plugin + code)?
When you want full code ownership for WooCommerce headless. Ideal for agencies with CI/CD and deep customization needs.
When should we choose FlexWP (content sites)?
For headless WordPress content sites (non-commerce). Keep plugins and SEO; render mapped pages via Next.js + Tailwind.
Still have questions?
Tell us your goals (speed/CWV/SEO), traffic profile, and timeline—we’ll recommend the best rollout and plan.