Agents Index

Organiq GEO

OnlineNew

Search Console and GA4 analysis (read-only Google): queries, decay, cannibalization, AI traffic.

Visit publisherConnectJSON

What it can do: 51 tools

  • get_capabilities read-onlyReturns a factual overview of this connector: what data it holds (Google Search Console synced daily into Organiq, plus GA4 referral sessions from AI assistants), the list of tools with when to use each, units, default p
  • get_ctr_benchmark read-onlyReturns the generic organic click-through-rate curve by Google position (1–20, fraction 0–1) used by score_opportunities and find_page_poaching_opportunities as the fallback when a property lacks its own volume, optional
  • check_connection read-onlyReports whether this request is authenticated and, if so, which Organiq account it uses (name, plan, how it authenticated), how many Search Console properties are available with their data coverage, and what is missing (
  • check_ai_access read-onlyChecks 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 domain's robots.txt for 8 AI robots (GPTBot, OAI-SearchBot, ClaudeBot, Perplexit
  • list_sites read-onlyLists the Search Console properties synced for the signed-in account: id, siteUrl (Search Console format), displayName, tags, branded_terms (used by the brand filter), whether GA4/Bing are mapped and the data coverage (d
  • get_site_summary read-onlyTotals of clicks, impressions, CTR and average position for one property over the period, with the comparison period and the change (absolute, Pct as fraction, ctrPoints in percentage points, position difference where ne
  • query_top_queries read-onlySearch queries of one property over the period, aggregated and sorted. Use for "what people search to find us", growth/decline lists and ranking changes. Each row has clicks, impressions, ctr, position for the period and
  • query_top_pages read-onlyPages (URLs) of one property over the period, aggregated and sorted. Use for best/worst pages and pages that gained or lost clicks. Each row has clicks, impressions, ctr, position for the period and, with a comparison, p
  • query_countries read-onlyCountries (ISO-3166-1 alpha-3, lowercase, e.g. bra) of one property over the period. Each row has clicks, impressions, ctr, position for the period and, with a comparison, prevClicks/prevImpressions/prevCtr/prevPosition
  • query_devices read-onlyDevices (MOBILE, DESKTOP, TABLET) of one property over the period. Each row has clicks, impressions, ctr, position for the period and, with a comparison, prevClicks/prevImpressions/prevCtr/prevPosition plus clicksChange/
  • get_timeseries read-onlyClicks, impressions, CTR and position per day, week (Monday as key) or month (yyyy-mm) over the period, with filters. Use for trend, seasonality and to locate the date of a drop. Days without data are omitted. / Série te
  • get_breakdown read-onlySplits 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 impressions and clicks per band, plus queryCount. Position of each query = impres
  • get_annotations read-onlyEvents annotated in the period for the property and globally: deploys, content changes, manual notes and Google algorithm updates (category "algo_update"). Use to correlate drops or gains with causes. Default: last 90 da
  • get_ai_traffic read-onlyReferral sessions from AI assistants (chatgpt.com, perplexity.ai, gemini, copilot, claude…) according to GA4 (dimension ai_source): per source (sessions, activeUsers, engagedSessions, keyEvents) for the period and the co
  • get_ctr_curve read-onlyThe property's real CTR by position (bucket = round(position), 1–20, impression-weighted) compared with the generic benchmark (31.7% at position 1 … 18.6% at 3 … 2.0% at 10). deltaPoints in percentage points (negative =
  • find_decaying_content read-onlyPages (or queries) that lost clicks between a BASELINE and the RECENT period. Recent = days/startDate/endDate; baseline = compare (previous = window before, year = one year earlier) or explicit comparisonStartDate/compar
  • analyze_cannibalization read-onlyQueries where 2+ pages of the property compete for the same search in the period. Per cluster: totals, Shannon entropy of impressions across pages (bits; higher = more even split = worse; level high >= 1.5, medium >= 1.0
  • score_opportunities read-onlyQueries between minPosition and maxPosition whose CTR is below the expected CTR for their position. expectedCtr comes from the property's own curve (ctrSource "own", when the bucket has volume) or from the benchmark; ctr
  • find_page_poaching_opportunities read-onlyQueries just outside the top (default positions 4–20) with the estimated click gain if they reached the CTR of the target position (default 3 → 18.6% benchmark, or the property's own CTR at that position when it has volu
  • get_ranking_changes read-onlyClassifies each query (or page) of the property by what happened between the comparison period and the current one: new (appeared), lost (disappeared), improved (position better by >= minPositionChange), declined (worse)
  • get_position_distribution read-onlyHow 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, clicks, impressions and impression share per band. Each query's position for a day
  • get_branded_performance read-onlyDaily series of branded and non-branded traffic (clicks, impressions, ctr, position per group, plus brandedClickShare) with totals for the period and the comparison, using the property's branded_terms. brandedTermsConfig
  • breakdown_by_path read-onlyGroups the property's pages by host (subdomain) and by the first `depth` path segments (1–4), e.g. "example.com/blog/*": pages per group, clicks, impressions, ctr, position, clickShare, comparison (prevClicks, clicksChan
  • get_query_performance read-onlyDaily performance of ONE search query on the property (optionally on one page). Returns totals for the period and the comparison with change, the daily (or weekly) series and the top counterparts (pages ranking for the q
  • get_page_performance read-onlyDaily performance of ONE page (URL) of the property. Returns totals for the period and the comparison with change, the daily (or weekly) series and the top counterparts (queries bringing the page traffic). Exact match (c
  • get_longtail_clusters read-onlySplits 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 / 4+; loose: 1–3 / 4–5 / 6+), with queries, clicks, impressions, ctr, position, sha
  • analyze_sampling_impact read-onlyHow much of the property's traffic Search Console hides from the query/page rows because of anonymization: exact totals per day (no dimensions) minus the sum of the query × page rows = hidden clicks/impressions, with hid
  • analyze_query_shapes read-onlyClassifies the period's queries into shapes and aggregates each: branded, question, comparison, transactional, local, longtail (5+ words), head (<= 2 words), other, with queries, clicks, impressions, ctr, position, share
  • get_query_shape_trend read-onlyWeekly share of impressions (or clicks) per query shape (branded, question, comparison, transactional, local, longtail, head, other) and of "AI-style" queries over the period (default 12 weeks), with sharePointsChange =
  • detect_anomalies read-onlyFlags days in the period whose clicks (or impressions, ctr, position) deviate from what the same weekday did in the previous baselineWeeks weeks (default 8): expected = median of those weekdays, scale = scaled MAD, zScor
  • detect_change_points read-onlyFinds the dates where the property's clicks (or impressions) moved to a new sustained level — a step up or down that holds for several weeks, as after a Google update, a migration or a content launch — using a robust CUS
  • forecast_traffic read-onlyProjects the property's clicks (or impressions) for the next `horizon` weeks (default 12) or months (default 6) from the history in the period (default 364 days): aggregates the daily series, estimates a multiplicative s
  • get_core_web_vitals read-onlyField Core Web Vitals of the property's origin (or a URL) from the Chrome UX Report history, weekly, per form factor (PHONE, DESKTOP): latest p75 of LCP, INP, CLS, FCP, TTFB with rating (good / needs_improvement / poor b
  • get_indexing_tracker read-onlyIndexing status of the property's inspected URLs (Search Console URL Inspection results stored by Organiq, plus the tracked_urls watch list): healthScore 0–100 (70 % indexed share + 30 % fresh-crawl share), indexed / not
  • list_url_inspections read-onlyLatest stored URL Inspection result per URL of the property: verdict, coverageState, indexingState, robotsState, pageFetchState, Google vs user canonical, lastCrawlTime, crawledAs, mobileVerdict, checkedAt, whether the U
  • request_indexingQueues up to 100 URLs of one property for submission to search engines, by two routes: IndexNow (Bing, Yandex, Naver, Seznam, Yep; needs the IndexNow key set for the property) and Google through the Indexing API (optiona
  • get_indexing_requests read-onlyLists the indexing requests made for the property (from request_indexing, the panel or the sitemap job), newest first: url, engine (indexnow / google), action, source (manual / sitemap / agent), status (queued, submitted
  • list_sitemaps read-onlySitemaps known to Search Console for the property: path, lastSubmitted, lastDownloaded, isPending, errors, warnings and contents per type (web, image, video, news: submitted URL counts). Search Console no longer reports
  • get_bing_performance read-onlyOrganic performance on Bing (Bing Webmaster Tools, weekly data) for the property: view=traffic gives weekly clicks/impressions with totals and change vs the previous same-length window; view=queries or view=pages gives t
  • get_genai_impressions read-onlyDaily impressions of the property in Google's generative AI features (AI Overviews and AI Mode) from the Search Console "Generative AI features" report, imported into Organiq (this report is not in the Search Analytics A

…and 11 more.

Connect it

Claude Code
claude mcp add --transport http organiq-geo https://organiqgeo.com/mcp
Claude.ai / ChatGPT
Settings → Connectors → Add custom connector
URL: https://organiqgeo.com/mcp
Cursor (~/.cursor/mcp.json)
{
  "mcpServers": {
    "organiq-geo": {
      "url": "https://organiqgeo.com/mcp"
    }
  }
}
VS Code (.vscode/mcp.json)
{
  "servers": {
    "organiq-geo": {
      "type": "http",
      "url": "https://organiqgeo.com/mcp"
    }
  }
}

Questions

What does Organiq GEO do?

Search Console and GA4 analysis (read-only Google): queries, decay, cannibalization, AI traffic. It exposes 51 tools to AI assistants.

What tools does Organiq GEO provide?

51 tools, including get_capabilities, get_ctr_benchmark, check_connection, check_ai_access, list_sites, get_site_summary, query_top_queries, query_top_pages, query_countries, query_devices, get_timeseries, get_breakdown….

How do I connect Organiq GEO to Claude, ChatGPT or Cursor?

Add the remote MCP endpoint https://organiqgeo.com/mcp as a custom connector or MCP server. Copy-paste setup is on this page.

Does Organiq GEO require an account or API key?

No sign-in was needed to list its tools. Individual tools may still need an account or API key.

Is Organiq GEO online?

As of 2026-11-19 our probe found it online. It answered 100% of our last 3 checks.

Who publishes Organiq GEO?

organiqgeo.com. The official MCP Registry verified that the publisher controls this domain before accepting the listing.

Similar in Web Search & Scraping