How to Publish GEO Content to WordPress from Promptwatch

For a long time the honest answer to "can Promptwatch publish to WordPress?" was "not yet." That changed. Promptwatch now lists WordPress next to Webflow and Framer as a CMS publishing target, through an official plugin that also handles visitor analytics and crawler log forwarding. If you read an older post on this site that said WordPress was coming soon, this is the update.

Why it matters: most content programs we see run on WordPress. A gap analysis that ends in a Google Doc still needs somebody to paste it into wp-admin, fix the formatting, and remember to track the URL. When the platform that found the gap can also stage the post and watch it get cited, the loop gets shorter and fewer things fall through.

Everything below comes from Promptwatch's WordPress integration guide and its publishing and tracking page, read on October 15, 2026.

Before you start

The plugin needs WordPress 6.0 or newer and PHP 7.4 or newer. It also needs pretty permalinks. If your site uses the Plain permalink setting, the plugin's settings page warns you and points you to Settings, Permalinks. Any option except Plain works. The site URL has to be a public HTTPS address.

Connect in two steps

WordPress doesn't use OAuth like Webflow or an API key like Framer. It uses the plugin plus a sync token.

In Promptwatch, click Settings at the bottom of the left rail, open CMS Integrations under Project settings, and click Connect on the WordPress card. The first step links to the plugin on WordPress.org. You can also search for "Promptwatch" under Plugins, Add New in wp-admin.
Install and activate the plugin, then open Settings, Promptwatch in wp-admin. Copy the Site URL and click Generate token. The token starts with pw_wp_.
Back in Promptwatch, paste both into the second step and click Connect WordPress.

Promptwatch probes the site before saving. A wrong token or an unreachable site fails right there with a specific error, rather than on your first publish. That is a small detail and a good one. The worst kind of integration is the one that says "connected" and fails silently a week later.

If WordPress runs on a different host from the public site, say a headless setup with WordPress at cms.example.com and readers on example.com, the connection settings ask where published content appears. Enter the path, such as /blog. Promptwatch then publishes through the CMS host but tracks the post on your project website, so Page Tracker and citations point at the page people actually see.

What a publish creates

Each document becomes one standard WordPress post. Re-publishing updates the same post rather than creating duplicates.

Title becomes the post title, and the slug from the publication card becomes the URL slug.
The description becomes the excerpt.
A leading standalone image is downloaded into the media library, set as the featured image, and removed from the body so themes don't show it twice.
The author is the WordPress user you pick in the connection settings. The default gives new posts the first administrator.
Categories can be set in the connection settings. Tags are not set. The post type is always post.

Draft first, then live

Open the document in the Promptwatch editor and find the Publication card. Publish as CMS draft creates a WordPress draft that exists in wp-admin but isn't public. WordPress drafts have no public preview URL, so the card's View content link takes you to the post's edit screen. Publish live changes only the post's status. Publishing one document never touches the rest of the site.

We'd always stage the first few as drafts and read them in WordPress before going live. The reason isn't that the plugin is risky. It's that the first drafts tell you whether your tone settings, author mapping, and categories are right, and those are cheaper to fix before anything is public.

The Content Agent can use the connection too: choose WordPress in its CMS Integration setting and pick Publish as draft or Publish live. A live publish adds the URL to the Page Tracker, where crawls, citations, and AI clicks for that page start to show. A draft push doesn't add it until the post goes live.

What breaks the connection

The token becomes invalid if you regenerate it or if your WordPress security keys rotate. The publication card then shows "WordPress connection expired" with a Reconnect button. Generate a new token and paste it in. The existing connection is updated, so publish history survives.

The two optional switches

The plugin can add the Promptwatch visitor analytics script without editing your theme, with admin browsing excluded by default. It can also forward crawler logs. That second one comes with a caveat Promptwatch states plainly: cached requests never reach WordPress, so coverage is partial compared with CDN-level ingestion. If you are behind Cloudflare, connect logs there instead.

Article allowances: Essential $95/mo includes 5 AEO articles, Professional $245/mo 15, Business $579/mo 30. Explore is free with 10 ChatGPT prompts. Related: publishing to Webflow from Promptwatch. Review: Promptwatch.

FAQ

Does publishing one post rebuild my WordPress site?

No. Publish live only changes that post's status.

Are WordPress tags set?

No. Categories can be set in the connection settings. Tags are not.

Should I use the plugin for crawler logs?

Only if you have no CDN option. Cached requests never reach WordPress, so coverage is partial.