Documentation
Automated publishing guide
How an approved fix travels from an audit finding to a verified change on your live website — and how to undo it.
Citable summary
AgenticSEO publishes approved fixes directly to your website. You connect a publish target once (WordPress, Webflow, HubSpot, or a GitHub repository), run an audit, review the generated titles, meta descriptions, JSON-LD, llms.txt, and FAQ answers, then approve them. The agent writes the changes to the live site, verifies the published URL reflects them, and records the run so any push can be rolled back.
Step 1: Identify visibility gaps
Run a Baseline Audit on your website. AgenticSEO crawls the pages you select and scores each one across six discoverability layers: classical metadata, Schema.org JSON-LD, AI-crawler access, answer-readiness, llms.txt coverage, and sitemap coverage.
- Every miss becomes a typed work item rather than a line in a report.
- A separate Prompt Audit runs your tracked buyer prompts against ChatGPT and Google Gemini and records whether your brand, a competitor, or neither was named.
- Gaps from both audits collect on the Close gaps step, grouped by the kind of change they need.
Step 2: Connect a publish target
In Setup, choose your website platform and authorize one connection. AgenticSEO supports WordPress (self-hosted and WordPress.com), Webflow, HubSpot, and any Git repository on GitHub — including sites hosted on Lovable, which publish through GitHub.
- GitHub needs a fine-grained personal access token scoped to the one repository, with Contents read/write and Pull requests read/write.
- WordPress uses an application password; Webflow and HubSpot use their own OAuth or API tokens.
- Connections are scoped to a single client, so an agency's clients never share credentials or content.
Step 3: Review what the agent wrote
Nothing is published from an audit alone. AgenticSEO generates the fix for each gap — a rewritten title, a meta description, a JSON-LD block, an llms.txt index, or an answer-ready FAQ passage — and presents it for review.
- FAQ answers open in an editor: change the question, rewrite the answer, delete a pair, add one, or regenerate a single gap.
- Edited drafts are marked as yours and are never silently overwritten by a later regeneration.
- Page-level fixes show the current value beside the proposed one so the diff is explicit.
Step 4: Approve the changes
Approval is the gate. Each fix and each FAQ set carries its own approve toggle, and only approved items are eligible to publish. Approving is recorded with the user and timestamp.
- You can approve a subset and leave the rest as drafts.
- Nothing in the pipeline can bypass this step — there is no auto-approve mode.
Step 5: Publish to the live site
Click publish and the agent writes the approved changes through the connection. On GitHub it commits to a branch, opens a pull request, and auto-merges it. On WordPress, Webflow, and HubSpot it writes to the page or post directly through the platform API.
- Progress is reported stage by stage: preparing, writing, merged, verifying, done.
- FAQ publishing writes both the visible content and matching FAQPage JSON-LD, and suppresses questions already live so nothing duplicates.
- Every push is recorded as a run with the files or URLs it touched.
Step 6: Verify and roll back if needed
After writing, AgenticSEO fetches the published URL and confirms the change is actually live — not merely committed. If verification fails, the run is marked failed and the recorded run can be rolled back to the previous markup.
- A snapshot of the previous markup is stored before any write.
- Rollback restores that snapshot through the same connection.
- Published items are written to a delivery ledger with the URL and timestamp, which is what the first-month delivery guarantee is counted against.
Step 7: Re-measure on a schedule
Publishing is not the end of the loop. Set a recurring audit — day of week or day of month plus a time — and AgenticSEO re-runs the same prompt set and re-scores the same pages so you can see whether the citation moved.
- Coverage and Share of AI Voice trends are plotted per cycle on the Track step.
- New gaps found in a later cycle reset the workflow steps, so completed work always refers to the current cycle.
Running the same loop over the API
Everything above is available headlessly. Integrators call the MCP server or the REST API to start an audit, poll its status, read the generated fixes, approve them, and trigger a publish — the approval gate, verification, and rollback behave identically.
POST /v1/audits # start a Baseline Audit for a website GET /v1/audits/:id # poll status and read findings POST /v1/fixes/:id/approve # approve one generated fix POST /v1/publish # push approved fixes to the connected site GET /v1/publish/:runId # verify the run, or roll it back
Full reference: API docs · integrator guide
Frequently asked questions
How does AgenticSEO publish directly to my website?
AgenticSEO publishes approved fixes directly to your website. You connect a publish target once (WordPress, Webflow, HubSpot, or a GitHub repository), run an audit, review the generated titles, meta descriptions, JSON-LD, llms.txt, and FAQ answers, then approve them. The agent writes the changes to the live site, verifies the published URL reflects them, and records the run so any push can be rolled back.
Do I have to approve changes before they go live?
Yes. Approval is a required gate on every fix and every FAQ set. Audits and generation never write to your site on their own, and there is no auto-approve mode.
Which platforms can AgenticSEO publish to?
WordPress (self-hosted and WordPress.com), Webflow, HubSpot, and any GitHub repository. Sites hosted on Lovable publish through their GitHub repository. Starter plans generate the same output for copy-and-paste; auto-publish is included on Pro and Agency.
What happens if a publish breaks something?
Each push stores a snapshot of the previous markup and is recorded as a run. If live verification fails, or you simply want the change reverted, rolling back that run restores the earlier markup through the same connection.
Can publishing run headlessly without the UI?
Yes. The full loop — audit, generate, approve, publish — is exposed through an MCP server and a REST API, so integrators can run it programmatically. See the API docs and the integrator guide.
Related: Fix AI visibility automatically · Agentic SEO architecture · Which plans include auto-publish · Sample report
See it write the fixes for your site
Free 3-page audit with publishable assets. No card, no sign-up.
Try the free previewAI visibility resources
The guides, comparisons, and free tools behind AgenticSEO.