Cituna writes daily articles from the questions buyers actually ask AI engines (one a day on Starter, up to ten on Max), and WordPress is the simplest place to put them. You connect once with a WordPress application password, a built-in feature since WordPress 5.6, so there is no plugin to install and no OAuth app to register. Each article arrives as a Post with headings, an FAQ block and structured data, and its SEO title and meta description go straight into Yoast SEO, All in One SEO, SEOPress or Rank Math. Nothing goes live until you approve it, unless you switch on automatic publishing. This guide covers connecting, choosing who approves each article, and the two failures people hit most: a host that hides application passwords, and an account whose role is too low to keep the schema block intact.
What this assumes
1. Create an application password in WordPress
Sign in to wp-admin and open Users → Profile. Scroll to Application Passwords, type a name you will recognise later such as "Cituna", and click Add New Application Password.
WordPress shows the password once, as four blocks of characters. Copy it now: you cannot view it again, only revoke it and make a new one. It is not your login password, and revoking it later disconnects Cituna without touching your account.

2. Paste your site details into Cituna
Publishing connections are stored per brand, so choose the brand in the top bar first. This is what stops an article for one site being published to another.
Open Integrations and click Connect on the WordPress card. Enter the Site URL exactly as you visit it, your WordPress username, and the Application Password you just copied.
3. Let the check confirm the connection
Cituna checks the application password against your site right away: that it signs in, and that the account can create posts. Nothing is posted. If WordPress refuses it you get the exact reason (wrong username, revoked password, a role that cannot create posts) and nothing is saved, so a credential that never worked cannot sit there looking connected.
A green Connected badge means the credential passed that check when you connected. If it is revoked later, the first article that cannot be delivered says so and asks you to reconnect.

4. Choose who approves each article
Open Articles. In the AutoSEO setup, pick the WordPress tile under "Where should the articles go?". Under "Who approves them?", I review each one first is the recommended answer, with two places to review: Review in Cituna keeps the article here until you edit it and click Approve & publish, and Review in WordPress sends it as an unpublished draft for you to publish in wp-admin.
Publish automatically puts each article live the moment it is written. You can switch between them later without touching the connection.
5. Turn on the daily article
Under "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 single most common reason people see no articles after setting everything up.
You can also click Write now in Articles to write the top topic immediately rather than waiting for the next run.
Troubleshooting
Does Cituna fill in my SEO plugin's title and description?
Yes, on Yoast SEO 27.7 or later, All in One SEO (Lite included), SEOPress (the free version included) and Rank Math. Right after saving the post, Cituna writes the article's SEO title and meta description into the plugin's own fields. Yoast before 27.7 takes no SEO fields over the REST API, so update it. The SEO Framework takes none either: it builds the title from the post title and the description from the excerpt, and Cituna sends the meta description as the excerpt. Keep one SEO plugin active, because two both print their tags in the page head.
Why did my structured data disappear from the published post?
WordPress strips <script> tags from posts saved by an account without the unfiltered_html capability and leaves the JSON inside on the page as text, so Cituna sends articles from such an account without their JSON-LD block. On a single site, Administrators and Editors have the capability and Authors do not. On a Multisite network only a Super Admin has it, and some hosts switch it off for everyone. Reconnect with an Editor or Administrator application password (a Super Admin on Multisite) and the next articles carry it again.
The connection worked yesterday and now says bad credentials.
Application passwords are revoked whenever the WordPress user changes their password, and some security plugins revoke them on a schedule. Create a fresh application password and paste it into the WordPress card again; nothing else about your setup needs to change.
Can I send articles to a page instead of a post, or to a custom post type?
AutoSEO delivers posts, because an article that is meant to earn citations belongs in the blog feed your site already exposes to crawlers. If you need a custom post type, use the webhook destination instead and route it yourself.
Will Cituna overwrite a post I edited in WordPress?
No. Editing an article inside Cituna saves to Cituna alone; Update on WordPress pushes it to the post. AutoSEO itself updates a live post only to add a link to a newer article or when a refresh rewrites its title, description and FAQs, and first checks that the post is still the copy it sent. If someone edited it in WordPress since, nothing is overwritten: the article offers Replace it on WordPress or Keep the site's version, and AutoSEO stops refreshing or relinking it unless you replace it.
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.

