Waggle works out what people are searching for, writes the article that answers it, and publishes it to a Foundation CMS site through the content API. This website's blog is written that way: the topic comes from real search data, the article is written and checked with Claude, and it lands on the site filed and searchable, with Bing told the moment it is live.
Overview
This integration connects Foundation CMS with Waggle, Swarm Labs' search and AI discoverability product. Foundation CMS is Swarm Labs' multi-tenant content management system on Cloudflare Workers. It holds a site's content and hands it to the site as whole, typed records, and every site runs as its own Worker with its own database and media bucket. Waggle optimises a business's presence across search engines and AI answers, and its writer turns that research into published articles.
It is the setup behind this website's own blog: Waggle writes the posts and publishes them to swarmlabs.io, which runs on Foundation CMS.
Business Context and Core Use Case
Publishing regularly is one of the most reliable ways to be found, and also one of the easiest to let slip. The hard part is rarely the writing; it is choosing topics people actually search for and getting each piece onto the site properly, with its category, search description and links in place. Waggle does both: it picks the topic from evidence and publishes through the Foundation CMS content API, so a finished, correctly filed article reaches the site without anyone copying text into a CMS.
The Applications Involved
Waggle (Waggle) researches, writes and checks each article. It runs in its own Cloudflare Worker, using the site's Google Search Console data, keyword data, the live search results and what the site has already published.
Foundation CMS (Foundation CMS) receives the article through its content API with a key scoped to that site and to the abilities the writer needs, records a revision, files the categories and publishes it.
How the Integration Works
Waggle's scheduler starts a run, and each run works through its steps as a durable workflow. It looks at the site's search performance, keyword demand, the live results for the query and the site's existing posts, then picks a topic that fills a real gap. The article is written and checked with Claude, and Waggle publishes it through the Foundation CMS content API, cover image first, then the post. Foundation CMS saves it the way an editor's save would, revision first, and on a site with the IndexNow setting on it pushes the new address to Bing straight away; Google finds it through the sitemap. Waggle records each run and post, so what was written and how it performs stay connected.
Immediate Operational Value
The blog keeps moving without a weekly meeting about what to write. Topics come from evidence, not guesswork, a check on existing posts keeps the site from repeating itself, and every article lands in the same shape as a hand-written one: same fields, same categories, same search description. Because the write goes through the same door as the editor, an editor can open and change any post in the admin like any other entry.
Security, Access, and Governance
Waggle's Foundation CMS key belongs to one site and is limited to the abilities it needs, such as writing posts and uploading media, so a leaked key costs one site and cannot touch others. Keys are hashed at rest, shown once when made, and record when they were last used, so a stale one is easy to spot and revoke. Every API write records a revision first, so any automated change can be undone.
Summary
Waggle decides what is worth writing about, writes it and publishes it; Foundation CMS makes sure it lands properly. The result is a site that publishes on evidence, with every post filed and searchable from the moment it goes live.
Frequently asked questions
Do Waggle's posts look different from hand-written ones?
No. The content API saves a post exactly as an editor's save does, with the same fields, categories and revision history, and editors can open and change it in the admin.
What can Waggle's key do?
Only what it was given, on one site: typically writing posts and uploading media. It cannot read or write any other site.
How quickly do search engines hear about a new post?
On a site with IndexNow switched on, Foundation CMS tells Bing and the engines that take the push at publish time. Google follows the sitemap.
Does this need Search Console?
Waggle's research is strongest with the site's own Search Console data, which it reads with read-only access.
