Building a Grounding Page for Your Brand

Last updated: June 24, 2026

A Grounding Page is one official URL that AI engines reach for ground-truth facts about your brand: what you are, who built you, what categories you serve, and how to cite you. Without it, engines patchwork facts from Wikipedia, Crunchbase, LinkedIn, and whichever blog post is freshest, often with inconsistent or wrong results. Every brand needs one, and it's the foundation for branded visibility.

Caveat: you can also use these insights to increase the information-density on your About Us-page

What a Grounding Page does

When someone asks about your brand, the engine needs to answer three questions: does this brand exist as a real, verifiable entity, what category does it belong to, and what are the core facts (founded, HQ, team, pricing model). Your Grounding Page is the single URL that answers all three cleanly, so engines stop reconstructing your brand from scraps.

The spec

H1: entity name only. Not "Welcome to Rankscale" and not "Rankscale, the AI Search visibility tool." Just the entity name. The surrounding page establishes the category.

Lead definition: one factual sentence in the form "[Name] is a [category] that [function]." For example: "Rankscale is an AI Search visibility platform that tracks how AI engines (ChatGPT, Google AI Overviews, Perplexity, Claude, Gemini, Copilot, Grok, Deepseek, Mistral) mention, cite, and describe brands across prompts, helps you report to leadership and provides specific recommendations to improve your AI visibility per prompt." This is the sentence engines source when asked "what is [brand]?"

Core facts grid using <dl>/<dt>/<dd> tags, not a table: Category, Founded, HQ, Team size, Founders, Domain, Status, Last reviewed. This is the semantic pattern engines prefer for fact lists.

FAQ section with the entity name in every answer. Five to ten FAQs, each answer containing the brand name at least once. "What is Rankscale? Rankscale is an AI Search visibility platform." Repeating the name reinforces the association for retrieval.

Volatile-facts block. A separate, clearly marked section for facts that change (pricing, team size, supported engines), so you can refresh them without re-reviewing stable facts.

"Is NOT" disambiguation (if needed). If your name clashes with another company or a common word, add an explicit line: "[Brand] is NOT [X]. It is [Y]." This is what saves you when engines confuse you with a namesake.

JSON-LD that mirrors the HTML. Organization schema with a sameAs array pointing to Wikidata, LinkedIn, and Crunchbase. Every fact in the schema must match the visible HTML.

Review date within 6 months. A Grounding Page reviewed more than six months ago isn't trustworthy. Build the refresh into your quarterly review.

Hub-and-spoke for multiple entity types

Most brands are more than an Organization. You may also be a Tool/Platform, a Service, a Publication, and so on. AI engines disambiguate per entity, not per brand, so the rule is one canonical URL per entity that has its own search demand. Everything else merges into the hub.

  • Independent search demand? Split it into its own spoke page (/product, /academy, /team/[name]).

  • No independent demand? Merge it into the hub as a section.

Every spoke schema points back to the hub (via isPartOf, publisher, provider, or worksFor), and the hub points out to every spoke (via hasPart, publishes, makesOffer, or employee). That reciprocal graph is what engines traverse.

The launch checklist

  • H1 is the entity name only

  • First paragraph is a one-sentence factual definition

  • Core facts grid uses <dl> tags

  • FAQ section repeats the entity name in every answer

  • Volatile-facts block is separated

  • "Is NOT" disambiguation added if applicable

  • JSON-LD Organization schema with sameAs array

  • Review date visible on the page

  • Page is not behind auth or a paywall

  • URL is simple (/about or /brand)

Do this now

Block two hours this week. Build your Grounding Page using the spec, publish it at /about or /brand, add it to your sitemap, and claim the sameAs links on Wikidata, LinkedIn, and Crunchbase.

Related Articles

  • Adding JSON-LD Schema for AI Visibility

  • Fixing an Entity Gap

  • Adding E-E-A-T Signals

  • What Is a PR Gap?