Install the tracker, query Search Console over MCP, read funnels, proxy the script, and combine GSC.
- 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 — 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 — 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 — 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 — 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 — 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 — 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 — 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.