WP Auto Blog AI

1. Install and activate the plugin.
2. Open WP Auto Blog AI > API & Integrations and add only the providers you plan to use.
3. Use Test Connection for configured providers.
4. Create a Campaign.
5. Add exact topics manually or import a CSV.
6. Review AI, Content, Images, Scheduler, Quality Gate and SEO/Linking settings.
7. Use Draft while testing. Resume/enable the Campaign when ready.
8. Review generated posts before switching a production workflow to immediate publishing.

1. In WordPress go to Plugins > Add New > Upload Plugin.
2. Upload wp-auto-blog-ai.zip from the marketplace package's Plugin folder.
3. Click Install Now, then Activate.
4. Open the new WP Auto Blog AI menu.

Do not upload the entire marketplace/download package through the WordPress plugin uploader.

A Campaign is an independent automation workflow. Each Campaign can have its own AI provider/model, editorial rules, image strategy, topics, category overrides, publishing schedule, Quality Gate and SEO/linking behavior.

Settings follow this precedence:

Global Defaults → Campaign → Category → Topic/CSV

A more specific value can override a broader default where the field supports overrides. Leaving an optional constraint blank generally means no Campaign-level constraint.

Save credentials only for services you use. Test configured connections before enabling production automation. Model names and provider availability can change; use a provider/model currently supported by your account.

Recommended workflow: supply/review exact topics before automation. Manual and CSV topics are preserved as the visible WordPress post title rather than being silently rewritten.

The included Examples/campaign-topics-example.csv demonstrates the available columns.

You can give the template to an AI assistant and ask it to prepare a reviewed batch of topics, then inspect the CSV before importing it.

Campaign content controls can define audience, tone, word limits, title constraints and other editorial requirements. Applicable settings are incorporated into the AI generation instructions and can also be checked by the Quality Gate.

Additional Prompt Instructions

This is one of the most important Campaign fields. Use it for detailed writing instructions that cannot be represented by ordinary controls: structure, brand voice, custom tables, buttons, formatting preferences, category-specific guidance, recurring sections, calls to action and other editorial requirements.

Be specific. A detailed prompt plus structured Campaign settings produces a more predictable automation workflow.

Featured images and content images have independent source/pool settings. Depending on your configuration you can use Media Library, Pexels, Pixabay, AI-generated images or Smart Fallback.

Media Library matching

The Filename/title must contain filter is case-insensitive and can match relevant attachment metadata including Media Library title and actual filename. For example, label a group with HOSTING- and use the same text as a Campaign filter.

AI image prompts

Campaigns can provide separate prompt instructions for featured-image generation and in-content image generation, allowing different visual direction for each use.

Stock-image usage remains subject to the source/provider's license and applicable attribution/use requirements.

Campaign scheduling supports intervals, allowed weekdays, optional publishing windows, randomization, pause/resume behavior and Campaign limits. Scheduling uses the WordPress site timezone by default, with an optional Campaign scheduling timezone where configured.

WordPress posts are still created/published through standard WordPress publishing functions.

The Quality Gate can validate generated content against enabled Campaign rules before publishing. When configured, the plugin can request an AI revision for repairable failures. Unresolved items can be routed to Needs Review rather than blindly published.

Exact duplicate-title protection is a hard safety: the plugin blocks creation when an existing WordPress post already has the exact supplied title.

WP Auto Blog AI supports Yoast SEO and Rank Math metadata workflows, including focus keyphrase/keyword controls where configured. Linking features can place contextual internal links with Campaign/category relevance and restrict external links to approved domains/settings.

No SEO plugin or automation can guarantee rankings, indexing, traffic or revenue.

The Campaign Image Labeler can add a prefix to the WordPress attachment title for multiple selected images. This creates a safe grouping mechanism for Campaign Media Library filters without physically renaming uploaded files/URLs.

Example: prefix selected hosting images with HOSTING-, then enter HOSTING- in the relevant Campaign Media Library filter.

The plugin uses native WordPress WP-Cron with queue locking, retry/backoff and stale-job recovery. WP-Cron is request-triggered, so low-traffic websites can run scheduled tasks late.

For time-sensitive production sites, a real server cron can call WordPress cron regularly. This is a hosting/WordPress operational configuration rather than a requirement of the plugin itself. If you replace WordPress's request-triggered cron, follow your host's instructions and test the site carefully.

Long AI/image pipelines can also be constrained by hosting execution limits. The plugin attempts to extend execution time where the host permits it, but restrictive hosting can still require a higher PHP execution limit.

External requests occur only when you configure/use the corresponding integration. Depending on Campaign settings, transmitted data can include topics, keywords, prompts, generated/revision content, image prompts and image-search queries.

API keys are stored in the WordPress database because background processing needs access to them. Keys are masked in the admin UI unless an authorized administrator explicitly reveals one. Do not send API keys in support tickets.

Provider privacy, retention, acceptable-use, pricing and output terms are separate and may change independently.

A Campaign is not processing

Check Campaign status, Auto Processing, queue status, next-run/schedule restrictions, API connection, daily/total limits and Debug/Health information.

Featured image was not assigned

Confirm the chosen source is enabled and configured. For Media Library filters, confirm the attachment title/filename contains the requested text and the physical attachment still exists.

Provider request fails

Use Test Connection, verify account billing/quota/model access, and inspect Debug logs. Provider model names and availability can change.

Scheduled publishing is late

WP-Cron depends on site requests. On low-traffic sites, consider a real server cron for WordPress.

Support should cover documented plugin functionality and reproducible defects. It does not include custom development, writing customer prompts, hosting administration, third-party provider outages/fees, or guarantees about AI accuracy/SEO performance.

When requesting help, include the plugin version, WordPress/PHP versions, selected provider/model/source, exact error and relevant Debug lines. Never include API keys.

The plugin already includes a Tutorials foundation. When your YouTube videos are ready, the safest scalable approach is to maintain a small JSON feed on your own website and let the plugin cache it for 12-24 hours.

Suggested JSON shape:

{
  "version": 1,
  "tutorials": [
    {
      "title": "Create Your First Campaign",
      "category": "Getting Started",
      "youtube_id": "YOUR_VIDEO_ID",
      "description": "Create and test a campaign from start to finish."
    }
  ]
}

Recommended implementation for a future maintenance release: fetch only from your fixed HTTPS documentation domain; validate JSON; sanitize all text; accept only valid YouTube video IDs; cache with a WordPress transient; fall back to bundled tutorial cards if the feed is unavailable; and never place arbitrary remote HTML/JavaScript into the WordPress admin.

Start with five videos: Installation & First Campaign; Connect AI Providers; Generate/Import CSV Topics; Featured & Content Images; Additional Prompt Instructions.

Back up your WordPress files and database before updates. Future releases should use increasing semantic versions (for example 2.0.3 for fixes, 2.1.0 for features and 3.0.0 for a major potentially breaking release).

Keep the last known-good commercial ZIP. Never silently replace a public release while retaining the same version number.