# SiteLine > SiteLine keeps Search Console history past Google's limits and adds cookieless analytics agents can query. From $4.99/month. SiteLine (siteline.tools) is operated by Aglet Technologies. It keeps Google Search Console data past the 16-month window, counts visitors without cookies, and exposes both to AI agents through two read-only MCP servers at https://siteline.tools/mcp/search-console and https://siteline.tools/mcp/analytics. ## Product - [Pricing from $4.99/mo: Search Console + MCP](https://siteline.tools/pricing): Starter $4.99/mo for 1M events, Growth $19.99 for 10M, Scale $99.99. Search Console, cookieless analytics and MCP on every tier. 7-day trial, no card. - [Google Search Console MCP server for AI agents](https://siteline.tools/mcp): A hosted Google Search Console MCP server for Cursor, Claude and ChatGPT. Query GSC clicks, queries and pages, plus cookieless analytics. Read-only. - [Privacy posture: cookieless by design](https://siteline.tools/trust): How SiteLine web analytics actually works: cookieless, no fingerprint theatre, hostname allowlists, and retention that matches the product. - [About SiteLine and who builds it](https://siteline.tools/about): Chris Richards builds SiteLine at Aglet Technologies: cookieless analytics, a Search Console import, and read-only MCP for AI agents. ## Docs - [SiteLine web analytics documentation](https://siteline.tools/docs): Cookieless pageviews, custom events, goals and funnels — bundled with your SiteLine subscription alongside Search Console. - [Install the analytics script tag](https://siteline.tools/docs/script): Add a single deferred script tag. Pageviews start on load; outbound links and file downloads stay off unless you opt in. - [React SDK for cookieless analytics](https://siteline.tools/docs/react): Install @siteline.tools/react for idiomatic TypeScript tracking in React apps. It wraps the shared @siteline.tools/tracker core. - [Custom events: track product actions](https://siteline.tools/docs/events): Named product actions count as billable events (1:1 with pageviews). Properties are capped to keep cardinality bounded. - [Goals and funnels in web analytics](https://siteline.tools/docs/goals): Define conversions in the product UI from paths and event names you already send. Goals do not emit extra billable events. - [First-party proxy for the tracker](https://siteline.tools/docs/proxy): Serve the script and collect endpoint from your own domain so more events survive ad blockers. You configure the reverse proxy; SiteLine has no managed CNAME. - [Event quotas and plans explained](https://siteline.tools/docs/billing): One subscription covers Search Console and web analytics. Event quotas reset on your Stripe billing-cycle anniversary. - [Privacy model: cookieless by default](https://siteline.tools/docs/privacy): SiteLine web analytics is cookieless by default: no first-party analytics cookie, no cross-site identity, and no consent banner for this tracking alone. ## Free tools - [Cookie banner traffic loss calculator](https://siteline.tools/tools/cookie-banner-traffic-loss-calculator): Estimate how many visitors consent-gated analytics miss. EU, UK and AU decline presets: visitors × decline rate × share gated. Free, in-browser. - [GSC opportunity analyzer](https://siteline.tools/tools/gsc-opportunity-analyzer): Upload a Search Console Performance CSV to find striking-distance queries, cannibalization, CTR-vs-position gaps and page decay. Free, in your browser. - [GSC regex builder for Search Console](https://siteline.tools/tools/gsc-regex-builder): Build and test Search Console regex filters in your browser. Templates for brand, questions, folders and exclusions, plus RE2 limits explained. - [UTM builder and checker](https://siteline.tools/tools/utm-builder): Build and validate UTM links in your browser: source, medium, campaign, content, term, a URL checker and shareable presets. Free, client-side, no login. - [GSC data expiry calculator](https://siteline.tools/tools/gsc-data-expiry-calculator): Enter a date to see when Google Search Console deletes that day's data under its 16-month limit, and which months expire next. Free, in your browser. ## Guides: Alternatives & comparisons - [SEOGets alternatives: 7 tools compared](https://siteline.tools/guides/seogets-alternatives): Seven SEOGets alternatives for Search Console work: SiteLine, the GSC API, BigQuery export, Looker Studio, Sheets, SEOTesting and Ahrefs. Checked Oct 2026. - [Cookieless analytics vs GA4: how they differ](https://siteline.tools/guides/cookieless-analytics-vs-ga4): GA4 identifies visitors with a first-party cookie. SiteLine uses a daily SHA-256 of truncated IP, user agent and rotating salt. That is the difference. - [GA4 alternatives: which one fits your situation](https://siteline.tools/guides/ga4-alternatives): Leaving GA4? Pick the job first: cookieless page analytics, Search Console history or product analytics. Then choose a tool, or stay on GA4. - [GA4 and the cookie banner: what changes](https://siteline.tools/guides/ga4-cookie-banner): GA4 needs a banner because it sets analytics cookies. Cookieless tracking removes that trigger for this script — not your privacy notice, or other pixels. - [GA4 for SaaS: the wrong tool for the site](https://siteline.tools/guides/ga4-for-saas): SaaS teams put GA4 on the app because it is already on the blog. Cookie identity, event cardinality and Ads coupling fight product questions. - [GA4 sampling and thresholds explained](https://siteline.tools/guides/ga4-sampling-and-thresholds): GA4 Explorations sample; Google signals threshold small slices; Search Console caps 25k rows/day. Unsampled on-site data still needs an honest identity. - [Open-source web analytics and self-hosting](https://siteline.tools/guides/open-source-web-analytics): Matomo, Umami and Plausible CE are real options. Self-host is ops, not privacy. SiteLine is hosted cookieless analytics plus Search Console — not a distro. - [Privacy-first analytics comparison for 2026](https://siteline.tools/guides/privacy-first-analytics-comparison): Compare Plausible, Fathom, Simple Analytics, GA4 and SiteLine on identity lifetime, Search Console history, event caps and agent access. A buying test. - [SiteLine vs Google Analytics: an honest grid](https://siteline.tools/guides/siteline-vs-google-analytics): SiteLine is cookieless page analytics plus Search Console. GA4 is cookies, Ads, Explorations and a free licence. Side by side, with what we won’t ship. - [Why teams leave GA4: consent, not a manifesto](https://siteline.tools/guides/why-teams-leave-ga4): Teams leave GA4 because consent-gated cookies make weekly numbers unusable. The UI, sampling and Ads coupling add cost. Privacy is rarely the real trigger. ## Guides: Comparisons - [Plausible vs Umami (2026): price and hosting](https://siteline.tools/guides/plausible-vs-umami): Plausible vs Umami on cloud pricing, free tiers, self-hosting licence, data retention, Search Console, API and MCP access. Checked 10 Oct 2026. - [SiteLine vs SEOGets: GSC history and price](https://siteline.tools/guides/siteline-vs-seogets): SiteLine vs SEOGets on Search Console history past 16 months, row limits, MCP, GA4, agency reporting and price. Where each wins, checked 8 Oct 2026. - [BigQuery vs hosted Search Console archive](https://siteline.tools/guides/bigquery-vs-hosted-search-console): BigQuery bulk export is forward-only. A hosted Search Console archive backfills Google's live window, keeps history while you subscribe, and adds UI/MCP. - [Search Console API vs MCP](https://siteline.tools/guides/search-console-api-vs-mcp): The Search Console API is how software fetches rows. MCP is how an agent asks questions. SiteLine fills a warehouse via the API, then serves it over MCP. - [Fathom vs Simple Analytics](https://siteline.tools/guides/fathom-vs-simple-analytics): Fathom and Simple Analytics are hosted cookieless traffic tools. Compare dashboards, site limits and blocker bypass. Search Console history is another job. - [Matomo vs GA4 with Search Console](https://siteline.tools/guides/matomo-vs-ga4): Matomo vs GA4 comparisons skip Search Console. Neither keeps GSC past 16 months or beyond the 1,000-row UI. Here is the comparison with both ledgers. - [Plausible vs Fathom](https://siteline.tools/guides/plausible-vs-fathom): Plausible and Fathom are both cookieless traffic analytics. The split is open source and self-hosting versus hosted polish, and what you need from GSC. - [Plausible vs Matomo (2026): price, privacy](https://siteline.tools/guides/plausible-vs-matomo): Plausible vs Matomo compared for 2026: pricing, cookies and consent, self-hosting effort, page overlay, heatmaps and Search Console, with a clear pick. - [SiteLine vs Fathom: archive or overlay](https://siteline.tools/guides/siteline-vs-fathom): Fathom shows Search Console in its dashboard for the window Google still holds. SiteLine copies it daily and keeps it. Prices, privacy and limits compared. - [SiteLine vs Matomo: hosted or self-run](https://siteline.tools/guides/siteline-vs-matomo): Matomo is a full analytics suite you can run yourself for free. SiteLine is narrower and hosted: cookieless traffic plus a stored Search Console copy. - [SiteLine vs Mixpanel](https://siteline.tools/guides/siteline-vs-mixpanel): Mixpanel is event analytics for identified users. SiteLine is cookieless website analytics plus a Search Console import. Pick the job, not the logo. - [SiteLine vs Plausible](https://siteline.tools/guides/siteline-vs-plausible): Plausible is cookieless traffic analytics. SiteLine adds a durable Search Console import: 16-month backfill, 25k rows a day, kept while you subscribe. - [SiteLine vs PostHog](https://siteline.tools/guides/siteline-vs-posthog): PostHog is product analytics: profiles, replay, flags. SiteLine is cookieless site analytics plus Search Console history. Different jobs, not a bake-off. - [SiteLine vs Simple Analytics](https://siteline.tools/guides/siteline-vs-simple-analytics): Simple Analytics is cookieless traffic reporting. SiteLine covers that job and stores Google Search Console history past 16 months, at 25,000 rows per day. - [SiteLine vs Umami: hosted or self-hosted](https://siteline.tools/guides/siteline-vs-umami): Umami is lightweight, often self-hosted web analytics. SiteLine is hosted cookieless analytics plus a Search Console import kept while you subscribe. ## Guides: Search Console - [Search Console regex examples](https://siteline.tools/guides/search-console-regex-examples): Copy-paste Google Search Console regex for brand, non-brand, questions, long-tail, comparisons, folders and URL parameters. All RE2-safe. - [Looker Studio Search Console limits](https://siteline.tools/guides/looker-studio-search-console-limits): Looker Studio's Search Console connector is a live chart, not a warehouse. ~16-month retention, 12-hour freshness, and what to do when YoY goes blank. - [Best Search Console history tools](https://siteline.tools/guides/best-google-search-console-history-tools): Compare ways to keep Search Console history past Google's 16-month window: Looker Studio, CSV, DIY API, BigQuery export, and hosted archives. - [Connect Google Search Console to SiteLine](https://siteline.tools/guides/connect-google-search-console-to-siteline): Step-by-step: register, grant webmasters.readonly, wait for the 16-month backfill, and confirm import status. What SiteLine copies on connect. - [Year-over-year in Search Console](https://siteline.tools/guides/year-over-year-search-console): Google's Performance report keeps about 16 months, so month 17 YoY is empty. How to compare honestly, avoid fake zeros, and keep a prior year. - [Google Search Console MCP: what it is](https://siteline.tools/guides/google-search-console-mcp): A Google Search Console MCP server lets an AI agent query clicks, queries and pages. Local or hosted options, what to ask it, and how SiteLine differs. - [Agency Search Console reporting](https://siteline.tools/guides/agency-search-console-reporting): Agency Search Console reporting that holds up: site totals for headlines, 25k rows/day for the tail, MCP for agents, unlimited sites, no averaged CTR. - [Combine Search Console with cookieless analytics](https://siteline.tools/guides/combine-gsc-with-cookieless-analytics): Read Search Console clicks against cookieless pageviews: landing pages, a daily visitor hash, two-day lag, and why query totals never equal the site total. - [Organic traffic is not Search Console](https://siteline.tools/guides/organic-traffic-vs-search-console): Organic sessions and Search Console clicks are different events. Anonymised queries, Google surfaces, consent, and a two-day lag explain most of the gap. - [Export more than 1,000 rows from Search Console](https://siteline.tools/guides/search-console-1000-row-limit): Search Console exports stop at 1,000 rows. Raise the API rowLimit to 25,000, use BigQuery bulk export or a hosted archive. Why rows never sum to the total. - [Search Console 16-month limit: when data expires](https://siteline.tools/guides/search-console-16-month-limit): Search Console keeps Performance data for 16 months, then each day is deleted from the UI and API. When a day expires, and how to copy it first. - [Search Console clicks are not analytics sessions](https://siteline.tools/guides/search-console-clicks-vs-analytics-sessions): A Search Console click is a SERP click. An analytics session is a visit. They will not match, and averaging position or CTR will not explain the whole gap. - [Search Console is not enough](https://siteline.tools/guides/search-console-is-not-enough): Search Console is a SERP ledger, not bounce rate, goals, or 17-month history. Pair it with cookieless analytics and stop treating GSC as a full report. - [Search Console plus on-site analytics](https://siteline.tools/guides/search-console-plus-on-site-analytics): Search Console is the SERP ledger. On-site analytics is what happened after the click. SiteLine keeps both, without averaging CTR or summing query rows. ## Guides: Privacy-first analytics - [UTM tracking without cookies](https://siteline.tools/guides/utm-tracking-without-cookies): UTM tags are read from the landing URL, so cookieless analytics records campaigns without a cookie or banner. What you keep, what you lose, naming rules. - [How much traffic does a cookie banner cost?](https://siteline.tools/guides/cookie-banner-traffic-loss): Estimate the visitors analytics never sees when a consent banner blocks GA4. Simple maths, EU, UK and AU ranges, and when cookieless removes the banner. - [Analytics and the Australian Privacy Act](https://siteline.tools/guides/analytics-and-the-australian-privacy-act): The Australian Privacy Act 1988 is not GDPR with extra vowels. How SiteLine maps to APPs, hashed IPs, overseas disclosure, and claims we will not make. - [Consent-free analytics](https://siteline.tools/guides/consent-free-analytics): Consent-free means this tracker sets no analytics cookie that ePrivacy treats as a banner. It is not GDPR-free, notice-free, or a pass for other pixels. - [Cookieless tracking explained](https://siteline.tools/guides/cookieless-tracking-explained): SiteLine sets no first-party analytics cookie. Visitors are a daily hash of truncated IP and user agent: what is stored, omitted, and sent to our servers. - [Do I need a cookie banner for analytics?](https://siteline.tools/guides/do-i-need-a-cookie-banner-for-analytics): A cookie banner is for cookies, not the word analytics. When a cookieless tracker removes the reason for one, and when the rest of the stack does not. - [EU analytics after Schrems](https://siteline.tools/guides/eu-analytics-after-schrems): Schrems II made US transfers a documented problem, not a ban on analytics. SiteLine is cookieless, not EU-only: events reach Aglet, Stripe and Cloudflare. - [First-party analytics proxy](https://siteline.tools/guides/first-party-analytics-proxy): Proxy SiteLine’s script and collect path from your host so more events survive blockers. Configure nginx, Caddy, Cloudflare or Vercel. No managed CNAME. - [GDPR analytics without a consent banner](https://siteline.tools/guides/gdpr-analytics-without-a-consent-banner): ePrivacy cares about cookies; GDPR cares about personal data. How SiteLine’s cookieless tracker changes the banner question, and what it does not legalise. - [IP anonymization vs cookieless analytics](https://siteline.tools/guides/ip-anonymization-vs-cookieless-analytics): GA IP anonymization still set a cookie. SiteLine truncates IPv4 /24 and IPv6 /48, hashes with a daily salt, and does not store the raw IP. - [Privacy-first analytics for agencies](https://siteline.tools/guides/privacy-first-analytics-for-agencies): Agency reporting without installing GA4 cookies on every client site. What SiteLine stores, what belongs in a proposal, and claims you should not make. - [Privacy-first analytics for SaaS](https://siteline.tools/guides/privacy-first-analytics-for-saas): SaaS can measure usage without a first-party analytics cookie. How SiteLine hashes visitors, what still hits our servers, and what belongs in the notice. ## Guides: How-to - [How to query Search Console with MCP](https://siteline.tools/guides/how-to-query-search-console-with-mcp): Prompts and tool calls for querying Google Search Console through SiteLine MCP: the call order, what each tool returns, and the mistakes to avoid. - [Combine Search Console and on-site analytics](https://siteline.tools/guides/how-to-combine-gsc-and-on-site-analytics): Use Search Console for queries and clicks, SiteLine analytics for what happened after landing. Same subscription, same domain list, two systems. - [How to proxy the SiteLine script](https://siteline.tools/guides/how-to-proxy-the-siteline-script): Reverse-proxy /js/script.js and POST /api/analytics/event on your domain. SiteLine does not manage CNAMEs. Ad-blocker loss drops, but it does not vanish. - [How to read SiteLine analytics funnels](https://siteline.tools/guides/how-to-read-analytics-funnels): Build a funnel from exact path, path contains, or event name steps. SiteLine shows visitors per step as a share of step one — derived, not extra events. - [How to set up SiteLine analytics goals](https://siteline.tools/guides/how-to-set-up-analytics-goals): Create goals in the dashboard from exact path, path contains, or event name. They derive from traffic you already send and add no billable events. - [How to track custom events in SiteLine](https://siteline.tools/guides/how-to-track-custom-events): Send named custom events with at most 10 properties. They are billable 1:1 with pageviews. Goals can match the event name later without a second payload. - [Install SiteLine on React](https://siteline.tools/guides/install-siteline-on-react): Mount @siteline.tools/react once at the app root with an absolute collect URL. Call track() for named events; App Router still needs a manual pageview. - [Install the SiteLine tracker](https://siteline.tools/guides/install-siteline-tracker): Add one deferred script tag with your public site id and an absolute collect URL. Pageviews start on load; cookies, extra events and banners stay off. ## Guides: Problem pages - [Agency client reporting, minus the bloat](https://siteline.tools/guides/agency-client-reporting): One SiteLine user per subscription, unlimited sites, Search Console plus cookieless analytics. Multi-member teams exist in code but stay off by default. - [Analytics blocked by ad blockers](https://siteline.tools/guides/analytics-blocked-by-adblockers): Filter lists cut third-party analytics scripts. Proxy the SiteLine script and collect path first-party to reduce the loss. It does not vanish. - [Why GA4 is confusing, and what to do](https://siteline.tools/guides/ga4-is-confusing): GA4 piles taxonomy, identity, and modeled conversions into one UI. SiteLine is cookieless pageviews, named events, dashboard goals, and Search Console. - [Unique visitors without cookies](https://siteline.tools/guides/unique-visitors-without-cookies): SiteLine unique visitors are a daily hash of truncated IP, user agent, and a rotating salt. No analytics cookie, no cross-day person, no GA4-style user id. - [Why analytics numbers don't match](https://siteline.tools/guides/why-analytics-numbers-dont-match): SiteLine will not match GA4, GSC clicks or ads. Daily hashes, blockers, bot filters, lag and different event definitions pull the totals apart on purpose. ## Guides: AI agents - [Gemini CLI Search Console MCP](https://siteline.tools/guides/gemini-cli-search-console-mcp): Connect Search Console history and cookieless analytics to Gemini CLI with gemini mcp add, an HTTP bearer token, and a GEMINI.md that keeps totals honest. - [Claude Code Search Console MCP setup](https://siteline.tools/guides/claude-code-search-console-mcp): Add SiteLine's Search Console and analytics MCP servers to Claude Code with claude mcp add, a team-scoped bearer token, and a safe query order. - [ChatGPT Search Console MCP connector](https://siteline.tools/guides/chatgpt-search-console-mcp): Connect ChatGPT to a Search Console MCP with SiteLine’s OAuth connector. Query clicks and pages in chat. Never paste a bearer token into the transcript. - [Claude Desktop Search Console MCP](https://siteline.tools/guides/claude-desktop-search-console-mcp): Claude Desktop can use SiteLine’s Search Console MCP as an OAuth connector or, in a local config, with a bearer token. Both are read-only. - [Claude connector for Search Console and analytics](https://siteline.tools/guides/mcp-search-console-analytics-for-claude): Add SiteLine to Claude.ai as a custom connector: the OAuth approval, adding both servers, revoking access, and when to move to Claude Code. - [MCP for Search Console and analytics in Cursor](https://siteline.tools/guides/mcp-search-console-analytics-for-cursor): Point Cursor at SiteLine’s two HTTP MCP servers with a team-scoped bearer token. Query Search Console and analytics from the agent that edits your repo. - [SEO analytics for AI agents](https://siteline.tools/guides/seo-analytics-for-ai-agents): Coding agents cannot log into Search Console or GA4. SiteLine exposes Search Console and cookieless analytics over MCP so agents can query real numbers. - [SiteLine MCP setup for AI coding agents](https://siteline.tools/guides/siteline-mcp-setup-for-agents): Connect Cursor, Claude Code, ChatGPT and other agents to SiteLine MCP: OAuth for connectors, a team bearer token for IDEs, two read-only servers. - [Why GA4 is a bad fit for AI agent workflows](https://siteline.tools/guides/why-ga4-is-a-bad-fit-for-agent-workflows): GA4 has no agent interface. Explorations are not tool calls, BigQuery is a pipeline, and consent holes look like traffic crashes. ## Optional - [Privacy policy for siteline.tools](https://siteline.tools/privacy): How Aglet Technologies collects, uses and protects information in SiteLine: cookieless analytics, Search Console data and data sent to AI agents. - [Terms of service for siteline.tools](https://siteline.tools/terms): The terms for using SiteLine, operated by Aglet Technologies: the trial, billing on each plan, acceptable use, Google data and liability.