Schema markup used to be a way to get stars in search results. Its function has changed. Structured data is now how you tell a machine, unambiguously, what your content is and what your organization is — rather than leaving it to be inferred from prose.

Most companies implement it in the wrong order, spending effort on markup that produces little and skipping the types that carry the most weight.

The priority order

1. Organization. The foundational entity declaration. Your legal name, URL, logo, description, the brands you operate, and your identity across other platforms. Everything else about you attaches to this. If you implement one schema type, implement this one, on every page.

2. FAQPage. The highest-yield type for answer engines by a wide margin. It hands over a set of question-and-answer pairs in a format built for extraction. Requirement: the questions must be real questions people ask, and the answers must be complete enough to stand alone when lifted out of context.

3. Service or Product. What you actually offer, with the specifics — what it is, who provides it, where it is available, what it costs if you are willing to say. This is what a machine consults to decide whether you match a described need.

4. Article and BreadcrumbList. For content pages: what this is, who wrote it, what it is about, where it sits in the site hierarchy. Breadcrumbs are cheap and disproportionately useful for helping a machine understand structure.

5. LocalBusiness. Essential if you have physical locations or defined service areas, irrelevant if you do not. Includes address, hours, service area and contact details.

Rules that decide whether it works

Mark up what is visible. Structured data describing content that is not on the page is a violation of every major guideline and it will be caught. Markup describes; it does not supplement.

Be complete within a type. A half-populated Organization block is much weaker than a full one. Fill in every property you legitimately have.

Use one canonical entity. The same organization name, URL and identifier everywhere. Multiple slightly different Organization declarations across your site fragment your identity — precisely the opposite of the goal.

JSON-LD, in the head. The format every major consumer prefers, and the only one that is straightforward to maintain.

Validate, then check it renders. Run it through a structured data validator, then confirm it appears in the served HTML. Markup injected by JavaScript after load may or may not be seen depending on the crawler.

The mistake almost everyone makes

Marketing FAQs written for conversion — three flattering questions with answers that are really pitches — marked up as FAQPage.

This produces nothing, because the questions do not match what anyone asks and the answers do not answer anything. The FAQ schema is only valuable when it contains the real questions from your sales calls and support inbox, answered plainly, including the ones with answers you would rather not give.

The question "what does this cost?" answered with "it depends on your needs — contact us" is worse than no markup at all. It signals to the machine that you are not a useful source for the most common question in your category.

What to expect

Structured data does not directly improve rankings and never has. What it does is make you legible: it removes ambiguity about who you are, what you sell and what your content answers.

In a world where an increasing share of discovery happens through machines summarizing rather than humans browsing, legibility is close to the whole game.