AutoPilot guide

How AutoPilot works

Once enabled, AutoPilot ticks every 2 minutes via WP-Cron. On each tick, it: (1) checks whether enough time has passed since the last article, (2) picks a source category, (3) asks GPT to suggest a title that hasn’t been used before, (4) queues an article job, (5) the queue worker picks it up and runs the full generation pipeline (outline → expand → humanize → image → SEO → publish).

Step 1 — Pick your cadence

Open AI AutoBlogger → AutoPilot → Schedule. Pick how many articles per day (or week). Common patterns:

• 1–2 / day — best for most blogs. Steady growth, never spammy-looking.
• 4–6 / day — content-heavy niches (recipes, news roundups, product reviews).
• 10+ / day — programmatic SEO plays. Make sure your hosting can handle it.

Step 2 — Pick source categories

AutoPilot pulls topic ideas from the categories you select. Each category becomes a “topic seed” — GPT generates titles that fit the category’s name and existing post titles. Keep categories tightly themed: a category called “Personal Finance” produces better titles than “Stuff About Money”.

Step 3 — Choose publish mode

Three options under AutoPilot → Publishing:

• Publish immediately — articles go live as soon as generation finishes.
• Save as draft — articles wait in Posts → Drafts for your review. Best for niches where you want a human eye before publish.
• Schedule publish — drip-publish queued articles at a fixed interval (e.g. one every 3 hours) regardless of generation time.

Avoiding duplicate titles

AutoBlogger sends GPT a list of your last 50 post titles in each category before asking for a new suggestion, with explicit instructions to avoid overlap. In practice, exact duplicates almost never happen. If you notice near-duplicates (same topic, different phrasing), tighten your category boundaries or add a “Do not write about: X, Y, Z” line to the category’s writing style profile.

Pause / resume / kill switch

The AutoPilot Status toggle on the Dashboard is the kill switch. Off = no new jobs queued; in-flight jobs finish then nothing else starts. Use this before site migrations, theme switches, or when you’re tweaking style profiles.