Google Search Console and Antlytics
Antlytics is privacy-first web analytics: what happens after someone lands on your site. Google Search Console is Google’s product for search performance: queries, impressions, CTR, and indexing.
You do not need to replace Search Console with Antlytics. Use both. A first-party “Connect Search Console” overlay in the Antlytics dashboard is on the roadmap; until that ships, keep GSC for search data and Antlytics for on-site behaviour — or combine them in your AI tools via MCP.
What each tool owns
| Question | Antlytics | Search Console |
|---|---|---|
| Pageviews, visitors, bounce, duration | Yes | No |
| Top pages and engagement after landing | Yes | Landing pages only (search clicks) |
Referrers (including google.com) | Yes — domain only, not query text | No |
| Goals and funnels (leads, sign-ups) | Yes | No |
| What people typed in Google | No | Yes |
| Impressions, CTR, average position | No | Yes |
| Indexing, sitemaps, crawl / coverage | No | Yes |
Antlytics will not invent search queries from pageviews. That data only exists in Google’s Search Console API.
Recommended setup for content and leads
- Verify the site in Search Console (domain or URL-prefix property).
- Install Antlytics and define goals for the outcomes you care about (enquiry form, booking page, thank-you URL).
- Publish and iterate content using GSC for discovery (impressions, queries, CTR) and Antlytics for whether those landings engage and convert.
- Optional: connect both MCPs in Cursor or Claude so one chat can draft a client report from both sources (see below).
Antlytics does not ship an SEO crawler, Lighthouse suite, or rank tracker. Those stay outside the product on purpose — see product philosophy in the repo docs.
Using Antlytics today without a GSC connection
For organic SEO work you can already:
- Watch Referrers for Google (and other search engines) share of visits
- Use Pages for which URLs get traffic and how they bounce / engage
- Use Goals and Funnels for lead outcomes on content landings
- Export a Site Report for the period (KPIs, top pages, referrers, campaigns)
Open Search Console in parallel when you need query text, impressions, or ranking context.
Combine Search Console with Antlytics MCP (near-term path)
If you use an AI coding tool that supports multiple MCP servers:
- Connect the Antlytics MCP (
https://www.antlytics.com/mcp) and authorise your account. - Connect a Google Search Console MCP (or equivalent Google tool your client supports) with read access to the same property.
- Ask for a combined brief, for example:
For themortgageroom.com.au last 28 days: from Search Console, list top queries and landing pages by clicks and impressions. From Antlytics, show pageviews, bounce, and goal completions for those paths. Suggest which articles to improve vs which topics to write next.
Antlytics tools such as get_top_pages, get_top_referrers, get_stats, and Pro generate_report cover on-site KPIs. GSC tools cover queries and search metrics. Keep the two sources labelled so you do not mix Google impressions into Antlytics visitor counts.
First-party dashboard integration (planned)
The public roadmap includes a Google Search Console integration: connect a property once and surface top queries and CTR next to pageview data in the dashboard. That remains optional / later — not core identity — and will not replace crawl or indexing views in Google’s console.
Until it ships, this doc is the supported path: GSC for search truth, Antlytics for on-site truth, MCP when you want both in one agent chat.