Verifying a Foundation CMS site in Google Search Console is a setting: paste the verification value and every page carries it. The site is built to be read well once verified, with a sitemap, structured data and robots rules generated from the content, and Waggle can read the Search Console data back to decide what to write next.
Overview
This integration connects Foundation CMS with Google Search Console. 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. Search Console verification is a site setting: the content value of Google's HTML-tag verification, which the site puts in the head of every page.
Business Context and Core Use Case
Search Console is where a business sees how Google actually treats its site: which queries it appears for, which pages are indexed and what is wrong. Getting there normally means asking a developer to add a tag. On Foundation CMS an administrator does it in a minute, and the site gives Google what it needs to read it well, generated from the content rather than maintained by hand.
The Applications Involved
Foundation CMS (Foundation CMS) carries the verification tag and produces the sitemap, structured data and robots rules from each site's content.
Google Search Console (Google Search Console) verifies ownership and reports on indexing and search performance.
How the Integration Works
In Search Console, choose the HTML-tag method and copy the value of its content attribute. Enter it in the site's search settings; the site adds the tag to every page, and Search Console can verify. Submit the site's sitemap there. Google does not accept IndexNow pushes, so it follows the sitemap to find new and changed pages. With Waggle, the Search Console data can be read daily and used to choose what to publish next.
Immediate Operational Value
Verification no longer needs a code change, and the things Search Console checks are produced by the platform: one canonical address per page, preview controls for snippets, and structured data that matches what is visible. Problems Search Console reports can usually be fixed in content, by the people who own it.
Security, Access, and Governance
The verification field only accepts the value itself, letters, digits, hyphens and underscores, so pasting a whole tag or a script is refused. Only administrators can change search settings. Verification grants access to search data, not to the site; who can see that data is managed in Search Console.
Summary
Paste one value and a Foundation CMS site is verified in Search Console, with a sitemap and structured data already in place for Google to read.
Frequently asked questions
Do I need a developer to verify the site?
No. An administrator pastes the verification value into the site's settings and every page carries the tag.
Does Foundation CMS push new pages to Google?
Google does not accept IndexNow pushes; it follows the sitemap. Bing and the engines that do accept a push are told at publish time.
Can I paste the whole meta tag?
Paste only the value of its content attribute. The field refuses anything else, so a script can never be pasted in.
Can Search Console data guide what we publish?
Yes. Waggle reads the site's Search Console queries daily and uses them to pick topics.
