AnswerLens

Audit product pages, review the report, and fix what AI assistants cannot read clearly.

Language: English / 简体中文

Demo report

See the report before you run anything.

The static-good demo shows the finished AnswerLens output: what changed, what is trustworthy, and which file to open first. Use it to decide whether the workflow is worth trying on one public site.

Demo score

90

The current sample-site score.

Key pages

11

Critical pages found in the demo site.

Run kind

audit

The demo uses the core audit path.

Report schema

0.3.0

Report artifact contract, not the package release.

What to look at

Start with the summary, then check the scorecard and fixes.

The demo is here to answer three visitor questions: what do I get, can I trust the evidence, and what would I do next?

share-summary.md

Start here for the plain-language audit story.

scorecard.md

Use this to verify coverage, checks, and score drivers.

recommendations.md

Use this to turn gaps into page changes.

Run metadata

Latest demo run

  • Site: AnswerLens static-good fixture demo
  • Mode: audit
  • Generated: Apr 28, 2026
  • Artifact schema version: 0.3.0
  • Rule version: 2026-04-14

https://fixture.local is the stable hostname inside the public demo fixture, not the AnswerLens site URL.

Example

Share summary contract

# Example AnswerLens Share Summary

> CI for AI discoverability.

This is a shortened example of the share layer produced by `corepack pnpm demo:fixture`.

## PR-ready summary

```md
## AnswerLens audit

**CI for AI discoverability.** Readiness: **90/100**. VAVR: **pending eval**.

### AI may miss this product because

- Thin key page: add plain-language explanations, evidence blocks, and stronger sections.

### Recommended next fixes

- Tighten structure and schema alignment on key pages
```

## Why this matters

This block is designed for pull requests, issues, and release notes. It gives teams a concrete before/after review unit without turning AnswerLens into a ranking promise or consumer AI UI scraper.

Report excerpt

Latest run excerpt

# AnswerLens Share Summary

> CI for AI discoverability.

Audit whether a product site can be read, cited, compared, and recommended by AI systems.

## Run

- Demo site: AnswerLens static-good fixture demo
- https://fixture.local is the stable fixture hostname inside the public demo fixture, not the AnswerLens site URL.
- Mode: Audit
- Run ID: 2ca954a0-9ff7-429e-973a-0718d650aebb
- Generated: 2026-04-28T02:37:15.912Z
- Rule version: 2026-04-14

## Metrics

| Metric | Value |
| --- | --- |
| overallScore | 90 |
| vavr | Pending |
| crawledPages | 11 |
| discoveredUrls | 11 |
| keyPageCount | 11 |
| missingPageTypes | none |



## AI may miss this product because

- **Thin key page** (warn, https://fixture.local/): Add plain-language explanations, evidence blocks, and stronger sections.

## Top fixes

- **Tighten structure and schema alignment on key pages**: Higher extraction quality and fewer ambiguous summaries.

## Shareable artifacts

- [share-summary.md](share-summary.md)
- [share-summary.zh.md](share-summary.zh.md)
- [share-summary.json](share-summary.json)
- [pr-snippet.md](pr-snippet.md)
- [pr-snippet.zh.md](pr-snippet.zh.md)
- [scorecard.md](scorecard.md)
- [scorecard.zh.md](scorecard.zh.md)
- [recommendations.md](recommendations.md)
- [recommendations.zh.md](recommendations.zh.md)
- [issues.json](issues.json)
- [site-audit.json](site-audit.json)
- [index.html](index.html)
- [index.zh.html](index.zh.html)
- [normalized-pages.json](normalized-pages.json)
- [competitor-diff.md](competitor-diff.md)
- [run.json](run.json)

## Guardrails

AnswerLens does not scrape consumer AI UIs, auto-post content, or guarantee answer-surface rankings.

After the demo

Make the demo useful on your own site.

Once the output makes sense, recreate it locally, run one public product site, then move the same report set into GitHub Actions.

  1. 1

    Recreate the sample locally

    Generate the same report files on your machine and confirm the CLI path works.

    Run sample
  2. 2

    Audit one public site

    Use the 5-minute quickstart on a product site your team can inspect.

    Open quickstart
  3. 3

    Review the first real report

    Read the summary, scorecard, and fixes before turning the path into CI.

    Open starter
  4. 4

    Add the Action

    Put the same report files into pull requests after the local audit feels useful.

    Open Action docs