Token导航 LogoToken导航

Agent Skill · 研究检索

kostja94-google-search-console(kostja94 Google 搜索 console)

kostja94-google-search-console 用于查找、检索和筛选相关信息,适合在 OpenClaw 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

kostja94-google-search-console 是研究检索类 Agent Skill,可用宿主为 OpenClaw,通过ClawHub获取,权限为需要联网;许可证为 MIT-0,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 12,715。

总安装 10,036周安装 406GitHub Stars 公开资料未说明下载 3,151核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT-0
版本
1.3.0

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:kostja94-google-search-console(kostja94 Google 搜索 console)
来源仓库:https://github.com/kostja94/kostja94-google-search-console
安装命令:
openclaw skills install kostja94-google-search-console
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install kostja94-google-search-console

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

kostja94-google-search-console 解析 Google Search Console 数据,解释搜索性能趋势、索引覆盖率与点击转化率。帮助用户理解关键词排名变动原因,制定内容更新计划。支持按日期、设备、国家等多维度筛选查看流量明细。需授权 GSC API 访问权限方可获取完整数据集。

适用宿主包括 OpenClaw,接入前应确认版本、权限和运行环境要求。

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 OpenClaw;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 openclaw skills install kostja94-google-search-console;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

kostja94-google-search-console 怎么安装?

在终端执行 openclaw skills install kostja94-google-search-console。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

kostja94-google-search-console 支持哪些 AI 工具?

公开资料标注支持 OpenClaw。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

kostja94-google-search-console 需要什么权限?

权限级别是需要联网。该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

kostja94-google-search-console 是免费的吗?

来源标注的许可证是 MIT-0。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

kostja94-google-search-console 用的人多吗?

公开数据是累计安装 10,036 次,近一周安装 406 次,下载 3,151 次。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

kostja94-google-search-console 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 专注 OpenClaw 一种宿主,触发方式和使用习惯不用来回切换。
  • 许可证明确为 MIT-0,商用和分发边界好判断。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 OpenClaw,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。
  • 需要许可证清楚、并且有第三方扫描结果的团队项目。

不太适合

  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
kostja94-google-search-console

kostja94 Google 搜索 console · 本页

10,036—需要联网MIT-0通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

name
google-search-console
description
When the user wants to analyze Google Search Console data, use 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," "title tag," "meta description," "GSC data analysis," "Search Console API," or "searchanalytics.query.
metadata
version
1.3.0

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 (no GA since 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

平台分布

OpenClaw

94.87%
按下载量换算2,989

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills