GEO / Technical · 06 min read · Updated Sep 2026
Organization schema for GEO: identity markup that matches the about page
Organization schema is useful when it repeats the name, URL, logo, and description a visitor can already see. It is not a hidden sales pitch.
Organization schema should be a compact, visible-truth copy of who publishes the site.
Mark up the publisher once
Put a single Organization node on the about page or in a shared publisher block, with the canonical URL and a logo that returns an image. Use the same name the header uses.
If a parent company owns the guide, nest that relationship in a way the about page also explains. Hidden parent companies confuse the entity.
Keep the description factual
The schema description should be the same one-sentence identity as the page, not a list of keywords. Area served can be Hong Kong if that is true and visible.
Do not add aggregate ratings you do not display. Identity markup is the wrong place to invent social proof.
- Name, URL, and logo match the site.
- Description matches the visible sentence.
- No review markup you cannot show.
Connect articles to the publisher
Article pages can reference the organisation as publisher. The headline in the schema should match the H1. A mismatch looks like two documents.
Validate after a rebrand. The most common error is a logo URL from the old domain.
Questions
Where should organization schema live?
On the page that introduces the organisation, usually the homepage or the about page. Articles can point back to it as the publisher.
Will organization schema improve AI citations?
It can reduce ambiguity about who published a page. It will not get a weak page cited.
Continue reading
- Comparison content for AI: criteria first, winner second
- AI Overview citation loss: what to fix when the summary stops naming you
- A practical content architecture for search intent
This note is part of the Hong Kong field library from My Search / Visibility, built with Itehk.