Seo Google
Run a structured Core Web Vitals and Lighthouse audit on a URL or origin so you can fix speed, UX, and SEO score issues before or after launch.
Overview
seo-google is an agent skill most often used in Launch (also Ship perf) that produces a Core Web Vitals and Lighthouse audit report for a target URL or origin.
Install
npx skills add https://github.com/agricidaniel/claude-seo --skill seo-googleWhat is this skill?
- CrUX field data table for LCP, INP, CLS, FCP, and TTFB with good/needs-improvement/poor distributions
- Lighthouse lab scores for Performance, Accessibility, Best Practices, and SEO
- 25-week CrUX history trends with direction and change columns
- Top opportunities table with estimated savings
- Written recommendations section with daily CrUX refresh note (~04:00 UTC)
- 5 CrUX metrics in the field table (LCP, INP, CLS, FCP, TTFB)
- 4 Lighthouse lab category scores
- 25-week CrUX history trends section
Adoption & trust: 1.7k installs on skills.sh; 8.5k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You need Google-aligned CWV and SEO lab scores in one report but keep reformatting CrUX and Lighthouse exports by hand.
Who is it for?
Indie builders validating page experience and SEO lab health on a specific production or staging URL before indexing pushes or ad spend.
Skip if: Teams that only need keyword research, backlink strategy, or on-page copy optimization without performance measurement.
When should I use this skill?
You have a target URL or origin and need a Google-aligned Core Web Vitals and Lighthouse SEO audit report.
What do I get? / Deliverables
You get a standardized audit with field metrics, lab scores, trends, opportunities, and recommendations ready to turn into a fix backlog.
- Core Web Vitals audit document with CrUX, Lighthouse, trends, opportunities, and recommendations
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Canonical shelf is Launch because the deliverable is an SEO-oriented performance audit (Lighthouse SEO category, CrUX field data) aimed at search visibility and page experience signals. Fits the seo subphase as the output maps directly to Google ranking UX metrics (LCP, INP, CLS) and lab SEO scoring—not generic infra monitoring.
Where it fits
After a deploy, fill the template with fresh Lighthouse runs to see if LCP or TTFB regressed before you tag a release hotfix.
Produce a CWV plus SEO score snapshot for the marketing domain ahead of indexing and launch announcements.
Compare 25-week CrUX trends when organic conversion softens and you need evidence that INP or CLS drifted.
How it compares
Structured CWV plus Lighthouse reporting template—not a keyword rank tracker or content brief generator.
Common Questions / FAQ
Who is seo-google for?
Solo and indie builders who ship web products and need Google Core Web Vitals and Lighthouse results summarized for SEO and perf fixes without building a custom report format each time.
When should I use seo-google?
Use it in Launch when polishing SEO and page experience before go-live, in Ship when checking perf regressions after a release, and in Grow when organic traffic drops and you suspect CWV or lab SEO scores degraded.
Is seo-google safe to install?
Treat it as a reporting template skill; review the Security Audits panel on this Prism page and only pipe in metrics from APIs or tools you already trust.
SKILL.md
READMESKILL.md - Seo Google
# Core Web Vitals Audit **URL/Origin:** {target} **Strategy:** {strategy} ## CrUX Field Data (28-day rolling average) Real Chrome user experience data from the Chrome UX Report. | Metric | p75 Value | Rating | Good Threshold | Distribution | |--------|-----------|--------|----------------|-------------| | LCP | {lcp_value} | {lcp_rating} | ≤ 2,500ms | Good: {lcp_good}% / NI: {lcp_ni}% / Poor: {lcp_poor}% | | INP | {inp_value} | {inp_rating} | ≤ 200ms | Good: {inp_good}% / NI: {inp_ni}% / Poor: {inp_poor}% | | CLS | {cls_value} | {cls_rating} | ≤ 0.1 | Good: {cls_good}% / NI: {cls_ni}% / Poor: {cls_poor}% | | FCP | {fcp_value} | {fcp_rating} | ≤ 1,800ms | Good: {fcp_good}% / NI: {fcp_ni}% / Poor: {fcp_poor}% | | TTFB | {ttfb_value} | {ttfb_rating} | ≤ 800ms | Good: {ttfb_good}% / NI: {ttfb_ni}% / Poor: {ttfb_poor}% | **Collection Period:** {collection_start} to {collection_end} ## Lighthouse Lab Scores | Category | Score | |----------|-------| | Performance | {perf_score}/100 | | Accessibility | {a11y_score}/100 | | Best Practices | {bp_score}/100 | | SEO | {seo_score}/100 | ## CrUX History Trends (25-week) | Metric | Direction | Change | Earliest → Latest | |--------|-----------|--------|-------------------| {trends_table} ## Top Opportunities | Opportunity | Estimated Savings | |-------------|-------------------| {opportunities_table} ## Recommendations {recommendations} --- *CrUX data updated daily ~04:00 UTC. 28-day rolling average.* *INP replaced FID as the responsiveness Core Web Vital on March 12, 2024.* *Generated {timestamp}.* # Google Search Console Performance Report **Property:** {property} **Date Range:** {start_date} — {end_date} **Search Type:** {search_type} ## Summary | Metric | Value | |--------|-------| | Total Clicks | {total_clicks} | | Total Impressions | {total_impressions} | | Average CTR | {avg_ctr}% | | Average Position | {avg_position} | ## Top Queries | # | Query | Clicks | Impressions | CTR | Position | |---|-------|--------|-------------|-----|----------| {queries_table} ## Top Pages | # | Page | Clicks | Impressions | CTR | Position | |---|------|--------|-------------|-----|----------| {pages_table} ## Quick Wins (Position 4-10, High Impressions) These queries rank on page 1 but below position 3. A small ranking improvement could yield significant traffic gains. | Query | Position | Impressions | Clicks | CTR | Opportunity | |-------|----------|-------------|--------|-----|-------------| {quick_wins_table} ## Device Breakdown | Device | Clicks | Impressions | CTR | Position | |--------|--------|-------------|-----|----------| {device_table} --- *Data freshness: Search Analytics has a 2-3 day lag. Data available for ~16 months.* *Generated {timestamp} via Google Search Console API.* # URL Indexation Status Report **Property:** {property} **URLs Inspected:** {total_urls} ## Summary | Status | Count | Percentage | |--------|-------|-----------| | Indexed (PASS) | {pass_count} | {pass_pct}% | | Not Indexed (FAIL) | {fail_count} | {fail_pct}% | | Neutral | {neutral_count} | {neutral_pct}% | | Errors | {error_count} | {error_pct}% | ## Detailed Results | URL | Verdict | Coverage State | Fetch State | Google Canonical | Last Crawl | |-----|---------|---------------|-------------|-----------------|------------| {results_table} ## Canonical Mismatches URLs where Google selected a different canonical than declared: | URL | User Canonical | Google Canonical | |-----|---------------|-----------------| {canonical_mismatches_table} ## Common Issues | Issue | Count | Priority | Action | |-------|-------|----------|--------| {issues_table} ## Rich Results Detected | URL | Rich Result Type | Status | |-----|-----------------|--------| {rich_results_table} --- *URL Inspection API: 2,000 inspections/day per site, 600/min.* *Generated {timestamp} via Google Search Console URL Inspection API.* MIT License - see repository root LICENSE file for complete terms. Copyright (