Start with complete data
Expose range, freshness, completeness, and cache provenance.
Search growth
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
Why BlogFactory
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.
Operations pulse
The overview keeps Search Console provenance, page-one opportunities, and dependencies visible before work begins.

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

How it works
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.
Capabilities and boundaries
Every result keeps scope and freshness visible.
Search work uses the same human approval boundary.
FAQ
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.
Yes. The public repository is available for self-hosting as a release candidate. BlogFactory Cloud is not available yet.
Inspect the public source, then follow the source-build Docker Compose guide for the open-source release candidate.