WordPress Blog on Autopilot with AI: The Complete Tutorial

Can you really put a WordPress blog on autopilot with AI?

Yes for producing and sending posts, no for judgment. A well-tuned pipeline picks topics, writes, schedules and drops posts into WordPress; a person checks the facts and decides what goes live.

Picture a small business owner who installs a plugin one evening that promises “3 SEO posts a day, hands-free.” Three months later, the blog has 270 posts, and some of them quote prices he doesn’t charge and services he no longer sells. Traffic hasn’t moved. The problem wasn’t AI: it was the lack of strategy upfront and of review in the middle.

This tutorial covers the other approach, the one that keeps a human at the two points where it matters. Here is who does what:

What does the full workflow look like, from strategy to published post?

The workflow fits in eight steps: keywords, topic, sequence, writing, review, sending to WordPress, internal linking, then measurement. Review is the only checkpoint nothing bypasses by default.

flowchart TD
  A[Keywords for your business] --> B[Topic grouped into a cluster]
  B --> C[Sequence you approve]
  C --> D[Writing at each due date]
  D --> E{Human review}
  E -->|Needs fixes| D
  E -->|Approved| F{Sending mode}
  F -->|Default| G[WordPress draft]
  F -->|Your choice| H[Live on the scheduled date]
  G --> H
  H --> I[Internal links checked]
  I --> J[Search Console tracking]
  J -->|Page slipping| K[Reviewed update]
  K --> H

Each arrow matches a section of this guide. If only one step stays manual, make it the “Human review” diamond.

How do you choose keywords and a topic before automating?

Start from what you sell, not from a number of posts to fill. A topic (or cluster) groups closely related queries the same reader asks; it is the basic unit of a series of posts that build on each other.

1. List the problems your customers type into Google before they buy: “how much does… cost,” “how to choose…,” “X vs Y.”
2. Group them by intent. “Heat pump price” and “heat pump installation cost” carry the same intent: one post, not two competing with each other.
3. Drop off-topic queries, even if they have volume. A post read by people who will never buy from you costs a review for nothing.
4. Pick one topic at a time. Five linked posts on the same subject beat five scattered ones.

This choice may also matter for AI assistants, but the link between topic depth and citations in ChatGPT or Gemini is an observation, not a published rule. The guide how to get cited by ChatGPT, Gemini and Grok separates what is documented from what is observed.

If you already work with Claude, ChatGPT or Cursor, you can also have them draft this plan from your data: the tutorial connecting your AI assistant to your SEO with MCP shows how.

How do you turn a topic into a publishing sequence?

A sequence is an ordered plan: a list of posts, a wait time between each one, a start date. It replaces “I’ll write when I have time” with a calendar that moves forward on its own.

Three settings are enough:

• Number of posts: the number the topic justifies, not the number your plan allows.
• Pace: one week between posts is a good start for a small team, because it leaves time to review.
• Start date: today, or timed to a launch or your return from vacation.

The number of posts written per month depends on the plan:

Full plan details are on the pricing page.

How do you connect WordPress securely?

With an application password, not your regular password. WordPress has had this feature since version 5.6 (December 2020): it gives a tool REST API access you can revoke at any time, without touching your login credentials.

In other words: even if this password leaked, it would not open your WordPress dashboard. Here are the steps, based on the official documentation:

1. Make sure your site runs on HTTPS. By default, WordPress only offers application passwords on a site served over HTTPS.
2. Go to Users > Profile, then the Application Passwords section.
3. Name it after the tool (“Tonaily,” for example): one password per integration, never shared between two tools.
4. Copy it right away. WordPress shows it only once. The spaces are there for readability and can be kept or removed.
5. Test it with the command from the documentation:

curl --user "your-username:xxxx xxxx xxxx xxxx xxxx xxxx" https://yoursite.com/wp-json/wp/v2/users/me

A JSON response with your name confirms access. According to the documentation, a 401 or 403 error has four common causes: the site isn’t detected as HTTPS, the regular password was entered instead of the application password, a security plugin disabled the feature, or a proxy or host strips the Authorization header.

For maximum control on the WordPress side, create a dedicated account for the tool. With the Contributor role, that account can write and manage its own posts but not publish them, according to the roles documentation: the tool can then only drop drafts, and a “live” send will fail. With the Author role, it can publish its own posts. Posts sent this way are attributed to that account: give it the name of the person who reviews them.

Draft or publish directly: which should you choose?

Drafts by default, until you have seen over several posts that review finds almost nothing left to fix. Direct publishing is decided after that, sequence by sequence, never across the board.

The WordPress REST API supports five statuses when creating a post, according to its reference:

What Tonaily sends: the title, the post body and the meta description, placed in the excerpt field (whether or not your theme uses it as the meta description). What it doesn’t send: the featured image, categories, tags and SEO plugin fields such as Yoast’s. You set those in WordPress, which is one more reason to go through drafts.

Should you schedule posts in WordPress or in the tool?

Both work, but native WordPress scheduling depends on your site’s traffic. WordPress publishes scheduled posts through WP-Cron, which only runs when a page loads.

The WordPress documentation says it plainly: WP-Cron “is only triggered on page load,” and “Scheduling errors could occur if you schedule a task for 2:00PM and no page loads occur until 5:00PM” (Plugin Handbook, Cron). On a small blog with little traffic, a scheduled post can therefore go out late. Hosts that replace WP-Cron with a real system task don’t have this problem.

When the tool holds the date and sends the post at the scheduled time, as Tonaily does, publishing no longer depends on visits. The tradeoff: the post only lands in WordPress on that date, unless you send it as a draft first to prepare the image and categories.

What should you review before a post goes live?

Facts, numbers, names, prices, and anything that commits your business. Google explicitly asks for this check on AI-generated content, metadata included.

The same page adds: “This review also applies to metadata like <title> elements, meta description elements, structured data, and alternate texts for images, which can appear in Search results.” Google’s spam policies also target content produced at scale to manipulate rankings, “no matter how it’s created”: what gets penalized is volume without value, not the tool. For the full framework (scaled content abuse, helpful content), read what Google’s rules on AI content really say.

How do you keep internal linking clean when posts keep coming?

Every new post should get at least one link from an existing page and point to its neighbors on the same topic. Google puts it simply: “Every page you care about should have a link from at least one other page on your site” (SEO link best practices).

Two directions to watch:

• From the new post to existing pages: the tool can handle this while writing, if it knows your site’s pages. Tonaily plans links as soon as the outline is approved: each post in the sequence targets at most 3 neighboring posts in the series and 3 site pages that already cover the subject.
• From existing pages to the new post: this is the direction people forget. Once the post is live, add a link from one or two older pages on the same subject, with descriptive anchor text rather than “click here.”

To spot orphan or poorly linked pages, the free internal link analyzer lists the links on a page.

How do you track results in Search Console?

Submit your sitemap once, then look at each post page by page: impressions, clicks, position. Give a post several weeks before judging it.

1. Submit the sitemap. Since version 5.5, WordPress exposes a sitemap index at /wp-sitemap.xml (WordPress announcement). If an SEO plugin generates its own, submit the plugin’s instead.
2. Request indexing for important posts with the URL Inspection tool. Google notes that a quota applies, that requesting again won’t make it faster, and that crawling can take “anywhere from a few days to a few weeks” (Ask Google to recrawl your URLs).
3. Read the Performance report filtered by page, not for the whole site: it is the post that needs to climb, not the average.
4. Update pages that slip rather than writing new ones on the same subject.

On paid plans, the LinkedIn, X and Facebook posts Tonaily writes from your articles are yours to publish: Tonaily connects to no social network. That is the last manual step in the chain, along with review: the two that put your name on the line in public.