9 April 2026 , Blackgate
Schema markup (usually JSON-LD in a script tag) describes your content in a structured vocabulary search systems understand. It can enable rich results where eligible, but the main reason to do it well is honest labelling - what the page is, who published it, and what questions the FAQ actually answers. It does not fix weak content; it should match what users see on screen.
Technical SEO basics like crawlability and Core Web Vitals still come first; see technical SEO priorities and Core Web Vitals in plain language if the foundation is shaky.
Article / BlogPosting
Use Article or BlogPosting when the URL is a dated editorial piece with a clear headline, date published (and modified when you materially update), author where you have a real byline, and publisher for the organisation. Image should reference what actually represents the article.
In day-to-day work, the useful question is: if a colleague read only the JSON-LD and the visible page, would they describe the same piece of content? If not, fix the page or the markup before you worry about rich results.
Do not mark thin affiliate pages or duplicate syndication as an “article” to chase rich snippets - that is a policy and trust problem.
FAQ
FAQPage is appropriate when the same FAQ is visible to users on the page, with question/answer pairs you stand behind. Inflating generic FAQs to capture queries - or content that is not a real FAQ layout - is exactly what search systems have pushed back on.
The awkward middle ground is the “FAQ” that is really a list of long-tail keyword paragraphs. Users skim past it; search systems have seen the pattern. Prefer fewer, honest Q&As that match what your contact form and sales team actually hear.
Breadcrumbs, organisation, and sitelinks
BreadcrumbList helps with navigation in results when your hierarchy is real. Organization (and LocalBusiness where it fits) on the home or about pages can clarify entity for the site. Keep IDs and URLs canonical and consistent with the live page.
Breadcrumbs in schema should mirror the breadcrumb trail a person sees, not a fantasy hierarchy invented for SEO. Mismatches are small on the page; they are confusing when a machine reads both the template and the markup.
Testing and maintenance
Schema has a long half-life in memory — teams forget to update the template when the design changes, and then errors in Search Console look like a crisis. Bake validation into the same moment you ship front-end changes.
- Use Rich Results Test to validate, then spot-check in GSC after deploy.
- When templates change, regenerate or include schema in the same deploy so markup does not rot.
Frequently asked questions
Does schema improve rankings?
It can affect appearance (rich results) and understanding; it is not a direct “ranking boost” for irrelevant pages.
JSON-LD vs microdata?
JSON-LD is the most maintainable for most modern stacks; keep it in sync with the template.
Should every page have schema?
Meaningful types only. Blanket markup across everything dilutes value and can trigger manual issues if wrong.
What about product and review schema?
Valid when the page has real product or review content - follow current quality and relevance guidelines for your market.
Where does this fit in a topic strategy?
Topical map - pillars and clusters for how to structure content; schema describes what a given URL is.