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.
Setup: connect the website once
In Setup, choose your website platform and authorize one connection. AgenticSEO supports WordPress (any install you control, plus WordPress.com), Webflow, HubSpot, and any Git repository on GitHub — including sites that 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 created under Users → Profile in wp-admin. Managed hosts such as WP Engine, Kinsta, Pressable, Flywheel and SiteGround run standard WordPress core, so the same Application Password works — do not use WP Engine User Portal / hosting API credentials, and turn off host-level password protection on any staging environment you connect, because it uses the same Basic Auth header. 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.
- Setup is also where you confirm your brand, product and category words, and set automatic re-checks.
Setup: measure the website
Run one Baseline Audit on the home page, or on the home page plus every section. AgenticSEO crawls the pages in scope and scores each one across 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.
- Pages that cannot be read score zero, and missing home-page metadata or JSON-LD caps the score — the number never flatters the site.
- AgenticSEO Health lists what is wrong and why it matters; nothing is edited on this page.
Fix & Publish: the technical fixes are written for you
Everything the audit found lands here as work: rewritten titles, meta descriptions, JSON-LD blocks, an llms.txt index, and robots/sitemap corrections — each one drafted and shown beside the current value so the difference is explicit.
- Nothing is published from an audit alone; drafts wait for a person.
- Edited drafts are marked as yours and are never silently overwritten by a later regeneration.
- SEO comes before AEO because ChatGPT and Gemini cannot cite a page they cannot crawl, index or parse.
Opportunities: measure the answers
The AEO baseline asks your buyer questions of ChatGPT and Google Gemini, checks the same phrases in Google, and records whether you, a competitor, or nobody was named. Questions come from your confirmed brand, product and category words plus what your website already says.
- Buyer questions and coined-category questions are scored; questions that use your brand or product name are accuracy checks only.
- Category Bridge questions use the words buyers already say and introduce your own term in the same answer, because nobody searches a name they have never heard.
- AEO Health shows what ChatGPT and Gemini answered, with the evidence behind each verdict.
Fix & Publish: approve the wording
Each question you lost becomes a gap. AgenticSEO drafts an answer-ready passage, you edit and approve it, and only approved wording is eligible to publish. Approval is recorded with the user and timestamp.
- Answers open in an editor: change the question, rewrite the answer, delete a pair, add one, or regenerate a single gap.
- You can approve a subset and leave the rest as drafts. There is no auto-approve mode.
- Nothing on this page writes to the live site.
Fix & Publish: publish, verify, roll back
Publishing happens in one place, after both lanes are done. 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 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.
- After writing, AgenticSEO fetches the published URL and confirms the change is actually live — not merely committed. A snapshot of the previous markup is stored before any write, so any run can be rolled back through the same connection.
- Published items are written to a delivery ledger with the URL and timestamp.
Aftercare: refresh the sitemap and llms.txt
Any change that adds, renames or removes a page needs the site's own indexes refreshed, or search engines and ChatGPT and Gemini keep working from the old map.
- Regenerate sitemap.xml so it lists the new and changed URLs with current dates, and re-submit it in Google Search Console.
- Regenerate llms.txt so it points at the pages that now answer your buyer questions.
- Check robots.txt still allows the AI crawlers and still names the sitemap.
Visibility: re-measure and watch it land
Publishing is not the end of the loop. Visibility is read-only: it re-scores the same pages and re-asks the same questions on the schedule you set, so you can see whether the citation moved. ChatGPT and Gemini need days to weeks to re-read a site.
- AI answers and Google search trends are shown per reading in Visibility.
- After any change, re-submit your sitemap in Google Search Console so Google re-reads the new pages.
- New gaps found in a later cycle reopen the work, so completed items always refer to the current cycle.
- The full deliverable for management, marketing and the website team lives on the Report page.
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 endpoint reference is provided to signed-in customers and integration partners.
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 (any install you control — including managed hosts like WP Engine, Kinsta, Pressable and Flywheel — plus 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 5-page audit with publishable assets. No card, no sign-up.
Try the free previewAI visibility resources
The guides, comparisons, and free tools behind AgenticSEO.