AutoSEO gets you found in AI answers and Google for the questions your buyers ask that your site has no page for. Every day it finds one, writes the article, and either sends it to your site or holds it in Cituna for you to read first. Starter writes one article a day, Pro three and Max ten, per brand. The topics are not invented: they come from questions with real search demand where you have no page in the top 20, from tracked prompts where none of the seven engines cite you, and from themes in the pages engines already cite. Every topic shows the numbers that earned it a place, so you can judge the pick before a word is written. Setting it up is three answers: where the articles go, who approves them, and switch it on. Everything else already has a working default.
1. Step 1: where should the articles go?
Open AutoSEO. The setup card asks three numbered questions, and this is the first. Pick the tile that matches how your site is built, not the name you know best. WordPress and Shopify take drafts you review. GitHub commits Markdown, for sites that build from files. Webhook sends the article to your own address, for everything else. Each tile says in one line what kind of site it is for.
A tile you have not connected yet links straight to Integrations. Connect it there and come back: the step ticks itself, so you can see the setup is one answer further on. Publishing connections are saved per brand, so every site you track connects its own.
Picking wrong is silent, which is why the tiles name the assumption rather than the brand: GitHub will happily commit Markdown to an app that serves from a database, report success, and publish nothing.
2. Step 2: who approves them?
Two answers. "I review each one first" is the recommendation: nothing goes live until you say so. "Publish automatically" puts every article live as it is written, with nobody reading it first. With GitHub the second answer is called Commit automatically, because your own build decides when a committed file becomes a live page.
When you review first, a second question appears underneath: review in Cituna, or review at your destination. Review in Cituna stops each article at Awaiting approval, where you read and edit the whole thing and publish it in one click. Reject keeps the copy for your records and sends nothing. Review in WordPress (or Shopify, or your own address) sends the article straight away as an unpublished draft, and you edit it there. A repository has no draft state, so GitHub offers only the Cituna half of this choice.
Turn on AutoSEO alerts in Integrations and you get an email or a Slack message when one is waiting, so a held article is never one you have to remember to go and look for.
3. Step 3: start writing
Switch on "Write articles every day". Connecting a destination does not start anything by itself, and a queue with automation off never drains. This is the most common reason a correct setup produces no articles. The switch stays disabled until steps 1 and 2 are answered, and it says which one is missing.
How many you get a day is set by your plan: one on Starter, three on Pro, ten on Max, per brand, counted on the UTC calendar day the article is delivered. Each article also uses a unit from your monthly article allowance, which you can see under Settings.
4. Fill and rank the topic queue
Press Refresh suggestions to rebuild the queue from data already in your workspace. It costs nothing and calls no vendor. Topics are ranked by opportunity, and the top one is written first: it is the highlighted first row of the queue, carrying the numbers that earned it its place and a Generate now button for when you do not want to wait for the daily run.
Add your own topic in your own words at any time, or send a specific keyword over from the Keywords tab. Skip anything you do not want written; a skipped topic is not suggested again.
5. Plan the month on the calendar
Switch the queue card to Calendar to see what has been written and what is booked next. Drag a topic onto a day, or use the date field on any topic, and it will be written on that day and not before it.
Unscheduled topics keep flowing in queue order on any day nothing is booked, so you only need to schedule the pieces that are genuinely time-sensitive: a launch, an event, a seasonal question.
6. Read, edit and approve before it ships
Every article with a stored body has an Open or Review button in the history. The Read view shows the complete article, including the search snippet: the meta title and description that never appear in the body. The Edit view lets you rewrite the title, intro, sections and FAQs, reorder or delete sections, and fix the meta.
Save draft writes your changes to Cituna alone. For an article awaiting approval, Approve & publish saves any edits and sends that exact copy live. For an article already delivered, Update pushes the correction to the existing destination item. These actions stay separate so saving can never publish or overwrite destination edits without asking.
7. Optional: tune the writing settings
Below the queue, the Writing settings card sets how many articles this site writes a day. Everything else in it is optional and already has a working default. Open Customise only when you want to change something specific.
What is in there: the language and the audience the writer aims at, a house voice in your own words, and the list of hosts it may name as sources (it names organisations, never links, and any host outside your list is rejected before publish). The two answer-engine gates, both on by default, require a question-form heading and an answer-first opening, which is the shape an AI engine lifts. Then the things every article carries: a generated hero image, a byline with a link to a page on your own site, an AI-assistance disclosure line, and the closing link a reader is ready for by the end.
A couple are only relevant to some stacks. IndexNow tells Bing, Yandex, Seznam and Naver the moment a page goes live, and needs a key file served from your domain. Extra frontmatter is for GitHub sites whose build requires keys Cituna has no concept of, such as a section or a category.
This card also holds "Your existing pages", which is how Cituna avoids writing something you already have and how it picks real internal links. It finds your sitemap on its own from robots.txt and the usual paths, so there is normally nothing to do. If yours lives somewhere else, put the address in there. Articles are written either way.
8. Let published articles improve themselves
Once an article is live, Cituna measures it weekly against its own Search Console rows. When a page is earning impressions and ranking well enough for a snippet to matter but still not getting the click, it is flagged for a refresh.
A refresh rewrites the SEO title, the meta description and up to two FAQ answers, and updates the live page in place. It never touches the body, the heading, the URL or the publication date. The ranking that page has earned is the thing being protected. At most three pages a site are refreshed a day, and never the same page twice inside 21 days.
You can also refresh one yourself: open a published article and use Refresh now, which appears only when Search Console has actually flagged the page.
Troubleshooting
Everything is connected but no articles are being written.
Read the status line at the top of the tab: it says which of four states you are in. "Not set up" means a step is unanswered. "Paused" means the switch in step 3 is off. "On but blocked" means it is switched on but cannot run, and it names the reason and the fix, which is usually a destination that is no longer connected. "Running" means the only thing left to check is the queue, and if that is full of topics booked for future dates the daily run correctly writes nothing today: the first row of the queue says so and offers to write one early.
Can I get more than one article a day?
Yes, on Pro and Max. The automatic run writes up to your plan cap per brand per day: one on Starter, three on Pro, ten on Max. Set the number for each site in the Writing settings card; asking for more than your plan allows is capped rather than refused, and the card tells you what the site will actually write. On top of the schedule you can press Generate now for up to two manual articles per brand per day, within your monthly allowance. Tracking more brands raises the total further.
An article failed to deliver. Do I lose the allowance?
No. The written draft is kept and the next run retries delivering that exact article rather than generating a new one, so a broken connection costs you nothing from the generation allowance. Fix the connection and it goes out on the next run, or push it yourself from the article. Turn on AutoSEO alerts in Integrations and Cituna emails you when a destination refuses an article, at most once a day per site, rather than leaving you to spot it on the tab.
Does editing an article change its URL?
No. The slug is fixed when the article is first delivered and is never re-derived from an edited title, because it is the article identity at the destination. Retitle freely; the published page stays at the same address.
Will it rewrite pages I have already published?
Only the ones it wrote, only their search snippet and FAQs, and only when Search Console says the page is being seen and not clicked. The body, headings, URL and publication date are never touched, it is capped at three pages a site a day, and a site set to Review in Cituna is never refreshed automatically at all. Pages you wrote yourself are never touched.
Drafted with AI assistance from our own research and Search Console data, and reviewed by Rahul A before publishing. Rules and prices change; check the linked official source before you act.