Do we really need to mark up article reviewers for SEO?

Why does Google ignore reviewer data in schema markup?

The statement is clear: Google does not use structured markup to display information regarding article supervisors or reviewers. Even though the 'editor' schema exists in Schema.org vocabulary, its use remains purely technical and does not yield any visible benefits in SERPs.

Specifically, if you add a "editor" attribute in JSON-LD to your content, Google will crawl it, but it will not use it to enrich snippets, knowledge panels, or any other display elements. The markup effort thus becomes fruitless from a direct SEO standpoint.

What does "the visible display is sufficient" mean in this context?

Google prioritizes what the user sees directly on the page. If the reviewer's name, role, and qualifications appear in a visible and understandable way in the HTML, that is sufficient for the content understanding algorithms to take it into account.

This aligns with the E-E-A-T logic: what matters is the editorial transparency displayed, not an invisible markup. A box stating “Reviewed by Dr. Martin Dupont, PhD in Marine Biology” at the top of the article does the job. No need to add a redundant JSON-LD layer.

In what cases is the 'editor' schema still used today?

Some CMS or plugins automatically generate this field, especially for news sites or structured blogs. The "editor" attribute remains technically valid and can serve other search engines, content aggregators, or third-party tools.

But if your goal is purely Google-centered, you can safely ignore it. There is no penalty waiting for you — it’s simply a neutral field, neither beneficial nor harmful for ranking.

• Google does not display reviewer data from structured markup in the SERPs
• The 'editor' schema exists but has no direct SEO impact on indexing or ranking
• The visible display on the page (standard HTML) is sufficient for Google to understand who reviewed the content
• No penalty for the absence of this markup — it's an optional and low-value effort
• Multi-author sites may continue to use it for internal organizational reasons or for other platforms

Is this statement consistent with observed practices in the field?

Absolutely. For years, no A/B test or field observation has shown a correlation between the addition of the 'editor' schema and an improvement in visibility, CTR, or position. Rich snippets do not elevate this field, unlike 'author' which may appear in certain contexts (Google News, old authorship).

What raises questions is why Schema.org maintains this field if Google — by far the largest consumer of this data — doesn’t use it. Likely a technical legacy or marginal use by other engines. [To verify]: Do Bing, Yandex, or Baidu utilize this markup? No public data confirms this to my knowledge.

Should we remove this markup if we have already implemented it?

No, unless it generates errors or inconsistencies in Search Console. An unnecessary but valid markup does not harm. However, if your CMS generates false or outdated data (e.g., editor mentioned while the role no longer exists), it’s better to clean up to avoid future algorithmic confusion.

The real question pertains to opportunity cost: how much time do you spend maintaining this field versus other high-ROI optimizations? If you must choose between correcting an 'editor' markup or improving your 'dateModified', 'author', or 'reviewedBy' (medical) tags, the priority is clear.

What are the alternatives to enhance editorial expertise?

Focus on visible and structured display: biographical boxes, mentions of qualifications, links to author profiles, sections “About the team.” Google analyzes standard HTML content with NLP models — a clear paragraph is better than an invisible JSON-LD.

For medical, scientific, or financial sites (YMYL), editorial transparency becomes a critical E-E-A-T criterion. Clearly display who wrote, who reviewed, who validated. But do it in human-readable HTML, not structured markup that no one will ever see.

What should you concretely do if you already have this markup in place?

Audit your current implementation. If the 'editor' schema is automatically generated by your CMS without errors, you can leave it as is — it does no harm. However, if you've developed a custom solution or dedicated plugin, ask yourself: could this time have been invested elsewhere?

Check in Search Console (Improvements section > Structured Data) if this field generates warnings or errors. If so, fix or remove it — a malformed markup can be problematic even if it is not used for display.

How to showcase editorial expertise without relying on markup?

Focus on visible display and contextual credibility. Create dedicated author/reviewer pages with detailed biographies, links to external publications, LinkedIn or ResearchGate profiles if relevant. These signals are crawlable and interpretable by Google without JSON-LD.

On each article, clearly display the reviewer's name, title, and specialty. Use semantic HTML tags (<address>, <cite>, microformats if you insist) but do not rely on structured markup to gain a competitive advantage in SERPs.

What mistakes should you avoid in managing editorial metadata?

Do not create redundant or inconsistent markup. If you mention an editor in JSON-LD but it does not appear anywhere on the visible page, that’s suspicious. Google could see it as an attempt to manipulate E-E-A-T signals — even if it is not directly penalized today.

Avoid overloading your pages with dozens of unused Schema.org fields. Simplicity prevails: better to have 5 properties utilized by Google (author, datePublished, publisher, mainEntityOfPage, image) than 20 dormant fields that weigh down the DOM and complicate maintenance.

• Check if the 'editor' schema generates errors in Search Console — correct or remove if it does
• Prioritize the visible display of reviewers/supervisors in standard HTML rather than in invisible JSON-LD
• Create dedicated author/reviewer pages with biographies, qualifications, and verifiable external links
• Do not waste time developing or maintaining an 'editor' markup if the goal is purely Google SEO
• Audit the entire structured markup to eliminate redundant or unused fields
• Invest in visible E-E-A-T signals (About, editorial transparency, clear legal mentions)