Blog / Technical SEO /
Schema markup in 2024: what’s still worth adding
Say a business owner adds FAQ schema and waits for the search result to bloom into a big helpful panel. The markup validates. The rich result never shows up.
That’s the reminder: structured data describes page content in a form search engines understand. It doesn’t promise a special display. In 2024, add schema when it accurately represents useful content and fits a supported feature.
Begin with the page, not the markup
Choose a page with a clear purpose: an organisation page, a product page with accurate details, an article with headline, author and dates, or breadcrumbs describing navigation. The page carries the information first. Structured data is a machine-readable copy of it, not a place to add claims visitors can’t see.
If the page is thin, misleading or out of date, JSON-LD won’t make it useful. Improve the information first, then decide whether a schema type fits and a search feature supports it. A green tick from a tool isn’t the test. The test is whether the markup matches what a person can verify.
Use markup that fits the visible content
For an organisation, make the name, URL and contact information consistent with the site. For a product, check the product name, price, currency, availability and identifiers against the actual offer. For articles, ensure the headline, author and dates reflect the published page. For breadcrumbs, represent the hierarchy users can navigate. Do not make up ratings, reviews or availability to satisfy a schema example.
Visible and structured versions drift. A price changes but the markup stays stale; a title is updated while the schema block describes the old one. If an app generates schema, inspect its output and check the theme or a second app isn’t creating duplicates. I’ve seen that overlap cause trouble on client sites. More markup isn’t better.
Be realistic about FAQ and HowTo
Google limited FAQ rich results in August 2023, showing them regularly only for well-known, authoritative government and health websites. So a typical commercial site shouldn’t add FAQ schema expecting the expanded result. A genuine FAQ section can still help people if it answers real questions. Eligibility and user value are separate.
HowTo rich results were restricted in 2023 and the feature was later deprecated in search. A tutorial may still be useful in clear steps, but HowTo markup is no sensible bet for a Google rich result in 2024. Don’t let an old plugin checklist send you hunting for enhancements that no longer apply.
Validate and monitor without chasing every warning
Use Google’s Rich Results Test for supported rich result features, and the Schema Markup Validator for broader schema.org validation. These tools answer different questions. Valid schema vocabulary doesn’t make a page eligible for a Google rich result, and a test can miss issues that appear only once the page is rendered or the template is used site-wide.
Check a representative page after deployment, then inspect Search Console’s relevant enhancement report if one is available. A report may show errors and warnings, but warnings are not all equal and a clean report does not promise visibility. Keep a record of the change and watch for template regressions when the CMS or plugin updates.
Keep the implementation maintainable
Use the CMS’s existing structured data features when they produce accurate output. Avoid adding a second plugin just because it promises more schema types. If the site has a developer, document which component owns each entity and where its values come from. This is especially helpful on sites where product data, navigation and content are generated from different systems.
When a field can’t be verified, leave it out or fix the source first. No placeholders in public structured data and no marking up hidden text. Search engines can ignore misleading markup, and data nobody can maintain gains you little.
Decide whether schema is worth the work
The practical question is whether the markup represents a real thing on the page and supports a useful search feature or data understanding. Prioritise accurate product and organisation details, article metadata and breadcrumbs when they fit the site. Treat FAQ and HowTo as content choices first, not guaranteed rich-result tactics.
Do not let a plugin decide the strategy
Many CMS plugins offer a checkbox for every schema type, which makes enabling everything seem sensible. I’d resist. Each field needs a truthful source, and each type should describe the page it appears on. If an app creates product data, inspect the page source or rendered result after a theme change. If a plugin generates organisation details, confirm that the values match the business’s current information. Keep a note of which extension owns each markup block. When a site changes hands, that documentation can save someone from adding a second implementation or deleting useful output. Schema maintenance is easier when it is treated as part of the site’s content model rather than a one-time optimisation trick.
Pick one important page and compare its visible content with its structured data. Is every field true today, and does the markup support a feature that still exists?