Sitearc
Start free

SolutionsSolo developers

For solo developers who build sites with an agent.

Connect every site you run. Claude Code or Codex gets the search data, site health and research to improve them. You see it all in one place.

Start freePricing at your size
Demo data. Rosa Delgado is a fictional developer with four sites.

The jobs on your plate.

You built the sites. Now they need running. Each job below has a feature that does it, and your agent can use every one.

  1. Know which site needs you

    Every site sits in one list with its status, search clicks and open work. A site shows Live only when its latest Vercel deploy is ready.

  2. Find what to fix

    A crawl scores every page out of 100 and lists what's broken, worst first. Search Console and GA4 sit side by side, never added together.

  3. Give your agent real data

    One MCP connection gives your agent about 130 tools. It reads search data, audits, feedback and your brand kit before it touches code.

  4. Ship fixes, then see if they worked

    Your agent opens a pull request and you check the exact preview. Sitearc measures the change against holdout pages.

  5. Start the next site the same way

    Your agent plans an Astro site on Vercel, from your own repository or a reviewed starter. Then it adds Google measurement. You approve each plan first.

  6. Research when a site needs it

    Keyword, competitor and backlink lookups run on credits. A keyword search is about 80 credits. Saved results are free to read again.

Connect Claude Code in one command.

Add Sitearc once, for every project. Then run /mcp to sign in. Codex and other MCP clients use the same URL.

  • 130 tools. Your agent reads the same search, analytics, audit, feedback and form data you see.
  • 61 are read-only. A read-only key sees only those.
  • 69 write or spend. They file proposals, open pull requests or buy research with credits.
  • None of them can approve. Decisions live in the dashboard, behind your sign-in.

Terminal

claude mcp add --transport http sitearc --scope user https://app.sitearc.ai/mcp

Then, inside Claude Code

/mcp

Pick Sitearc and sign in. Claude can now read your sites.

Set up the next site, too.

Start from your own Astro repository or a reviewed starter, then add measurement. Your agent plans each step. You approve the plan before anything is created.

  • Astro setup. A Vercel project built from a pinned commit of your repository, or a new private one from the starter.
  • Google measurement. A GA4 property and stream, a consent-gated tag, ownership checks and the sitemap.
  • Approvals expire. Each one covers exactly the listed accounts, for 30 minutes.

Agent-requested setup

Review your website setup

Check the exact repository and hosting account before approving. Approval expires; an agent can continue only this approved run.

Letterpress SupplyAwaiting approval
GitHub source · create private repository
rosadelgado/letterpress-supplyReviewed Sitearc Astro starter v1
Vercel · create in rosadelgado
Astro project + preview deployment
  1. 01Verify pinned Astro source
  2. 02Create Vercel project
  3. 03Deploy + verify HTTPS

This creates the resources shown in your selected accounts. The exact reviewed starter version is committed to this new private repository and built on Vercel. Approval expires after 30 minutes.

Approve this setupCancel run

Google measurement · exact approved website

https://letterpresssupply.example
Awaiting approval
Connected Google identities
Analytics: rosa@rosadelgado.exampleSearch Console: rosa@rosadelgado.example
Analytics account
Letterpress Supply
Property / stream
Create a new GA4 property · Create web stream
Property settings
America/New_York · USD

GA4 configuration

planned

Website Analytics connection

planned

Website Search Console connection

planned

Code review / deployment

planned

GSC ownership

planned

Sitemap

planned

Approval permits only the listed GA4 and URL-prefix ownership and sitemap operations. No DNS change, site edit or email is included.

Approve exact measurement planCancel
Demo data. The review screens your agent links you to.

See whether each change worked.

Sitearc measures every shipped change against holdout pages. The result reads Won, Backfired or Inconclusive, and Sitearc works it out, not your agent.

  • Shipped means merged as approved. Sitearc counts a change only when what merged is the preview you approved.
  • Results become learnings. Your agent's next proposal cites what worked before.
Demo data. A change Claude shipped through GitHub, measured against 3 holdout pages.

A week with Sitearc.

Five working days, one developer, three live sites. Claude Code does the reading and the drafting. You make the calls.

Rosa Delgado is a fictional developer. She runs three live sites and is setting up a fourth.

  • A person
  • Your agent
  • Sitearc
  1. Monday

    Check every site in one list

    • You

      You open Websites. Trailhead Maps shows Google Analytics needs reconnecting, so you reconnect it.

    • Your agent

      Claude reads last week's Search Console data for each site and lists pages losing clicks.

      get_search_opportunities
  2. Tuesday

    A problem in the data becomes a proposal

    • Your agent

      On Tide Tables, Claude finds twelve harbor pages sharing one title. It files a proposal with its evidence and a 28-day prediction.

      create_proposal
    • You

      You read the evidence in the Work queue and approve the proposal.

  3. Wednesday

    The fix goes through GitHub

    • Your agent

      Claude opens a pull request with the new titles and submits it for review.

      github_open_pull_request
    • You

      You check the exact preview, approve it in Sitearc, and merge in GitHub.

  4. Thursday

    Sitearc starts measuring

    • Sitearc

      Sitearc confirms what merged is what you approved. It starts measuring against 3 holdout pages.

    • Your agent

      On another site, Claude runs a crawl and turns 3 broken links into ideas.

      run_site_audit
  5. Friday

    Last month's change reports back

    • Sitearc

      A change shipped four weeks ago reads Won. Sitearc works out the result itself, not your agent.

    • Your agent

      Claude records what it learned. Later proposals cite it.

      record_learning

Pricing for one person.

Start free, with every site you run. Move to Pro when you want research, rank tracking and scheduled sync.

  • Free covers unlimited sites, MCP on saved data and 500 page renders a month.
  • Pro is for you alone, with no seat to add.
  • Saved data, Search Console and GA4 reads never cost credits.
Full pricing and every credit cost

Pro at your size

$99a month

You alone, no teammates

Owner
$99
Teammates
$0
Unlimited sites and workspaces
Included
Clients and reviewers
Free

A month like this6,700 credits

An example: 3 sites, 100 tracked keywords and light research. Pro includes 100,000 credits a month.

That fits inside the allowance, with 93,300 to spare. No pack needed, so the month is $99.

Start free

Free is the trial. Monthly, cancel any time.

What Sitearc doesn't do yet.

Better you hear it here. These are on the list, not in the product.

  • WordPress plugin (not released)Not yet

    Changes ship through GitHub pull requests today.

Connect your first site today.

Free has unlimited sites and never expires. Your agent can start the same day.

Start freeRead the docs