WordPress

Paste a WordPress site's URL and Zitegen reads its public REST API — no plugin, no export, no migration. Content is fetched fresh at build time and is never copied into or stored by Zitegen. A site URL alone is enough for any public, published content ("Quick Connect"); add a WordPress Application Password only if a test connection says the site needs authentication (private or gated content).

A single Zitegen site can pull from any number of WordPress installs at once — a blog on one, a knowledge base or case-study feed on another. Each connection has its own label, so it's easy to tell them apart when binding content on the canvas or in a page's component tree.

Once connected, browse every post type a connection exposes — including custom post types and ACF fields — with a live field inspector. Click any field to copy its {{dot.path}} placeholder, then use it to bind a section or card to that WordPress connection's live data.

A bound section shows a small sample of the connection's real posts right in the canvas — not just the empty card template — so you can see roughly what visitors will see while you're still styling it, the same live-preview behavior a Filterable Collection gets for Zitegen's own content types. You're always editing the one shared card template, never an individual post; a not-yet-connected or unreachable site just falls back to showing the unresolved template instead of breaking the editor.

A WordPress-bound grid supports the same visitor-facing pagination (numbered pages, load more, infinite scroll) and filter bars as a Filterable Collection of Zitegen's own content — both run entirely in the visitor's browser over the cards baked in at publish time. Filter fields use the same {{dot.path}} names as the card's placeholders (e.g. a search box matching against title.rendered). Dynamic mode is the one Filterable Collection feature that doesn't apply — a WordPress collection always bakes its full set at publish.

Everything above pulls WordPress content into your Zitegen site. A connection can also run in reverse for forms: a Zitegen form's submissions can optionally relay into that WordPress site's Fluent Forms plugin, on top of — never instead of — landing in your site's own Leads tab. See Forms & Leads for how to set up the mapping and what a delivery failure looks like.