Your homepage is the one page every AI engine reads when it needs to know who you are. It should state your brand name, what you sell, and who you serve in plain text on the page itself, and it should carry Organization markup that says the same facts in structured form. Google says Organization markup on a homepage can help it understand your organization and tell it apart from other organizations with similar names. No special markup is needed to appear in Google AI Overviews or AI Mode, and a page must be indexed and eligible to show with a snippet to appear as a supporting link there, so the homepage job is clarity plus crawlability, not a trick.
Why AI gets your brand wrong from the homepage
- The name on the page is ambiguous. A brand name that is also a common word, a place, or another company's name gives the model nothing to separate you from the rest.
- The homepage is a slogan and a hero image. "Built for the bold" tells a model nothing about what you sell, what it costs, or who buys it.
- The facts live in JavaScript. If the brand name, description, and links only appear after scripts run, most AI crawlers never see them.
- The site contradicts itself. The header says one name, the footer says another, the About page says a third, and the listings say a fourth.
- There is no structured identity. The page has prose but no Organization block, so a machine has to guess which strings are the name, the logo, and the official profiles.
The fixes, in order
1. Write one plain identity paragraph
Put it near the top of the homepage, in visible text. It needs four facts: the brand name exactly as customers know it, what you sell, who it is for, and where you operate or ship. Example wording: "Northwind Outdoor is an online store selling waterproof hiking boots for walkers in the United States." Keep it factual. Cut adjectives that carry no information.
2. Add Organization markup that matches the page
Add one Organization block to the homepage. Google recommends placing it on the homepage or a single page that describes your organization, such as the About page, and not on every page. There are no required properties. Add the ones that apply: name, url, logo, description, and sameAs links to your official profiles. Use the most specific subtype that fits, such as OnlineStore for an ecommerce site.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Northwind Outdoor",
"url": "https://[yourdomain.com]/",
"logo": "https://[yourdomain.com]/logo.png",
"description": "Online store selling waterproof hiking boots for walkers in the United States.",
"sameAs": [
"https://www.linkedin.com/company/northwind-outdoor",
"https://www.instagram.com/northwindoutdoor"
]
}
</script>
In the example, [yourdomain.com] is a placeholder, replacing yourdomain.com with your actual domain. Use your real profile URLs in sameAs, and only profiles that are unambiguously yours.
3. Make the markup and the visible page agree
Every fact in the Organization block must match text a visitor can read. If the markup says one name and the header shows another, you have created two competing facts. Fix the page first, then the markup. The same rule covers your logo, your contact details, and your address if you publish one.
4. Link the homepage to the pages that prove the identity
A homepage that links to About, the catalog, contact, and shipping or returns pages gives crawlers a short path to the facts behind the identity paragraph. Link with words that say what the page is, such as "About Northwind Outdoor" and "Shipping and returns", not "click here". Internal links are also one of the practices Google lists as relevant for AI features.
5. Serve the identity in the first HTML
Check the page source with JavaScript off, or fetch the page as a crawler would. The brand name, the identity paragraph, and the main links should be present in the code the server sends. If they only appear after scripts run, fix the rendering before you tune anything else on this page.
6. Check that crawlers can reach the page
Confirm robots.txt allows the AI crawlers and that no edge rule blocks them. A homepage that returns an error to a crawler is invisible no matter how clear its copy is.
The fundamentals
These mechanics are shared across every engine and covered in full in their own guides:
- •The allow rules crawlers check first, see our guide to allowing AI crawlers in robots.txt
- •What goes in the llms.txt file, and how to publish it, see our guide to writing a good llms.txt file
- •The markup engines read on product pages, see our product schema guide
Say you run a cycling shop called Ridgeway
There is another Ridgeway in your region, a roofing company. Your homepage says "Ridgeway" and shows a photo of a bike, but never says you sell and repair bicycles, and your Organization block is missing. An engine that reads the page has to guess which Ridgeway you are, and it may pick the roofer. You add one identity paragraph naming Ridgeway Cycles, bicycle sales and repair, and your city, plus an Organization block with the same name, your logo, and sameAs links to your profiles. Nothing else on the site changes. The next crawl now has a name, a trade, a place, and a set of profiles that all point the same way.
What this guide does not cover
This guide covers the homepage as an identity page. It does not cover product pages, category pages, or the transaction layer that lets an agent complete a purchase. It also does not cover monitoring: if the facts on the homepage change, the markup and the listings have to change with them.
Check your own brand now
Run the free scan. It takes seconds, no signup, and shows whether AI crawlers can read your homepage today: aizii.ai/aeo-scan
Run the free scanSources
- Google Search Central, Organization structured data (specific): https://developers.google.com/search/docs/appearance/structured-data/organization
- Google Search Central, AI features and your website (specific): https://developers.google.com/search/docs/appearance/ai-features
- Google Search Central, Product structured data (specific): https://developers.google.com/search/docs/appearance/structured-data/product
- Schema.org, Organization type (general standard): https://schema.org/Organization
- OpenAI bots documentation (specific): https://platform.openai.com/docs/bots
Note: links marked specific point to the page that supports the claim in this guide. Links marked general docs point to the vendor's general docs section for that topic, not to a page that proves every step. Check the vendor docs for the current path before relying on a menu name or click path in this guide.
