01
Understand my site
Build an editable website profile from homepage, sitemap, robots, RSS, schema, sampled pages, and owner context.
Site type and audience
Content model
Technical snapshot
How it works
Search growth operating system for vibe-coded websites.
Search Lighthouse is built for founders who can ship fixes quickly, but need a clear answer to three questions: what does search see, what is blocking growth, and what should be fixed next?
Current domain
searchlighthouse.com
Current State
Ready for First Scan
Current Limitation
The site needs its first crawl and search evidence before prioritizing growth work.
Recommended Action
Run a public scan, then add Search Console data when deeper diagnosis is needed.
Expected Outcome
Prioritized implementation-ready tasks.
Core workflow
One evidence-to-action loop.
02
Analyze search growth
Combine site-wide crawl evidence with Search Console CSV/ZIP or Pro OAuth data to explain what Google is testing.
Site-wide structure
Queries and pages
CTR and exposure gaps
03
Inspect Google indexing
Pro Indexing Insights runs from Monitoring, works through URL Inspection caps in the background, and creates a normal report when complete.
GSC sitemap snapshots
Full URL review
Indexing Insights report
04
Tell me what to fix
Turn findings into priorities, tracked tasks, and implementation-ready briefs for Codex, Cursor, Claude Code, or markdown.
Fix Now findings
Task drawer
Copyable implementation brief
Don't write prompts.
Search Lighthouse turns findings into implementation-ready tasks for Codex, Cursor, Claude Code, and markdown workflows.
Codex
Cursor
Claude Code
Markdown workflows
Evidence
Report
Task
Implementation
Verification
Generate For
Codex
Cursor
Claude Code
Ship
Replace generic scores with stage, blocker, and next action.
Scores still exist as signals, but the dashboard leads with what an operator actually needs: current state, top priority, recommended action, and the evidence behind it.
Data needed
Needs Search Data
Typical Symptoms
- No Search Console rows yet
- Only crawl evidence is available
Focus
- Run the first scan
- Add GSC or CSV data
Stage 0
Not Indexed
Typical Symptoms
- Few or no indexed pages
- Sitemap, robots, or canonical uncertainty
Focus
- Fix discovery
- Clarify indexable pages
Stage 1
Google Testing
Typical Symptoms
- Low CTR
- Limited page visibility
Focus
- Improve snippets
- Improve internal links
Stage 2
Early Growth
Typical Symptoms
- Some pages are working
- Topic coverage is uneven
Focus
- Expand proven topics
- Strengthen GEO readiness
Stage 3
Authority Site
Typical Symptoms
- Search visibility depends on trust
- AI citation readiness matters
Focus
- Maintain source quality
- Monitor regressions
Data model
Store enough history to explain whether fixes worked.
Search Lighthouse keeps site context, search rows, indexing evidence, reports, implementation tasks, task attempts, verification, monitoring runs, and usage history so later analysis can explain what changed.
Website profile
Editable AI summary, business model, content model, audience, sitemap state, robots state, schema, RSS, and test accounts.
Search snapshots
Imported rows, normalized metrics, selected time windows, connected GSC metadata, and last fetched timestamps.
Google indexing evidence
GSC sitemap snapshots, tracked URL inventory, URL Inspection review state, and Pages exports when users upload them.
Task history
Saved findings, task status, report history, implementation tasks, verification attempts, monitoring runs, and usage events.
The final output is implementation work.
Every Fix Now finding can become one scoped task with evidence, acceptance criteria, and a markdown brief that can be pasted directly into Codex.
Sample report output
Clear enough to ship
Current StateGoogle Testing
Top PriorityImprove exposed snippets
Recommended ActionRewrite title templates
EvidenceSearch impressions without clicks
# Implementation Task Brief Goal Improve click-through from exposed search pages. Source Finding Low CTR on pages already receiving impressions. Task Rewrite the shared title and meta description template for exposed pages. Acceptance Criteria - Preserve existing routes and page content - Keep titles specific to each page entity - Add a concise benefit in the meta description Verification Wait for fresh Search Console data, then compare CTR and clicks for the affected pages.