Is structured data a ranking factor?

No. Google has said repeatedly that structured data is not a ranking factor. It does not lift your position in the results. What it can change is how your result is presented and how clearly machines read the page.

So why add schema markup at all?

Three reasons. It can earn rich-result appearances that lift click-through rate, it feeds entity data into knowledge panels and other surfaces, and it gives aggregators and AI assistants a machine-readable summary of the page.

Do rich results raise rankings through a click-through boost?

Only indirectly. A richer snippet can earn more clicks at the same position, which grows traffic. Google does not translate that into a higher ranking, and no markup guarantees that a rich result will be shown.

Does FAQ markup still produce rich results?

Rarely. Since August 2023 Google shows FAQ rich results only for well-known, authoritative government and health websites. On other sites the markup is still read, but it should not be expected to change the search result.

Does HowTo markup still produce rich results?

No. Google deprecated HowTo rich results. They stopped appearing on mobile in August 2023 and on desktop the following month. The markup is harmless but no longer earns a special appearance.

Does structured data actually affect rankings?

Structured data is the most over-sold task on a technical SEO checklist, and the most under-explained. Adding it will not move your page up the results. It changes something else entirely: how your result can be displayed, and how confidently a machine can read the page without guessing.

Here is the short version: structured data is not a ranking factor, but it is a presentation and comprehension tool, and that still matters.

What structured data does and does not do

Claim	Verdict
Raises your position in the results	No — it is not a ranking factor
Can add a rich result (price, rating, breadcrumb)	Yes — when the type is eligible and Google selects it
Improves click-through rate	Often — a more informative snippet earns more clicks
Guarantees a rich result will appear	No — Google shows them at its discretion
Helps assistants and aggregators parse the page	Yes — machine-readable beats prose
Replaces the need for good content and links	No — those are what earn the ranking

Notice that rankings appear exactly once in the list, under “No”. Everything the markup buys you is on the presentation side.

What Google actually says

Google’s own structured-data guidance frames markup as a way for Search to understand the content and to enable enhanced appearances. When it narrowed FAQ and retired HowTo rich results in 2023, the announcement stated plainly that the change “should not be considered a ranking change”.

The same guidance notes that structured data which is not used does not cause problems — it simply has no visible effect. That is a useful calibration: markup is a lever on appearance, not a lever on position.

Where the indirect effect lives

The one real, measurable benefit is click-through rate. A result that shows a price, a star rating or a breadcrumb trail is more informative than a plain blue link, and more informative results tend to be clicked more at the same position. More clicks means more traffic, not a better rank.

That path is real but fragile:

Rich results are shown selectively. Google may show them for one query and not another.
They can be lost. FAQ rich results were narrowed to a subset of sites; HowTo was retired outright.
Structured data that contradicts the visible page risks a manual action, which is a ranking problem.

The two types people get wrong

Most of the confusion comes from FAQ and HowTo, both of which used to be the easiest win in the toolkit:

FAQPage rich results are now shown only for well-known, authoritative government and health websites. Everyone else should treat the markup as machine-readable clarity, not a SERP feature.
HowTo rich results are deprecated entirely. There is no device, query or market where they appear.

Adding either one purely to “get rich results” is the mistake. Add them only if the type genuinely describes the page.

What is worth marking up

The types that still earn their keep are the ones that describe a real entity on the page: Organization, BreadcrumbList, Article, Product, LocalBusiness and Event. A breadcrumb is the safest starting point because every page with a path already has the data:

{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [
    { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://example.com/" },
    { "@type": "ListItem", "position": 2, "name": "Answers", "item": "https://example.com/faq" },
    { "@type": "ListItem", "position": 3, "name": "Does structured data affect rankings?" }
  ]
}

Ship markup that matches what a visitor actually sees, and expect a presentation change rather than a ranking change.

Common mistakes

Waiting for a ranking bump. Teams add markup, see no movement in position, and conclude it failed. Position is not what markup controls.

Marking up content that is not on the page. A rating, price or answer that exists only inside the JSON is a guideline violation, not a shortcut.

Chasing retired types. Adding HowTo or FAQPage in the hope of a rich result now leads nowhere for most sites.

Letting the markup drift. Once the page changes, the markup is wrong, and stale data is worse than none.

Assuming a rich result is permanent. Even valid, eligible markup can stop being displayed. Treat appearance as a bonus.

Where this tool fits

The JSON-LD generator builds these blocks from a form and validates the required fields as you type, so you ship data that is readable, accurate and maintainable — the part of structured data that actually pays off.