SEO Implementer
Provide the fix list. Connect your CMS. Let the agent implement and publish.
Private pilot · Browser Use execution in your own Chrome · live CMS acceptance pending.
Private workspace
Open your private access link to continue. No email or password required.
1. Connect one CMS editor
Sign in to your CMS directly in Chrome. Never paste its password here.
Create an action-plan run below, authorize it, then use its pairing code in the extension.
2. Run a complete audit action plan
Download Chrome extension + local helper · Install the helper once, then load the Chrome extension. See docs/CHROME-TEST.md in the package.
Paste the action-plan JSON, CSV or Markdown table exported by the SEO audit. Every row stays in the report, including blocked items. The Browser Use Chrome extension connects just your selected CMS tab. Sign in to your CMS personally, then enter the pairing code in the extension.
Use the exact CMS editor URL above. Install the local helper and Chrome extension once, then connect from the CMS tab. Keep Chrome open; Stop in the extension disconnects the agent. No provider key or debugging-port setup is needed.
Legacy single-field pilot
Prepare a single change
The extension lets you select fields and a save button. Only those controls can be changed.
Manual proposal / n8n planner output
Paste JSON with action_id, reason, edits:[{field_id,after}], public_url, checks:[{kind,expected}]. Check kinds: title, description, canonical, h1, text.
4. Review, approve and verify
Learning and evidence
Verified fixes create tenant-private candidate recipes. These are stored procedures, not model retraining or permission to repeat a write.