In developmentSEO CMS for static websites
SEO Command Center
SEO content on several sites, without touching the repository by hand.
SEO Command Center reads Search Console data, builds the editorial plan, prepares articles that follow each site's template and publishes them with a checked commit on GitHub.
- In development, used on the sites I manage
- Real Search Console data
- Checked publishing
SEO Command Center
- Search Console queries
- Clusters by intent
- Editorial plan
- Draft from the template
- Slug and link checks
- Commit on GitHub
TotalPublished
The problem
A static site is fast. Updating it, much less so.
Every new piece of content becomes a change to the repository: write the file, follow the template, update the internal links, check the slug, commit. If the person running the site isn't a developer, the process stalls; if they are, it's still repetitive.
SEO Command Center separates editorial work from the repository: whoever writes and optimises works in an interface, and the repository stays clean and versioned.
How it works
Step 1
Reads the real queries
Search Console shows which searches bring visits, at which position and with what CTR: the work starts there, not from guesses.
Step 2
Builds the plan by cluster
The AI groups keywords by intent and proposes each article's structure: title, sections, questions, internal links.
Step 3
Prepares and checks
The draft follows the site's template; frontmatter, slug and internal links are checked before publishing.
Step 4
Publishes with a commit
A commit or pull request on GitHub, with credentials in Cloudflare Secrets and a trail for audits and rollbacks.
What it does
A space for each site
Templates, slug structure, internal links, tone and editorial rules live apart: an article for one site can't spill into another.
Opportunities from the data
Searched topics without a dedicated page, articles between positions five and fifteen worth updating, related keywords not covered yet.
Drafts to review, not to write
The structure and a first version arrive ready: the editor's job is to review, not to build from scratch.
Checks before the push
Complete frontmatter, valid slug, existing internal links: if something doesn't add up, the article doesn't go out.
Isolated credentials
Each site's keys stay in Cloudflare Secrets, never in the code or the interface.
Every change tracked
Every publication is a commit: you know what changed, when, and you can roll back.
Built with: Cloudflare Workers · Cloudflare D1 · AI · Google Search Console API · GitHub API · Astro
Who it's for
People running several static sites
Each site has its own rules, but the editorial work happens in one place.
People working on SEO
You start from real queries and measured opportunities, instead of a keyword list chosen on instinct.
Teams that want a clean repository
Nobody edits files by hand: every piece of content goes in with a checked commit.
Frequently asked questions
Is it available yet?
Not to outside users yet. It's in active development and I use it on the sites I manage. Access, pricing and availability will be published only once it's stable across more contexts.
Which sites does it work with?
It's designed for static sites versioned on GitHub, like those built with Astro, where every piece of content is a file in the repository.
What does the AI do?
It groups keywords, proposes the article structure and prepares a first draft. Nothing is published without checks and approval.
Where are the credentials kept?
In Cloudflare Secrets, separate for each managed site.
Interested for your own sites?
The product isn't open to outside users yet. If you run static sites and want to know whether it fits, write to me and I'll tell you where it stands.
Part of the Suite: all my products with one login and dedicated support. Discover the Suite →
← All products