Specter for WordPress

Edit your whole WordPress site with AI, in your browser.

Connect your WordPress site in the browser and your posts and pages open as clean, structured content. Run AI recipes across the whole archive at once, review each change as a diff, and Specter publishes back over the WordPress REST API.

Self-hosted WordPress or WordPress.com Business+ · nothing to install · browsing & diffs are free · workspaces open with 500 free credits.

Also for: Ghost →  ·  Shopify →  ·  Webflow →

Specter webapp showing an active WordPress connection with an AI recipe diff ready to review

Why WordPress operators reach for Specter

The Block Editor is good for one post. You have thousands.

WordPress is the workhorse of the open web — and the most painful platform on this list to run modern content operations on. The Block Editor was built for handcrafted pages, not bulk work. The REST API is comprehensive but times out on long runs. AI plugins paste GPT output straight into the editor with no quality control and no view of the rest of your site. Specter sidesteps all of that: connect your site in the browser, run AI recipes with the whole archive as context, review every change as a diff, and publish back over the REST API.

What you can do

The workflow layer between WordPress and AI

Specter isn’t an AI and it isn’t a CMS. It’s the workflow and control layer: connect your live WordPress site in the browser, run AI recipes across the whole archive, and review every change before it ships — so the model can finally reach your content, all of it, at once.

Full-archive context for AI

Connect your WordPress site and every post and page lands in one workspace as clean, structured content. AI recipes run with your whole site as context — so they weave accurate internal links and match your tone across the archive.

Bulk operations you actually review

Run an AI recipe across thousands of posts — rewrite intros, fix product mentions, regenerate Yoast/Rank Math meta, swap CTAs. Review the whole pass as a diff, approve what is right, and publish back through the WP REST API.

Everything in one workspace

WordPress sits side by side with Ghost, Shopify, and Webflow. Run the same recipe across more than one platform, review each, and publish back — without logging into separate admins.

Recipes, not one post at a time

AI runs as recipes across your connected content, not pasted post-by-post into a chat window. The whole site is the context — and you review every change as a diff before publishing.

Two-way sync

Edit in your workspace and the change publishes back. Edit in the WP admin and Specter pulls it in. Posts round-trip with full frontmatter, tags, categories, status, dates, featured image.

Dry-run diff before you publish

Every run shows up as a diff first — which WordPress posts would be created, updated, or flagged as conflicts. Browsing and reviewing diffs are free, and every publish keeps a snapshot for rollback.

Application Passwords, never your main login

Specter authenticates via WordPress Application Passwords, scoped to posts and pages. Revoke from your WP admin any time.

Credits, not lock-in

Connecting WordPress, browsing posts, and reviewing diffs are free. Only AI runs spend credits, and every workspace opens with 500 free. Your content stays yours.

How it works on WordPress

Three steps. No drama.

01

Step

Generate an Application Password

In WordPress admin: Users → Profile → Application Passwords. Name it "Specter" and copy the password — you’ll only see it once.

02

Step

Connect WordPress in the browser

Open your Specter workspace, add a WordPress site, paste your site URL, username, and the Application Password. Specter tests the connection, then pulls your posts and pages into the workspace.

03

Step

Run a recipe, review the diff, publish

Edit a post by hand or run an AI recipe across the whole site. Review every change as a diff, approve what is right, and Specter publishes back over the REST API. Every publish keeps a snapshot for rollback.

What round-trips today

The WordPress capability map

Specter syncs the text content of your WordPress site — body, frontmatter, taxonomies. Users, themes, plugins, and WooCommerce are out of scope.

Pushes and pulls today

Post body (markdown ↔ WP blocks/HTML), title, slug, status (draft/pending/published/scheduled/private), publish date, tags, categories, author, excerpt, featured image URL, Yoast / Rank Math primary SEO fields (title, description, canonical), post type (posts and pages).

Specter never touches

Users, comments, themes, plugins, WooCommerce orders/products, media library (referenced by URL only), Elementor / Divi page-builder internals, custom post types beyond posts and pages (on the roadmap). See the full capability matrix →.

Credits, not lock-in

Browsing is free. Only AI runs spend credits.

Connecting WordPress, reviewing diffs, and publishing edits cost nothing. Only AI recipe runs spend credits, and every workspace opens with 500 free.

Prefer your own machine?
Desktop
  • Run the engine locally, your posts as plain .md files on disk
  • Open-source and self-hostable
  • Nothing routed through our servers
  • Desktop Core is $99/year; engine is free on GitHub
Desktop & open-source edition →

FAQ

WordPress questions, answered

Does Specter work with WordPress.com?
WordPress.com Business or higher (where the REST API is enabled and Application Passwords work). The free, Personal, and Premium tiers don’t expose what Specter needs. Self-hosted WordPress works on any plan — anywhere you control the install.
What about the Block Editor and page-builders?
For standard posts, Specter converts Gutenberg blocks ↔ markdown cleanly. For Elementor, Divi, Beaver Builder, and other page-builder pages, the body comes through as the underlying HTML — Specter doesn’t try to round-trip page-builder layouts (they’re not really markdown content). Bulk-edit those in the page-builder itself.
Does Specter touch WooCommerce data?
No. Orders, customers, products, inventory, and Stripe are out of scope. Specter syncs posts and pages only. Product descriptions are not currently in scope — that’s tracked on the roadmap.
What about Yoast or Rank Math?
The primary SEO fields — meta title, meta description, canonical — round-trip in the frontmatter of each post. Plugin-specific advanced fields (schema overrides, social cards) are not currently synced.
Will Specter overwrite edits made in the WP admin?
Not without asking. Specter flags conflicts (where both you and WordPress changed the same post since the last sync) and shows you both versions. You can set a default if you’d rather not be interrupted. Every publish also keeps a snapshot, so rolling back is a decision, not a recovery project.
Does it work with multisite?
Each site in a multisite network is treated as its own connection. Add one Specter connection per network site you want to sync.

Bring AI to your whole WordPress site

Connect in the browser and start with 500 free credits. Prefer files on your own disk? There’s a desktop and open-source edition too.

Guides

Get the most out of Specter + WordPress

Guide

Connect WordPress to the Spectersync webapp

Connect your WordPress site to the Spectersync webapp in a few minutes: site URL, username, Application Password. Covers self-hosted WordPress, WordPress.com plan requirements, and what to do if the REST API is blocked.

Read guide →

Guide

Generate a WordPress Application Password for Spectersync

Generate a WordPress Application Password for the Spectersync webapp in under a minute: Users → Profile → Application Passwords. Covers scopes, revoking, why app passwords beat your main login, and what to do if a 2FA plugin blocks them.

Read guide →

Guide

How Specter handles the WordPress Block Editor (Gutenberg)

An honest look at what round-trips cleanly between Gutenberg and the clean content you edit in Spectersync — and what doesn't. Standard blocks work. Page-builder blocks come through as opaque HTML.

Read guide →

Guide

How to add a CTA to every WordPress post at once

Insert a call-to-action into every WordPress post at a consistent location — after the second H2, before the conclusion, wherever — by connecting your archive to the Spectersync webapp, running one AI recipe, reviewing the diff, and publishing back.

Read guide →

Guide

How to bulk edit WordPress posts for SEO (at scale)

Bulk edit WordPress posts for SEO: connect your site to the Spectersync webapp, run one AI recipe across every post, review the diff, and publish back through the REST API.

Read guide →

Guide

How to bulk-fix broken internal links across WordPress

Find and fix broken internal links across every WordPress post at once: connect your site to the Spectersync webapp, run a recipe to swap dead URLs or old domains, review the diff, and publish back.

Read guide →

Guide

How to bulk-write meta descriptions for WordPress posts

Bulk-generate meta descriptions for every WordPress post: connect your archive to the Spectersync webapp, run an AI recipe to fill the gaps, review the diff, and publish back. Works with both Yoast and Rank Math.

Read guide →

Guide

How to edit WordPress posts with AI

A hands-on workflow to edit WordPress posts with AI: connect your site to the Spectersync webapp, run a recipe across the archive, review the diff, and publish back via the REST API.

Read guide →

Guide

How to protect your WordPress content with Spectersync

Spectersync keeps a clean, structured copy of every WordPress post in your workspace, with a snapshot behind every publish — so a bad edit or plugin mishap is a rollback, not a recovery project. Not a replacement for a full site backup.

Read guide →

See all WordPress guides →