Multi-page Lighthouse audit via the MIT-licensed Unlighthouse CLI. Free-tier alternative to running PageSpeed against every URL on a site — no API quota burn, runs locally.
Scanned 9/6/2026
Install to Claude Code
npx -y skills add Infrasity-Labs/dev-gtm-claude-skills --skill seo-unlighthouse --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Seo Unlighthouse?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/infrasity-labs-seo-unlighthouse-4cb4a26b)More formats (shields.io, HTML) on the badges page.
---
name: seo-unlighthouse
description: Multi-page Lighthouse audit via the MIT-licensed Unlighthouse CLI. Free-tier alternative to running PageSpeed against every URL on a site — no API quota burn, runs locally.
metadata:
compatibility: "Requires Node 18+ and the unlighthouse-cli npm package. Run extensions/unlighthouse/install.sh to pre-warm."
---
# seo-unlighthouse
Run Lighthouse against every URL on a site (up to a configurable cap)
and aggregate the results. Useful when:
- PageSpeed Insights' free quota (25k QPD) isn't enough for a large site.
- You want offline / local CWV measurement (CI integration, restricted environments).
- You need a quick site-wide regression check after a deploy.
## Prerequisites
- Run `extensions/unlighthouse/install.sh` (no API key needed).
- Node 18+ on `$PATH`.
## Routing
| Command | Effect |
|---|---|
| `/seo unlighthouse <url>` | Mobile audit, up to 200 routes, JSON+HTML report in a temp dir |
| `/seo unlighthouse <url> --device desktop` | Desktop form factor |
| `/seo unlighthouse <url> --max-routes 50 --output-dir ./reports` | Cap + persist |
All flags forward to `scripts/unlighthouse_run.py` which handles
url_safety pre-flight and subprocess timeout management.
## Output handling
The wrapper reads `ci-result.json` from the Unlighthouse output dir and
returns it parsed. Aggregate fields:
- `score.performance` (median across audited routes)
- `score.accessibility`, `score.bestPractices`, `score.seo`
- Per-route breakdown is available in `<output_dir>/ci-result.json`
## Cross-skill delegation
- For single-URL field data (CrUX), use `seo-google psi` / `seo-google crux`.
- For LCP subpart decomposition on slow pages, use the
`scripts/lcp_subparts.py` workflow (Phase C).
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!