Google Search Console logo

Google Search Console

Community
kostja94
google-search-console

When the user wants to analyze Google Search Console data, use the GSC API, or interpret search performance. Also use when the user mentions "GSC," "Search Console," "indexing report," "Core Web Vitals," "Enhancements," "Insights report," "search performance," "search queries," "search performance report," "URL inspection," "impressions," "CTR," "average position," "index coverage," "GSC data analysis," "Search Console API," or "searchanalytics.query." When the user wants to rewrite title tags (not only report on them), use title-tag. For meta description rewrites, use meta-description.

Overview

Publisherkostja94
Repositorymarketing-skills
Skill namegoogle-search-console
Stars
979
Forks
137
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by kostja94 on GitHub. Read the source before you install it.

Installation

Install the Google Search Console AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/kostja94/marketing-skills.git /tmp/marketing-skills
mkdir -p .claude/skills
cp -r /tmp/marketing-skills/skills/analytics/seo/google-search-console .claude/skills/google-search-console
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Google Search Console in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Google Search Console on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Google Search Console is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Analytics: Google Search Console

Guides analysis of Google Search Console (GSC) data: performance metrics, indexing, sitemaps, Core Web Vitals, and rich results. Covers best practices for monthly monitoring and actionable insights.

When invoking: On first use, if helpful, open with 1-2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.

Scope

  • Performance: Clicks, impressions, CTR, average position; API for export
  • Insights: Simplified overview; top/trending content and queries
  • Indexing: Pages indexed, pages not indexed, reasons (Coverage)
  • Technical: Sitemaps, Core Web Vitals, Enhancements
  • API: searchanalytics.query for programmatic access
  • Methodology: How to read charts, avoid common mistakes, correlate with releases

Analysis Best Practices

Chart Reading

PracticeWhy
Focus one metric at a timeStacked bar charts hide fluctuations; toggle off other metrics to see each clearly
Don't compare just two pointsEnd-of-month vs prior month misses mid-month drama; examine full trend
Check beyond top 10Many reports default to top 10; scroll or paginate for more rows
Screenshot chartsGSC retains limited history; save images for future reference
Record in spreadsheetExport at month-end; use formulas to track correlations over time
Track release datesJoin dev standups, read release notes; correlate GSC shifts with deployments

Investigation Workflow

  1. Pinpoint date: When did the metric change?
  2. Correlate: Any releases, CMS changes, server maintenance, third-party code?
  3. Decide: Investigate, correct, overlook, or monitor closely
  4. Loop in: Product or dev team for root cause

Key Reports & Metrics

1. Performance (Search Results)

Location: Performance ? Search results

MetricUse
ClicksTraffic from Google Search
ImpressionsHow often site appeared in results
CTRWhether users think page answers query
Average positionRanking trend

Dimensions: Query, page, country, device, date. Filter by search type: web, image, video, news. Use to find low-CTR high-impression pages (title/meta optimization opportunities).

Search appearance: AMP, blue link, rich results (filterable in UI and API).

CTR Benchmarks by Position

Use to compare actual CTR vs expected. Benchmarks vary by SERP features (AI Overviews, featured snippets). Zero-click: When SERP features satisfy intent without a click, organic CTR drops; factor into expectations. See serp-features (Zero-Click section), featured-snippet. Clean SERPs:

PositionExpected CTR (baseline)With AI Overviews (lower)
125-35%~19%
212-18%~12%
38-12%~7%
4-55-7%~5%
6-102-5%2-5%

Interpretation: If actual CTR is below expected for your position, prioritize title/meta optimization. Over 90% of first-page results have CTR below 10%; significant upside exists.

Low CTR, High Impressions: Optimization Workflow
  1. Identify: Sort by impressions; filter positions 1-10; 1,000+ monthly impressions
  2. Compare: Actual CTR vs expected for position (see table above)
  3. Gap: e.g., position 4 at 2% CTR vs expected 5-7% ? ~3-5% uplift potential
  4. Action: Optimize title and meta per title-tag, meta-description; add schema for rich results (+10–20% clicks)
Rich Results & CTR

Pages with review stars, FAQ schema, or other rich snippets see 10-20% more clicks. See schema-markup.

2. Insights Report

Location: Performance ? Insights (or Overview)

Simplified overview; replaces standalone Search Console Insights. Data from GSC only (GA data removed Dec 2024).

CardUse
Clicks and impressionsSite visibility and click effectiveness
Your contentTop, trending up, trending down pages
Queries leading to your siteTop, trending up, trending down queries
Top countriesGeographic audience
Branded vs non-brandedBrand recognition (AI-labeled; may mislabel)
Additional traffic sourcesImage, Video, News search, Discover

Trending: Based on click change vs previous period. Click items to jump to Performance report filtered to that item.

Query groups: Similar queries grouped; group name = best-performing query. Not available for sub-properties or low-impression sites.

3. Page Indexing (Coverage)

Location: Indexing ? Page indexing

Status grouping (updated): Valid + Valid with warning ? Indexed. Error + Excluded ? Not indexed.

Indexed vs Not indexed are complementary: Not all site content should be indexed. Login, admin, duplicate content, legal boilerplate, and low-value pages often intentionally use noindex. Indexed and non-indexed pages can reference each other (e.g., sitemap includes indexable URLs; noindex pages still exist and link internally). Non-indexed is not inherently a problem--investigate only when important pages are excluded. See indexing (noindex usage) and robots-txt (crawl control) for when to exclude.

MetricAction
Pages indexedTurn off "Pages not indexed" to view alone; watch for drops
Pages not indexedTurn off "Pages indexed" to view alone; watch for spikes. Distinguish intentional (noindex, robots) from accidental

Filter: All submitted pages / Unsubmitted pages only (dropdown near top).

Source column: Indicates whether issue is caused by website or Google.

Why pages are not indexed: Drill into reasons and example URLs. Common culprits:

  • Duplicate content
  • Noindex tags
  • Redirect errors
  • 5xx errors
  • 404 errors
  • Blocked by robots.txt
  • Discovered ? currently not indexed
  • Crawled ? currently not indexed

Quick check: If trend line is stable, spend ~3 seconds; move on. Investigate if fourth column (trend) shifts.

Diagnosis workflow: GSC Coverage ? click Issue ? view sample URLs ? identify pattern ? fix (see indexing for fix actions).

Coverage issue types:

IssueMeaningNext step
Crawled - currently not indexedCrawled but not indexedSee indexing
Excluded by "noindex" tagIntentionally excluded; often valid (login, admin, legal, etc.)Ignore if expected; verify important pages not accidentally noindexed
Blocked by robots.txtCrawl blockedSee robots-txt; may be intentional
Redirect / 404Redirect or missingFix URL or redirect
Duplicate / CanonicalDuplicate contentUsually OK; keep canonical

URL Inspection: Verdicts: "URL is on Google," "URL is on Google, but has issues," "URL is not on Google." Use for important pages; verify canonical, internal links, sitemap; Request indexing if needed.

4. Video Indexing (If Applicable)

Location: Indexing ? Video indexing

  • Videos indexed / Videos not indexed: Toggle off the other for clear view
  • Why videos are not indexed: Thumbnail blocked, invalid size/format, not in main content, etc.

See video-optimization for video SEO; youtube-seo for YouTube.

5. XML Sitemaps

Location: Indexing ? Sitemaps

CheckAction
StatusConfirm each sitemap says "Success"
URLs indexedClick sitemap ? see indexed count; drops indicate indexing issues
Bellwether sitemapsFor large sites, monitor templated sitemaps (by country, language, division)

Enterprise: Glitches can block new URL crawling, cause hreflang confusion, delay fresh content discovery.

6. Core Web Vitals

Location: Experience ? Core Web Vitals

Priority: Mobile first (Google's higher expectations for mobile).

MetricMobileDesktop
Good URLsTargetSecondary
Needs improvementFixMonitor
Poor URLsFixMonitor

Why URLs don't have good score: Click "Open report" → grouped example URLs by issue type. For threshold values and fixes, see core-web-vitals.

Tip: Historical chart is short; export to spreadsheet for longer trends. Share with dev team regularly; correlate dates with releases.

Layout (updated): Two tables--Poor or Need improvement; Good (click "View data about usable pages").

7. Enhancements (Rich Results)

Location: Experience ? Enhancements (Product snippets, Merchant listings under Shopping)

Status (updated): Two-tier?invalid (critical issues, may not appear) vs valid (no critical issues; may still have warnings). Warnings no longer top-level.

TypeExamples
ContentBreadcrumbs, FAQ, Events, Videos (see video-optimization), Job postings, Review snippets, Q&A, Discussion forums
ShoppingProduct snippets, Merchant listings
OtherRecipes, Datasets, Hotels, Vacation rentals, Profile pages, Practice problems, Math solvers, Image metadata

Note: Reports show sample items, not full list. Use URL Inspection for unlisted URLs.

8. AI Overviews (GSC Limitation)

  • GSC: AI Overviews clicks/impressions are not separated from organic in Performance report.
  • Workaround: Filter queries that tend to trigger AI Overviews to estimate AI-driven visibility:
(?i)^(who|what|where|when|why|how|which|is|are|can|does|should)|\b(vs|versus|compare|difference|pros and cons|guide|tutorial|best|top|list)\b

For GA4 AI traffic tracking, see ai-traffic-tracking.

9. Links & Disavow

Location: Links (inbound links), Security & Manual Actions

  • Links report: View links to site and pages; anchor text distribution.
  • Disavow file: Submit via GSC when necessary (manual penalty, toxic links). Use sparingly; over-disavowing can harm. See backlink-analysis for when to disavow.

Search Console API

Method: searchanalytics.query() --exposes all Performance report data.

Metrics

Clicks, Impressions, CTR, Position.

Dimensions

date, query, page, country, device. Search appearance (AMP, blue link, rich results). Filter by search type: web, image, video, news.

Limits

LimitValue
Rows per day per search type per property50,000
Rows per response25,000 (use pagination: startRow, rowLimit)
Data availability2-3 days after

Tip: Run daily queries for one day of data to avoid quota. Verify data presence first (dimensions: date only, no filters).

Optimization: Gzip compression; fields parameter for partial responses; pagination for large datasets.

References: Search Console API, searchanalytics.query

Monthly Audit Checklist

  • Performance: Clicks, impressions, CTR, position trends
  • Insights: Top/trending content and queries (if available)
  • Page indexing: Indexed vs not indexed (isolated views)
  • Why not indexed: Trend lines for key reasons
  • Sitemaps: All "Success"; indexed URL counts stable
  • Core Web Vitals: Mobile good/needs improvement/poor
  • Enhancements: No new invalid items (critical issues)
  • Links: No manual actions; disavow only if needed (see backlink-analysis)
  • Data exported to spreadsheet (month-end snapshot)
  • Charts screenshotted for history
  • Release notes reviewed for correlation

Output Format

  • Summary: Key findings, trends, anomalies
  • Metrics: Specific numbers and date ranges
  • CTR analysis: Actual vs expected by position; low-CTR high-impression pages
  • Title/meta opportunities: Pages with CTR gap; specific optimization suggestions
  • Action items: Prioritized fixes (indexing, CWV, sitemaps, enhancements, title/meta)
  • Correlation: Suspected causes (releases, config changes)
  • Next steps: Monitoring plan, dev handoff

Related Skills

  • title-tag, meta-description, page-metadata: Title and meta optimization for low-CTR pages; hreflang
  • xml-sitemap: Fix sitemap errors
  • indexing: Resolve indexing issues
  • core-web-vitals: CWV optimization; fix LCP, INP, CLS
  • mobile-friendly: Mobile Usability report; mobile-first indexing
  • schema-markup: Fix structured data / rich results
  • backlink-analysis: When to disavow; backlink audit
  • seo-monitoring: Full SEO data analysis, benchmark

Frequently asked questions

What does the Google Search Console AI skill do?

When the user wants to analyze Google Search Console data, use the GSC API, or interpret search performance. Also use when the user mentions "GSC," "Search Console," "indexing report," "Core Web Vitals," "Enhancements," "Insights report," "search performance," "search queries," "search performance report," "URL inspection," "impressions," "CTR," "average position," "index coverage," "GSC data analysis," "Search Console API," or "searchanalytics.query." When the user wants to rewrite title tags (not only report on them), use title-tag. For meta description rewrites, use meta-description.

Why use Google Search Console on TypingMind?

Because you install it once and use it with any model. Google Search Console is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Google Search Console in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/kostja94/marketing-skills/tree/main/skills/analytics/seo/google-search-console. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Google Search Console?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Google Search Console?

As many as you like. As long as a model supports skills, you can use Google Search Console with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Google Search Console AI skill free?

Yes. It is published on GitHub by kostja94 under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇