Audit AI Brand Mentions: Alias, Homonym, Source Rules

By William Zhu · Cofounder, InfiniSynapse · Published: 2026-09-08 · Last updated: 2026-09-14 · Last verified: 2026-09-14 · Reviewed by the InfiniSynapse Data Team.

Reviewed by: InfiniSynapse Data Team · method review 2026-09-14. Homepage alias counts and Organization sameAs. No engine mention run. No Wikidata item claimed.

Trust / COI: About · Corrections. SEO Health is a commercial product from this team. Alias counts are our homepage HTML, not market prevalence.

TL;DR

Homepage copy uses InfiniSynapse 85 times and never writes “Infini Synapse.” That is the ai brand mentions ledger we actually have.

Direct answer: Treat ai brand mentions as an alias list plus two later columns: mention and citation. On 2026-09-14 the homepage HTML counted InfiniSynapse 85, SEO Health 10, Data Agent 29, Infini Synapse 0, aimeetup 0, infinitegrowth 0. Organization sameAs listed four URLs: YouTube, X, GitHub InfiniSynapse, and GitHub allwefantasy. No answer engine was queried. The sample cannot establish prevalence.

An ai brand mentions rate built from invented confusion rows is already off the job. Keep unused aliases as unused.

What you will learn

• Which strings appear on the homepage
• Which identities sit in sameAs
• Why a missing space is a real alias decision
• When Wikidata is a vocabulary, not our item
• Where Claude and Perplexity coding live

What an alias ledger records

Key definition: ai brand mentions start as a ledger of approved strings and rejected lookalikes. A later engine row may add mention and citation. The ledger exists even when those columns are empty.

People open ai brand mentions after a dashboard counts “Infini” as the company and also as a Latin prefix. Homonyms need a second reviewer. Do not force them into the total.

Wikidata:Introduction is the entity-vocabulary page we fetched (HTTP 200). We did not claim a Wikidata Q-id for InfiniSynapse on this desk. Schema.org sameAs answered 200 after --compressed with title “sameAs - Schema.org Property.” That property is the slot. It is not a mention.

SEO Health stays the deterministic evidence foundation for public HTML reads. A later InfiniSynapse Server API long-task workspace may classify a submitted pack over SSE /api/ai/events; the API does not browse Perplexity for you.

sameAs is a URL list

The homepage Organization node lists four sameAs URLs. None of those URLs is the string “SEO Health.” ai brand mentions that treat a product nickname as sameAs are mixing copy with identity links.

Schema.org Organization is the type. W3C JSON-LD 1.1 is the syntax. Neither invents a Q-id.

Rejected strings stay on the ledger

“Infini Synapse” (space) counted 0. aimeetup counted 0 on the homepage. infinitegrowth counted 0. Those zeros are decisions. ai brand mentions that drop zeros make the next analyst re-litigate the alias.

Homepage counts and sameAs URLs

Fetched https://infinisynapse.com/ on 2026-09-14 (91,875 bytes; html lang="en"; canonical https://infinisynapse.com; no hreflang).

sameAs URLs: youtube.com/@infinisynapse, x.com/InfiniSynapse, github.com/InfiniSynapse, github.com/allwefantasy.

Figure: Counts are homepage HTML. sameAs membership is URL membership, so the name strings sit at 0.

W3C Web Annotation Data Model is why a later mention needs a target span, not a vibe. Crossref metadata is a scholarly metadata surface. It is not our brand index.

FTC and homonyms

FTC endorsements guidance is why we will not dress Organization sameAs as an independent review. NIST publications search is a library, not an entity-resolution verdict on this host.

Wikidata item help explains items. We still did not mint one here. ai brand mentions that invent a Q-id to look finished are fabricating identity.

How to reproduce the ledger

curl -sS -A 'InfiniSynapse-SH1-desk/2026-09-14' -o /tmp/home.html \
  https://infinisynapse.com/
python3 -c 't=open("/tmp/home.html").read();
print(t.count("InfiniSynapse"), t.count("Infini Synapse"), t.count("SEO Health"))'

Parse JSON-LD for sameAs. Compare URL membership to string counts. ai brand mentions reproduction stops there until a reviewer codes an actual engine span.

Package infinitegrowth@0.1.1; -V printed 0.1.0. aivisibility on a sibling printed unauthorized. That gate is not a mention.

What a later engine row still needs

Approved alias. Matched span. Mention yes/no. Owned citation yes/no. Third-party citation yes/no. Reviewer. Date. ai brand mentions fail when a homonym is coerced.

Two columns after the ledger

Mention and citation stay independent. An owned docs URL can be cited while the prose never names the brand.

Sample-size limit

This desk coded no engine spans. The sample cannot establish how often Gemini or Claude names the company, and it does not prove a content edit moved a mention.

As of 2026 this page is not a customer mention export.

Failure modes that invent prevalence

Nickname as sameAs. SEO Health is copy, not a sameAs URL.

Space variant ignored. Infini Synapse counted 0 and must stay 0.

Wikidata intro as our item. We fetched the intro. We did not claim a Q-id.

Unauthorized as “unmentioned.” Login failed.

Synthetic confusion rows. Older drafts invented counts. They are gone.

Award text as a mention engine. Homepage award sentences are first-party copy.

An ai brand mentions memo that skips the homepage table is already late.

How a reviewer should read the ledger

Start with the zeros. “Infini Synapse,” aimeetup, and infinitegrowth counted 0 on the homepage. Those zeros are as important as the 85. If a later engine says “Infini Synapse,” the ledger already marked that string rejected unless a reviewer promotes it. ai brand mentions that treat every lookalike as approved will inflate the next total.

Read sameAs as URLs only. YouTube, X, and two GitHub profiles are identity links. They are not product nicknames. SEO Health appearing ten times in HTML does not put SEO Health into sameAs. Data Agent appearing 29 times does not either. Write those nicknames on a “copy only” list.

Do not mint a Wikidata Q-id to look complete. We fetched the introduction page. That is vocabulary. If a later desk finds a real item, store the Q-id and the retrieval date. Until then the cell is empty.

When an engine row finally exists, attach it to one approved alias and one span. Mention and citation stay independent. An owned URL in a source list without the alias in prose is citation without mention. The reverse also happens. ai brand mentions that force both bits to yes are editing the answer.

Homonyms go to a second reviewer. Do not let a single analyst decide that “Infini” always means the company. If the span is ambiguous, mention = unresolved. Unresolved is not a zero and not a one.

Award sentences on the homepage are first-party copy. They can contain InfiniSynapse many times. They are not engine mentions. Do not add them to a prevalence chart. The 85 already includes that copy. The ledger’s job is to show what we call ourselves, not what Claude said.

If you only have the homepage table, you have the desk. That is enough to reject a prevalence slide. It is not enough to claim engines name the brand. Write both. A later span log is an addendum. Do not put invented confusion counts back into the main table.

Two people counting the same HTML should get the same integers unless the homepage shipped. Store the byte count 91,875 beside the table. ai brand mentions that recount a stale local checkout will disagree with the 2026-09-14 fetch.

What stays on disk after this desk

Keep the homepage HTML, the count table, and the four sameAs URLs copied as plain text. That is the 2026-09-14 ai brand mentions packet. If a later engine span arrives, it gets its own file with alias, span, mention, citation, and reviewer. It does not edit the 85.

Export the Organization JSON-LD block as homepage-organization.json. Future homepage redesigns will change counts. Diff the JSON, not your memory. ai brand mentions that recount from a slide will drift.

Keep a rejected-alias list: Infini Synapse, aimeetup, infinitegrowth, and any new lookalike a reviewer adds. Promotion requires a dated note. Silent promotion is how homonyms re-enter the total.

Wikidata stays a maybe. If a Q-id appears later, store the retrieval date and the item URL. Until then the cell is empty. Do not paste a guessed identifier to look finished.

Award copy on the homepage remains first-party. It already sits inside the 85. Do not double-count it as an engine mention. ai brand mentions that add award sentences to a prevalence chart are counting ourselves twice.

The decision this page supports is ledger hygiene. It does not decide campaigns. When someone asks “how often do AIs name us,” point at the empty span folder. Empty is allowed. A fake rate is not. That stop is the product of ai brand mentions on this URL.

Package pin and binary version go in versions.txt beside the unauthorized sibling note, so nobody claims we ran aivisibility on the homepage.

Keep the ledger boring

Boring is the point. The next homepage ship will change the 85. Diff it. If SEO Health appears 11 times, write 11. If a designer adds “Infini Synapse” in a hero, the rejected list must be revisited the same day. ai brand mentions that wait a quarter to notice a space variant will ship a homonym into ads.

Print the four sameAs URLs in the ticket footer every time. People forget GitHub @allwefantasy is on the Organization node. Forgetting it does not remove it. Adding a fifth URL is a schema change, not a mention.

When legal asks whether we “tracked brand mentions,” the accurate answer is: we counted our own homepage strings. Anything about Claude or Perplexity is a different folder. Keep that sentence in the packet so ai brand mentions does not get cited as an engine study.

Nearby guides

The Perplexity hub owns vendor 403/200. This page owns the alias ledger.

The AI visibility hub remains the category page. ai brand mentions stay on aliases.

Frequently Asked Questions

Did we measure mention rates in any engine?

No. ai brand mentions on this desk are homepage strings and sameAs URLs.

Is SEO Health in Organization sameAs?

No. It appears in HTML 10 times. The sameAs list is four profile URLs.

Should “Infini Synapse” be treated as approved?

Not on this homepage. The count was 0. Keep it rejected until a reviewer changes the ledger.

Does Wikidata introduction prove we have an item?

No. The intro page answered 200. That is vocabulary, not a Q-id.

May we publish a prevalence chart from this article?

No. The chart is HTML count versus sameAs membership. It cannot establish engine prevalence.

Conclusion

Use ai brand mentions when the job is to refuse a prevalence tile until approved strings and rejected lookalikes are written down. This 2026-09-14 pass counted homepage aliases and four sameAs URLs. Stop when those zeros and those four links remain visible. A bounded ledger beats an unsupported mention rate.

An unused alias on the homepage is a ledger row, not a mention from Claude or Perplexity. Until an engine span exists, ai brand mentions end at the HTML table. Reprint the four sameAs URLs whenever someone asks “where is the official profile list.” If a fifth URL appears, that is a schema edit with its own date. If a space variant appears in a hero, reopen the rejected list the same day. Do not wait for a quarterly brand workshop to notice the homepage already changed. A same-day note in the packet is enough process for ai brand mentions. If nobody writes the note, the next analyst will recount 85 and miss the new space variant.