In short: You can automate almost every step of a WordPress blog: topic ideas, drafts, featured images, SEO fields, scheduling and publishing. A person should still review each post before it goes live. Google recommends exactly that and lists mass-produced AI pages without added value as an example of spam. Technically you need WordPress 5.6 or later, HTTPS, an application password and a user with the right role.
How to automate blog posts: what software can take over
Almost every blog post passes through the same stages: idea, draft, image, SEO details, date and publication. You can hand each stage to software, fully or in part.
| Stage | What can run automatically | What a person should do |
|---|---|---|
| Topic ideas | Collect suggestions for a keyword, an audience or a season | Pick the ones that fit your business and your readers |
| Draft | Outline and first draft in your tone of voice | Check the facts, add your own experience and examples |
| Featured image | Generate the image, set size and format | Check the image itself, read and correct the alt text |
| SEO fields | Suggest title, description, slug and tags | Read every suggestion, because it can appear in search results |
| Scheduling | Spread posts across a fixed rhythm | Agree on the order and on dates that matter |
| Publishing | Create or release the post on time through the REST API | Approve it and look at the live result |
A simple rule of thumb: automate the busywork, not the responsibility. A tool can collect ideas, draft text and fill a calendar. Whether a post is accurate and right for you is for someone who knows the subject to decide.
Where a person has to review
Language models write fluently, but they do not look facts up. Google says so plainly in its guidance on generative AI (external link): "Keep in mind that generative models don't retrieve facts, but predict a likely sequence of words based on their training data. Because of this, generative AI outputs may contain inaccuracies (also known as hallucinations)."
Google's recommendation is clear: "It is critical to manually factcheck and review all AI-generated content for accuracy and trustworthiness before publishing." The same page adds that this review also covers title elements, meta descriptions, structured data and image alt texts, because they can appear in search results (Google Search Central: generative AI guidance, last updated 1 October 2026 (external link)).
In practice, a review means:
- Check numbers, names, dates, prices and quotes against a reliable source
- Add your own experience, such as a real customer question
- Read the title and meta description as if they were already in the search results
- Correct alt texts so they describe the image plainly
- Open every link and make sure it goes where it should
More in our guide Does Google penalize AI content?
What Google allows and what counts as spam
Google's post on AI content says: "Appropriate use of AI or automation is not against our guidelines" (Google Search Central Blog, 8 February 2023 (external link)).
Google draws the line at volume without value. Its spam policies say: "Scaled content abuse is when many pages are generated for the primary purpose of manipulating search rankings and not helping users" (Google spam policies, last updated 28 August 2026 (external link)). The examples include using AI to generate many pages without adding value, turning other people's content into many pages through automated synonyms or translation, and running several sites to hide how much content is being produced.
For your automation, that means:
- Schedule only as many posts as you can review properly. A daily limit per site helps.
- Never publish other people's content, not even translated or reworded.
- Do not write to a word count. Google asks in its guidance on helpful content: "Are you writing to a particular word count because you've heard or read that Google has a preferred word count? (No, we don't.)" (Google: creating helpful content, last updated 5 October 2026 (external link)).
Technical requirements in WordPress
Application passwords since WordPress 5.6
External tools do not sign in with your normal password. They use an application password. The REST API Handbook explains: "As of 5.6, WordPress has shipped with Application Passwords, which can be generated from an Edit User page (wp-admin -> Users -> Edit User)" (WordPress REST API Handbook: Authentication (external link)).
According to the integration guide, an application password is 24 characters long, can be revoked at any time from the user profile and cannot be used to log in through wp-login.php. By default the feature is only available on sites served over HTTPS (WordPress: Application Passwords Integration Guide (external link)).
The REST API and post statuses
Through the REST API, tools exchange data with your site as JSON (WordPress REST API Handbook (external link)). Every post has a status: publish, future (scheduled), draft, pending (waiting for review) or private (REST API reference: Posts (external link)). Start with draft or pending, so nothing reaches your blog unreviewed.
If the connection fails, the usual causes are a security plugin that blocks the REST API or application passwords, a server that strips the Authorization header, or a site that is not served over HTTPS.
Roles and permissions
Create a separate WordPress user for the tool and give it only the rights it needs. WordPress roles include Editor, who can publish and manage posts, including those of other users; Author, who can publish and manage only their own posts; and Contributor, who can write posts but cannot publish them (WordPress: Roles and Capabilities (external link)). With a separate user you can revoke access later without touching your personal account.
Daily limits and a pause button
A mistake in an automation repeats itself until somebody notices. Cap the number of posts per day and per site, and make sure you can pause the automation straight away.
Four ways to automate, compared
Which option fits depends on how many sites you run, who reviews and how much tech you want to maintain.
| Option | How it works | Strengths | Limits |
|---|---|---|---|
| Write by hand, schedule in WordPress | You write the post and set a date, the post gets the status "future" | Full control, no extra tool | Every step takes time, ideas and images stay manual |
| Build it yourself, for example with ChatGPT or n8n | You draft in a chat tool, or build your own workflow that creates drafts through the REST API | Very flexible, every step your way | Setup, maintenance, error handling and the review step are on you |
| WordPress plugin | A plugin creates or schedules posts inside the dashboard | Everything in one place in WordPress | One more plugin to keep updated on every site, features vary a lot between plugins |
| External service (SaaS) | A service writes, schedules and publishes, and connects for example with an application password | Planning, review and publishing in one place, also for several sites | Another account, ongoing costs, data is processed by the provider (check the data processing agreement) |
Plugin or external service?
A plugin suits you if you run a single site and like doing everything in the dashboard. An external service is often the better fit when several people review or several sites come together. Building it yourself makes sense if you know APIs and have time for maintenance. Either way, a person reviews before anything is published.
How to automate blog posts in WordPress in seven steps
- Set your goal and rhythm. Write down who the blog is for and how often a post should appear. Pick a rhythm your review can sustain.
- Build a topic list. Collect questions from customer calls, e-mails and quotes. Keep suggested ideas only if your readers would care.
- Create a user and an application password. Add a separate WordPress user with a suitable role. Generate an application password in that user's profile and enter it only in the tool, never in e-mails or chats.
- Connect the tool and test it. Enter your site address, the user name and the application password. Send a test draft and check that it arrives in WordPress.
- Generate drafts, do not publish directly. Have new posts created as draft or pending first. Set your tone of voice and list words to avoid.
- Review and approve. Read the text, title, description and alt texts, check the facts and add your own experience. Only then does a responsible person approve the post.
- Schedule, publish, adjust. Spread approved posts across fixed dates and set a daily limit. Check each live post and refine your settings.
Checklist before your first automated post
- WordPress 5.6 or later, site served over HTTPS
- A separate user for the tool with the lowest role that works
- Application password stored only in the tool
- REST API reachable, no security plugin blocking application passwords
- New posts start as draft or pending
- A named, responsible person approves every post
- The review covers text, title, meta description and alt texts
- A daily limit per site and a way to pause
- No content taken from others, not even translated
- Real author details instead of invented profiles
How Blog Automation supports this workflow
Blog Automation is an external service for WordPress only. You connect a site in three steps with an application password, and no plugin is needed. It requires WordPress 5.6 or later with HTTPS and a user with the Editor role (recommended) or Administrator. More on connecting WordPress without a plugin.
AI posts move through the statuses draft, in review, approved, scheduled and published. Nothing is scheduled or auto-published until someone with the approve right has signed it off, as described in the approval workflow. In the Pro plan, you set up automations per site with days, time, a maximum per day and a mode: draft for review, or publish after approval. More on automated blog posting on a schedule, the AI blog writer with your own tone of voice and plans and tokens.
Frequently asked questions
What is autoblogging, and how is it different from a reviewed workflow?
Autoblogging usually means posts are created and published without any human review, often from other people's feeds. Google's spam policies (external link) name scraping feeds to generate many pages with little value as an example of spam. A reviewed workflow automates the same tasks, but a person decides before each post goes live.
Which steps should I not automate?
Anything that needs judgement: whether the facts are right, whether a post fits your business, which of your own experience belongs in it and whether it should go live at all. Google's guidance on generative AI (external link) recommends checking all AI content by hand before publishing, including titles, descriptions and alt texts. That review stays with a person.
Can I edit an automated post after it goes live?
Yes. A post created through the REST API is a normal WordPress post. You edit it in the editor like any other post, change the text, image or category, or set it back to draft. After bigger changes, read the title and meta description once more.
How many automated posts should I schedule per week?
Google does not name an ideal number. Its guidance on helpful content (external link) does list extensive automation on many topics as a warning sign. Schedule only as many posts as your team can review properly, and increase the volume once your review runs reliably.