Flx Headless

Published WordPress Pages, single Posts, the blog index, category archives, tag archives, search results, and the 404 page. Drafts, pending, and private content are not rendered through Flx Headless. Menus, comments, and full-site rendering are not covered.

Flx Headless automatically falls back to WordPress's native rendering for that request. No configuration is required to enable this fallback.

No. Flx Headless has no dependency on WooCommerce or any other plugin.

The Settings section of the Flx Headless screen shows https://render.flxheadless.com as placeholder text and a suggested starting point. It is operated by the Flx project as a ready-to-use Render service, and using it is entirely optional. The Render URL field is empty until an administrator enters and saves a value — no data is sent to that or any other service automatically. After activation, Flx Headless also shows a dismissible setup notice in wp-admin offering to enable this same service with one click; nothing is sent unless that click happens or a Render URL is saved manually on Settings — dismissing the notice sends nothing and leaves the Render URL empty. Administrators may use the suggested service, run their own self-hosted Flx Render service, or point to any other service implementing the Flx Render API.