Seo
Ship crawlable pages with correct meta, structured data, and on-page SEO aligned to Lighthouse and Google guidelines.
Overview
seo is an agent skill most often used in Launch (also Grow content, Ship launch prep) that applies Lighthouse-style technical and on-page SEO fixes to crawlability, metadata, and structured data.
Install
npx skills add https://github.com/addyosmani/web-quality-skills --skill seoWhat is this skill?
- Lighthouse-oriented technical SEO: robots.txt patterns, meta robots, and crawlability guardrails
- On-page SEO coverage with ranking-factor table (content ~40%, backlinks ~25%, technical ~15%, CWV ~10%, on-page ~10%)
- Structured data and sitemap optimization guidance for indexable public URLs
- Explicit scope boundary: does not cover backlink authority building
- Pairs with Core Web Vitals skill for page-experience factors outside pure SEO markup
- Ranking-factor table lists content quality ~40%, backlinks ~25%, technical SEO ~15%, Core Web Vitals ~10%, on-page SEO ~
- Skill version 1.0 in metadata (author web-quality-skills).
Adoption & trust: 23.4k installs on skills.sh; 2.2k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your site ships features fast but search engines cannot crawl, index, or render rich results because robots, meta, and structured data are wrong or missing.
Who is it for?
Indie founders polishing a public marketing site, docs, or store right before or after launch.
Skip if: Pure authority or backlink strategy, or teams that only need Core Web Vitals tuning without indexation work.
When should I use this skill?
Improve SEO, optimize for search, fix meta tags, add structured data, sitemap optimization, or search engine optimization.
What do I get? / Deliverables
You leave with concrete HTML and robots.txt patterns, indexation controls, and structured-data steps that align public URLs with Google and Lighthouse SEO expectations.
- Updated robots.txt and meta robots directives
- Structured data snippets and on-page meta improvements
- Sitemap and crawlability recommendations aligned to Lighthouse SEO
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Search visibility is the canonical Launch shelf because the skill targets indexing, snippets, and technical crawl rules before growth content compounds. SEO subphase matches technical and on-page optimization work—robots, sitemaps, meta robots, and structured data—not paid distribution.
Where it fits
Generate sitemap.xml and robots.txt before flipping the marketing site to public indexation.
Add JSON-LD and title or description templates so key URLs qualify for richer search snippets.
Audit blog posts for noindex mistakes and canonical gaps after publishing a content batch.
How it compares
On-page and technical SEO checklist—not a replacement for content strategy or link outreach.
Common Questions / FAQ
Who is seo for?
Solo builders using Claude Code or Cursor who own the HTML and deploy pipeline for a product site and need agent-guided SEO fixes.
When should I use seo?
At Launch for meta and structured data, during Ship launch prep for sitemaps and robots.txt, and in Grow when tuning content pages for indexability.
Is seo safe to install?
Check the Security Audits panel on this page; MIT-licensed web-quality-skills—still review what your agent changes in production routes and robots rules.
SKILL.md
READMESKILL.md - Seo
# SEO optimization Search engine optimization based on Lighthouse SEO audits and Google Search guidelines. Focus on technical SEO, on-page optimization, and structured data. ## SEO fundamentals Search ranking factors (approximate influence): | Factor | Influence | This Skill | |--------|-----------|------------| | Content quality & relevance | ~40% | Partial (structure) | | Backlinks & authority | ~25% | ✗ | | Technical SEO | ~15% | ✓ | | Page experience (Core Web Vitals) | ~10% | See [Core Web Vitals](../core-web-vitals/SKILL.md) | | On-page SEO | ~10% | ✓ | --- ## Technical SEO ### Crawlability **robots.txt:** ```text # /robots.txt User-agent: * Allow: / # Block admin/private areas Disallow: /admin/ Disallow: /api/ Disallow: /private/ # Don't block resources needed for rendering # ❌ Disallow: /static/ Sitemap: https://example.com/sitemap.xml ``` **Meta robots:** ```html <!-- Default: indexable, followable --> <meta name="robots" content="index, follow"> <!-- Noindex specific pages --> <meta name="robots" content="noindex, nofollow"> <!-- Indexable but don't follow links --> <meta name="robots" content="index, nofollow"> <!-- Control snippets --> <meta name="robots" content="max-snippet:150, max-image-preview:large"> ``` **Canonical URLs:** ```html <!-- Prevent duplicate content issues --> <link rel="canonical" href="https://example.com/page"> <!-- Self-referencing canonical (recommended) --> <link rel="canonical" href="https://example.com/current-page"> <!-- For paginated content --> <link rel="canonical" href="https://example.com/products"> <!-- Or use rel="prev" / rel="next" for explicit pagination --> ``` ### XML sitemap ```xml <?xml version="1.0" encoding="UTF-8"?> <urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"> <url> <loc>https://example.com/</loc> <lastmod>2024-01-15</lastmod> <changefreq>daily</changefreq> <priority>1.0</priority> </url> <url> <loc>https://example.com/products</loc> <lastmod>2024-01-14</lastmod> <changefreq>weekly</changefreq> <priority>0.8</priority> </url> </urlset> ``` **Sitemap best practices:** - Maximum 50,000 URLs or 50MB per sitemap - Use sitemap index for larger sites - Include only canonical, indexable URLs - Update `lastmod` when content changes - Submit to Google Search Console ### URL structure ``` ✅ Good URLs: https://example.com/products/blue-widget https://example.com/blog/how-to-use-widgets ❌ Poor URLs: https://example.com/p?id=12345 https://example.com/products/item/category/subcategory/blue-widget-2024-sale-discount ``` **URL guidelines:** - Use hyphens, not underscores - Lowercase only - Keep short (< 75 characters) - Include target keywords naturally - Avoid parameters when possible - Use HTTPS always ### HTTPS & security ```html <!-- Ensure all resources use HTTPS --> <img src="https://example.com/image.jpg"> <!-- Not: --> <img src="http://example.com/image.jpg"> ``` **Security headers for SEO trust signals:** ``` Strict-Transport-Security: max-age=31536000; includeSubDomains X-Content-Type-Options: nosniff X-Frame-Options: DENY ``` --- ## On-page SEO ### Title tags ```html <!-- ❌ Missing or generic --> <title>Page</title> <title>Home</title> <!-- ✅ Descriptive with primary keyword --> <title>Blue Widgets for Sale | Premium Quality | Example Store</title> ``` **Title tag guidelines:** - 50-60 characters (Google truncates ~60) - Primary keyword near the beginning - Unique for every page - Brand name at end (unless homepage) - Action-oriented when appropriate ### Meta descriptions ```html <!-- ❌ Missing or duplicate --> <meta name="description" content=""> <!-- ✅ Compelling and unique --> <met