Schema: sameAs

Markup for Person according to Schema.org is a flexible way of marking up any type of person related to your website or business. With this example you will learn how to easily and manually mark up important people related to your webpage.

Use Organization to mark up your company details on your company website. This example shows you all the details of how to do it manually.

A clear, readable and advanced example in json+ld markup for Events. Use it to understand how you can explicitly structure relevant data about upcoming or finished events on your own webpage resources.

Use the Schema.org definition of LocalBusiness to improve the listing of your local store. This in-depth example shows you exactly how to manually mark up your location.

WebPage markup should be the cornerstone of all your markup work. WebPage can and should per definition be used on all webpages without exception. Follow our simple, yet deep WebPage markup example to understand how.

In-depth EducationalOrganization JSON-LD example wired into the Xoo universe as the Royal Institute of Medicine, Jane Xoo's alma mater, founded 1863 in Copenhagen. First XooCode example to explicitly teach schema.org subtype selection: why CollegeOrUniversity is a better choice than base Organization, and how to pick the right subtype for schools, hospitals, NGOs, and government bodies.

ClaimReview JSON-LD example for a fact-check of the claim that Jane Xoo's pediatric framework reduced infant mortality by 60%. Covers claimReviewed, reviewRating with the textual verdict scale, itemReviewed as a Claim with firstAppearance, and how Google uses ClaimReview for the fact-check rich result and label in search results.

MusicRecording JSON-LD example for a film score track from The Children's Doctor documentary. Covers byArtist, recordingOf with MusicComposition and ISWC code, ISRC code, inAlbum cross-reference, duration in ISO 8601, and ListenAction for streaming links.

DigitalDocument JSON-LD example for a downloadable PDF whitepaper on structured data ROI. Covers hasDigitalDocumentPermission for access control, encoding with MediaObject for file metadata, pagination, and how DigitalDocument differs from Article for non-HTML published content.

Corporation JSON-LD example for the fictional Redpoint 9 Corp, parent company of Xoo Code Inc. Covers tickerSymbol (the only property unique to Corporation), the MIC exchange format, and how Corporation differs from Organization for publicly traded companies.

NewsMediaOrganization JSON-LD example for the Dunmore Herald newspaper. Covers the 10 editorial trust properties (ethicsPolicy, masthead, correctionsPolicy, verificationFactCheckingPolicy, etc.) that Google News uses as publisher credibility signals.

Airline JSON-LD example for a fictional Nordic airline serving Dunmore. Covers iataCode (shared with Airport), boardingPolicy with BoardingPolicyType enum, and how Airline markup feeds Google Flights and travel knowledge panels.

MusicGroup JSON-LD example for the Copenhagen Ensemble, the orchestra from The Children's Doctor documentary score. Covers album, genre, track (the 3 properties unique to MusicGroup), the PerformingGroup hierarchy, and how MusicGroup connects to MusicAlbum and MusicRecording.

NGO JSON-LD example for the Children First Foundation, a non-profit established in Jane Xoo's name. Covers nonprofitStatus with country-specific NonprofitType enums, funder, areaServed, and how NGO differs from Organization and FundingScheme for non-profit entities.

OnlineMarketplace JSON-LD example for a fictional Xoo marketplace. Covers hasStore (the one property unique to OnlineMarketplace), the OnlineStore/OnlineBusiness hierarchy, and how marketplace markup relates to merchant identity in Google Shopping.

DefinedTerm JSON-LD example for a glossary entry. Covers inDefinedTermSet, termCode, and about (the 3 properties unique to DefinedTerm), plus how DefinedTerm works with DefinedTermSet for structured glossaries and taxonomies.

PodcastSeries JSON-LD example for the Xoo Code podcast. Covers webFeed and actor (the 2 properties unique to PodcastSeries), plus how PodcastSeries connects to PodcastEpisode and PodcastSeason.

BodyOfWater JSON-LD example for lakes, rivers, seas, oceans, canals, ponds, reservoirs, and waterfalls. Landform subtype with no unique properties but with 8 specialized subtypes.

AdministrativeArea JSON-LD example for political jurisdictions: countries, states, cities, school districts. Place subtype with no unique properties but 4 specialized subtypes: Country, State, City, SchoolDistrict.

LandmarksOrHistoricalBuildings JSON-LD stub for historic landmarks and heritage buildings. Direct Place subtype with no unique properties. Often dual-typed with TouristAttraction.

OceanBodyOfWater JSON-LD stub for the five major oceans. Direct BodyOfWater subtype with no unique properties.

SeaBodyOfWater JSON-LD stub for seas and semi-enclosed marine waters. Direct BodyOfWater subtype with no unique properties.

Canal JSON-LD stub for artificial waterways. Direct BodyOfWater subtype with no unique properties.

Continent JSON-LD stub for continents. Direct Landform subtype with no unique properties.

Volcano JSON-LD stub for volcanic mountains and vents. Direct Landform subtype (not Mountain) with no unique properties.

Country JSON-LD example for ISO 3166-1 sovereign states. Direct AdministrativeArea subtype used in address chains, eligibleRegion / ineligibleRegion rules, and Place containment.

State JSON-LD example for first-order national subdivisions (US states, Australian states, Indian states, German Länder). Direct AdministrativeArea subtype, commonly nested via containedInPlace into Country.

City JSON-LD example for incorporated cities and towns. Direct AdministrativeArea subtype used to anchor LocalBusinesses, events, and knowledge-graph entries into a municipal jurisdiction.

ProfilePage JSON-LD example for a person or organisation profile page. Direct WebPage subtype. Google's Profile Page rich result keys on this type.

Thing JSON-LD example for the root of the entire schema.org vocabulary. Every type descends from Thing. Use it directly only when no subtype fits; its 13 properties (name, url, image, identifier, sameAs, potentialAction, etc.) are the universal entity signals every page should publish.