For the complete documentation index, see llms.txt. Every page on this site is also served as Markdown: append `.md` to any URL, or send `Accept: text/markdown`.
Skip to content
Attensira LogoAttensira
Start free

Free tool

Brand entity checker

The brand entity checker looks your brand up where assistants resolve entities: Wikipedia, Wikidata and the Organization markup on your own homepage. It shows what each source says, which entries share your name, and what is missing, so an assistant can tell your brand apart from others with the same name. Free, no account, nothing tied to you.

Start freeSee what AI says about you

7 days free · card required

Or use the free tool below

Check a domain

Seconds, on our server · Free, no sign-up

Three surfaces, read directly.

We ask the Wikipedia API whether a page exists at your name, ask Wikidata which items match it, and fetch your homepage to read the Organization JSON-LD out of the HTML — its @type, its name, and every URL in its sameAs array.

Then we request each of those sameAs URLs. A profile you list that no longer answers is worse than one you never listed, and nothing here is reported as valid on the strength of being written down.

Your result appears here

Name searched
Wikipedia
Wikidata
Homepage Organization
sameAs profiles

See our own run

Share
Our runattensira.com

Inputattensira.com

Name searched
Attensira, from our Organization JSON-LD
Wikipedia
No page, no search result
— Fails
Wikidata
No item
— Fails
Homepage Organization
Found, 6 JSON-LD blocks parsed
✓ Passes
sameAs profiles
X, LinkedIn, GitHub: all 3 answered
✓ Passes
Brand entity checker, production, n=1 run ·

Which surfaces does it read?

  1. Wikipedia

    Two MediaWiki API questions: is there a page at this exact title, and what does search return. A title match is a fact; a search hit is a candidate, not proof it is you.

  2. Wikidata

    The items matching your name, by id, label and description. It never picks one and calls it yours.

  3. Your homepage markup

    Every JSON-LD block, parsed for an Organization node, its name and each sameAs entry it declares. Then each sameAs URL is requested and its answer shown.

What does it say about Attensira?

We ran it on attensira.com. The result is unflattering, and it explains an answer we saw the day before.

Perplexity, “what is Attensira”, 3 Oct 2026, verbatim

“Attensira” can refer to two different things, depending on context: … If you mean a medication brand name: some websites use “Attensira” as a name for an ADHD treatment …

In 2 of 3 Perplexity samples on 3 October 2026, the answer to “what is Attensira” also described a medication sold under a similar name. With no Wikidata item, an engine has no identifier to tell the two apart, so it hedges.

Our homepage markup is in order. What is missing is outside our site, and more markup cannot create an entity. Coverage by others, consistent profiles and, in time, a referenced Wikidata item can.

The run is the result panel at the top of this page. Read on 4 Oct 2026.

Which checks only prove presence?

We hold no Crunchbase or LinkedIn API access. If your markup lists a profile on one of those hosts, we request that exact URL and label the result presence-only, kept apart in three outcomes.

  • Answered. A success status. Verdict: the URL answers; not that the profile is yours, current or complete.
  • Not there. A 404 or 410. Verdict: a real absence, the only outcome that fails the sameAs entry.
  • Refused us. A 403, 429 or a host's own status. Verdict: unchecked, not disproved; a wall is a fact about the host, not the page.

What can on-page work not fix?

Robots rules, structured data, headings and llms.txt are yours to edit this afternoon. A Wikipedia article is not, and neither is a Wikidata item with real references. Both are written by other people under notability rules you do not control, and Wikipedia's conflict-of-interest guideline (read 4 October 2026) strongly discourages editing articles about your own company.

So if this tool finds no Wikipedia entity, the reading is not "go and make one". The surfaces you do control carry more weight: an Organization node whose sameAs resolves, one name across every profile you own, and coverage on third-party sites that write about your category.

Do not invent a sameAs. Pointing at a Wikipedia article that does not exist creates a broken claim, which this tool reports as not there. Our own markup has no Wikipedia sameAs for that reason.

How does the crew work on an entity that is missing?

Inside Attensira, every pitch arrives as a draft you can edit. The first ten go out from your own mailbox, sent by you. Sending for you is off unless you turn it on, in act mode. Off-site work.

Pitch draftWaits for you to send it
To
The editor of a site that already lists tools in our category
Subject
A tool for your list: Attensira

Attensira is software that does your AI-search visibility work. If it fits your list, here is a one-line description, our homepage and the profiles we keep consistent.

Introduce Attensira to a site that already lists tools in our category

Outreach agentOutreach · would hand you a pitch draft like thisExample · the kind of change this finding calls for, not one that shipped

How do you act on each finding?

  • No Organization node in the homepage markup at all. This is the first thing to fix and the cheapest. One JSON-LD block with @type: Organization, your legal name, your canonical URL and a sameAs array of profiles that genuinely exist. Check the block renders and parses with the structured data validator.
  • An Organization node with an empty sameAs. You have told an assistant your name and nothing that corroborates it. Add only the profiles you actually maintain and can point at today.
  • A sameAs entry that returns 404. Remove it or repoint it. A dead claim is worse than a missing one: it is the one piece of your markup that can be demonstrated wrong.
  • A sameAs entry that redirects somewhere else. The row names the final URL. Put that URL in your markup instead, so the claim and the destination are the same string.
  • The name in your JSON-LD is not the name anyone searches. The result header shows exactly which string was searched and where it came from. If that string is wrong, the whole report is answering the wrong question. Re-run it with the optional name field filled in, then fix the name in your markup.
  • Several plausible Wikipedia or Wikidata matches. If an entity with your name exists and is somebody else, as the medication in our own example above is, the risk is not absence but misattribution. The fix is unambiguous naming everywhere you control: the same name, the same one-line description and the same canonical URL on every profile.

Why re-run it after the first pass?

Because the surfaces change without you. Profiles get renamed, company pages get merged after an acquisition, a social handle changes and every sameAs pointing at the old one starts returning 404. None of that shows up in your analytics, and none of it breaks a page. It makes your markup less true each time, and this check is where it shows: the not there rows.

Questions people ask about this check

You found a Wikipedia page with my brand name. Is that my entity?

We do not know, and we will not guess. The exact-title result tells you a page exists at that title; the search results are candidates for the term we searched. Deciding whether an article is about your organization is a judgment that needs someone who knows the company. An assistant resolving your name to a different entity with the same name is a worse outcome than resolving it to nothing, which is why we surface the candidates rather than silently picking one.

Should I create a Wikipedia page for my company?

Not by writing it yourself. Wikipedia's conflict-of-interest guideline strongly discourages editing about your own company and sends new articles from paid editors through Articles for Creation, and a page that fails the notability bar is deleted. The realistic path is third-party coverage that meets their sourcing bar, after which an editor may write one. This is the part of AI search visibility that is a go-to-market job rather than a template change.

The LinkedIn row says you were refused. Is my profile broken?

We do not know, and the row says so rather than guessing. LinkedIn walls automated requests, and what the row records is the status it actually returned to us, nothing more. It is marked unchecked, not failed. We will not turn "a host would not talk to us" into "your profile is missing": the whole reason that row exists is to show you exactly what we could and could not read.

Can you tell me whether ChatGPT knows who my company is?

Not from here, and nothing that runs in a browser can. This tool reads public APIs and your own HTML. It does not query an assistant, it does not see anyone's traffic, and it does not intercept anything. What an assistant actually says about your brand is a separate measurement, taken by asking the assistants themselves and sampling the answers over time.

Why is there no score out of a hundred?

Because we would have to invent the weighting, and the invented part is the part you would act on. There is no published relationship between "has a Wikidata item" and "gets cited" that we could weight honestly. Each surface is reported as what it is: present, absent, or unreadable, with the reason attached.

Do you store the domains I check?

Not against you. There is no account, no email field and no history tied to you. The result is held for about an hour in a shared cache keyed by the domain, so an identical check in that window is answered from the cache rather than hitting Wikipedia and Wikidata again. That means a repeat can show you the earlier answer rather than a fresh one. It is a cached re-run, not a saved snapshot of yours.

This checks your entity. Attensira's crew works on the sources.

Start freeSee what AI says about you

7 days free · card required