Guides · The Promptable Sites team · Updated October 2026

Run Your Website With a Team of AI Agents

Short answer: When your website is plain files in your own GitHub account, you can give it a small team of AI agents. One researches your industry and suggests articles. One studies which pages perform best and drafts improvements to the weaker ones. One keeps the site tidy: broken links, outdated posts, what to cut. Each runs on a schedule with Claude Code routines and drafts its changes for your approval. With your main branch locked, nothing goes live until you say so.

What a “promptable site” is

A promptable site is one an AI can work on directly. Its pages are plain files, its history is saved, and every change can be previewed before it goes live. That’s what lets you hand recurring work to agents.

Website builders like Squarespace don’t work this way. Squarespace’s official developer tools cover products, orders, contacts, and domains, but none of them let outside software edit pages, posts, or design.¹ More: Why Squarespace Isn’t Built for AI Agents

How the agents run: Claude Code routines

A routine is a saved Claude Code task that runs on its own. You write the instructions once, choose your site’s GitHub repository, and set a schedule: hourly, daily, weekdays, or weekly. Monthly and quarterly schedules need a custom setting from the command line (/schedule update).²

• It runs in the cloud, so your computer can be off.²
• It saves its work to a separate branch in GitHub, named with claude/, unless its instructions say otherwise.²
• You review what it did and approve the change, or ask for edits.²
• It’s available on Pro, Max, Team, and Enterprise plans and uses the same usage limits as the rest of your Claude plan.²

Routines are in research preview, so details may change.²

Agent 1: The researcher

Job: find topics your customers are asking about and recommend articles to write.

Schedule: monthly.

Sample instructions:

Research what people in [your industry] are asking about this month. Check our existing articles first so you don’t repeat them. Recommend five new articles. For each, give a working title, who it’s for, the question it answers, and two or three sources. Save the list as a new file in the ideas folder.

What it needs: web access. The default cloud environment only reaches a short list of developer sites, so change the routine’s environment to allow wider internet access.²

Agent 2: The optimizer

Job: learn from your best pages and improve the weaker ones.

Schedule: monthly.

Sample instructions:

Using last month’s Search Console data, list our five best and five weakest pages by clicks. Compare them. For the three weakest pages that get impressions but few clicks, draft a better title, search description, and opening paragraph. Keep every page address the same. Explain each change.

What it needs: your Google Search Console data. Search Console has an API that reports clicks, impressions, click-through rate, and average position.³ The routine needs read-only access to your Search Console data. On Pro and Max plans, store the key as a network secret on the routine’s environment, never in your site’s files. Ordinary environment variables are visible to anyone who uses the environment.⁴

Agent 3: The caretaker

Job: keep the site current and tidy.

Schedule: weekly for links, quarterly for content.

Sample instructions:

Weekly: check every link and image on the site. Fix broken internal links. List broken outside links with a suggested replacement.

Quarterly: read every article. Flag any that are out of date, thin, or overlapping. For each, recommend update, combine, or remove. For anything removed or combined, add a redirect from its old address to the closest related page.

What it needs: just the repository.

The redirect rule matters. When a page is removed, its address should point to the closest related page. Otherwise Google treats it as missing and drops it.⁵ See The Redirect Checklist

Rules that keep agents safe

• Approve everything. Routines draft; you publish. Don’t set them to publish on their own.
• Lock your main branch in GitHub with a rule nobody can bypass, including you. Routines push as your GitHub account, so a rule you can skip, they can skip too.²
• Give each routine only what it needs. Remove connectors and access it doesn’t use. A routine can use every tool in an included connector without asking.²
• Write the rules down. A short guide file in your site tells every agent how the site is built and what never to change, like page addresses without redirects. Claude Code reads it at the start of every session.⁶
• Read the run, not just the status. A green status means the routine ran, not that it succeeded. Open it and check.²

What it costs

Routines are included in paid Claude plans and draw from the same usage as your other Claude work.² Pro is $20 a month, or $17 a month billed yearly.⁷ Hosting a site of plain files on Cloudflare is free.⁸

We’re running this on our own site

Promptable Sites is our lab. We’re setting up these three agents on promptablesites.com first and will share what works, what doesn’t, and the exact instructions we use.

Questions owners ask

Do I need to know how to code? No. You write instructions in plain words and review what the agents draft. It helps to be comfortable reading a list of changes.

Can an agent publish on its own? It can be set up that way, but we don’t recommend it. Keep a person approving every change.

How much of my Claude plan will this use? It depends on your site’s size and how often the routines run. Start with weekly or monthly schedules and check your usage page.²

Can I do this with Squarespace? Not for pages and posts. Squarespace’s official developer tools don’t let outside software edit them.¹ Unofficial tools exist, but they work through your login session and aren’t supported by Squarespace.

What if routines change? They’re in research preview, so the setup may change.² The ideas here, an agent per job, a schedule, and approval before anything goes live, will carry over to whatever comes next.

Sources