← SearchFitCONTENT HISTORY

Update to SearchFit

Snapshot Sep 30, 2026 · 23:00 UTC · version 1.0.0

Collection source: not recorded for this historical snapshot.

WHAT CHANGED · RULE-BASED ANALYSIS

First saved snapshot

No earlier snapshot is available to establish a change.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "name": "google-search-console-report",
  "description": "Report Google Search Console data for a brand. Use for clicks, impressions, CTR, average position, top search queries, top landing pages, or how published articles perform in Google. Do not use for GA4 sessions or conversions, which belong to google-analytics-report, and do not use for visibility inside AI assistant answers, which belongs to ai-visibility-report.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 1296
    }
  ],
  "skill_md_contents": "---\nname: google-search-console-report\ndescription: Report Google Search Console data for a brand. Use for clicks, impressions, CTR, average position, top search queries, top landing pages, or how published articles perform in Google. Do not use for GA4 sessions or conversions, which belong to google-analytics-report, and do not use for visibility inside AI assistant answers, which belongs to ai-visibility-report.\n---\n\n# Google Search Console report\n\nReport what the brand's site did in Google search: who searched, what they saw, and what they clicked.\n\nEvery tool here is scoped to one brand and takes `brand_id`.\n\n## Step 1: resolve the brand\n\nCall `list_brands`. If more than one, ask which. Keep `brand_id` for every later call.\n\n## Step 2: confirm Google is connected\n\nCall `list_connectors`.\n\nIf Google is not connected for this brand, say so and stop. Tell the user to connect it in the brand's Connectors settings. Do not substitute another source and do not estimate.\n\n## Step 3: refresh only if asked\n\n`sync_search_console` pulls fresh data and takes time. Run it when the user wants current figures. Otherwise report what is stored, and say when it was last synced.\n\n## Step 4: pull the numbers\n\n- `get_search_performance` for clicks, impressions, CTR and average position over a period.\n- `get_top_queries` for the searches bringing people in.\n- `get_top_pages` for the pages receiving them.\n- `get_published_content_urls` to tie performance back to articles produced in SearchFit.\n- `get_audience_breakdown` for country and device splits.\n\n## Step 5: report\n\nState the date range and the site every number came from. A figure without its window cannot be checked.\n\nRules that keep the report honest:\n\n- **Give clicks with impressions.** Impressions alone overstate reach. A page with 10,000 impressions and 12 clicks is a problem, not a success.\n- **Search Console lags by roughly two to three days.** Never present the most recent two days as complete, and never read the dip there as a real decline. Say the window excludes them.\n- **Average position is weighted across impressions.** It can move because a different mix of queries fired, not because any single ranking changed. When position moves and clicks do not, say that rather than implying the site moved.\n- **Compare equal windows.** 30 days against 7 days is not a trend. If comparing, use matching lengths and say so.\n- **CTR needs context.** A low CTR at position 3 is a title and description problem. The same CTR at position 30 is normal. Read them together.\n- Never fill a gap with an estimate. If a query returned nothing, say it returned nothing.\n\n## Step 6: say what to do about it\n\nClose with a small number of specific actions tied to the data:\n\n- High impressions and low CTR: rewrite the title and meta description for those queries.\n- Position 5 to 15 on a valuable query: the page exists and nearly ranks, so improving it usually beats writing a new one.\n- Queries with no matching page: a content gap. Hand off to the content-production skill.\n\n## Boundaries\n\n- Search Console measures Google only. If the user asks how the brand appears in ChatGPT, Perplexity or similar, that is the ai-visibility-report skill, and answering it with Search Console data would be wrong.\n- For sessions, users, engagement or conversions, use the google-analytics-report skill.\n- For a combined client or monthly report across several sources, use the performance-report skill.\n"
}

SHA-256: 07ca81905a55571f0f2a3812db99a04280f72d4c231148dac0a1be3b4995f4ae