Exact capability
Read the authorized repository structure and prepare content/code artifacts, branches and PR-linked approval records for the selected site.
Explore SEOForge
Live integration · publishing
Prepare repository-native changes without creating a production backdoor.
SEOForge works only in an authorized repository context, creates proposal work on a non-default branch and preserves code-owner review, branch protection and the repository’s deployment controls.
Nothing publishes without approvalPaid product accessNo ranking guarantees
proposal/seo-184
build ✓ lint ✓ routes ✓
merge: human required
Requested access
Selected repository installation/access, repository contents and pull-request metadata needed for the configured proposal path; production secrets are not requested.
Cannot
Push directly to the default branch, bypass required reviews, merge, deploy, alter protections or retrieve repository/CI secrets.
Credential protection
Provider access stays outside agent context.
- Installation or provider grant stored in the integration layer
- Repository selection remains tenant- and site-scoped
- Tokens and secret values are redacted from runs and artifacts
- Revocation stops new repository work
- Audit history records proposal and production state
Setup
Connect, detect, validate.
- 01
Choose GitHub during paid site onboarding
Evidence, owner and next state remain visible.
- 02
Authorize the intended repository only
Evidence, owner and next state remain visible.
- 03
Detect framework, default branch and commands
Evidence, owner and next state remain visible.
- 04
Run a read/build readiness check
Evidence, owner and next state remain visible.
- 05
Configure reviewers and protected production path
Evidence, owner and next state remain visible.
Example workflow
A Next.js metadata fix arrives as a checked proposal.
SEOForge reproduces duplicate canonicals, edits the existing metadata convention on a proposal branch, runs repository commands, attaches affected routes and waits for the code owner. Your GitHub workflow—not an agent—merges and deploys.
Limitations
Repository detection cannot guarantee every custom build or deployment environment. Private dependencies, required environment variables, monorepo policies and CI checks must be available to the configured validation path.
Questions
Know the boundary before connecting production.
Can SEOForge merge after I approve in chat?+
No. Merge and deployment remain in the configured protected human production path.
What happens after revocation?+
New repository work stops and affected workflows show a connection error; existing Git history remains yours.
Paid deployment · human authority
Connect GitHub with the same protections your team already trusts.
Choose a plan, select the repository and validate the proposal path before activating agents.