Do you really need to stick to the supported page types for the reviewed-by schema?

What is the reviewed-by markup and why does Google limit it?

The reviewed-by markup indicates that content has been verified by a qualified expert. Google introduced it mainly for medical content, where the reliability of information can have direct consequences on users' health.

The restriction to supported page types is not a technical whim. It is a deliberate editorial decision: Google wants to activate this signal only in YMYL areas where expert verification adds measurable value. Currently, MedicalWebPage is the main application field.

Why does schema.org allow certain combinations that Google ignores?

Schema.org is an open and extensible vocabulary. It technically allows reviewed-by to be added to many types of content, including NewsArticle or BlogPosting. However, just because the vocabulary permits it doesn't mean Google will take it into account.

The engine applies its own eligibility rules. It reads the markup, checks the declared page type, and if this type is not on its internal whitelist, it simply ignores reviewed-by. No error in the Search Console, no alert — just radio silence.

How can you know which page types are actually supported?

The official Google documentation on structured data remains the only reliable source. For reviewed-by, only MedicalWebPage is explicitly mentioned as of today. Some publishers have tested other types without observing any rise in rich results.

The problem? Google rarely updates this list proactively. You need to monitor official announcements, Mueller's interventions, or changes in the Search Console to detect potential openings for other types of content.

• Reviewed-by works only on page types explicitly supported by Google, not on all those allowed by schema.org
• Forcing implementation on an undocumented type (NewsArticle, Recipe, etc.) generates no measurable SEO benefit
• The official Google documentation on structured data is the only reference for knowing eligible types
• MedicalWebPage remains the main validated use case for reviewed-by to this day
• No errors appear in the Search Console if the markup is ignored — making diagnosis difficult

Is this restriction consistent with Google's YMYL strategy?

Yes, perfectly. Google is progressively tightening its requirements on Your Money Your Life content. The reviewed-by markup on MedicalWebPage aligns with this logic: it strengthens the E-E-A-T signal by clearly identifying who validated the information.

What is striking is the reluctance to extend this markup to other YMYL verticals. Finance, law, nutrition — these are areas where expert validation would bring real value. But Google is making slow progress, likely to limit abuse.

In what cases could this markup become relevant elsewhere?

On the ground, some publishers of legal or financial content have attempted to implement reviewed-by on NewsArticle or BlogPosting-type articles. Result: zero visible impact, even with experts clearly identified via schema Person.

It is likely that Google is internally testing the extension of this markup to other types. But until an official announcement comes to broaden the scope, it is better to focus your efforts on documented types rather than speculate. [To be verified] regularly through documentation updates.

What are the consequences of non-compliant implementation?

Technically, nothing catastrophic. The markup will simply be ignored, with no penalty. But this is wasted development time and a source of confusion for teams who think they have implemented a functional E-E-A-T signal.

More insidiously, it can mask underlying issues. If you rely on reviewed-by to compensate for a deficit in editorial authority, you are missing the real issue. E-E-A-T signals fundamentally depend on the intrinsic quality of the content and the author's reputation, not on an isolated markup.

What should you do if you have already implemented reviewed-by on unsupported types?

Start with a thorough audit of your existing markups. Identify all content where reviewed-by is present and check the declared page type. If this type is not in the official Google documentation, you know that the markup is inert.

Then, two options: either you remove the markup to lighten your code and avoid confusion, or you leave it in anticipation of a potential future expansion. Personally, I prefer to clean up — a non-functional markup adds nothing and creates technical debt.

How to implement reviewed-by correctly on MedicalWebPage?

If you manage a medical site, ensure that your pages properly use @type: "MedicalWebPage" and not WebPage or Article. The reviewed-by should point to a clearly identified Person or Organization entity, with a name, qualifications, and ideally a unique identifier (sameAs linking to a LinkedIn profile, a professional directory, etc.).

Always test with the Google Rich Results Test. If reviewed-by appears in the recognized properties, that's a good sign. If not, check the JSON-LD syntax and the page type. And keep in mind that even with perfect markup, Google may choose not to display it in the SERPs — it's a signal among others, not an automatic trigger for rich results.

Should we anticipate the extension of reviewed-by to other types of content?

It's hard to predict Google's timeline. What is certain is that the finance, law, and nutrition verticals are logical candidates. If you operate in these sectors, prepare your authors and reviewers: having well-documented expert profiles will be a prerequisite.

In the meantime, focus on classic E-E-A-T signals: detailed author bios, mentions of qualifications, links to external publications, citations from third-party sources. These elements already work, with or without reviewed-by. The markup will enhance an existing signal, not create one from scratch.

Ensuring compliance with structured data and optimizing E-E-A-T signals requires sharp technical and editorial expertise. If your internal teams lack resources or specific skills in these areas, support from a specialized SEO agency can save you valuable time and prevent costly visibility errors.

• Audit all existing reviewed-by markups and verify their page type
• Remove non-compliant markups or leave them on standby depending on your strategy
• On medical sites, exclusively use @type: "MedicalWebPage"
• Document reviewers with Person or Organization, including qualifications and identifiers
• Test with Rich Results Test and monitor recognized properties
• Watch for official Google announcements to detect the extension to other types