AI Search Audit
Real crawl · Lighthouse via PageSpeed Insights · 6-pillar GEO/AEO analysis
⚙️ API Keys PSI: not set
click to expand ▼
PageSpeed Insights
Free key from Google Cloud Console → Enable PageSpeed Insights API → Create credentials → API key. Takes 2 min. Stored in memory only, never sent anywhere except Google's API.
Without a key: Jina crawl + AI analysis still run. Lighthouse scores won't appear.
Context:

/ 100
Lighthouse Scores Mobile Desktop
What we actually fetched
Pillar Scorecards — click to expand
Priority Gaps
Platform Notes
Action Plan
What Not To Do
🔬 Go deeper with Chrome DevTools MCP (local)

This audit used PageSpeed Insights for Lighthouse scores. For full Agentic Browsing audits, device emulation, performance traces, and accessibility tree inspection, run Chrome DevTools MCP locally in your AI coding agent (Claude Code, Cursor, Cline):

Install (one command)
npx chrome-devtools-mcp@latest
Claude Code config (~/.claude/mcp.json)
{ "mcpServers": { "chrome-devtools": { "command": "npx", "args": ["-y", "chrome-devtools-mcp@latest"] } } }
Example prompts once installed
Run a Lighthouse audit of https://example.com with formFactor mobile Emulate a Pixel 7 and screenshot the homepage Check the agentic browsing score for https://example.com Run performance_start_trace on https://example.com and find LCP blockers

Requires Node.js 20.19+ and Chrome stable. Lighthouse audit docs · Emulation docs

Enter a URL above to run a real crawl audit.