BlogPilot

BlogPilot is a content strategy and autoblogging plugin for WordPress. It discovers keywords, groups them into topic clusters, writes full posts across 15 content genres using your own Anthropic (Claude) API key, and publishes them on a schedule.

What it does

Every screen and feature in this plugin is available on all plans; nothing is locked, hidden, or disabled locally. Features marked (Pro) are ones whose work is performed by the hosted BlogPilot API, and the API applies your plan’s limits to them. When a request exceeds your plan the API declines it and the plugin displays that message.

• Keyword Discovery — finds keywords using DataForSEO search volume and difficulty data (optional), Google autocomplete suggestions, and an intent-aware genre classifier, then groups related keywords into topic clusters.
• AI Content Generation — writes full posts (title, body, meta description, featured image) across 15 content genres using your own Anthropic API key, and can publish on a recurring schedule.
• Multi-Niche Support — create and manage as many independent content niches on one WordPress install as you like, each with its own keywords, publishing queue, and schedule. Keyword discovery and content generation for a niche run through the BlogPilot API, and the free plan’s API quota covers one niche (Pro removes that limit).
• Site Diagnostics — link health, technical checks, and content-gap analysis run locally and work on every plan; the AI-scored 12-point post SEO audit and one-click AI repairs run through the BlogPilot API (Pro).
• Accessibility Auditor — runs a live Google PageSpeed Insights accessibility scan from your browser and can inject a one-click CSS fix for common contrast issues, helping you work toward WCAG 2.1 AA conformance.
• Google Search Console Integration — connects your own GSC property (via OAuth) and surfaces posts that are close to ranking, underperforming on click-through rate, or already ranking well. Available on every plan.
• Cerebro (Pro) — a conversational assistant inside the WordPress admin that reads your site’s diagnostics and GSC data and suggests (and can execute) next actions.

How the AI features work

Keyword research, clustering, content generation, and diagnostics scoring run through the BlogPilot API, a hosted service operated by this plugin’s developer, using your own Anthropic API key for the actual writing. The plugin sends the data each feature needs (for example, a list of keywords, or post metadata for scoring) to the API and applies the result locally in WordPress. No keyword, cluster, niche, or post content is permanently stored by the API — only license, site registration, encrypted API key, and usage-count records are kept, for as long as your license or trial is active. See the «External services» section below for details.

The free plan includes API quota for 1 content niche and 15 AI-generated posts per month at no cost, with no time limit. The quota is applied by the API, not by the plugin: you can create any number of niches locally, and the API reports the limit when you run discovery or generation for a niche beyond your plan. A paid Pro plan (billed via Paddle, a merchant-of-record payment provider) removes those limits and unlocks the remaining hosted features: Cerebro and the AI post SEO audit and repairs. A 14-day trial of the full Pro feature set starts when you click the Start Free Trial button shown on the plugin’s admin pages.

External services

This plugin relies on the external services listed below. None of them are contacted silently: each is called only after you enter the relevant credentials or explicitly enable or connect the feature. For every service, this section states what it is, what it is used for, and what data is sent and when.

BlogPilot API (operated by the plugin developer) The hosted service that runs keyword discovery, clustering, genre classification, content generation, diagnostics scoring, AI post repairs, CTA and voice generation, social-media derivatives, featured-image sourcing, and Cerebro chat. Data sent and when: when you click Start Free Trial or activate a license key, your site URL and license key are sent to register the site. When you run one of the features above, the plugin sends only the data that feature needs — for example the niche description and keyword list for discovery, post titles and content snippets for diagnostics and repairs, or writing samples for voice analysis — plus your third-party API keys (stored encrypted) when you push credentials. Content is processed per request and is not retained; only license, site-registration, encrypted-key, and usage-count records are stored. Terms of Service | Privacy Policy

Anthropic (Claude) API The AI model behind all text generation, called by the BlogPilot API using your own Anthropic key. The plugin also contacts api.anthropic.com directly from your server in exactly two cases: to validate the API key you type into Settings, and to list available models for the connection-status display. Data sent and when: prompts built from your keywords, post titles, excerpts, and niche settings whenever an AI feature runs; the API key itself during validation. Terms | Privacy

DataForSEO (optional) Supplies keyword search volume and difficulty data for discovery and scoring. Data sent and when: keyword strings, sent when discovery or keyword scoring runs, and only if you have entered your own DataForSEO credentials. Terms | Privacy

Google Autocomplete (suggestqueries.google.com) Free fallback source of keyword suggestions when DataForSEO is not connected. Data sent and when: seed keyword strings, sent when keyword discovery runs. Terms | Privacy

Google News RSS Supplies headlines used by the news and app-update content genres and for trending context. Data sent and when: the niche topic string, sent when those genres generate a post. Terms | Privacy

Google PageSpeed Insights Powers the accessibility audit. Data sent and when: the public URL of the page being audited, sent when you click Scan. Terms | Privacy

Google Search Console (optional, Pro) Surfaces ranking opportunities for your own verified property. Data sent and when: OAuth tokens and query requests for your property, sent when you connect GSC and when signal fetches run. Terms | Privacy

Pixabay, Pexels, Unsplash (optional) Stock featured-image sources. Data sent and when: an image search term derived from the post keyword, sent (via the BlogPilot API) when a featured image is sourced, and only for providers whose API key you have entered. Pixabay: Terms | Privacy Pexels: Terms | Privacy Unsplash: Terms | Privacy

OpenAI (gpt-image-1, optional) AI featured-image generation when selected as the image provider. Data sent and when: the image prompt for the post, sent when a featured image is generated, using your own OpenAI key. Terms | Privacy

Paddle Merchant-of-record payment processing when you buy a Pro plan. Checkout happens on Paddle’s hosted page; the plugin never handles or stores card details. Data sent and when: your purchase details, provided by you directly to Paddle at checkout. Buyer Terms | Privacy

Sociophile (optional; operated by the plugin developer) Sociophile is a social-media scheduling service run by this plugin’s developer at sociophile.superappsdomain.com. BlogPilot can turn a published post into scheduled social posts there, so you do not have to rewrite each article for every network by hand. It is entirely optional and is contacted only after you switch on Settings > Social > «Push derivatives to Sociophile» and supply your workspace URL and ingest key; with that switch off, nothing is ever sent.

Data sent and when — there are two separate transmissions, both triggered by publishing a post:

1. Scheduled social posts. When a BlogPilot post is published (or when you click «Push to Sociophile» on the post queue), the plugin sends the post’s title, permalink, the niche or product name, a generated batch identifier, and the generated social-post text for each platform and funnel stage you selected, together with the time each should be posted. This is sent through the BlogPilot API, which holds your workspace address and ingest key, and is forwarded from there to your Sociophile workspace.

2. Conversion signal. If the published post was written from a keyword that Sociophile itself supplied (Sociophile can send your best-performing social posts back to BlogPilot as keyword ideas), the plugin then makes a second, direct call to your workspace at {your Sociophile URL}/api/ingest/signal-converted, authenticated with your ingest key. That call carries only the batch identifier, the post’s URL and title, and the internal ID numbers of the keywords involved, so Sociophile can mark those suggestions as acted upon. No post content is included. The request is fire-and-forget: BlogPilot does not wait for or read a reply.

Sociophile also sends data to your site rather than the other way round: if you connect it, it calls this site’s /wp-json/bpv2/v1/social-signals endpoint to deliver those keyword suggestions. That endpoint rejects any request without your ingest key.

Terms & Conditions | Privacy Policy | Data deletion

Telegram Bot API (optional) Pipeline notifications to your own Telegram bot and chat. Data sent and when: notification text (post counts, publish events, alerts), sent when those events fire, and only if you have entered your own bot token and chat ID. Terms | Privacy

Internet Archive (Wayback Machine) Used by the broken-link repair action: when a link in one of your posts no longer resolves, the plugin asks the Wayback Machine whether an archived snapshot of that address exists so it can be offered as a replacement. Data sent and when: the single broken URL being repaired, sent to archive.org only at the moment you click the repair action for that link. Nothing is sent during a normal scan. Terms | Privacy

Websites you link to, and RSS feeds you configure (not a single service) Two features make requests to third-party addresses that you choose, rather than to a fixed service: 1. The link-health and post-audit scans send a HEAD request to each external link found in your own published posts, to check whether it still works. Only the address itself is requested; no personal data is sent. 2. The RSS-driven content genres fetch the feed URLs you enter for a niche. Only the feed address is requested, when generation runs for that niche. Because these addresses are supplied by you, their operators and privacy terms vary; each request goes only to the address concerned.