seo-google
by AgriciDanielseo-google is a Google SEO APIs skill for Search Console, PageSpeed Insights, CrUX, Indexing API, and GA4 organic traffic. Use it to verify indexation, inspect URLs, review Core Web Vitals, and pull real Google field data before making SEO recommendations. It also supports a seo-google guide for Keyword Research when Google Ads access is configured.
This skill scores 78/100, which means it is a solid directory listing candidate: users get a clearly triggerable Google SEO workflow with enough operational detail to justify installation, though they should expect some setup overhead and should consult the references for full execution guidance.
- Strong triggerability: the frontmatter marks it user-invokable and names many concrete intents like Search Console, PageSpeed, CrUX, URL inspection, and GA4 organic.
- Real workflow substance: the body and references cover authentication setup, API endpoints, request shapes, quotas, and SEO-specific use cases across multiple Google APIs.
- Good leverage for agents: it exposes real field data sources such as Search Console, CrUX, Indexing API, and GA4 instead of generic SEO advice.
- Setup is non-trivial: users need a Google Cloud project plus API key and/or service account, and GA4/Indexing/Search Console require credentials.
- Some guidance is distributed across references, so quick adoption may require reading multiple docs rather than relying on one concise install page.
Overview of seo-google skill
What seo-google does
The seo-google skill gives you direct access to Google SEO APIs instead of guessing from generic prompts or third-party estimates. It is built for people who need real field data for Search Console, PageSpeed Insights, CrUX, Indexing API, and GA4 organic traffic in one workflow.
Best-fit users and jobs
Use the seo-google skill if you need to verify indexation, inspect URLs, compare impressions and clicks, audit Core Web Vitals with real user data, or pull organic traffic trends from GA4. It is especially useful for SEO operators, technical SEOs, content teams, and agents that need Google-native evidence before making recommendations.
Why it is different
The main value of seo-google is not broad SEO theory; it is source-of-truth data. It bridges crawl-based analysis and Google’s own APIs, so you can move from “this page looks fine” to “Search Console shows low CTR” or “CrUX shows poor INP on mobile.” That makes it stronger for decision-making than a normal freeform prompt.
When seo-google is the right fit
Choose seo-google when the task depends on real Google data, account setup, or API-backed diagnostics. It is less useful if you only want content brainstorming, keyword ideation without Google Ads access, or a one-off SEO explanation that does not require live data.
How to Use seo-google skill
Install and check prerequisites
For the seo-google install step, add the skill through your skills workflow and then verify credentials before asking for analysis. The repo expects Google API auth to be present, and the skill’s first practical dependency is a working config in ~/.config/claude-seo/google-api.json.
Start with the right input shape
The seo-google usage pattern works best when you provide a specific URL, property, or goal. Good inputs look like: “Audit https://example.com/pricing for indexation and CWV,” “Compare GSC queries for sc-domain:example.com last 28 days,” or “Check GA4 organic landing pages for the blog section.” Avoid vague asks like “improve my SEO,” because the APIs need a target and a date range.
Read these files first
For a reliable seo-google guide, inspect SKILL.md first, then references/auth-setup.md, references/search-console-api.md, references/pagespeed-crux-api.md, and references/ga4-data-api.md. If your task involves notifications or submit/inspect flows, also read references/indexing-api.md; for keyword research, use references/keyword-planner-api.md.
Workflow that gets better results
A practical workflow is: confirm auth, identify the data source, define the property or URL, choose a date window, then request only the metrics you need. Example: “Using seo-google, check GSC Search Analytics for sc-domain:example.com over the last 28 days, surface pages with high impressions but low CTR, and explain likely titles to rewrite.” That is better than asking for a broad SEO review because it tells the skill what to fetch and how to frame the output.
seo-google skill FAQ
Is seo-google only for Search Console?
No. Search Console is central, but the seo-google skill also covers PageSpeed Insights, CrUX, Indexing API, and GA4 organic data. That matters if you want one skill for indexation, performance, and traffic diagnosis instead of separate prompts.
Do I need both API key and service account?
Usually yes for full coverage. API key access is enough for PageSpeed Insights and CrUX; Search Console, Indexing API, and GA4 require a service account. The skill is most useful when you have both configured.
Can I use seo-google for Keyword Research?
Yes, but with a boundary: seo-google for Keyword Research depends on Google Ads/Keyword Planner access, which is more involved than the other APIs. It is best when you need Google-sourced volume or forecast data, not when you only need quick topic ideas.
When should I not use this skill?
Do not use seo-google if you lack credentials, do not have a verified property, or only need a generic SEO checklist. It is also not the best choice for pure content generation because its strength is API-backed evidence, not drafting.
How to Improve seo-google skill
Give the skill decision-ready context
The fastest way to improve results is to include the property type, URL pattern, date range, device focus, and success metric. For example: “mobile CWV on /blog/ pages,” “GSC pages with impressions > 1,000 and CTR < 2%,” or “GA4 organic traffic for the last 90 days excluding branded landing pages.” This lets seo-google return actionable slices instead of broad summaries.
Ask for one analysis lane at a time
The skill performs better when you separate indexation, rankings, Core Web Vitals, and traffic into distinct tasks. A request like “check URL inspection, then GSC, then GA4” often creates noisy output; a better approach is to ask for one lane first, then iterate based on what it finds.
Watch for common failure modes
The most common blockers are missing auth, wrong property format, and asking the skill to infer data it cannot fetch. Another frequent issue is overbroad keyword requests without enough seed terms or without Google Ads credentials. If you want seo-google to help with keyword research, say whether you need ideas, historical volume, or forecasts.
Iterate from evidence, not intuition
After the first output, refine with the exact anomaly you saw: “Pages with high impressions but low clicks,” “URLs with poor INP only on mobile,” or “indexing failures for recently published pages.” That turns seo-google into a diagnostic loop and makes the second pass far more useful than a single generic audit.