Sitearc
Start free

Getting started

Create an account, add a website, connect your agent and approve your first change.

This is the shortest path from a new account to a change you can approve. Each step says what you will see.

1. Create an account

Sign up at app.sitearc.ai. Free needs no card and has no time limit.

You land on Websites. It stays empty until you add a site.

2. Add a website

Choose Add website and enter the domain. Sites are unlimited on every plan, so add each one you run.

The site’s Overview fills in as data arrives. Until a source is connected, it shows what is missing instead of a zero.

3. Connect Google, GitHub and Vercel

Connect accounts once, under Settings › Connected accounts. Every site uses them unless you pick a different account for that site.

  • Search Console gives clicks, impressions, position and queries.
  • Google Analytics 4 gives sessions, key events and landing pages.
  • GitHub lets your agent open pull requests on the repositories you select.
  • Vercel links deployments, so a site reads Live when production is ready.

Connect a site covers each one in detail.

4. Connect your agent

Sitearc’s MCP server lives at https://app.sitearc.ai/mcp. In Claude on the web, add it as a custom connector and sign in.

In Claude Code, add it once for every project:

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

Then run /mcp inside Claude Code and sign in. Codex and other clients use the same address. The Agents guide covers each client and API keys.

5. Ask for the brief

Start every session the same way:

Read the project brief for my site and tell me what is connected.

Your agent calls get_project_brief. It reports the connected sources, active learnings, running experiments and shared context. It spends no credits.

6. Approve a first change

Ideas arrive in Work from site checks, feedback, forms and search data. You accept an idea, or your agent can. Accepting creates a proposal.

Your agent records the exact change, its evidence and the direction it predicts. You approve the proposal in Work.

Your agent then opens a pull request and submits its preview. You approve that exact preview, and merge in GitHub.

Sitearc checks that the merge matches what you approved. Then it measures the change against holdout pages and computes the result.