Checking your site before it goes live

vage check

Renders the whole site without writing anything, then reports:

• broken links, links to drafts, and links that redirect
• missing assets, malformed URLs and script URLs
• missing or duplicate titles and descriptions
• canonical URLs that are relative or point to another site
• invalid JSON-LD, and Article data missing recommended fields
• basic accessibility: lang, image alt text, link text, image dimensions
• undeclared analytics events

Errors exit with code 1. --strict also fails on warnings, and --json gives machine-readable findings.

vage audit

Builds the site, then checks every page against size budgets (JavaScript, CSS, images, fonts, total, requests) and runs axe accessibility rules.

npx vage audit                  # budgets and accessibility
npx vage audit --lighthouse     # also Lighthouse in Chrome (npm i -D lighthouse)
npx vage audit --url https://your-site.com   # PageSpeed and real-user CrUX data

--url uses your own Google API key: set PAGESPEED_API_KEY, or save one with npx vage connect pagespeed.

Lab scores are one simulated page load and vary between runs. Field data (CrUX) reflects real Chrome users at the 75th percentile, and it's missing for sites without enough traffic. Passing checks don't guarantee rankings, rich results or AI citations.