Submit the active site
Keep indexing requests limited to the selected domain.
Search Growth · Discovery
Use scoped indexing providers and semantic internal-link evidence after reviewed changes, without confusing submission with ranking or publication.
BlogFactory · Editorial control schematics
High impressions · low CTR
Why BlogFactory
Keep indexing requests limited to the selected domain.
Track accepted, queued, skipped, and failed submissions.
Use the site page corpus for relevant internal-link work.
Submission requests discovery; it never guarantees indexing or ranking.
Indexing
The captured surface keeps the active site, Search Console connection, configured providers, and submission state visible.

How it works
Start after the current content version is approved and delivered.
Submit the changed URL through a configured provider for the active site.
Use semantic page context to propose relevant links through review.
Capabilities and boundaries
Configured providers remain scoped and inspectable.
Link proposals use the active site corpus.
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.