The site plan is on Pro and Agency, at Site plan on any tracked site. Where the task list says what to do, the plan says where, in what order, and with what words.
What it reads
We crawl up to 60 pages of your site, following your sitemap and internal links and respecting robots.txt. Each page is reduced to its title, description, headings, visible text, schema types and a set of signals: prices, opening hours, an address, question-shaped headings, dates, noindex, and whether the content only appears after JavaScript runs. Nothing on your site is changed.
How the plan is built
Every non-branded buyer question from your latest check is matched to the page that should answer it. A page that matches but where assistants did not name you becomes an expand item. A question with no page becomes a create item, and so do comparisons against the rivals assistants name most, a market roundup and an FAQ page when the site has none. The reasons winners are credited for, and the facts assistants got wrong, become fact items placed on the page where assistants would read them. Problems on existing pages become technical items, plus one site-wide item from the readiness checks. The sources assistants cite that you are not on become off-site items.
When a model key is configured, the writer model sharpens every item with page-specific steps, outlines and paste-ready copy built only from facts visible in your pages. It never adds facts.
What each item carries
The page URL, why it matters, the evidence (question, rival, issue), ordered steps, an outline of headings for new or expanded pages, the facts you need to supply, and copy you can paste. Items have a priority, a week and an effort size. Create items are placed on the Autopilot calendar as planned articles.
Working the plan
Open an item and click I've done this, with a note if you like. We re-read the page within seconds and re-run the check that raised the item: a thin page needs at least 250 words, a missing title must be present, noindex must be gone, a fact must appear in the text, a new page must be live. The item shows done, verified on page or done, page unchanged with what is still open. Weekly checks then look for the questions the item targeted flipping your way, and mark it verified: answers moved.
Filter by All, To do, Done or Verified. Not relevant dismisses an item; Undo puts it back. Rebuilding the plan keeps the status of every item that is still there.
Doing it with an agent
Click Do it with your agent for the one-line Claude Code command, the MCP config for Cursor and Claude Desktop, and the prompt that works. Agents read the plan, edit your site, and mark items done; every change is attributed, checked on the page, and can be undone. Details on the agents page. No MCP? Download PLAN.md and give the agent the file.