Findings

Evidence-linked strengths, weaknesses, and prioritized recommendations from every scan.

Updated 2026-08-06

Findings are the evidence-backed story behind your score. Each scan produces strengths, weaknesses, and recommendations. Every item cites crawl evidence — page URLs plus short excerpts — so you can verify and ship fixes with confidence.

Finding types

TypePurposeTypical count
StrengthsFactors that help assistants recommend you (clear product pages, trust signals, docs)Up to 5 per scan
WeaknessesGaps that block confident recommendations (missing FAQ, thin About, blocked crawlers)Up to 5 per scan
RecommendationsPrioritized actions (priority 1–10) with why, impact, and evidenceUp to 8 per scan

Evidence-linked recommendations

Every recommendation includes:

  • Priority1 is highest urgency; sort and ship in that order when capacity is limited.
  • Why — why the gap matters for AI discoverability.
  • Impact — expected effect on visibility if fixed.
  • Evidence — one to three crawl citations (url + excerpt) from your site corpus.

Recommended workflow

  1. 1

    Sort by priority

    Start with priority 1–3 recommendations. Free plans show a preview (typically top recommendations and a limited weakness set); Pro unlocks the full list.

  2. 2

    Map to Studio assets

    Many recommendations map directly to Content Studio types — faq, schema, llms_txt, docs, comparison, and more.

  3. 3

    Add to the weekly plan

    Promote findings into the Weekly Execution Plan so work is sequenced with effort and impact labels.

  4. 4

    Verify after ship

    Rescan or wait for monitoring to confirm weaknesses clear and strengths hold.

Plan gating

Free workspaces see a gated preview: a limited number of recommendations and weaknesses, with the remainder locked until upgrade. Pro shows all findings and opportunities. Locked counts appear in the report UI so you know what Pro unlocks.

Business profile section

Alongside findings, each analysis extracts a business profile: product, target customers, positioning, messaging clarity, documentation quality, and trust signals. Use it as the source of truth when generating Studio assets so FAQ and schema stay consistent with how the crawl understands you.

FAQ

Why is a finding empty or thin?

Thin crawls (JS-only pages, blocked bots, timeouts) reduce evidence. Fix crawl access first via the technical audit, then rescan. See also Missing results.

How are findings different from opportunities?

Findings describe your site’s structural strengths and gaps. Opportunities emphasize competitive prompt wins — where peers get recommended and you do not.

Can I export findings?

Share a public report at /r/[slug], or pull tasks into the weekly plan and Studio fix packs for implementation handoff.

Related

Still stuck? Contact support with your project URL and what you already tried.