Before an engine can recommend you, it has to resolve your site to one entity: this company, this name, these profiles. That certainty comes from your homepage's structured data and a few plain signals around it. Enter your domain — thirteen checks, each with the exact fix.
Reads your homepage, its JSON-LD, the logo URL and /about. Cached for 10 minutes. Nothing stored. Why entity clarity matters →
Reading your homepage…
Engines build a graph of things — companies, products, people — and attach what they read to the right node. If your site does not say clearly which node it is, mentions of you elsewhere may never connect back to your domain, and answers about your category may name a competitor whose entity is cleaner. Structured data on the homepage is where that identity is declared.
JSON-LD present and parseable · an Organization entity · its name · that name in the visible text and title · url on this domain · logo set and resolving · a description · at least two sameAs profiles · a Wikipedia or Wikidata link among them · a WebSite entity · entities cross-linked by @id · an About page that answers 200.
Yes. Wikidata accepts items for companies that meet its notability rules even when no Wikipedia article exists, and engines use it as the canonical entity id. Create the item, fill in official website, founding date, headquarters and social profiles, then point your sameAs at it.
Whether the facts are true, how engines actually describe you, and product or article schema on deeper pages. The free Reflexa check shows the other side — what ChatGPT, Claude and Perplexity say about you for your buyers' real questions.
The free check runs your real buyer questions across ChatGPT, Claude and Perplexity — mentioned, recommended and cited, per engine, with the answers as evidence.