Integrations
Connect AnswerLens where your team already reviews work.
Start with GitHub Actions for PR checks. Add provider-based evals, Search Console imports, or Bing helpers only when they help validate what the basic audit already found.
What ships now
Current integrations
| Integration | What it does |
|---|
| GitHub Action | Runs AnswerLens in pull requests, workflow_dispatch runs, and artifact uploads. |
| OpenAI and Perplexity eval | Adds eval-mode benchmarking when you want answer quality checks on top of audit. |
| Search Console import | Validates key-page evidence against imported page-level Search Console exports. |
| Bing / IndexNow helper | Adds helper-mode validation and candidate URL preparation without live submission. |
| Release assets and Pages | Turns demo outputs and docs into reusable public pages and downloads. |
Suggested path
How teams usually start
- Open the live demo report.
- Run the sample-site demo locally.
- Run one real-site audit.
- Add the GitHub Action when the report is useful.
That order keeps setup understandable without turning every integration into a separate product.
External setup
Starter files
The external-repo setup is public and copyable.
Use the starter overview when you need a citable explanation of the .github/answerlens/ layout before handing someone the raw example files.
That keeps the Action setup clear for forks, releases, and external guides.
What this connects to
Related proof pages
- FAQ: answer first-run workflow questions.
- Compare: explain how the GitHub workflow differs from hosted dashboard products.
- Pricing: explain where Action and eval usage create variable cost.
- Security: explain secret handling and review expectations.
- Starter bundle: show the external-repo layout and report review order.
- Developer advocacy teams: connect integrations to docs and examples.