Search Console limits, a Google Search Console MCP, and pairing rankings with cookieless on-site analytics.
- 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 — 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 — 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 — 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 — 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 server — SiteLine's Google Search Console MCP server has ten read-only tools, including movers, striking distance and queries for a page. Setup for Cursor and Claude.
- 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 — 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 — Organic sessions and Search Console clicks are different events. Anonymised queries, Google surfaces, consent, and a two-day lag explain most of the gap.
- Search Console 1,000-row limit — Search Console caps the Performance export at 1,000 rows. The API defaults to 1,000, allows 25,000 a request, and stops a day at 50,000.
- Search Console 16-month limit: when data expires — 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 — 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 — 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 — 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.