Add a blog to your AI-built website
For sites with a custom front end, including sites built with AI.
Keep your existing website and add a blog that matches its design. Structura researches and writes the articles; your website displays them on your own domain. Article delivery sends a complete article to your website when you publish it.
Before you start
You need a published website, a backend that accepts HTTPS requests and a database to store articles. Your builder can create these, but you must test the result. This is a custom integration, not an official Lovable, Bolt, v0 or Replit connector.
Article delivery is available for Headless sites in the customer portal. WordPress sites don’t offer it.
Sites on a framework don’t use Article delivery either. If you pick Next.js, Astro, Nuxt, SvelteKit or Another framework or app as your site’s Platform, your site fetches published posts from the Content API instead, and the setup wizard shows the requests.
Article delivery requires a paid Structura base plan. You do not need the Channels add-on. For a free headless setup, use the public Content API instead. AI usage and builder hosting may cost extra.
Steps
The fastest route starts with your site’s address: Connect a site opens the site setup wizard, and its last step, Connect, walks you through the receiver.
-
In the customer portal, select Connect a site. Enter your Public website URL and select Continue. Structura reads your site, creates it and opens Site info.
-
Under Platform, check that your builder is selected, or pick My own backend for a site you built yourself. When Structura recognized your builder, the field says Detected from your site. A custom domain often hides the builder; then the field says Not detected and you pick it from the list (or Change platform if the guess was wrong). Structura recognizes a v0 site from the tag v0 adds to its pages, even on a custom domain. Without that tag it suggests Next.js, which fetches from the Content API; pick v0 if you built your site with v0.
-
Work through the wizard. Its last step before Done is Connect. Copy the prompt into your builder; it is the same prompt as your builder’s tab below, and it points your builder at the delivery contract. Lovable adds a receiver route inside your site, usually
/api/public/structura-articles; Bolt creates a Supabase Edge Function namedstructura-articles; v0 and Replit add a route at/api/structura. On a custom-built site, follow the contract directly. Then paste the receiver URL your builder gives you and select Continue. -
On Verify, copy the Signing secret into your backend’s secret storage as
STRUCTURA_SIGNING_SECRET. It is shown once. Never paste it into the builder chat, public code or browser environment variables. Your builder may offer a secrets form in its chat; use that rather than pasting the secret as plain text. The connection is saved as soon as the secret appears, so you can leave for your builder and come back any time to send the test: the Connect step then shows the saved connection as Not tested, with Send test article. -
Choose Send a test article now to check the receiver straight away. Your site saves it as “Structura test article”; delete it afterwards. A passing test marks the connection Connected right away. Or choose Test with my first real article and select Test later: nothing is sent, and your first published article is the test. If you’re not ready to paste a receiver URL, select Connect later and come back from the Channels page.
-
Create a campaign in the language you want to publish. Use review mode for your first article. Publish a draft, then open Activity and your public article URL. Check the title, body, images, language, metadata and mobile layout.
A connection you make in the wizard sends articles from every campaign. To rename it or pick campaigns, open it on your site’s Channels page.
Your site’s Overview shows the Article delivery state: Connected, Not tested or Not connected.
Connect a site that’s already in Structura
The Connect your site dialog still works for any headless site you already have. On the site’s Channels page, select Install on the Article delivery card. Pick your platform, copy the prompt into your builder and paste the receiver URL it gives you, then continue with steps 4 and 5 above. If you close the dialog before you test, the connection is already saved: on the Connections tab, select Configure, then Send test article and Save. On Done, rename the connection if you like and pick the campaigns to send.
Prompt for your builder
Add a blog to my existing site without replacing its design. Use my current fonts, colors and navigation. Add /blog and /blog/[slug], with real 404s for missing posts, crawlable article pages, metadata, canonical URLs and sitemap entries.
Connect Structura Article delivery. Follow the delivery contract at https://docs.structurawp.com/en/reference/article-delivery
Add the receiver the way this project supports it: a public HTTPS POST route inside the site at /api/public/structura-articles, or, only if this project cannot host a route, a Supabase Edge Function named structura-articles with JWT verification off (verify_jwt = false). Add a persistent articles table. Read the raw request body before parsing it. Keep STRUCTURA_SIGNING_SECRET in the project’s secrets only.
Verify X-Structura-Signature against the exact raw UTF-8 request body and X-Structura-Timestamp using HMAC-SHA256(secret, timestamp + "." + rawBody). Reject timestamps outside 5 minutes and invalid signatures before changing data. The only supported event is the JSON body’s event "post.published" with schema_version 1; there is no event header. Reject other events or schema versions with 422. Read STRUCTURA_SIGNING_SECRET from the receiver’s environment or secrets at request time only; never store it in a database or vault, and never expose it through a function, RPC or endpoint the browser can call.
Use a database transaction with a unique event_id to deduplicate deliveries and upsert articles by site.id + post.id + post.locale. Reject older revisions. The article body is post.html (sanitized HTML) with post.markdown beside it; there is no post.content field. Store post.html and the available SEO fields. post.featuredImage is an object with url and alt, or null; use its url for the article’s hero image and og:image, and its alt as the alt text. Sanitize HTML when rendering. In the article page head, emit every post.jsonLd entry in the order received, including the first (BlogPosting), each safely serialized in its own <script type="application/ld+json">; do not merge, deduplicate, rewrite or replace them, and do not add a BlogPosting or Article node of your own. Render post.author (name, avatarUrl, bio, link to url) as the byline when it is not null. Respond with 2xx only after durable storage; duplicate valid events should also return 2xx.
Do not ask me for the value of STRUCTURA_SIGNING_SECRET yet: use a temporary value for your own tests, and ask for the real one after you reply with the receiver URL; I get it from Structura once I paste your URL there. Test a valid delivery, a bad signature and a replay, then open a delivered article page and confirm the canonical URL, the featured image and every JSON-LD script really render, before you say it’s done. If the hosting cannot return real 404 status codes or serve /sitemap.xml as XML, say so instead of adding client-side stand-ins. When done, reply with the public URL of the receiver so I can paste it into Structura.What happens next
Each new publication sends one article, including drafts you approve later. Drafts stay private. Articles keep their content language; notification language does not translate them. Existing posts are not imported automatically.
Later edits and deletions are not synchronized by this first delivery option. Update the copy on your site, or use the Content API when you need the current published state. Repeated delivery can happen; the receiver must deduplicate it.
Common issues
-
Not tested: the connection is saved, but no test or real article has reached your receiver since you set it up or changed its URL or secret. Select Send test article on the setup wizard’s Connect step, or open the connection on the Connections tab, select Send test article, then Save. You can also publish a new article and check Activity. Confirm the campaign binding.
-
HTTP 401/403: check the signing secret, raw-body verification and any hosting access protection. On Bolt, also check that the
structura-articlesfunction does not require a JWT. -
HTTP 404: use the deployed receiver URL, not a builder preview page.
-
HTTP 429/5xx or a timeout: Structura makes one immediate retry. There is no durable queue or automatic retry later. Fix the receiver and reconcile missing posts through the Content API.
-
Article unavailable: confirm the post is public, has content and has a public URL.
-
Article too large: the complete JSON payload must fit within 1 MB. Large articles should be read through the Content API.
-
Plan not entitled: article delivery needs an active paid subscription. Check your plan and payment status. The Channels add-on is not required.
Related pages
Last verified