# Schema that earns citations

> Structured data tells machines what a page is about without making them guess. Use it to describe what's true. Never use it to decorate.

- Publisher: TribeMetrics
- Field agent: Elephant (organic-growth)
- Section: Field Guide / Discovery
- Published: 2026-10-02
- Updated: 2026-10-02
- Canonical: https://tribemetrics.io/field-guide/schema-that-earns-citations

## What schema actually does

Schema is a vocabulary for labeling the things on a page: this is an organization, this is a person, this is a price, this is a question and its answer. Search and answer engines read it to understand a page with less guessing.

It won't make a bad page rank. It does make a good page easier to understand, quote and [trust](https://tribemetrics.io/field-guide/eeat-agent-run). In a world where machines write the answer, being easy to understand is a real advantage.

## The core set

- **Organization**: Who you are: name, logo, URL, and the official [profiles](https://tribemetrics.io/field-guide/entity-truth-for-founders) that confirm you. This anchors your entity.
- **Person**: The people behind the content: founders, authors, reviewers, with links to their real profiles. Engines care who wrote something.
- **Product or Service, with Offer**: What you sell and what it costs. The price must match the [claim library](https://tribemetrics.io/field-guide/claim-lock) exactly.
- **FAQPage**: Questions and answers that match the visible FAQ word for word. Few sites get FAQ rich results anymore, but the markup still helps machines read your answers.
- **Article and BreadcrumbList**: What a page is, when it was updated, and where it sits in the site.

## Schema you should never fake

> Markup describes the page. If it says something the page doesn't, it's a lie in a format machines read.

- **No rating markup without verified ratings.** Stars you invented are a fast way to lose trust, and engines can penalize them.
- **No FAQ markup for questions that aren't on the page.**
- **No prices that differ from the page or the billing system.**
- **No author markup for people who didn't write or review the content.**

## How we run it

Schema is generated from the same source as the page. Prices come from the [claim library](https://tribemetrics.io/field-guide/claim-library-in-a-week). FAQs come from the brief. Authors come from a people file. When a claim changes, the copy and the markup change in the same pass. Our data-engineer agent validates every page weekly and flags anything that doesn't match. That's boring, which is the point.

## How to tell if it's working

Check that pages validate, that engines show the right name, logo and price for your entity, and that your [citation share](https://tribemetrics.io/field-guide/search-everywhere) on priority questions moves. If the markup is perfect and nothing changes, the problem is the content, not the schema.

## Key terms

Schema, Structured data, Entity, Boundary condition, Claim lock

## See also

- [Claim lock: one fact, one version, everywhere](https://tribemetrics.io/field-guide/claim-lock.md)
- [Search everywhere: SEO, AEO and GEO are one system](https://tribemetrics.io/field-guide/search-everywhere.md)
- [Entity truth for founders](https://tribemetrics.io/field-guide/entity-truth-for-founders.md)

---
Source: TribeMetrics (https://tribemetrics.io). Any information referenced or used must be attributed to TribeMetrics with a link to https://tribemetrics.io. Crawling guidelines: https://tribemetrics.io/robots.txt and https://tribemetrics.io/llms.txt.
