SEO Optimization
Audits and fixes technical SEO, on-page metadata and structured data using Lighthouse SEO audits and Google Search guidelines.
Marketing & SEOIntermediate★ 2,741⑂ 249AI score 9/10Last updated: Aug 24, 2026
What it does
- Evidence-led audit workflow: runs
lighthouse_auditvia Chrome DevTools MCP (or falls back to Lighthouse CLI), then inspects what Lighthouse can't see — response headers, redirects,robots.txt, sitemap coverage, canonical consistency across templates, Search Console evidence. - Technical SEO: robots.txt and meta robots patterns, canonicals, XML sitemaps (50k URL / 50MB limits, sitemap index), URL structure rules, HTTPS and security headers.
- On-page SEO: titles and meta descriptions (character counts treated as lint proxies, not pass/fail), heading hierarchy, image filenames and alt text, descriptive internal anchor text.
- Structured data: defers to
references/STRUCTURED-DATA.mdfor Organization, Article, Product, FAQ and Breadcrumb JSON-LD plus validation links. - AI-era section: separates Lighthouse Agentic Browsing, search indexing, and AI citation; documents the real effect of
OAI-SearchBot,PerplexityBot,Claude-SearchBot,Google-Extended, and treatsllms.txtas optional and experimental. - Mobile & international: viewport, 48px tap targets, font sizes, hreflang,
langdeclaration — closing with a priority-ordered audit checklist.
Who it's for
- Frontend/fullstack developers owning SEO for their own site, docs or blog
- Teams cleaning up meta tags and schema on Next.js, Astro or WordPress builds
- Technical SEO practitioners who need defensible answers about AI crawlers
Example uses
- "Audit SEO on our product detail pages" → runs the Lighthouse SEO audit, finds duplicate titles, missing descriptions and a wrong canonical, patches the templates and re-runs.
- "Add structured data to this blog post" → emits Article + Breadcrumb JSON-LD describing only visible content, then validates with the Rich Results Test.
- "How should we handle AI bots?" → distinguishes training crawlers (GPTBot, ClaudeBot) from search crawlers (OAI-SearchBot, Claude-SearchBot) and writes robots.txt with the consequences spelled out.
· · · Install guide · · ·
Try it now, no install
Paste this into Claude to use the skill without installing anything.
Read the instructions in this file and follow them to help me: https://raw.githubusercontent.com/addyosmani/web-quality-skills/HEAD/skills/seo/SKILL.md What I want: (describe your task here)
If Claude can't open the link, open it yourself and paste the contents instead.
↓ If it works for you, download the ZIP below and install it. Then it runs on its own — no pasting each time.
Install in the Claude app (no terminal)
- Download the ZIP with the button below.
- In Claude, open Settings → Capabilities and turn on 'Code execution and file creation'. (one time)
- Go to Customize → Skills → + → 'Upload a skill' and upload the ZIP.
Install in Claude Code
Let Claude do it — paste this into Claude Code
Install the skill I found on Claude Skill Mart. Copy the skills/seo folder from the GitHub repo addyosmani/web-quality-skills into my ~/.claude/skills/addyosmani-seo/. When it's done, tell me in one line what this skill can do.
Install with a command instead
git clone https://github.com/addyosmani/web-quality-skills.git /tmp/web-quality-skills && mkdir -p ~/.claude/skills && cp -r /tmp/web-quality-skills/skills/seo ~/.claude/skills/seo⚠ This is a third-party skill. Check the source repository before installing.
- Open a terminal.
- Clone the repository:
git clone https://github.com/addyosmani/web-quality-skills.git - Create the skills directory:
mkdir -p ~/.claude/skills - Copy just this skill:
cp -r web-quality-skills/skills/seo ~/.claude/skills/seo- Copy the whole folder so
references/STRUCTURED-DATA.mdcomes along.
- Copy the whole folder so
- Optional: add the sibling skills it links to —
cp -r web-quality-skills/skills/core-web-vitals web-quality-skills/skills/web-quality-audit ~/.claude/skills/ - Restart Claude Code and ask something like "improve SEO on this site" to trigger it.
- Recommended: connect Chrome DevTools MCP, or install the CLI with
npm i -g lighthouse, so rendered-page audits actually run.
View source on GitHub ↗License: MIT