Create a headless space
You’ll create a headless space — a Structura site that lives entirely in the customer portal, with no WordPress install — and see where your posts appear once campaigns run. If your site runs on WordPress, follow Install the plugin instead; this page is for everyone else: Next.js, Astro, Nuxt, custom sites, and mobile apps.
A headless space works like any other Structura site: you set up your brand, run campaigns, and review posts. The difference is where posts end up. Instead of publishing into WordPress, Structura stores them in the cloud and serves them from a public Delivery API that your website fetches — Structura becomes your content backend.
Before you start
You’ll need:
- A Structura account — sign in at app.structurawp.com .
- The address of your public website (e.g.
https://example.com) — the site where your readers will actually see the posts.
You do not need a developer to create the space or generate content. You (or your developer) only need code changes at the very end, to display the posts on your site — see What happens next.
Steps
-
In the customer portal, choose Add site. You’ll be asked Where does your content live?
-
Pick the Headless card and select Create a headless space.
-
Enter your Public website URL — where your readers actually are. Structura uses it to ground SEO suggestions and to make sure links inside delivered posts point at your real domain.
-
The Site name fills in from the URL; change it if you like, then select Create headless space.
-
The setup wizard opens, the same one WordPress sites use: brand positioning, persona, and visual style. Complete it (or skip steps and return later — the space already exists).
-
Create your first campaign. The flow is identical to the WordPress one — see Your first campaign; everything on that page applies except the WordPress-specific screens.
What happens next
- Generated posts appear under your site’s Posts in the portal, waiting for review. Publishing a post makes it available on the Delivery API — it does not appear on your website by itself.
- Your site’s Delivery API page shows the exact web addresses your site uses to fetch published posts, one feed per language you publish in. Send that page to your developer — the technical details live in the Headless delivery API reference.
- Once your site fetches and displays the feed, new posts flow through automatically: campaign runs → you review → publish → your site picks it up.
Common issues
- “…is already connected to this workspace.” Each domain can be connected once per workspace. If the domain belongs to an old site you removed, remove it fully first (see Removing a site).
- Posts are published but my website doesn’t show them. The Delivery API only stores and serves content — your website has to fetch it. Check with your developer that the integration from the Delivery API page is in place, and that your site rebuilds or revalidates when content changes.
- My blog is in several languages. Run one campaign per language. Each language becomes its own feed on the Delivery API page.