Writing Pages with AI

What It Does

A workflow can write a page, post, or doc for one of your websites with your own Claude API key, on a schedule you choose, from instructions you write. For example: every Monday at 8 AM, write a short post about this week's lawn care and keep it as a draft for me to look over. It runs in your own workspace and saves the page in your own Websites app, the same as a page you add yourself. Nothing is written anywhere else.

You build it in Workflows: pick when it runs (a schedule, an event, or Run), then add the Write a Website Page, Post, or Doc With AI step (action sites.write_page). To make it live on its own as well, add the Publish a Website's Ready Pages step after it (action sites.publish_site). A new workflow is saved turned off; a person turns it on.

The Write Step

• Site: the number of one of your websites.
• Instructions: what to write, in your own words, up to 20,000 characters. Say who it is for, what it should cover, and how long it should be.
• Kind: page, post, or doc. Post is the start. A post is dated the day it is written.
• Use Search Console: yes to give Claude your website's top searches from the last 28 days (the searches, clicks, views, and position), from your own Google Search Console connection.
• Use Ahrefs: yes to give Claude your website's top keywords from your own Ahrefs connection.
• Ready: yes to save the page ready to publish. Leave it off to keep it a draft for a person.

Claude writes a title, an address, a summary, the search title and description, a focus keyword, sections with headings, and, when it fits, questions and answers. They are saved as ordinary heading, text, and question blocks you can change on the page like any other. Claude is told never to invent prices, numbers, names, or promises your instructions do not give, never to write code, and not to repeat a title your website already has. If the address it picks is taken, the next free one is used, such as spring-tips-2.

Drafts Wait for a Person

Unless the step says Ready, the page is a draft and shows in the website's changes waiting, the same as a change an assistant saves. Look it over in Pages, change what you like, mark it ready, and publish. Add a Tell people something is waiting for them step to the workflow if you want a notice when a draft is ready.

The Publish Step

Publish a Website's Ready Pages publishes the website the same as Publish on the screen: the ready pages become the next version, with the note "Published by a workflow" in the history. It is refused while any change saved by an assistant is waiting for a person, so a workflow never makes live something nobody has looked at. Go back to an earlier version from History like any other.

Keys and Where They Come From

• The page is written with your own Claude API key, added in Settings, AI Agents. Its use is billed to your own Claude account.
• Search Console and Ahrefs numbers come only from your own connections in Settings, Connections, Connected Services. They are read for that one run and sent only to your own Claude account. They are never kept in the run.
• Search Console and Ahrefs numbers need an address that is serving the website.

When It Does Not Work

Each failure is one plain sentence on the run in Workflows:

• No Claude key: "Writing uses your company's own Claude API key. An owner or admin adds it in Settings, AI Agents." Nothing is sent and nothing is saved.
• No Search Console or Ahrefs connection when the step asks for it: the step says which connection to add, and Claude is not asked.
• Claude does not accept the key: the step fails at once and says to check the key.
• Claude, Google, or Ahrefs is busy: the step is tried again after 1 minute, 5 minutes, 30 minutes, then 2 hours, as many times as its retries allow.

Test Run checks the step and that a Claude key is connected. It asks Claude nothing and saves nothing.

Who Can Do What

Building a workflow is for anyone who may manage workflows. A connected assistant may put the write step in a workflow only if the person behind it may build websites, and the publish step only if they may publish a website (owners, admins, and anyone whose role allows it). Whatever an assistant saves is turned off until a person turns it on.