# Free AI Visibility Report: live page and newsletter experiment

The plain `/free-visibility-report` URL retains the existing production landing design and its default intake. The refreshed experience is an explicit campaign opt-in at `/free-visibility-report?variant=newsletter`. Unknown, absent, differently cased or repeated variant parameters keep the default. There is no random traffic allocation and no landing-page cookie assignment.

The newsletter variant’s free AI visibility report tests a starting sample of 100 AI-generated buyer questions on ChatGPT. See how often a brand appears, which competitors are mentioned, what AI says about it, and which sources are cited in the answers.

The free report checks ChatGPT only. It is a snapshot, not ongoing tracking or a ranking across every AI model. The questions are generated around the website and business context; they are not measured search volume or a log of real users’ queries. The report shows the actual answer count used in its scores.

## What is included?

- Visibility: the percentage of tested answers that mention the brand.
- Share of voice: the brand’s share of all tracked brand mentions and its competitive ranking.
- Your topics: share of voice across buyer-question topic groups and the competing brands in each group.
- Sentiment: how positively or negatively AI describes the brand, with saved brand-assessment excerpts where available. These assessments are separate from the sources cited in buyer-question answers.
- Questions and answers: the tested prompts, example wins, and answers where competitors outperform the brand.
- Sources and pages: websites and exact pages cited in the buyer-question answers.
- Site health: homepage technical and AI-readiness checks when audit results are available.
- Next steps: three 30-day objectives identified by Searchable’s Agent, with a plan behind each goal.

## How do I get the report?

1. Select Brand or Agency. Agencies choose whether the report is for their agency or a client.
2. Enter the website to analyze and your name and work email.
3. Verify the email address with a six-digit code.
4. Follow the preparation progress or return through the emailed report link when it is ready.

Preparation takes a few minutes, though timing varies. No payment details are required. The free report does not automatically activate full platform access.

[Try the newsletter report flow](https://app.searchable.com/ai-visibility-report?variant=newsletter)

## How do I interpret the scores?

Visibility answers “How often does the brand appear?” If a brand appears in 65 of 100 tested answers, visibility is 65%.

Share of voice answers “How much of the conversation does the brand own?” It uses all tracked brand mentions, so its denominator differs from visibility.

Sentiment answers “How positively or negatively does AI describe the brand?” It is separate from mention frequency.

Answers can vary between runs and change as models and websites change. A mention is not a visit, a sale or a guaranteed ranking. The public HubSpot example uses sanitized saved report data, not a live assessment of the visitor’s website.

## Can I run a report for a client?

Yes. Select Agency, choose the client report option and enter the client website. You can receive the report at your own work email address.

## How do I get full platform access?

Speak with the Searchable team. A demo can cover ongoing tracking, a wider prompt universe, detailed topic and sentiment analysis, Searchable Agent, AI traffic analytics and content tools. The team helps activate the account and confirms model and feature availability. The free report does not include free tracking across Gemini, Claude, Perplexity or every other model.

[Talk to the Searchable team](https://www.searchable.com/contact-sales)

## Free report usage

More than 7,500 free reports have been generated across versions of Searchable’s free-report experience. This conservative lower bound is based on a 17 October 2026 snapshot of completed initial reports for verified external recipients, excluding internal, test and outbound cohorts and deduplicating reruns. It is not a count of paid customers or of today’s 100-question report version alone.

Free reports have been requested by people using verified matching work-email domains at Coca-Cola, Salesforce, Dell, PwC, ADP and Thomson Reuters. This describes report usage, not a corporate endorsement.

The newsletter hero says “Check your AI visibility. Get your free report in minutes.” Its heading and copy container allow up to 1080px on wide screens, while the subtitle keeps its existing measure and mobile content stays contained. The field label is “Enter the website you want to check”, with “e.g. apple.com or disney.com” as the placeholder. Its native GET submit button is nested inside the same rounded input container, matching the original joined control. The inset orange button stays within the field on phones too, with a compact “Get report” label and the full accessible action name. Valid websites and campaign parameters carry into Arya’s existing `/ai-visibility-report` signup, with the entered website taking precedence over any arriving `domain` value. The globe slot previews a favicon after a syntactically valid host stays unchanged for 300ms, using the report’s existing favicon URL helper. The globe remains visible while loading or on failure; invalid input and host changes immediately hide any previous site’s icon. Favicon availability never blocks submission. Desktop fine-pointer visitors get input focus without scrolling; mobile visitors do not get an unsolicited keyboard. Inline errors keep invalid websites on the page. The hero preserves “No credit card required”. Its secondary “Explore the report” link and arrow are omitted, leaving website entry as the hero action. At Sam’s request, the separate trust lines are combined into one larger statement above the logos: “Trusted by 30,000+ marketers and professionals from leading brands.” The trust heading scales from 22px to 28px and highlights only “30,000+” in Hi-vis Orange 500. This is a platform-wide trust statement, not a count of free reports. The logo wall displays the first ten curated logos (two desktop rows), retaining the full 20-brand source evidence, with no section divider above or below the proof. The ten curated logos remain sourced from the verified free-report recipient snapshot; that evidence is separate from the platform-wide trust statement. The preview renders the actual report components with a sanitized, saved HubSpot report at the same-origin `/free-visibility-report/example` route in every environment. The example is a separate document so its report navigation and scroll region do not affect the landing page. Its initial iframe URL has no fragment, preventing browser anchor navigation from pulling fresh landing-page visits away from the hero. A landing-owned control-panel frame shows the example name and read-only status. The inline preview is inert and ignores pointer input, so wheel and touch gestures continue scrolling the page. Its “Click or tap to view report” button opens the actual report in the shared Radix dialog, with a visible close control, contained scrolling and focus restoration on close. Only one iframe is mounted at a time; the inline frame remounts when the dialog closes. The dialog shows the same hydrated report on production and local previews; there is no screenshot fallback or dependency on a second local server. The report reflows to the available mobile width and the close toolbar remains visible. Escape from the embedded document closes the preview and restores focus. The landing page does not recreate the report header, sidebar, charts, controls or metrics. Desktop and mobile layout and charts belong to the actual report. The public example’s report headings use the existing Geist Sans (`font-sans`) typeface, keeping their report sizes and spacing. The landing uses its opt-in public preview mode: chapter navigation, topic expansion, answer disclosures and prompt filters work on the saved data. Account controls stay locked, every commercial action requests a free report, and the embedded YouTube/demo card is omitted. A page-owned “Want your own report?” invitation is fixed at the landing page’s bottom-right corner on desktop, with a 44px dismiss button. Its orange gradient header is 160px tall on desktop and 128px on mobile, with a centred white “Free visibility report” badge. At 850px and below, or on viewports 640px tall and below, it sits in normal page flow so it does not obscure the report. The intake destination is shared with the landing CTA and includes the same URL/cookie attribution; embedded links navigate the top frame. Ordinary viewer reports keep their existing interactive behavior and booking dialogs. The example makes no report, PDF or brand-colour API calls, contains no report access token or viewer details, and cannot activate an account or booking. It is excluded from indexing. Production never embeds a developer URL or the production app origin, and existing framing protections remain intact. All eight offer explanations remain in server-rendered HTML in the optional “What’s included in your free report” disclosure, presented as a compact two-column table with section row headers and concise descriptions. Cells wrap long words at mobile widths and with enlarged text without requiring horizontal scrolling. Mobile logos stay contained within their grid cells. Conditional audit availability and saved assessment excerpt availability remain explicit. The report preview leads directly into the free-report CTA; there is no separate screenshot gallery. The taller orange CTA uses the shared `DarkFinalCtaAsciiBackground` Searchable logo shader in white without the shadow logo, behind the copy and button. It has a 360px minimum height on desktop and 400px on narrow mobile layouts, allowing content to grow. The repeated report-request sentence and link below that card are removed.

The landing page leads with the report offer, verified company-logo proof and the eight report contents, then a direct free-report CTA and FAQs. There are no standalone process, methodology or full-platform sales sections. Delivery, verification, calculation and snapshot details remain in the FAQs. All inline conversion links enter the free-report intake. Full-platform activation details remain in the access FAQ.

The hero subtitle interweaves three compact inline metric labels into one sentence: Visibility, Share of voice and Sentiment. Each inherits the surrounding subtitle’s font size, weight and line height. Labels and their proportionally sized icons use Hi-vis orange 500, with one matching dotted underline spanning both icon and label, without an icon background, enclosing pill or separate badge row. Hovering, keyboard focus or tapping opens a short plain-language definition through the shared Radix tooltip. Escape and outside interaction dismiss it. The terms use ordinary inline text flow to align their text baseline with the sentence. They are native buttons with visible keyboard focus; their labels are the report’s own metric names.

The page canvas, hero and navigation background are white; the inline metric labels sit directly on that surface.

The hero opens directly with the headline “Check your AI visibility. Get the free report.” at up to 72px on desktop and 44px on mobile. Top padding is 88px on desktop, 72px on tablet and 56px on narrow mobile screens. There is no separate eyebrow label. The subtitle reads “Understand your Visibility, Share of voice and Sentiment in ChatGPT, with a report built around 100 generated buyer questions.”

Connor’s 19 October 2026 search-intent copy pass targets “AI visibility checker” in the absolute page title: “Free AI Visibility Checker: Get Your AI Visibility Report”. The description is “How often does ChatGPT recommend your brand? Get a free AI visibility score and report with competitors, sentiment, and cited sources. No card needed.” Open Graph and Twitter use the same constants. The report heading is “What your free AI visibility report shows.”, the final CTA heading is “See where your brand stands in ChatGPT.” and the FAQ heading is “AI visibility report FAQs.” The page-owned invitation title remains visually identical but is a paragraph rather than another H2. The ten visible FAQs and FAQPage structured data share the same array, including the new “How do I check my brand's AI visibility?” question.

## Experiment routing and source

The default design is preserved in `legacy/content.tsx`, `legacy/below-fold.tsx` and `legacy/free-visibility-report-cta.tsx`, ported from the production landing ref `fc6cb224d58f0ad5aa480031ce22a256b3a31a85`. The hero, report request form, preview, proof and FAQs retain their production content. The legacy form carries `variant=control` to the existing intake, preserving the entered domain and attribution. Shared site navigation and global design tokens remain shared.

The newsletter design uses its existing refreshed components and the hydrated HubSpot example. Every report request explicitly includes `variant=newsletter`, including actions inside the example. Attribution cannot overwrite that fixed variant. The default retains production translation-backed title/description and canonical URL. The newsletter variant uses its refreshed metadata, is `noindex,follow`, and canonicalizes to the plain landing URL. Newsletter requests go directly to Arya’s existing `/ai-visibility-report` signup. That flow submits `experience: "ai_visibility_report"`; its existing backend logic owns provisioning, prompt generation, email events and report routing. The query parameter selects the public landing design and travels as attribution; this landing does not add another persisted backend assignment or change the old signup/report logic. The original CTA remains on `/free-visibility-report/get-report`. Activate the newsletter landing after the existing app experience in #7641 is available on its configured app origin.