SEO Optimization Skill for Muse
Ship pages that search engines and AI agents can actually find
- What
- Ship pages that search engines and AI agents can actually find
- Cost
- Free
- Needs
- Node.js with npx (for the Lighthouse CLI fallback) or Chrome with the Chrome DevTools MCP for live rendered-page audits; your own website or pages to audit. Optional: free Google Search Console access for indexation evidence. No paid APIs.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Teaches your agent to run evidence-led SEO audits instead of guessing: live Lighthouse SEO and Agentic Browsing checks via Chrome DevTools MCP (with a CLI fallback), then the signals Lighthouse can't see on its own — response headers, redirects, robots.txt, sitemap coverage, canonical consistency across templates, and structured-data eligibility. Covers crawlability (robots.txt, meta robots, canonicals), XML sitemaps, HTTPS and security headers, on-page work (title tags, meta descriptions, heading hierarchy, image SEO, descriptive internal linking), mobile SEO, hreflang for international sites, and a full SEO audit checklist sorted by priority. Especially current: a whole section on agentic browsing and AI discoverability — which crawler bots do what (OAI-SearchBot, PerplexityBot, Claude-SearchBot, Google-Extended), training controls vs search controls, and why llms.txt is an optional experimental proposal, not a ranking factor. Discovered via skills.sh. Honest note: it is a disciplined audit method, not a ranking button — it explicitly refuses to invent ranking-factor weights or promise ranking changes, and it treats a Lighthouse SEO score as a useful subset of checks, not a prediction of rankings; indexation outcomes always stay with the search engines. Skill Harbor never reviews the code, review it yourself before use. Not verified.
Curated by Skill Harbor — free, open-source skill (MIT) by @addyosmani.
Version:
Quick answer
SEO Optimization Skill for Muse is a free Muse skill that teaches your agent to run evidence-led SEO audits instead of guessing, with live Lighthouse SEO and Agentic Browsing checks via Chrome DevTools MCP and a CLI fallback. It then covers the signals Lighthouse cannot see alone, including response headers, redirects, robots.txt, sitemap coverage, canonical consistency, and structured-data eligibility.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit afa8da9Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: Node.js with npx (for the Lighthouse CLI fallback) or Chrome with the Chrome DevTools MCP for live rendered-page audits; your own website or pages to audit. Optional: free Google Search Console access for indexation evidence. No paid APIs. Install "SEO Optimization Skill for Muse" for me. Runs evidence-led SEO audits: live Lighthouse SEO and Agentic Browsing checks, crawl/index controls (robots.txt, meta robots, canonical URLs), XML sitemaps, on-page optimization (titles, meta descriptions, headings, image SEO, internal linking), JSON-LD structured data, mobile and international SEO, plus honest AI-discoverability guidance (crawler controls, llms.txt reality check). Repository: https://raw.githubusercontent.com/addyosmani/web-quality-skills/afa8da942115f2961fdbfa80807ea0b232ff6c00/skills/seo/SKILL.md Pinned version: install the code at commit afa8da942115f2961fdbfa80807ea0b232ff6c00 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files: references/) from the repository path into a temporary folder 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "seo". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. pick Lighthouse CLI or the Chrome DevTools MCP for audits, and point it at the pages to audit). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- afa8da9 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.