Schema markup is code added to a web page that labels what the page contains, such as an organisation, a product, an article, a person or a breadcrumb trail. It uses the shared schema.org vocabulary and is usually written as JSON-LD. Search engines use it to understand a page and, for some types, to show richer results.
Also called: Structured data, JSON-LD
This short block tells search engines who runs a site and which profiles belong to the same company. It sits in the page's HTML and visitors never see it.
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Example Software Ltd",
"url": "https://example.com",
"sameAs": [
"https://www.linkedin.com/company/example",
"https://www.g2.com/products/example"
]
}
Google's documentation recommends JSON-LD where your site setup allows it, though it accepts Microdata and RDFa too.
For B2B firms the main value is clarity, not stars in results. Organization markup with sameAs links helps machines join your website, LinkedIn page and review profiles into one entity. That matters when an AI tool decides whether "Example" the software company is the same as "Example" the consultancy. Product or SoftwareApplication markup states what you sell. Breadcrumbs show where a page sits on your site.
Be realistic about what it can do. Markup describes a page; it does not make a weak page rank. And some rich results have gone away: Google stopped showing FAQ rich results in Search from 7 May 2026 (Search Central documentation updates, checked 7 Nov 2026). FAQPage markup is still valid code that labels questions and answers, and our free FAQ schema generator builds it for you.
We run your buyers' real questions through ChatGPT, Perplexity and Google, then send you a short report on who gets named, cited and recommended.
We reply within one business day.