Representative example

Last updated

A sample Foundation

Your Foundation is free, and it is the one step we ask you to approve before your Crawl runs. Before AI engines can recommend you, they have to be able to read you, trust the structure, and find the answer. So the Foundation maps your market, buyers, and competitors, then checks the technical state of your site and flags what's blocking citations today. The company below is invented to show the shape. A real Foundation runs on your own category, your own buyers, and a scan of your own site.

  • 48 pages analyzed
  • 5 buyer personas
  • 6 competitors
  • 14 findings
Representative example · illustrative data

This page walks through the foundation. To see how it feeds the measurement that follows, open the sample report →

If you've just started a Foundation, this is what's landing in your account, and how to review it.

A Foundation answers one question before any score is produced: are we measuring you in the right world, and can AI even read you today? It has two halves. First, the market map: your category, the people who buy, what they evaluate, why they search, and who you're compared against. Second, the technical state of your site: whether AI crawlers can reach you, how citable your content is, and the specific findings blocking you. You approve it, and that starts your Crawl. Everything below is built to demonstrate the deliverable. None of it is real customer data.

Overview

The cover: who we analyzed, how much of the site, and the headline count of what we found.

AI Visibility Foundation

[Client]

Work management for distributed teams

[client-website] 48 pages analyzed Analyzed June 2026

Before AI engines can recommend you, they have to be able to read you, trust the structure, and find the answer. This review maps your market, buyers, and competitors, then checks the technical state of your site and flags what blocks citations today.

2 critical 4 high 5 medium 3 low

What this is and what to check

The severity counts are your at-a-glance read on how much is in the way of citations right now. A pile of critical and high findings is common and fixable; it's the map of the work, not a verdict. Confirm the basics first: the right company, the right category, and a page count that looks like your real site, not a stray subdomain.

Company profile

How the engines should resolve what you are: your category, your segment, your products, and the names you go by.

Work management / project management software for distributed teams

Mid-market Async Planner Dependency Tracker Timezone Scheduler

Also known as: [Client], [Client] App, [Client] PM

What this is and what to check

This is the identity every query and score inherits. If the category is wrong, the whole Crawl measures the wrong market. Read it as if an engine wrote it about you to a buyer: is this the category you actually compete in, and are these the products and names buyers would search? The "also known as" list matters because engines have to connect every variant of your name to one company.

Who buys this

The 5 buyer personas that shape how AI describes this category. Your visibility is measured against each. Personas are shown by role, not by name.

Head of Remote Operations

Operations

Director Influence · High Veto power

Project Manager

Delivery / PMO

Manager Influence · High

Engineering Manager

Engineering

Manager Influence · Medium Veto power

RevOps Manager

Revenue Operations

Manager Influence · Medium

Founder / Owner

Executive

Founder Influence · High Veto power

What this is and what to check

Each persona becomes a slice of the query set, so a missing or wrong persona means a missing slice of your market in the final scores. Check that these are the roles who actually sign and use the product, and that whoever really controls the budget is here with veto power. The most common correction is adding the decision-maker who got left off.

Who you're compared against

6 competitors AI weighs you against when buyers ask for recommendations. These define who you're measured next to in share of voice and head-to-head visibility. Shown as illustrative archetypes rather than named brands.

Competitor A primary

The category incumbent buyers benchmark everyone else against.

Competitor B primary

The agency favorite, strong on client-facing reporting.

Competitor C secondary

The dev-tool-native option engineering teams default to.

Competitor D secondary

The all-in-one suite that surfaces in "simple PM" searches.

Competitor E primary

The async/remote specialist closest to your own positioning.

Competitor F emerging

The low-cost challenger that wins on price in early comparisons.

What this is and what to check

This set is the scoreboard your share of voice is measured on, so it has to match reality. The Crawl can also surface "surprise competitors" the engines name that you didn't list, but it benchmarks you carefully only against the brands defined here. The most common correction is adding a competitor you actually lose deals to, or fixing a tier that's set too high or too low.

What buyers evaluate

The capability taxonomy buyers ask about, and where your content reads as strong or thin today. The quote is the buyer's own language for each.

Cross-timezone scheduling strong

"does it handle teams across time zones automatically?"

Async status updates strong

"can we cut standups and still know status?"

Dependency tracking moderate

"can I see what's blocking what across teams?"

Integrations (dev + chat tools) moderate

"does it connect to the tools we already use?"

Resource & capacity planning weak

"can I see who's overloaded before it's a problem?"

Reporting & dashboards weak

"can leadership get a portfolio view without me building it?"

What this is and what to check

Strong means your public content already answers that capability question well; weak means the answer is thin or missing, so an engine reaches for a competitor instead. These ratings preview where the action plan will concentrate. Check that the capabilities you actually win on are here, and flag any "weak" that's really a strength your content just isn't telling.

AI crawler access

2 of 8 AI crawlers are blocked. A blocked crawler cannot index your content, so the engine it feeds can never cite you, no matter how good the page is. This is the first thing to fix.

GPTBot Allowed
OAI-SearchBot Allowed
ClaudeBot Allowed
PerplexityBot Blocked
Google-Extended Allowed
Applebot-Extended Allowed (default)
Amazonbot Allowed
CCBot Blocked

What this is and what to check

This is the most mechanical, highest-leverage part of the whole review. No content fix matters on an engine whose crawler can't reach you. "Allowed (default)" means no rule in robots.txt names that crawler, so it gets in by default — worth an explicit rule, but nothing is blocking it today. We also list any paths robots.txt closes to everyone, since a crawler can be allowed on the site and still locked out of your product pages. There's usually nothing for you to correct here; it's a fix for whoever owns the site's robots.txt and edge rules.

Content quality signals

AI platforms preferentially cite fresh, well-structured, deeply-covered pages they can extract clean passages from. Here's how your indexed pages score.

Structure 74/100
Schema coverage 61/100
Freshness 58/100
Extractability 46/100
Depth of coverage 35/100

What this is and what to check

These scores explain why a page that reads fine to a human still doesn't get cited. Low depth and extractability mean engines can't lift a clean answer from the page; low freshness means it's trusted less. You don't correct these numbers; they set the agenda for the action plan, which targets the weakest signals first.

Findings

14 findings, ordered by severity. Each is a concrete, owner-assigned fix. A representative sample follows.

critical Two AI crawlers are blocked in robots.txt
Crawlability Owner · Web / Eng Effort · Low

What we found

PerplexityBot and CCBot are disallowed in robots.txt.

Why it matters

Two engines your buyers use can't read the site, so they can never cite [Client] regardless of content quality.

Recommended fix

Allow both crawlers in robots.txt and confirm no edge or WAF rule blocks them.

Scope: robots.txt, site-wide

high Top capabilities lack extractable explainer pages
Content depth Owner · Content Effort · Medium

What we found

The capabilities buyers ask about most, cross-timezone scheduling and dependency tracking, live in marketing one-liners, not in pages that answer the question directly.

Why it matters

Engines cite pages that answer the question in extractable language; thin coverage cedes the answer to a competitor.

Recommended fix

Publish dedicated, well-structured pages for the top capabilities, written in the buyer's own phrasing.

Scope: /features/*, new pages

medium Product and pricing pages are missing schema
Structured data Owner · Web / Eng Effort · Low

What we found

Key pages lack SoftwareApplication and Offer schema.

Why it matters

Without schema, engines struggle to resolve what [Client] is and which category it competes in.

Recommended fix

Add SoftwareApplication and Offer JSON-LD to the product and pricing pages.

Scope: /, /pricing/

low High-value pages are going stale
Freshness Owner · Content Effort · Low

What we found

Several high-traffic pages haven't been updated in 14+ months.

Why it matters

Stale pages are cited less; freshness is both a ranking and a citation signal.

Recommended fix

Refresh and re-date the highest-traffic capability and comparison pages.

Scope: top 10 pages

What this is and what to check

Findings are the actionable core of the Foundation: every one names what's wrong, why it costs you citations, who owns the fix, and how much effort it takes. They're ordered by severity so the highest-leverage fixes come first. You don't approve or reject findings; they're a diagnosis of your real site. They're also what the action plan turns into specific, sequenced work.

How to review & approve

Reading your own Foundation takes about five minutes. Here's how to do it well, and what each decision means.

  1. 1

    Read it top to bottom

    The market map first (profile, buyers, competitors, what they evaluate, why they search), then the technical state of your site (crawler access, content quality, findings).

  2. 2

    Check the map against how you actually sell

    Are these the buyers who sign, the competitors you lose deals to, the capabilities you win on? The technical findings are a diagnosis of your real site, so there's nothing to approve there; just the map is yours to correct.

  3. 3

    Approve, or request changes

    In your account, approve the foundation or request changes with a note on what to fix. Requesting changes is normal and expected, not a setback.

Approve when

The profile, buyers, competitors, and capabilities all match how you actually go to market. Your 150 questions arrive with it, and they are yours to adjust. Once it locks, allow up to 72 hours for the Crawl and your full visibility report. The action plan comes with the report.

From there the Loop writes against the plan: three pages a week, published to a Studio on your own subdomain, with the same questions re-asked every month.

Request changes when

A key persona is missing, a competitor you lose deals to isn't listed, a capability is mis-rated, or the category misreads what you sell. Tell us what to fix; we revise and send it back for approval.

Why we make you approve it

The foundation maps your market and drives query generation and every downstream score. Your approval is the quality gate that makes the Crawl yours rather than ours. One thing it does not do: approving the foundation never unlocks or charges you for the action plan. That's a separate part of the Crawl. Approval only starts the visibility run.

What happens next

Your Foundation is the first step

When your Foundation lands, open it in your account, read it, and approve it, or request changes if something's off. Your 150 questions arrive with it, and they are yours to adjust. Once the questions lock, allow up to 72 hours: your full visibility report follows, scored across ChatGPT, Claude, Gemini, and Perplexity. The action plan arrives with the report.

New to Resonate? Start your own Foundation and it arrives built on your company.

Frequently asked questions

What people ask most when they first see a sample Foundation.

Is this a real company's Foundation?

No. It is a representative example built with illustrative data to show the shape of the deliverable. The company, personas, competitors, and findings are invented. A real Foundation is built on your own category, your own buyers, your own competitive set, and a scan of your own site.

How long does my Foundation take?

It's delivered to your account, in about an hour, and we email you when it's ready. From there it waits for you. Nothing is measured until you review and approve it.

What if something in it is wrong?

Request changes. Add a missing persona, a competitor you actually lose deals to, or correct the category framing. Requesting changes is normal and expected. We revise it and send it back for approval. It's better to fix the map now than to measure against a wrong one.

Does approving the foundation unlock or charge me for the action plan?

No. Approving your Foundation only starts the visibility run. The action plan is a separate part of the Crawl and is never unlocked or charged by approving the foundation.

What happens after I approve it?

Your 150 questions arrive with the Foundation, written from it, and you can adjust the set or revise the Foundation it came from. Once the questions lock, allow up to 72 hours. The Crawl runs during business hours and your full visibility report follows, scored across ChatGPT, Claude, Gemini, and Perplexity. The action plan arrives with the report.

Why do I have to approve it at all?

The foundation maps your market and drives query generation and every downstream score. Your approval is the quality gate: it makes sure we measure you against the right category, the right buyers, and the right competitors before any numbers are produced.