Site audits - Lightsage
Site Audit commands
Site Audit commands read the latest stored website audit for the organization associated with your API key. They do not start a new crawl.
Commands
| Command | Description |
|---|---|
lightsage site-audits list |
List every audited page and its actionable issues. |
lightsage site-audits retrieve --site-id <site_id> |
Retrieve one audited page’s issues and recommended fixes. |
List website audit results
lightsage site-audits list --output-format json
The response contains a short audit summary and a pages array. Each page includes its URL, score, priority, issue count, and actionable issues. Each issue explains what is wrong, the supporting evidence, and the recommended fix:
{
"site_id": "3f93c9d4-0478-53f3-812f-3e5de85a8bc7",
"url": "https://example.com/docs",
"title": "Developer documentation",
"score": 84,
"grade": "B",
"status": "warning",
"priority": "medium",
"issue_count": 1,
"issues": [
{
"id": "markdown-support",
"category": "access",
"severity": "warning",
"message": "No agent-readable Markdown response was found.",
"recommendation": "Serve Markdown when the client requests it.",
"evidence": "Content-Type was text/html."
}
]
}
If the organization has not completed a website audit, audit is null and pages is empty. Use --jq to select IDs and page scores:
lightsage site-audits list \
--output-format json \
--jq '.pages[] | {site_id, url, priority, issue_count, issues}'
Retrieve one audited page
Copy a site_id from the list response:
lightsage site-audits retrieve \
--site-id 3f93c9d4-0478-53f3-812f-3e5de85a8bc7 \
--output-format json
The detail response returns that page directly with the same focused issue fields shown above. A site_id is derived from the organization and normalized page URL. Use the ID returned by site-audits list rather than constructing it yourself.