What it checks
Check the public story
Can someone understand your category, proof, pricing, comparisons, and setup path from the public page alone? AnswerLens checks those signals, plus schema and internal links.
CI for AI discoverability.
AnswerLens
Use AnswerLens when your website is the source material for AI answers. It checks whether public product pages are clear, evidenced, and easy to review, then writes GitHub-ready report files.
Product fit
Does AnswerLens fit your site?
It is built for teams that want public pages and GitHub review to stay in sync. It is not a hosted monitoring dashboard, a ranking tool, or a consumer AI scraper.
What it outputs
Review the evidence
The product surface is the report set: share-summary.md, scorecard.md, recommendations.md, and JSON results your team can review in PRs or issues.
Who should use it
Best fit
Use it when product marketing, docs, developer advocacy, or open-source maintainers share responsibility for pages that need to stay understandable and citable.
Try it in this order
See the output before setup, then run one real page.
Start with a finished report, recreate it locally, run one public product site, and add GitHub Actions only after the report is worth reviewing again.
- 1
Open the demo report
Inspect the finished HTML report, summary, scorecard, and recommendations before installing anything.
Open demo - 2
Run the sample site
Recreate the same output locally so the command and report files are familiar before you use your own URL.
Run sample - 3
Audit one public site
Run the quickstart against one product page set and read the summary before changing copy or wiring CI.
Open quickstart - 4
Add the Action
Move the same report set into pull requests with the pinned starter workflow.
Open Action docs
Demo score
90
Current score from the stable public sample site.
Key pages
11
Critical pages found in the demo site.
First report
share-summary.md
Start here before reading the scorecard and recommendations.
Latest release
v0.3.2
Current published version line.
Report package
You get a report set your team can actually review.
The useful output is simple: a short summary, a scorecard, and a fix list you can discuss in product, docs, or PR review.
share-summary.md
Share the audit in a PR, issue, or team note.
scorecard.md
Inspect the score, page coverage, and failed checks.
recommendations.md
Turn gaps into copy, proof, and structure fixes.
When you need a versioned download, open the latest release.
Current signal
What the demo says right now
Demo site: AnswerLens static-good fixture demo
https://fixture.local is the stable hostname inside the public demo fixture, not the AnswerLens site URL.
Top issue: Thin key page (warn) - Add plain-language explanations, evidence blocks, and stronger sections.
Top fix: Tighten structure and schema alignment on key pages - Higher extraction quality and fewer ambiguous summaries.
Open reports in order: share-summary.md, then scorecard.md, then recommendations.md.
Product pages
What to read next
Open these pages when you need pricing, trust, FAQ, comparison, or setup context beyond the demo report.
- Pricing and packaging: open-source, BYOK, and release-asset cost model.
- Security and trust: secrets, review flow, and non-goals in one page.
- Docs index: activation references, scoring notes, and GitHub Action usage.
- Starter bundle: external
.github/answerlens/layout before CI setup. - FAQ: first-run questions in visible, citable language.
- Compare: how AnswerLens differs from dashboard-first AI visibility tools.
- Integrations: GitHub Actions and validation helpers together.
Team fit
Who usually reads next
These use-case pages show the jobs teams usually try first.
- Product marketing teams: turn homepage, pricing, and comparison gaps into reviewable fixes.
- Developer advocacy teams: strengthen docs, proof pages, and self-serve evaluation paths.
- Open-source maintainers: use README, releases, Pages, and reports as the public distribution stack.