Understand the report

Your report is the Infrared Signal readout: a 0–100 AI Visibility Score, narrative summary, strengths and weaknesses, and evidence-linked findings. Read it as a structural readiness instrument — then decide what to fix next.

The AI Visibility Score (0–100)

The score aggregates observable dimensions such as crawl readiness, entity clarity, and answer coverage. It estimates how prepared your site is to be understood and recommended by assistants. It is not a guarantee of mentions, rankings inside a model, or revenue.

Score bands

Summary

The summary translates pipeline output into a short narrative: what the scan found, where you look strong, and where structural gaps concentrate. Use it to brief stakeholders who will not read every finding.

Findings (evidence-linked)

Findings are actionable issues or opportunities. Each should be interpretable without guessing — and where evidence exists, linked to a URL plus an excerpt from your site or related artifacts. That evidence trail is what makes VisibleMax operational instead of advisory-only.

• Prioritize findings that block crawl or entity clarity before long-tail content ideas.
• On Free, you see top findings only — remaining recommendations/weaknesses may be locked until Pro.
• Map findings to owners (web, content, legal/trust) before the weekly plan meeting.

Strengths and weaknesses

Reports surface strengths (keep and amplify) and weaknesses (fix first). Free may show a limited weakness set. Pro reveals the full opportunity and recommendation sets used by the weekly plan and Content Studio.

Public share links

Completed reports can be shared via public URLs at `/r/[slug]`. These views are designed for stakeholders and screenshots: score and top recommendations in a redacted, shareable form. Do not put secrets in public page content you expect to appear in evidence.

• Share /r/[slug] with founders, agencies, or customers evaluating AI readiness.
• Keep the in-app report as the source of truth for gated Pro detail.
• Company entity storytelling may also appear on /c/[slug] profiles when published.

Suggested reading order

1. Score + band — set expectations.
2. Summary — align the team on the story.
3. Weaknesses / top findings — pick the first ship list.
4. Strengths — avoid regressing what already works.
5. Public link — socialize the baseline before changes.

Common misreads

• “Score dropped, so AI stopped liking us.” — Often a crawl or content regression; inspect evidence URLs.
• “We are Strong, so we can ignore findings.” — Strong means readiness, not saturation of every buyer prompt.
• “Free locked items are unimportant.” — They are gated for plan reasons; impact may still be high.
• “A competitor mention means we failed.” — Probe outcomes vary; track trends across rescans on Pro.