Start with complete data
Expose range, freshness, completeness, and cache provenance.
Coordinate complete-day analytics, ranked opportunities, dated plans, page diagnosis, indexing, and internal links inside the same editorial workflow.
BlogFactory · Editorial control schematics
High impressions · low CTR
Expose range, freshness, completeness, and cache provenance.
Create dated refresh, snippet, link, indexing, or new-content actions.
Use page, query, inspection, and sitemap evidence first.
Report correlation without causal or ranking claims.
The overview keeps Search Console provenance, page-one opportunities, and dependencies visible before work begins.

Performance trends and ranked opportunity classes share a screen so teams can see why an action is being proposed.

Read complete-day property data and bounded page/query opportunities.
Add a dated action and hand content changes into the draft flow.
Compare later complete-day windows without claiming causation.
Every result keeps scope and freshness visible.
Search work uses the same human approval boundary.
Yes. Content, sources, permissions, provider access, search properties, and destinations remain scoped to the authorized site.
No. Agent authority stops at approved CMS draft creation. Live publishing, deletion, credentials, and account administration stay outside MCP.
Self-host the AGPL-3.0-only release candidate for free, or create a managed BlogFactory Cloud account from $5 per month. Both editions keep CMS delivery draft-only.
Inspect the public source, then follow the source-build Compose guide — or let Cloud run it from $5 a month. The boundary is identical in both.