Articles

Schema

Add schema that supports the page instead of decorating it.

Structured data works best when it matches the real page: article, FAQ, breadcrumb, product, service, organization, or software details that users can verify.

Schema is strongest when it reinforces what is already visible on the page.

Article schema can clarify the headline, description, dates, author, and publisher. Breadcrumb schema helps search engines understand location. FAQ schema only belongs when the page actually includes question-and-answer content.

FAQ and HowTo markup are worth a note of their own. Google removed HowTo rich results in September 2023 and stopped showing FAQ rich results in May 2026, so neither is a route to a display feature any more. Both are still valid, still recognized structured data, and still the clearest way to describe questions and steps to an answer engine — but a page should carry them because the visible content is genuinely a question set or a step sequence, not to earn a result Google no longer shows.

Adding markup that exaggerates the page creates maintenance risk and can make the content look less trustworthy.

Content Miner checks whether the page has the right structured signals for its job, then keeps the recommendation tied to the visible content.

How to audit this page type

A useful content audit should be repeatable. Instead of rewriting from instinct, build a small evidence trail for the URL, the pages around it, and the reason a change is worth making.

1. Check the page by itself.

Start with the public checker so the page has a baseline across SEO, GEO, AEO, and AIO. For schema, the first pass should show whether the page has enough visible structure, metadata, headings, and answer coverage to deserve deeper review.

2. Compare it against the surrounding content.

A single URL can look fine until it is compared with the rest of the site. The site scan is where duplicate intent, repeated answers, weak ownership, and competing internal links become easier to see.

3. Choose the smallest honest action.

The right fix is not always a rewrite. Some URLs need a stronger summary, some need schema cleanup, some should be merged into a better page, and some should stay because they serve a distinct role.

What to check before changing the page

  • Confirm the page has one clear job and that the title, H1, summary, and primary section headings all support that job.
  • Compare the URL against nearby pages before rewriting. Schema issues are often library issues, not isolated page issues.
  • Check whether the page is indexable, canonical to itself, included where appropriate in the sitemap, and reachable from internal links.
  • Look for answer-ready sections: a direct explanation, useful examples, limitations, and a next step that fits the reader's intent.
  • Record the decision before making changes so the team knows whether the URL should be combined, differentiated, updated, or kept.

This keeps the audit grounded. The goal is not to create more pages or chase a score in isolation. The goal is to make the strongest page easier to find, easier to understand, and easier to trust.

Practical audit notes

Match structured data to visible content.

Schema should describe what the page actually contains. Article, breadcrumb, organization, software, FAQ, product, and service markup all have a place, but only when the content supports the markup.

Use schema to support trust.

Dates, authors, publishers, product names, and breadcrumbs help machines understand the page. They also create maintenance obligations, so the markup should stay aligned with the visible page.

FAQ

How does Content Miner evaluate schema?

Content Miner looks at the page in context: the visible content, metadata, headings, schema signals, internal structure, and nearby pages that may be competing for the same intent.

Should I rewrite the page as soon as a score is low?

No. A low score is a triage signal, not an automatic rewrite order. The next step is to read the evidence, check whether another page already owns the intent, and decide whether to combine, differentiate, update, or keep the page.

Why does the article mention the portal?

The public checker is useful for one URL. The portal is where full-site overlap groups, saved scan history, exports, and plan access live, so larger cleanup decisions do not disappear after one anonymous check.

Next stepCheck a page or run the gated duplicate-content scan.
Try checker