Skip to main content

Integration

Publish straight to WordPress

cpywrk researches the topic, writes the article, runs it through six quality checks, and then puts it on your WordPress site. You connect the site once. After that, publishing is one button and nothing is copied and pasted anywhere.

Start free trial See the whole pipeline

Two kinds of WordPress, two ways in

Most guides skip this, and then the steps stop matching what you are looking at. WordPress.com and a self-hosted WordPress site connect differently, so start by working out which one you have.

WordPress.com

Your site is hosted by WordPress.com and you log in there. Connecting is a single authorisation step: cpywrk sends you to WordPress.com, you approve it, and you pick the site.

Self-hosted WordPress

You installed WordPress on your own hosting, which is what most business sites run. Connecting uses an application password, a feature built into WordPress since version 5.6. There is nothing to install.

Connecting a self-hosted site

About five minutes, once, and no plugin.

  1. Create an application password in WordPress

    Go to Users, then Profile, and scroll to Application Passwords. Give it a name you will recognise later, such as cpywrk, and add it. WordPress shows the password once and never again, so copy it before you leave the page.

  2. Open Integrations in cpywrk

    Settings, then Integrations, then WordPress (Self-Hosted).

  3. Enter the site URL, your username and the password

    The site URL is the address people visit, for example https://yourcompany.com. The username is your WordPress login, not your email address.

  4. cpywrk checks it before saving

    The credential is tested against your site REST API straight away and stored encrypted only if it works. A typo, or a REST API locked down by a security plugin, fails here in the ten seconds you are paying attention rather than silently at publish time three weeks later.

Connecting WordPress.com instead

Settings, then Integrations, then Connect on the WordPress.com row. You approve cpywrk on WordPress.com and choose the site. There is no password to copy, because the authorisation is held as a token you can revoke from your WordPress.com account whenever you want.

What happens when you press Publish

The article arrives formatted

Headings, lists, links and tables come across as real HTML, not as a wall of text you have to restyle. What you approved in cpywrk is what appears on the site.

Images land in your media library

The images generated for the article are uploaded to your WordPress media library as WebP, so they serve from your own domain and the asset is yours. cpywrk is not a permanent image host, and an article still pointing at our servers would be one infrastructure change away from breaking. Republish with a regenerated image and the old file is removed rather than left behind.

You choose the post type

cpywrk reads the post types your site actually exposes, so if your theme or a plugin defines its own, it is on the list. If your site does not report them, cpywrk offers posts and pages.

Where you stay in control

Handing publishing rights to software is a real thing to ask, so here are the two things worth knowing before you do it.

  • You can revoke it yourself, instantly. Delete the application password in WordPress and the connection stops working. You do not need to ask us, and articles already published stay where they are.
  • The credential never leaves the server. It is encrypted at rest and is never sent to your browser, which is why the integrations screen shows you the connection rather than the password.

Not on WordPress?

Shopify connects the same way, and anything else receives the finished article through a webhook that hands over the article and its images to whatever you do run.

Questions

Can cpywrk publish directly to WordPress?
Yes. cpywrk connects to both WordPress.com and self-hosted WordPress sites, and publishing is one button once connected. The finished article arrives formatted, with its headings, links and images already in place.
Does cpywrk need a WordPress plugin?
No. A self-hosted site connects with a WordPress application password, which is built into WordPress and needs nothing installed. WordPress.com connects by authorising cpywrk from your WordPress.com account.
Where do the article images end up?
In your own WordPress media library. cpywrk uploads the generated images to your site as WebP, so they serve from your domain and you own the asset. cpywrk is not a permanent image host, and an article that still pointed at our servers would break the day we moved them.
Can cpywrk publish to a custom post type?
On a self-hosted site, yes. cpywrk reads the post types your site actually exposes and lets you choose one, so a theme or plugin that defines its own type is available rather than ignored. If your site does not report its types, cpywrk offers posts and pages.
How do I disconnect cpywrk from my WordPress site?
Revoke the application password in WordPress under Users, then Profile. That disconnects the site immediately and does not require contacting cpywrk. Articles already published stay where they are.

Connect your site and watch one article go out

The trial is one full article, every step and every check, in your own time. No card.

Start free trial