← CitunaCONTENT HISTORY

Update to Cituna

Snapshot Nov 12, 2026 · 00:09 UTC · version 0.2.2

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save Cituna and check future changes in Following.

Up to 3 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Use Cituna's connected Google Search Console properties to analyze queries, pages, clicks, impressions, ranking opportunities, zero-click pages, intent, coverage and AI-style searches.",
  "included_files": [],
  "name": "search-console",
  "skill_md_contents": "---\r\nname: search-console\r\ndescription: Use Cituna's connected Google Search Console properties to analyze queries, pages, clicks, impressions, ranking opportunities, zero-click pages, intent, coverage and AI-style searches.\r\n---\r\n\r\n# Analyze Google Search Console with Cituna\r\n\r\nRead [connection and evidence rules](../../references/connection-and-evidence.md).\r\n\r\n## Connection and scope\r\n\r\nCall `gsc_status` and resolve the requested property from all connected accounts.\r\nIf disconnected, guide the user to https://cituna.com/integrations to connect\r\nGoogle and verify the property, then recheck. Do not ask for Google credentials\r\nor claim this MCP can connect, disconnect or verify a Google property directly.\r\n\r\nSelect the report that directly answers the request:\r\n\r\n| Request | Tool |\r\n| --- | --- |\r\n| Traffic summary, top queries/pages, country/device splits | `gsc_overview` |\r\n| Specific dimensions, filters, dates or pagination | `gsc_query` |\r\n| Queries near page one worth improving | `gsc_striking_distance` |\r\n| Pages with impressions and few or no clicks | `gsc_zero_click_pages` |\r\n| Brand, competitor, commercial and other query intent | `gsc_query_mix` |\r\n| Sitemap pages without observed impressions | `gsc_coverage_gap` |\r\n| Multiple owned pages competing for the same query | `gsc_cannibalisation` |\r\n| Queries with conversational or AI-style wording | `gsc_ai_searches` |\r\n\r\n## Query and interpret correctly\r\n\r\n- Use a bare `domain`, or the exact accessible `siteUrl` where supported. Observe\r\n  each tool's schema: overview supports 1–90 days; several analysis tools and\r\n  raw queries support 1–480 days. Never assume the same bounds for every tool.\r\n- For `gsc_query`, choose dimensions from `query`, `page`, `country`, `device`,\r\n  `searchAppearance`, `date`. Pair explicit `startDate` and `endDate`, or use\r\n  trailing `days`. Filters combine with AND. Paginate with `startRow` when a\r\n  response reaches `rowLimit`; disclose sampling if not retrieving every row.\r\n- State dates and GSC reporting lag. Inspect returned `history`, actual covered\r\n  dates and `windowTruncated` before describing a period as a full month/quarter.\r\n  Use comparable windows and property scopes for trends.\r\n- Use returned site totals for site totals. Named-query rows omit anonymized\r\n  queries, so summing them may undercount. Calculate aggregate CTR from total\r\n  clicks divided by impressions; do not average row percentages. Do not average\r\n  positions without the appropriate weighting and scope.\r\n- Striking-distance `priority` is an ordering heuristic, not forecast traffic.\r\n  For zero-click pages, preserve the tool's distinctions between brand searches,\r\n  snippet issues, page-two position and deeper ranking. Phrase causes as the\r\n  report's classifications rather than independently proven diagnoses.\r\n- No impressions is not proof a page is unindexed. `gsc_coverage_gap` compares\r\n  sitemap URLs with observed impressions and cannot separate indexing failures\r\n  from low visibility. Recommend checking URL Inspection when needed.\r\n- `gsc_ai_searches` identifies query wording; it does not measure Google's AI\r\n  Overviews/AI Mode totals or prove where an individual query originated. Keep\r\n  those heuristic results separate from Cituna's measured AI-engine answers.\r\n- Join GSC demand to prompt tracking, citations or content opportunities only\r\n  with explicit matching evidence. If the match is semantic, label it as such.\r\n- Google access is read-only. This plugin cannot submit sitemaps, request\r\n  indexing, change Google settings or mutate GSC data.\r\n\r\n## Relevant tools\r\n\r\n`gsc_status`, `gsc_overview`, `gsc_query`, `gsc_striking_distance`,\r\n`gsc_zero_click_pages`, `gsc_query_mix`, `gsc_coverage_gap`,\r\n`gsc_cannibalisation`, `gsc_ai_searches`.\r\n"
}

SHA-256 of public snapshot: 3ced56bdeaae135f5bbafbc4ff6fe2a1c602b2e6ddc580eb26e332b93205a3cf