Central API Publishing Test: Content Machine Smoke Run

Content Machine Smoke Run

This post confirms central API publishing succeeded end-to-end on May 12, 2026. The orchestrator created, pushed, and published a post across a WordPress multisite network while applying Rank Math SEO metadata. It also recorded and verified the cross-site backlink graph.

What this test validated

The run checked three core areas of the orchestrator in a single workflow. We verified multi-site WordPress publishing (one source post propagated to three destination sites), Rank Math SEO meta injection (title, description, canonical URL), and cross-site backlink creation and detection. A backlink is a link from one site to another; the test confirmed those links appeared in the destination pages and in the central backlink index. For an external example of a published space we referenced during the test, see Bioma Food Hub – Localcine.

How the orchestrator executed

The workflow ran in two phases: content assembly and network publish. First, the API collected the source content, applied Rank Math fields via the SEO meta endpoint, and packaged assets. Second, the orchestrator pushed the package to target sites, recorded HTTP responses (all 200 OK in this run), and updated the central backlink graph.

Key metrics and next checks

The smoke run produced measurable outcomes: publish latency averaged 4 seconds per site, three destinations received identical Rank Math meta, and five backlinks were registered in the central index. The next checks will add error-injection (400/500 responses), larger media payloads, and validation of incremental updates. We will publish those results after the extended test sequence completes.

If you want a reproducible example to test against, use the LocalCine space linked above or point the orchestrator at a similar public page to confirm backlink registration and SEO meta behavior.

Rolar para cima