Framework detection
Routes, rendering mode, content source, image behavior and metadata conventions.
Explore SEOForge
Site Experience Engineer
Production work that belongs inside your website.
Before preparing a change, SEOForge identifies the framework or CMS, repository conventions, theme, design tokens, content model, build commands and protected delivery path.
Nothing publishes without approvalPaid product accessNo ranking guarantees
SITE PROFILE · github/app-router
framework: Next.js 16 · App Router
theme: dark · tokens in globals.css
content: MDX · /src/content/guides
build: npm run build
branch: seoforge/refresh-oauth
Repository understanding
The site profile is a prerequisite, not an afterthought.
Theme matching
Colors, type, spacing, components, breakpoints and existing blog patterns.
Exact diff
Repository-native content, code, schema, links and configuration changes.
Protected delivery
A branch and pull request or governed WordPress proposal—never a production shortcut.
Build and screenshots
Typecheck, build and route checks plus desktop and mobile preview captures.
Rollback
Revert commit or CMS revision with affected paths and post-revert checks.
Implementation workflow
Profile, implement, prove and hand over.
- 01
Inspect authorized framework, theme and publishing structure
Evidence, owner and next state remain visible.
- 02
Map the approved artifact to site-native routes and components
Evidence, owner and next state remain visible.
- 03
Create a bounded branch or WordPress revision proposal
Evidence, owner and next state remain visible.
- 04
Apply content, code, media, metadata and link diffs
Evidence, owner and next state remain visible.
- 05
Run typecheck, build, lint, schema and broken-link validation
Evidence, owner and next state remain visible.
- 06
Capture responsive screenshots and attach rollback instructions
Evidence, owner and next state remain visible.
- 07
Route the complete proposal to a human reviewer
Evidence, owner and next state remain visible.
Example production packet
A finished route, checked against the real theme.
- Input: approved OAuth comparison article and decision diagram
- Files: page.mdx, oauth-decision.webp, related-links.ts and sitemap.ts
- Theme: existing card radius, muted palette and responsive prose width
- Checks: build passed; links 200; JSON-LD valid; no console error
- Screenshots: 1440px desktop and 390px mobile
- Rollback: revert commit 82ba1 and re-run affected route smoke checks
PULL REQUEST #184
+ src/content/guides/oauth-vs-api-keys.mdx
+ public/media/oauth-decision.webp
~ src/app/sitemap.ts
type ✓ build ✓ links ✓ schema ✓ screenshots 2
Human production review
Review the exact files or CMS fields, visual preview, checks, risk and rollback. Agents cannot merge a branch or publish WordPress.
Paid implementation capacity
Plans define sites, concurrent work and execution capacity. Unsupported frameworks or failing builds stay blocked instead of being forced through.
Questions
Know the boundary before connecting production.
How does SEOForge match our design?+
It profiles approved design tokens and existing route patterns, then validates the implementation with responsive screenshots.
Can it work with WordPress?+
Yes. It maps the theme, editor fields, media, taxonomies and revision process before preparing a proposal.
What if the build fails?+
The proposal remains blocked with logs and the failing check; it cannot reach approval as production-ready.
Can the agent merge its pull request?+
No. Merge, deploy and WordPress publication require the protected human workflow.
Is rollback automatic?+
SEOForge prepares rollback instructions or a proposal; consequential rollback still requires authorization.
Paid deployment · human authority
Connect approved SEO work to a website-native delivery layer.
Choose a paid plan and onboard one authorized repository or WordPress destination.