Homepage H1, schema name, and title tag should agree. Here is a three-field consistency check you can finish in five minutes.
Three strings teach most systems who you are on a page: the title tag, the visible H1, and the schema name. When they disagree, you have not built a mysterious multi-channel brand — you have built a reconciliation problem.
Homepage H1, schema name, and title tag should agree. Here is a three-field consistency check you can finish in five minutes.
Why the H1 counts for AEO
The H1 is the on-page headline machines and people treat as the document's primary label. If the title says "Northstar Analytics", schema says "Northstar Analytics, Inc.", and the H1 says "Welcome to the future of insights", you trained three different labels.
Answer engines and entity resolvers like repeated, identical anchors. You already fight ambiguity across the open web; do not add ambiguity inside your own HTML. See one brand, one entity.
Assistants that cite sources still need a readable page. Pew Research (March 2025) found AI Overviews on roughly 18% of searches in their study, and most summaries (88%) cited three or more sources. Being eligible to be one of those sources starts with a page that knows its own name.
The three-field consistency check
Pull one URL (start with /). Fill this table:
| Field | Where to look | Exact string today | Match? |
|---|---|---|---|
| Title tag | <title> in source | ||
| H1 | First meaningful <h1> | ||
| Schema name | Organization / WebSite / Product name |
Pass rule: Same canonical brand or product name appears in all three, character-for-character for the core name (legal suffixes like Inc. can live in schema only if you also expose the short name consistently somewhere obvious).
Fail examples:
| Title | H1 | Schema name | Problem |
|---|---|---|---|
| Northstar Analytics | Welcome aboard | Northstar Analytics | H1 lacks entity |
| NS Analytics | Northstar Analytics | Northstar | Three spellings |
| Pricing | Pricing | Acme Pricing Cloud | Brand missing on pricing title/H1 |
| Northstar | North star Analytics | Northstar Analytics | Spacing/casing drift |
Five-minute pass (homepage)
- Open the homepage → View Source (or "View Page Source").
- Copy
<title>into a note. - Copy the first real
<h1>text (ignore visually hidden duplicates if you can; fix duplicates after). - Find JSON-LD Organization (or WebSite) and copy
name. - Compare. If any field lacks the canonical string, file a one-line fix ticket.
- Repeat for
/aboutand/pricing. - Paste the canonical string into your design system docs so the next landing-page sprint does not reinvent it.
You do not need a workshop. You need the same noun in three places.
What "agree" means in practice
| Element | Should include | Can also include |
|---|---|---|
| Title | Canonical name | Category, short benefit |
| H1 | Canonical name or clear product name | Supporting clause |
Schema name | Canonical name | alternateName for real nicknames |
Using alternateName in schema is fine for true aliases. Inventing a marketing H1 that never appears in schema is how brand mismatches start. Pair this with title tags for entity clarity so the tab and the headline stop arguing.
Design and CMS footguns
Hero text as an image.
If the only "H1" is pixels in a PNG, the HTML may lack a heading or use a generic one. Put real text in an <h1>.
Multiple H1s from components.
A React layout that injects an H1 in the nav and another in the hero teaches noise. One primary H1 per page.
Client-rendered H1.
If the heading only appears after hydration, many crawlers never see it — fix with SSR/static for marketing routes.
CMS "display title" vs "SEO title" drift.
Editors change one field and not the other. Make the canonical name a shared token or a required snippet.
A/B tools rewriting the H1 only in the browser.
Test variants that keep the brand string stable; experiment with the clause after the em dash.
Broader entity alignment (after the five minutes)
Once Home/About/Pricing match, extend the same string to:
- LinkedIn company name (entity match guide)
- Google Business Profile name if you are local (GBP as AEO signal)
- sameAs profile display names where you control them
| Surface | Same canonical name? | Owner |
|---|---|---|
| Title / H1 / schema | Web | |
| Marketing | ||
| GBP | Local / ops | |
| Crunchbase | Corp / marketing |
Mistakes
- Treating H1 as a slogan slot and moving the brand to a logo only
- Matching title and H1 but leaving schema as an old legal entity you no longer use publicly
- "Consistent" wrong names — all three say the deprecated brand
- Fixing production and leaving the template that regenerates bad H1s on new landing pages
- Shipping a partner cobrand H1 that never returns to your canonical name on your own domain
How to verify
- Re-run the three-field table after deploy
- Crawl for pages whose H1 is "Home", "Welcome", or empty
- Confirm Organization JSON-LD still parses
- Optional BrandKnown re-scan: readiness reflects website checks (identity/access), not a promise that citations moved
Honest ceiling: aligned H1s do not compel an assistant to recommend you. They stop you from being unreadable to the systems that try. Similarweb / TechCrunch reporting in June 2025 put AI-platform referrals far smaller than Google Search referrals in absolute terms (about 1.13B AI referrals to top sites vs about 191B Google Search referrals that month) — so classic Search still matters. Entity-clear pages help both.
Spend five minutes. Make the three fields say the same name. Then move on to harder problems.