Package Exports

pagesight
pagesight/src/index.ts

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (pagesight) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

Pagesight

See your site the way search engines and AI see it.

npm install pagesight

Your AI assistant can write your code. Now it can see your site. Index status, performance, real-user metrics, search traffic, meta tags, structured data, AI crawler access — one package, one call.

=== Site Audit: https://example.com ===

HIGH    Missing canonical URL
HIGH    7,772 sitemap URLs submitted, 0 indexed
MEDIUM  Missing og:image — no social preview image
MEDIUM  Accessibility score: 89/100
LOW     Missing Twitter Card tags
LOW     No structured data (JSON-LD) found

Tools

Tool	What it does
`audit`	One-call site audit. Runs all checks in parallel. Returns prioritized findings.
`pagespeed`	Lighthouse scores, Core Web Vitals, opportunities, failing audits with fix links.
`metatags`	OG, Twitter Card, canonical, JSON-LD with schema validation, redirect chain, image validation.
`inspect`	Google index status, canonical choice, crawl state, rich results.
`sample_inspect`	Sample URLs from a sitemap and batch-inspect. Diagnoses indexing patterns.
`performance`	Search analytics — clicks, impressions, CTR, position. `compare: true` for period-over-period.
`crux`	Real-user Core Web Vitals (p75, histograms).
`crux_history`	CWV trends over time — up to 40 weekly data points.
`robots`	robots.txt validation (RFC 9309) + AI crawler audit (139+ bots).
`sitemaps`	Search Console properties and sitemaps with submitted/indexed counts.
`setup`	Auth status and OAuth setup.

Setup

Add to your MCP config:

{
  "mcpServers": {
    "pagesight": {
      "command": "npx",
      "args": ["pagesight"],
      "env": {
        "GSC_CLIENT_ID": "your-client-id",
        "GSC_CLIENT_SECRET": "your-secret",
        "GSC_REFRESH_TOKEN": "your-token",
        "GOOGLE_API_KEY": "your-api-key"
      }
    }
  }
}

robots, metatags, and pagespeed work without credentials.

Full setup

Google Cloud Console — enable Search Console API, PageSpeed Insights API, Chrome UX Report API
Create OAuth client ID (Desktop app) + API key
Configure:

GSC_CLIENT_ID=your-client-id.apps.googleusercontent.com
GSC_CLIENT_SECRET=your-client-secret
GSC_REFRESH_TOKEN=your-refresh-token
GOOGLE_API_KEY=your-api-key

Why Pagesight

Every data point comes from a verifiable source. Google's APIs, real Chrome users, RFC 9309, schema.org, a community-maintained bot registry. No invented scores. No rules we can't cite.

"Title must be under 60 characters" — Gary Illyes: "an externally made-up metric."
"Only one H1 per page" — John Mueller: "You can use H1 tags as often as you want."
"Minimum 300 words per page" — Mueller: "not a quality factor."

Pagesight reports what the sources report. Nothing more.

License

MIT