NewSend finished articles to WordPress, Shopify or any site, as drafts you approve.Publish articles to WordPress and Shopify.

Publishing to your website

Connect WordPress, Shopify or a webhook of your own, and send articles to your site as drafts or live: by hand, by the agent, or automatically.


Connect your website once, and Citeroot can put an article on it. You choose whether it arrives as a draft for you to check, or live for visitors to see.

It is on the paid plans (Grow, Pro, Max and Enterprise). Each project has its own connection, because a project is one website.

#Three ways an article gets there

  • You press a button. Open an article in Docs or Article Studio and press Send to your site as a draft or Publish live.
  • You ask the agent, or an AI app you connected (Claude, ChatGPT and others). For example: "write an article for my weakest question and send it to my site". It sends a draft unless you say to make it live.
  • Automatically. In Settings → Publishing, tick Send every new article automatically. Every article the agent or Article Studio finishes then goes to your site.

#What is sent, and what is not

  • The article's title, its body as HTML, a short description and the last part of its web address.
  • The Before you publish notes are for you. They are never sent. The title tag, meta description and web address written there are sent as fields where the site has a place for them.
  • An article with blanks left in [square brackets] never goes live. It is sent as a draft, and Citeroot tells you which blanks are left.
  • Sending the same article again updates the post already on your site. It does not make a second one.
  • Raw HTML and scripts in an article are sent as plain text, so nothing can run on your site.

Start with drafts. Read each article on your site before visitors see it.

#WordPress

You need a WordPress user who can write posts (an Author, Editor or Administrator), and an application password for that user. An application password is a separate password for one app. It is not your login password, and you can remove it at any time.

  1. In WordPress, open Users → Profile.
  2. Scroll to Application Passwords. Type a name, for example "Citeroot", and press Add New Application Password.
  3. Copy the password it shows.
  4. In Citeroot, open Settings → Publishing, choose WordPress, and enter your site's address, the user name and that password. Press Connect.

Articles arrive under Posts. The short description goes in the post's excerpt. If you use an SEO plugin, copy the title tag and meta description from the article's notes into the plugin's fields.

If it doesn't connect:

  • "WordPress refused the username or application password." Make a new application password. Use the user name, not the email address.
  • "We couldn't find WordPress's REST API." Check the address. A security plugin may have switched the REST API off.
  • No Application Passwords section. WordPress shows it only on sites that use https. Some security plugins hide it.

#Shopify

Articles go into a blog in your store, under Content → Blog posts.

Shopify changed how stores connect apps in January 2026, so there are two ways.

Stores set up since 2026: client ID and secret

  1. In Shopify's Dev Dashboard, create an app for your store.
  2. Give it the write_content permission.
  3. Install it on your store.
  4. Copy its client ID and client secret.
  5. In Citeroot, open Settings → Publishing, choose Shopify, and enter your store's address (the one ending in .myshopify.com), the client ID and the secret.

The app and the store must be in the same Shopify organisation.

A custom app made before 2026: access token

If your store already has a custom app (Settings → Apps → Develop apps) with the write_content permission, choose Access token and paste its Admin API access token.

Either way you can name the blog the articles go in. Leave it empty to use the store's first blog. The author name is shown on each article.

The title tag and meta description are not set in Shopify's search engine listing. Copy them from the article's notes.

#Webhook

For any other system, Citeroot can send each article to an address of yours as a signed POST. It works with your own code, and with Zapier, Make or n8n (use their "catch a webhook" step).

In Settings → Publishing, choose Webhook and enter the address. It must start with https://. Citeroot sends a test request (ping) and saves the connection if your address answers 200. It then shows a signing secret once. Copy it.

What we send

POST https://example.com/hooks/citeroot
Content-Type: application/json
X-Citeroot-Event: article.draft
X-Citeroot-Timestamp: 1794744000
X-Citeroot-Signature: sha256=<hex>

{
  "event": "article.draft",
  "sent_at": "2026-11-15T12:00:00.000Z",
  "project": { "id": "prj_…", "name": "Your brand", "website": "example.com" },
  "article": {
    "id": "brf_…",
    "status": "draft",
    "title": "…",
    "slug": "…",
    "title_tag": "…",
    "meta_description": "…",
    "html": "<p>…</p>",
    "markdown": "…"
  }
}
  • event is article.draft, article.published or ping (the test, with no article).
  • article.id stays the same when an article is sent again, so you can update the page you made before.
  • Answer with any 2xx status when you have taken the article. If you answer with JSON such as { "url": "https://example.com/blog/my-page" }, Citeroot shows that link on the article. Add "live": false if you kept a published article as a draft, and Citeroot will say so.

Check the signature

The signature is an HMAC-SHA256 of the timestamp, a full stop and the raw body, with your signing secret, written in hex:

const crypto = require("crypto");
const expected = "sha256=" + crypto.createHmac("sha256", SIGNING_SECRET).update(timestamp + "." + rawBody).digest("hex");
const ok = crypto.timingSafeEqual(Buffer.from(expected), Buffer.from(signatureHeader));

Refuse a request whose signature is wrong, or whose timestamp is more than a few minutes old. To get a new signing secret, connect the same address again.

#Safety

  • What you type when you connect (a password, a token, a secret) is stored encrypted and is never shown again.
  • Citeroot only sends to the site you connected. It does not follow a redirect to another address.
  • Disconnect in Settings → Publishing stops new sends at once. Posts already on your site stay there.
  • To cut Citeroot off from the site's side, remove the application password in WordPress, or uninstall the app in Shopify.

#What it doesn't do

  • It doesn't upload images, set categories or tags, or schedule a post for later.
  • It doesn't delete or unpublish a post on your site.
  • It sends articles, not reports or plans.
  • An AI app connected through the MCP server can publish too, when you ask it, with the same rules. A read-only API token can't.

Last updated Nov 15, 2026 · Suggest an edit