Claude SEO prompt / Content
Brief and write one article
Claude shows the brief, waits for a yes, starts the job and polls it. Done arrives with an article_id and a score; failed arrives with the reason.
- Calls
generate_articleget_article_status- Cadence
- When you have a keyword ready
- Key
- Content API key
Spends article credits. Refused with 402 when the workspace has none, and with 409 when the keyword already has an article.
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.
Write one article for the [project name] project on [keyword]. Before calling generate_article, show me the brief you will pass: the angle, the reader, three points it must cover, under 4000 characters. Wait for my yes. After the call, poll get_article_status about every two minutes and tell me the status each time: queued with the queue position, drafting, revising, then done with the article_id and score, or failed with the error. Stop polling after done or failed.
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.
generate_articlea job for a new article on a keyword. Spends article credits. Refuses a keyword that already has an article
get_article_statuswhere a job stands: queued (with queue position), drafting, revising, done with an article_id and score, or failed with the error
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.