Documentation
Content engine: articles from your own Search Console data
What the AutoPSEO content engine does end to end, from site scan and topics to writing, translation, covers, delivery and upkeep, and what you control.
The content engine turns your own Search Console data into published articles. It scans your site, finds searches you appear for but have no page about, writes articles in your site's format and languages, translates them, draws covers, delivers everything to your own site through a signed webhook, and keeps published articles fresh. You set the pace, whether a person approves each article, the languages and the kinds of page. AutoPSEO's writer or your own AI does the writing.
How it works, end to end
- Scan. Turning the engine on reads your robots.txt, sitemaps, three months of Search Console data and your pages, then proposes languages, content types, an article format and topic rules for you to apply. See setup.
- Topics. Searches arrive from Search Console every day, from your own site, from your saved keywords, and from you or your AI. Gates drop brand searches and anything your pages already cover, a model routes each topic to a content type, and a review compares it with your closest pages. See topics.
- Queue. Each day the most promising reviewed topics move into the queue, and the writer takes them one at a time at the pace you set.
- Writing. A brief from the search results and your own site, a draft in your format, a validator and an editor review. By default the draft then waits for your approval. See writing and review.
- Translation. Every other language of your site, each checked against the original. See translation.
- Cover. An image in the style of your existing covers when your site shows them, checked for logos and text. See covers.
- Delivery. A signed webhook sends the article to your site, which stores and renders it. See delivery.
- Upkeep. Articles that lose clicks are refreshed, pages with a weak click-through rate are optimised, duplicates can be merged with a 301, and list pages rebuild themselves. See maintenance.
Who writes
- AutoPSEO's writer works the queue at your pace. Each article it drafts counts against your plan's monthly article quota.
- Your own AI connects over MCP and works from the same queue, with the same brief, rules and checks. Its drafts do not count against the quota. See writing with your own AI.
Who writes the topics in the queue under Settings decides which of the two takes queued topics. Your own AI can also write and rewrite at any time, whichever you choose.
What you control
| Setting | Default |
|---|---|
| New articles per week | 2 (0 to 14; 0 pauses the engine) |
| Approve every article before it goes live | On |
| Who writes the topics in the queue | AutoPSEO, at the pace above |
| Language articles are written in, and other languages | From the scan's proposal; 27 languages available |
| Content types | Paths, the searches each one takes, its own counts and instructions |
| Article format | Title, sections, FAQ, takeaways, sources, links, categories |
| Topic rules | Brand terms, words that mean the same, noise words, on-topic and off-topic words |
| Where articles are published | AutoPSEO hosting until you connect your site's webhook |
Your content stays yours
The engine is built to deliver: your site receives every article, translation and cover through the webhook, stores it and renders it, and keeps all of it the day you stop using AutoPSEO. Your site's text is treated as the original: before a queued change to an article is written, AutoPSEO reads your current version when your site can export it, and your site can refuse any update written from an older one. If your site can hand over the articles it already has, the scan takes them over so they can be refreshed and translated too.
Until your webhook is connected, articles are served from AutoPSEO's own address so they are not stuck. Hosting explains that, and how to switch it off once your site renders the articles.
What it costs
| Plan | Articles a month | Optimisations a month | Research credits |
|---|---|---|---|
| Starter, US$19 | 10 | 20 | 5,000 |
| Pro, US$45 | 40 | 80 | 20,000 |
| Business, US$279 | 200 | 400 | 100,000 |
The 7-day trial includes 2 articles and 2,000 research credits. Translations, topic routing and review, and the research behind your own AI's briefs use research credits (1,000 credits are US$1). The scan, covers, list pages and your own AI's drafts cost no article quota. Details: writing and review and pricing.
Where to find it
Open a property and choose Content in the Research group of the sidebar. Before the engine is on, the page offers Turn on the content engine. Afterwards it shows Your site, Waiting for review, Being written, Queue, Backlog, Published, Turned down, Content types, Settings and Where articles are published. The Your site page holds the scan, its proposal and the Ready to write checklist.
You need Search Console connected (Connecting Search Console), full access to the property, and an active plan or trial.
In this section
- Turning on the engine: the scan and its proposal.
- Topics: sources, gates, routing, review and the backlog.
- Writing and review: format, content types, checks, approval and quota.
- Translation: languages and translation checks.
- Covers: when covers are drawn, and bringing your own.
- Delivery: the webhook protocol for developers.
- Your own AI: writing over MCP, and unattended runs.
- Maintenance: refreshes, optimisations, merges and takedowns.
- Hosting: optional serving from AutoPSEO.
- Typed pages: pages built from parts, list pages and new paths.
For the wider product, see features, and for the MCP server that also answers Search Console questions, the Search Console MCP.
In this section
Turning on the content engine: the site scan and proposal
Turn the content engine on and it scans your sitemaps, Search Console data and pages, then proposes languages, content types, a format and topic rules.
Content engine topics: sources, gates, routing and review
How the content engine finds topics in Search Console, your site, saved keywords and your own AI, then filters, routes and reviews them before writing.
Writing and review: article format, content types and quota
The article format every writer follows, content types and their counts, the checks a draft must pass, approval and publishing, and the monthly quota.
Translating articles into your site's languages
How the content engine translates articles into your site languages, the checks every translation passes, and how a site whose own AI writes handles them.
Article covers: when they are drawn and how they are checked
When the content engine draws a cover, how the brand-free scene and picture are made and checked, the file your site receives, and bringing your own image.
Delivery webhook: receiving articles on your own site
The signed webhook that sends AutoPSEO articles to your site: headers, each event and payload, the answers to give, retries, waiting commands and IndexNow.
Writing with your own AI over MCP
Let Claude or another MCP client write from the content queue: claim topics, read briefs, send drafts, translations and covers, or run unattended on a Mac.
Keeping articles fresh: refreshes, optimisations, merges and takedowns
Refresh articles that lose clicks, optimise pages with a weak click-through rate, merge duplicates with a 301 and take articles down in the content engine.
AutoPSEO hosting: optional serving of your articles
What AutoPSEO hosting serves, why delivery to your own site is the recommended setup, how to stop hosting, and how pages can follow your site's own look.
Typed pages, list pages and new paths
How the content engine writes pages whose address is built from parts such as company and role, keeps list pages current, and adds or removes paths.