SEO by platform
SEO for WordPress.com
Sites hosted on wordpress.com cannot use the self-hosted WordPress connectors: /wp-json/ is not reachable there, and plans below Business cannot install plugins. This connection exists for exactly those sites, and you connect it with your WordPress.com account rather than a pasted credential.
How publishing works on WordPress.com
You connect by signing in: choose WordPress.com on the Publishing grid, approve access on wordpress.com, and the connection is made without typing a token. Articles then publish into the site's blog as ordinary posts, flow off the same content calendar as every other platform, and each publish is verified by fetching the public URL.
Articles come off a planned calendar
Plan items on the content calendar and write them two ways: click Write on a card, or let Auto-write pick each one up at midnight on its calendar date. Both run the same researched pipeline, which drafts the article and then revises it against the content score across sweeps.
Help centre: Content calendarInternal links point at pages that exist
With a website selected and an audit completed, the writer links to real crawled URLs from your site, never paths it invents. The 1-to-6 slider is enforced after generation as a hard rule, so the count you set is the count you get.
Every article is scored before you ship it
The content score runs 36 fixed checks in 6 categories, with no randomness anywhere: the same page always produces the same score. Each check comes back as a pass, a warn or a fail, and each failure names its specific fix.
Published means the public URL answered
After every publish we fetch the public URL and record what came back. Published shows only when the page was found, a fresh 404 waits out a grace window, and a server error never concludes the page is missing.
The connection is probed daily
A daily authentication probe runs against every connection. A failure marks it unhealthy with the cause named, authentication, permissions, or unreachable target, so you find out before the next article tries to publish into a dead connection.
What this connection will not do
Stated up front, because finding out after the first publish costs more. Each line is a fact about what we send WordPress.com, not a guess about the platform.
The connection cannot carry JSON-LD: WordPress.com strips script tags out of post content, so sending it would publish the schema as visible text. Add structured data with a WordPress.com SEO plugin where your plan allows one.
There is no separate SEO title to write: WordPress.com hosts no SEO plugin on the plans this connector exists for, so the post title is the one readers and Google see. Rename the post if it must differ.
Connect it in three steps
The same fields the connect wizard asks for, in the order it asks.
Choose WordPress.com
Open the project's Publishing tab. The WordPress.com card is also what site detection recommends when your site is hosted there.
Approve access on wordpress.com
Click through to WordPress.com and approve the connection while signed in to the account that owns the site. No token is typed or pasted.
Send a test publish
Publish an article and open it in your WordPress.com dashboard. Once the first posts reach Published, the chain is proven end to end.
Questions people ask
The ones that decide whether this fits, answered with the verdict first.
- Why not use the normal WordPress connection?
- Because it cannot reach a wordpress.com-hosted site. The self-hosted connector talks to /wp-json/, which 404s on wordpress.com hosting, and the plugin cannot be installed below the Business plan. This connector goes through WordPress.com itself.
- I moved my site to self-hosted WordPress. Which connection now?
- Switch to the WordPress or WordPress Plugin connection. Those speak to your own install directly and, through the plugin, also carry structured data and the SEO title, which wordpress.com hosting has no place for.
- Do my published posts survive disconnecting?
- Yes. They are ordinary posts on your site. Disconnecting removes our access, nothing on the site changes.
Other platforms
Same pipeline, different door. Every platform page states what its connector sends and what it will not.
WordPress
Two connectors, one pipeline. Publish with an application password, or install the plugin and paste one Integration Key. Either way the article arrives with its images uploaded into your own media library, and the publish is confirmed by fetching the public URL.
Wix
Wix stores posts in Ricos, its own structured editor format, rather than HTML. So each article is converted, headings, lists, links and images, into that format before publishing, and posts open cleanly in the Wix editor as if written there.
Framer
Framer does not expose a public API that lets an outside service create CMS items on any site, so there is no direct connector to pretend with. What Framer does offer is two doors we already serve: it imports a CMS collection from an RSS feed, and its official Zapier and Make integrations create CMS items from a webhook.
SEO by platform
See it on your own site
A free audit grades your site A+ to F, then the calendar, the writer and the WordPress.com connection do the week's work. No card required.