Categories › Business & Finance › Market data, stocks & crypto
Search Console and GA4 analysis (read-only Google): queries, decay, cannibalization, AI traffic.
Remote server: your requests and data go to organiqgeo.com. Claude Code: claude mcp add --transport http organiq-geo https://organiqgeo.com/mcp · Claude app: Settings → Connectors → Add custom connector.
The tools this server listed when we connected to it, in its own words.
get_capabilities — Returns a factual overview of this connector: what data it holds (Google Search Console synced daily into Organiq, plus GA4 referral sessionget_ctr_benchmark — Returns the generic organic click-through-rate curve by Google position (1–20, fraction 0–1) used by score_opportunities and find_page_poachcheck_connection — Reports whether this request is authenticated and, if so, which Organiq account it uses (name, plan, how it authenticated), how many Search check_ai_access — Checks whether AI crawlers can read one public web page and whether the page is set up to be cited. For the exact URL path it evaluates the list_sites — Lists the Search Console properties synced for the signed-in account: id, siteUrl (Search Console format), displayName, tags, branded_terms get_site_summary — Totals of clicks, impressions, CTR and average position for one property over the period, with the comparison period and the change (absolutquery_top_queries — Search queries of one property over the period, aggregated and sorted. Use for "what people search to find us", growth/decline lists and ranquery_top_pages — Pages (URLs) of one property over the period, aggregated and sorted. Use for best/worst pages and pages that gained or lost clicks. Each rowquery_countries — Countries (ISO-3166-1 alpha-3, lowercase, e.g. bra) of one property over the period. Each row has clicks, impressions, ctr, position for thequery_devices — Devices (MOBILE, DESKTOP, TABLET) of one property over the period. Each row has clicks, impressions, ctr, position for the period and, with get_timeseries — Clicks, impressions, CTR and position per day, week (Monday as key) or month (yyyy-mm) over the period, with filters. Use for trend, seasonaget_breakdown — Splits the period's traffic into branded/nonBranded (by the property's branded_terms) and into position bands (1-3, 4-10, 11-20, 21+) with iget_annotations — Events annotated in the period for the property and globally: deploys, content changes, manual notes and Google algorithm updates (category get_ai_traffic — Referral sessions from AI assistants (chatgpt.com, perplexity.ai, gemini, copilot, claude…) according to GA4 (dimension ai_source): per sourget_ctr_curve — The property's real CTR by position (bucket = round(position), 1–20, impression-weighted) compared with the generic benchmark (31.7% at posifind_decaying_content — Pages (or queries) that lost clicks between a BASELINE and the RECENT period. Recent = days/startDate/endDate; baseline = compare (previous analyze_cannibalization — Queries where 2+ pages of the property compete for the same search in the period. Per cluster: totals, Shannon entropy of impressions acrossscore_opportunities — Queries between minPosition and maxPosition whose CTR is below the expected CTR for their position. expectedCtr comes from the property's owfind_page_poaching_opportunities — Queries just outside the top (default positions 4–20) with the estimated click gain if they reached the CTR of the target position (default get_ranking_changes — Classifies each query (or page) of the property by what happened between the comparison period and the current one: new (appeared), lost (diget_position_distribution — How the property's queries spread across position bands 1-3, 4-10, 11-20 and 21+ for each day (or week) of the period: number of queries, clget_branded_performance — Daily series of branded and non-branded traffic (clicks, impressions, ctr, position per group, plus brandedClickShare) with totals for the pbreakdown_by_path — Groups the property's pages by host (subdomain) and by the first `depth` path segments (1–4), e.g. "example.com/blog/*": pages per group, clget_query_performance — Daily performance of ONE search query on the property (optionally on one page). Returns totals for the period and the comparison with changeget_page_performance — Daily performance of ONE page (URL) of the property. Returns totals for the period and the comparison with change, the daily (or weekly) serget_longtail_clusters — Splits the period's queries into head, chunky middle and long tail by word count (preset balanced: 1–2 / 3–4 / 5+ words; strict: 1 / 2–3 / 4analyze_sampling_impact — How much of the property's traffic Search Console hides from the query/page rows because of anonymization: exact totals per day (no dimensioanalyze_query_shapes — Classifies the period's queries into shapes and aggregates each: branded, question, comparison, transactional, local, longtail (5+ words), hget_query_shape_trend — Weekly share of impressions (or clicks) per query shape (branded, question, comparison, transactional, local, longtail, head, other) and of detect_anomalies — Flags days in the period whose clicks (or impressions, ctr, position) deviate from what the same weekday did in the previous baselineWeeks wdetect_change_points — Finds the dates where the property's clicks (or impressions) moved to a new sustained level — a step up or down that holds for several weeksforecast_traffic — Projects the property's clicks (or impressions) for the next `horizon` weeks (default 12) or months (default 6) from the history in the periget_core_web_vitals — Field Core Web Vitals of the property's origin (or a URL) from the Chrome UX Report history, weekly, per form factor (PHONE, DESKTOP): latesget_indexing_tracker — Indexing status of the property's inspected URLs (Search Console URL Inspection results stored by Organiq, plus the tracked_urls watch list)list_url_inspections — Latest stored URL Inspection result per URL of the property: verdict, coverageState, indexingState, robotsState, pageFetchState, Google vs urequest_indexing — Queues up to 100 URLs of one property for submission to search engines, by two routes: IndexNow (Bing, Yandex, Naver, Seznam, Yep; needs theget_indexing_requests — Lists the indexing requests made for the property (from request_indexing, the panel or the sitemap job), newest first: url, engine (indexnowlist_sitemaps — Sitemaps known to Search Console for the property: path, lastSubmitted, lastDownloaded, isPending, errors, warnings and contents per type (wget_bing_performance — Organic performance on Bing (Bing Webmaster Tools, weekly data) for the property: view=traffic gives weekly clicks/impressions with totals aget_genai_impressions — Daily impressions of the property in Google's generative AI features (AI Overviews and AI Mode) from the Search Console "Generative AI featuNot tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.