Skip to content
Start a free audit

Claude SEO prompt / Publishing

Publish as a draft

Lists the connections with their health, then pushes one article as a draft and reports the result fields as returned. A draft has no public URL, so its state is unverified, and that is expected.

Calls
list_integrationspublish_article
Cadence
Per article
Key
Content API key

Writes to your CMS. Draft here; pass status publish only when you mean it.

All 16 prompts in the playbook

Copy the prompt

Square brackets are yours to fill before you send. In a fresh conversation, paste the brand brief from the playbook first, then this.

Call list_integrations for [project name]. Show each connection with provider, status, last_error and auto_publish_status. If there is exactly one, use it; otherwise ask me which. Then call publish_article for article [article_id] with status draft. Report sent, requested, state and external_url exactly as returned. If state is unverified, say that a draft has no public URL to verify and that this is expected.

The brief and the connect steps live on the playbook page.

What each call returns

At least one of these is a workspace tool, so the server needs a content API key from a project's Developer tab.

  • list_integrations

    a project's publishing connections: provider, status, last error, and the draft-or-live default

  • publish_article

    the result of pushing one article through one connection: sent, external_url, and a state that reads published only after the public URL was fetched and carried the article

More publishing prompts

Draft by default. A publish call reports sent, then a state, and the state reads published only after the product fetched the public URL and found the article on it.

Run it on your own data

A project's Developer tab issues the content API key this prompt needs. The playbook's connect steps take about two minutes.

Create a free accountConnect Claude