CMS
WordPress integration
Core WordPress will accept a finished post over the REST API without a plugin. The work is in deciding what else on the site is already trying to do the same job.
No card · 30 credits on signup
- Body, headings and internal links
- Meta title & description
- JSON-LD structured data
- Canonical URL & a named author
- Featured image with alt text
Every article, formatted for WordPress — nothing to paste.
Connecting WordPress
Live in a few minutes.
Step 1
Confirm the REST API is reachable
Open your site's /wp-json/ path in a browser over HTTPS and confirm it returns a JSON index rather than a 401, 403 or 404.
Step 2
Create a dedicated user and an application password
Add a WordPress user whose role can publish posts and upload files, and use it only for this integration so that revoking access later does not disturb a human account.
Step 3
Connect the project in SEOPulser
In the project's integration settings, choose WordPress and supply the site URL, the username and the application password.
Step 4
Decide who owns meta descriptions and schema
Open any existing post in a browser, view source, and search for application/ld+json.
Step 5
Set taxonomy, author and state defaults
Choose the default category new articles land in, decide whether tags may be created on demand or must match terms that already exist, and select the WordPress user posts will be attributed to.
Step 6
Publish one article in draft-first mode and inspect it
Set the project's autopilot mode to draft first, let a single article run all the way through, and open the resulting post in the WordPress editor.
What lands where
Every field maps cleanly.
- Title and slugPost title and post slug
- Article body (Markdown)Post content
- Meta description and excerptPost excerpt and the SEO plugin's description field
- Featured image and alt textMedia library attachment set as the featured image
- Author entityPost author user, plus the author node in the Article graph
- Categories and tagsPost categories and post tags
- Publish state and schedulePost status and post date
- JSON-LD graphA script tag inside the post content
Worth knowing first
The honest limitations.
Every destination constrains something. These are the ones worth knowing before you commit a content program to WordPress.
- Script tags in post content are subject to WordPress's own filtering.
- Core WordPress has no meta description field.
- The REST API is frequently blocked.
- Custom post types and custom taxonomies are only addressable if they were registered with REST support.
- WordPress.com is a different platform under the same name.
From content chaos to search results
Without a system
- Content takes forever, or costs a fortune
- Generic AI drafts never rank
- No schema, no author, no canonical
- Publishing is a manual copy-paste chore
- Scaling too fast gets you flagged
With SEOPulser
- Research to publish, fully on autopilot
- Your answers make every draft original
- JSON-LD and a named author on each
- One-click publishing to your CMS
- Cadence ramped to your site's age
What's different
Built to rank, not just to publish.
Structured data on every article
Article, FAQ, HowTo and Breadcrumb JSON-LD are generated inside the pipeline and stored with the piece, so they travel to whatever you publish to.
Real named authors
Every article is bylined to a named person with a bio and a profile page — not the brand as a schema.org Person, which Google advises against.
Your first-hand experience
Before drafting, you answer a few questions only you can, and the answers go into the piece as material a model could never have inferred.
An MCP server for the loop
Claude, Codex or your own agent reads the calendar, answers questions, queues generation and controls autopilot — over the same API the dashboard uses.
Pace matched to site age
Publishing cadence ramps against when your site was first seen, so a young domain never ships at a volume that reads as scaled content abuse.
Search Console improvements
Connect GSC and it finds near-miss rankings, CTR gaps and thin pages, then rewrites them as accept-or-reject hunks — on posts we didn't write, too.
Pricing
Start free. Pay when it’s working.
Thirty credits on signup — three full articles, published to your own site. No card.
Professional
Most popular$69/mo
Billed annually
- 100 articles a month
- 3 projects
- Search Console improvement loop
- MCP server and REST API keys
- Article, FAQPage, HowTo and BreadcrumbList JSON-LD on every piece
Questions people actually ask
Do I need to install a plugin to connect WordPress?
No. The connection uses the REST API that ships with core WordPress and an application password generated in a user's profile. There is nothing to install, update or keep compatible on your side. The trade-off is that we work within what core exposes, which is why head markup is harder to reach than post content and why meta descriptions depend on whichever SEO plugin you already run.
Will this conflict with Yoast or Rank Math?
They coexist, but the structured data needs a decision. Both plugins emit their own Article graph with an author and publisher, so publishing our JSON-LD on top produces two descriptions of the same page. View source on a post, search for application/ld+json, and pick one owner. Usually that means letting the plugin keep Article and letting us supply FAQPage and HowTo, or turning the plugin's schema off for posts.
Can articles go into a custom post type?
Only if the post type was registered with REST support enabled. Many plugin-created types were not, and in that case they are invisible to every API client, not just ours. The same applies to custom taxonomies. If you control the code that registers the type, adding REST support is a one-line change; if a plugin registered it, you are dependent on that plugin's author.
What if my host blocks the REST API?
That is common on managed and security-hardened hosting, and it shows up as a 401 or 403 on a connection check rather than something ambiguous. The fix is on the WordPress side: allowlist the endpoints, relax the rule that blocks authenticated write requests, or re-enable application passwords if a security plugin disabled them. Test by loading your site's /wp-json/ path in a browser before opening a support ticket.
Does the featured image go into my media library?
Yes. The image is uploaded as a normal attachment, alt text is written to the attachment record, and it is then set as the post's featured image, so it behaves like anything you uploaded by hand. The connecting user needs upload capability. If you run a media offload plugin, expect the final URL to be rewritten to your CDN after the upload completes.
Can it publish as a draft instead of going live?
Yes, and on WordPress that is the mode we would start with. In draft-first autopilot, generated articles are written with draft status and appear in your posts list for review in the standard editor. Approve-each goes further and holds generation itself until you clear the piece. Both are project settings, so the gate does not depend on anyone remembering to apply it.
- GhostPublishes through the Ghost Admin API using a custom integration key, filling the post fields Ghost already has — including per-post code injection for structured data.
- WebflowWrites finished articles into a Webflow CMS Collection, mapped field by field, with a separate publish step and a plan for where the JSON-LD lives.
- WixPublishes into the Wix blog through an authorized app, with a candid account of where the platform's control over head markup limits what any external tool can do.
- WebhooksA signed publish event delivered to an endpoint you own, carrying the article, its metadata and the generated JSON-LD graphs. Everything after that is your code.
Connect in minutes
Publish to WordPress without touching a draft.
Connect once, confirm the brief, and articles arrive on your WordPress site with structured data and a real author attached. Keep the review gate on until you trust it.
3
Free articles on signup
- No credit card
- Published to your own site
- JSON-LD and a named author
- Cancel anytime