Connect the tools a website already uses
How Sitearc works with Search Console, Analytics, GitHub, Vercel, Astro and your agent, and what each connection makes possible.
Each connection reads one thing your site already produces. None of them write to your site on their own.
- Adding the MCP server to a Codex workspaceAdd the hosted MCP server to Codex, verify it with free calls, and keep a record of the connection.A filled connection record
- Astro SEO: the three config decisions and the layout that emits canonicalsWhat Astro's site, trailingSlash and output format actually control, plus the layout code that emits a canonical tag.A copyable config, a layout canonical block and a six-step build check
- Connecting Sitearc to Claude CodeThe install path, and the five steps that prove the connection works. A filled verification record before any credits are spent.A filled install and verification record
- Google Search Console setup, with the first report read outProperty type, verification and permissions, then a filled first-month reading with the arithmetic written down.A filled setup record and a first-month reading
- Preview deployments as evidenceWhat a preview proves, what production proves, and a filled pre-merge check run against one pull request.A filled pre-merge deployment check
- Reading GA4 for a client who asks simple questionsA question-first reading map for one property, with the denominators, the consent caveat and the two readings to distrust.A filled question and denominator table for one month
- Search Console and Analytics in one viewWhy search clicks and site sessions disagree, with a filled reconciliation table and the three explanations for a gap.A filled reconciliation table for one month
- What the GitHub connection can and cannot writeThe GitHub App behind every pull request your agent opens. What it needs first, and the boundary it never crosses.A filled connection record, a link_repo sequence and a failure table