Luis Rita AI Blog Writer with Sources

Luis Rita AI Blog Writer with Sources is a draft-first AI blog writer. It creates normal WordPress block content from your brief and selected sources, and never publishes automatically.

This plugin is bring-your-own-key only and needs no account. An optional paid add-on, AI Blog Writer Pro, is sold separately.

• Use your own OpenAI, Anthropic, Google, or xAI API key and choose a GPT, Claude, Gemini, or Grok model.
• Get topic ideas for your subject, and a primary phrase, supporting terms, and reader questions for your topic.
• Choose a Delegated or Guided workflow, supply up to eight source URLs, and review the outline in Guided mode.
• Get a normal WordPress draft with sources, warnings, metadata suggestions, and provenance.
• Save writer profiles linked to WordPress author accounts, preview their style, and get drafts written in the profile’s voice.
• Rewrite one section of a draft, or regenerate it from the sources you choose.
• Reopen the brief behind any job and reuse it for a new version.
• See related published posts to link to, and track provider usage with costs estimated from each model’s list price and optional monthly cost ceilings.
• Use the plugin’s screens in English, German, French, Spanish, Brazilian Portuguese, or Japanese, following each user’s WordPress language.

Generated content can contain errors, unsupported claims, or bias. Human review is required before publication. No ranking, traffic, accuracy, or legal-safety guarantee is made.

AI Blog Writer Pro (optional)

The free plugin is complete on its own. AI Blog Writer Pro is a separate paid add-on that finds sources automatically, checks every factual claim in the draft against its sources, checks citations and links, offers an optional second-model fact-check, and applies SEO suggestions to Yoast SEO, All in One SEO, and SEOPress. It runs on your own AI key, with a 14-day free trial. The plugin’s screens mention it in a few places until it is installed; each mention can be dismissed, and the aibcg_show_pro_prompts filter turns them all off.

External services

This plugin sends data to up to three kinds of external destinations. The first two happen only after an administrator configures an API key or a user supplies URLs; the third only if an administrator turns on usage data. Nothing is sent during installation or activation.

1. Your selected AI provider

Requests go to the provider matching the configured API key:

• OpenAI — https://api.openai.com/v1/models, https://api.openai.com/v1/responses
• Anthropic — https://api.anthropic.com/v1/models, https://api.anthropic.com/v1/messages
• Google — https://generativelanguage.googleapis.com/v1beta/models, .../v1beta/models/{model}:generateContent
• xAI — https://api.x.ai/v1/models, https://api.x.ai/v1/chat/completions

What is sent, and when:

• Test connection (Settings → Test connection, and automatically once when an administrator submits a new article brief): the API key and a request for the provider’s model list. No content is sent.
• Outline stage (after a job reaches the outline stage): the API key, selected model, your brief fields (topic, talking points, audience, search intent, keyword phrases, tone, length, language, market, call to action, include/avoid notes), today’s date, the selected writer profile, and extracted notes plus titles and URLs of the selected sources.
• Draft stage (after the outline is generated in Delegated mode, or approved in Guided mode): the same brief, date, writer profile, and source notes, plus the approved outline.
• Topic ideas (New article → Need a topic?): the API key, the subject you type, the brief’s audience, language, and market, today’s date, and the titles of up to 50 recent posts (published, scheduled, pending, and drafts) so the ideas avoid them.
• Keyword ideas (New article → Suggest keywords for this topic): the API key, the topic, the brief’s audience, language, and market, and today’s date.
• Propose writer profile (Writer profiles → Propose editable profile): the API key, your prompt text, and any writing sample you paste.
• Preview a writer profile’s style (Writer profiles → Preview this style): the API key, the profile fields in the form, today’s date, and the sample topic.
• Rewrite section (block editor sidebar): the API key, the section content, your instruction, and the notes of the draft’s sources, or of the sources you tick for “Regenerate using selected sources”.

Never sent: WordPress credentials, other database contents, visitor data, or payment data. API keys stay server-side and are never exposed to the browser or the REST API.

Provider terms and data policies apply to everything sent:

• https://openai.com/policies/terms-of-use/
• https://openai.com/policies/privacy-policy/
• https://developers.openai.com/api/docs/guides/your-data
• https://www.anthropic.com/legal/commercial-terms
• https://www.anthropic.com/legal/privacy
• https://ai.google.dev/gemini-api/terms
• https://policies.google.com/privacy
• https://x.ai/legal/terms-of-service
• https://x.ai/legal/privacy-policy

2. Source URLs you supply

During research, your server fetches each URL in the brief with a plain HTTP request identified as Luis-Rita-AI-Blog-Writer/<version>; <your site URL>. No brief content, key, or user data is sent. Private addresses are rejected, redirects are limited to three, and responses are capped at 1 MB.

3. Usage data (optional, off by default)

Only if an administrator turns on “Share anonymous usage data” (on the first-run screen or in Settings → Usage data), the plugin sends anonymous statistics about its own use to https://telemetry.sourcedwriter.com/v1/batch, run by the plugin author, once a day and when the plugin is deactivated.

• What is sent: a random install ID created when usage data is turned on; the plugin, WordPress, and PHP versions; the site language; the provider and model in use; whether jobs complete or fail, at which stage, and with which error code; ranges for article length, sources, duration, and token use; the estimated cost per draft; and which features are used (Guided mode, writer profiles, section rewrites, Rank Math). Settings → Usage data lists every event, and Diagnostics shows the exact data waiting to be sent.
• Never sent: the site address, names, emails, user or post IDs, API keys, briefs, topics, keywords, source URLs, outlines, article text, writer profiles, or error messages. The server does not store IP addresses or request headers, and keeps events for 24 months.
• Turning it off deletes the install ID and anything not yet sent. Diagnostics → Usage data → Delete data on server deletes everything already sent. Defining AIBCG_DISABLE_TELEMETRY as true in wp-config.php keeps it off and hides the option.
• Privacy policy: https://sourcedwriter.com/privacy/ — full list: https://sourcedwriter.com/docs/privacy-and-external-services/#usage-data

Privacy and data retention

What the plugin stores

In your own database only: jobs (brief, status, settings snapshot, owner, linked post), sources and extracted notes, generated outline and draft versions, usage and estimated cost per request, writer profiles, post meta on generated drafts (job ID, provenance, SEO suggestions, warnings), the risk acknowledgement in user meta, and settings plus encrypted API keys in options.

Nothing is sent to the plugin author unless an administrator turns on usage data (see External services). It is off by default, contains no content or personal data, and can be turned off or deleted at any time. Its settings and queue are stored in the aibcg_telemetry option.

Retention

A daily WP-Cron event enforces the Prompt/source/log retention days setting (default 90). For completed jobs older than the cutoff it deletes sources and artifacts and clears the stored brief. Older usage rows are deleted. Generated posts are always kept.

Personal data export and erasure

Tools → Export Personal Data returns a user’s jobs and writer profiles. Tools → Erase Personal Data removes their profiles, sources, artifacts, generated-content post meta, and acknowledgement, and unlinks their jobs and usage. Posts are kept.

Uninstall

Uninstall always removes the plugin capabilities and the usage data option, and sends nothing. Define AIBCG_REMOVE_DATA_ON_UNINSTALL as true first to also delete plugin tables, options, encrypted keys, transients, and metadata on every site. Generated posts and linked author accounts are always kept.

Troubleshooting

Error messages link to their fix on the Troubleshooting page. The most common ones:

Missing or invalid API key

Keys are stored per provider: after changing the provider, click Save Changes, then save its key. Keys defined in wp-config.php cannot be edited here. Saving keys requires Sodium.

Provider errors

provider_http_401: key rejected. `provider_http_429`: rate limit or quota. `provider_unreachable`: the server cannot reach the provider over HTTPS. "Selected model is unavailable": choose another model and test the connection again.

Jobs stay queued

WP-Cron is not running. Check AI Blog Writer → Diagnostics, schedule wp-cron.php from a server scheduler, then click Retry stage.

Source URLs fail

Sources must be public HTML or plain-text pages. Replace the URL and start a new job.

Reporting a problem

Download the JSON report from AI Blog Writer → Diagnostics. It excludes API keys, prompts, article text, and source notes.