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 Stage
Ready for First Scan
Biggest Problem
The site needs its first crawl and search evidence before prioritizing growth work.
Next Action
Run a public scan, then add Search Console data when deeper diagnosis is needed.
Expected Outcome
A prioritized fix plan with implementation-ready tasks.
Core workflow
Only three product actions.
02
Analyze my search growth
Normalize Search Console CSV, ZIP exports, and OAuth data into trend windows that explain what Google is testing.
24h, 7d, 30d, 90d windows
Queries and pages
CTR and exposure gaps
03
Tell me what to fix
Turn findings into priorities, tracked tasks, and implementation-ready briefs for Codex, Cursor, Claude Code, or markdown.
Top 3 priorities
7/30/90 day roadmap
Copyable build 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
Search Analysis
Finding
Fix Plan
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 stage, biggest problem, top priority, and the next implementation step.
Data needed
Needs Search Data
Typical Symptoms
- No Search Console rows yet
- Only crawl evidence is available
Focus
- Run the first scan
- Add GSC, Bing, 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, imported search rows, trend summaries, and optimization history so future analysis can compare before and after.
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.
Fix history
Saved findings, issue status, report history, fix plans, and usage events so the system can compare change over time.
The final output is implementation work.
Every mature report should produce priorities, expected result, difficulty, and a markdown brief that can be pasted directly into Codex.
Sample report output
Clear enough to ship
Current StageGoogle Testing
Biggest ProblemLow CTR
Next ActionRewrite title templates
Expected ImpactMedium
# Search Growth Plan Goal Improve indexability and CTR for the selected domain. Tasks 1. Fix sitemap consistency 2. Improve title templates for exposed pages 3. Add citation-ready entity blocks 4. Strengthen internal links Constraints - Minimal code changes - Preserve routes - Validate with the next 30-day trend window