BlogTend Connector

Yes. The plugin is the WordPress half of the connection; the researching, writing and scheduling happen in BlogTend. On its own the plugin sits idle and does nothing. Starting is free and takes no card.

That is the thing worth being fussy about. Every article is written from research it actually fetched — the sources are listed in the post and re-checked at publish time — rather than from a model's memory. It arrives as structured blocks: tables where there is a choice to make, steps where there is a process, a real FAQ, a takeaways box. Judge it on the output: publish in draft mode first and read a couple before you let anything go live.

Google's guidance is about whether content is helpful and original, not about how it was produced. What gets penalised is mass-produced pages made only to game search. Which is exactly why BlogTend researches before it writes, cites what it used, skips topics you have already covered, and lets you hold everything for review. You are still the publisher — read what goes out.

No. Three modes: publish live on schedule, land in your WordPress Drafts for approval, or hold in BlogTend until you send it. Switch whenever you like.

Yes. It is an ordinary WordPress post. Edit, delete, re-categorise, change the featured image — exactly as you would with something you wrote.

The connector hands BlogTend your palette, fonts and content width from the active theme and Site Editor, and the article blocks are painted from those. That is what the GET /theme endpoint is for.

The plugin acts as the user selected under Publish as. That user needs to be able to publish posts, upload files and manage categories; any administrator, and usually any editor, already can. The connection can never do more than that user is allowed to, and it only applies to posts, media, categories, tags and the current-user endpoint.

Yes — point Publish as at a user with a narrower role. An Author can create and publish their own posts and upload images but cannot create categories, so category creation will be refused while everything else keeps working.

Settings → BlogTend → Regenerate. The previous token stops working immediately and the new one is shown once. Paste it into BlogTend to reconnect. Rotate it if you think it has been exposed, or when someone who had access to it leaves.

No. Only a hash of it is stored, so it cannot be recovered — generate a new one instead. The settings page shows the last four characters so you can tell which token a site is using.

Nothing leaves on its own. The plugin has no scheduled jobs and makes no outbound requests. It only answers requests that arrive with a valid token, and it answers with exactly what was asked for: the connection status, your categories, recent post titles and links, your theme's design tokens, and the IDs and URLs of content it just created.

Yoast SEO and Rank Math are written to directly. If neither is active, the SEO title, description and focus keyword are stored as post meta (_autopress_seo_title, _autopress_seo_desc, _autopress_seo_keyword) so a theme or another plugin can pick them up.

Some servers strip the Authorization header before PHP sees it. BlogTend also sends the token in an X-AutoPress-Token header, which is not affected, so this is rare. If you would rather fix the header, add this to your .htaccess above the WordPress rules: SetEnvIf Authorization "(.*)" HTTP_AUTHORIZATION=$1

Usually, yes: the connector authenticates the request before those restrictions are evaluated. If a plugin blocks the REST API outright, allow the autopress/v1 routes in its settings.

BlogTend was previously called AutoPress. The REST namespace, header and option names kept the old identifier so that sites connected before the rename keep working without reconnecting.

This version replaces it. Activate BlogTend Connector and the old copy is deactivated automatically; your token and settings carry over, and you can delete the old plugin.

Yes. Each site in the network has its own token and publishing user under its own Settings → BlogTend.