Should you really invest in structured markup if Google is ignoring authorship?

Why does Google prioritize entities over authors?

Google has shifted from a web pages focus to one on interconnected entities. The engine seeks to comprehend the relationships between people, places, concepts, and organizations to accurately respond to complex queries.

Structured markup via schema.org facilitates this mapping. When you mark up a product with Product, a place with LocalBusiness, or an event with Event, you provide data that can be utilized by the Knowledge Graph. The author? It is a weak entity in the current ranking equation.

What does this disinvestment in authorship really mean?

From 2011 to 2014, Google launched and then abandoned Google Authorship, which displayed the author's photo and name in the SERPs. The signal was strong: your identity mattered. Today, Mueller confirms that this author-content link is no longer used as a ranking factor.

The engine is more interested in what is said rather than who wrote it and how it fits into its knowledge graph. Your recognized expertise elsewhere (Wikipedia, Wikidata, LinkedIn) can play a role, but the isolated Author markup holds no weight.

Are all types of markup equal for Google?

No. Google prioritizes valuable structured data: data that enriches its rich snippets, supports Google Shopping, enhances Maps, or structures Featured Snippets. Product, Recipe, HowTo, FAQPage, and Organization demonstrate proven ROI.

Markups such as Author, Person, or even certain fields in Article are technically valid but ineffective for ranking. Google may ingest and store them, but they are not utilized in the visible algorithm. This is passive data.

• Priority entities: products, organizations, places, events, FAQs, recipes, videos
• Authorship markup: technically correct, but no SEO impact observed
• Schema.org remains essential for structuring content that can be leveraged by the algorithm
• The Knowledge Graph feeds off Wikidata, Wikipedia, and recognized public entities, not local Author markup
• A famous author benefits from indirect entity associations, not from HTML code

Is this statement consistent with what is observed on the ground?

Yes, completely. For years, A/B tests on adding or removing Author markup have shown no measurable difference in ranking. Sites that have heavily implemented Person and Author have never outperformed those that have omitted them.

On the other hand, the gains from Product, FAQPage, HowTo, or VideoObject are documented everywhere. Google displays this data in SERPs, generates rich snippets, and boosts CTR. Authorship? Nothing. Even for YMYL content where expertise should matter.

What nuances should be added to this view?

Google claims to invest in entities. But which ones exactly? [To be confirmed] — the statement remains vague. We know that Organization, Brand, and Place are utilized. For Person, it's murky: a Person entity connected to Wikidata or a verified LinkedIn profile can create indirect connections.

The problem is that Google never documents these mechanisms. We can only guess through correlation. A well-known author with a Wikipedia page likely benefits from an indirect authority signal, not due to markup, but because of their recognized external entity.

In which cases does authorship markup retain some residual value?

For internal semantic consistency and preparing for any potential return of Google on the topic. If tomorrow the algorithm reintegrates authorship, those who have maintained the markup will be ready. Minimal marginal cost, potential future benefit.

Another scenario: alternative engines and third-party tools. Bing, Yandex, and some content aggregators utilize this data. If your traffic comes from more than just Google, it might matter. But let’s be honest: for 95% of French-speaking sites, Google is the only judge.

What should be prioritized for implementation on your site?

Focus on structured data with direct impact. If you are selling, use Product and Offer. If you publish practical content, utilize HowTo and FAQPage. If you have a local business, LocalBusiness with all properties (hours, reviews, geolocation) is essential.

Forget the obsession with Author markup unless you maintain a global consistency for other reasons (syndication, partnerships). Do not waste time linking every article to a detailed Person profile if Google ignores it.

What mistakes should be avoided in the implementation of schema.org?

The first mistake: overloading markup with unnecessary entities. Marking up Author, Publisher, Editor, Contributor on every page is pointless if the engine does not read them. You are polluting your code for zero return.

The second mistake: believing that markup compensates for weak content. Google reads the text, HTML structure, and user signals first. Schema.org comes after. A poorly written article with perfect markup will never rank.

How can I check if my structured data is being utilized by Google?

Use the Search Console, under the Enhancements section. Google explicitly tells you which types of rich snippets it detects and displays. If your Author or Person markups never appear in the reports, they are being ignored.

Also test using Google's Rich Results Test tool. It validates the syntax but primarily shows you what Google can display in SERPs. No authorship preview? Normal, Google does not use it.

• Audit current structured data: keep only those with proven ROI (Product, FAQ, HowTo, Organization)
• Remove or archive complex Author/Person markups if there is no external use (Bing, syndication) justifying them
• Implement FAQPage on high potential Featured Snippet pages
• Link the Organization entity to verified social profiles (sameAs) to strengthen the Knowledge Graph
• Monitor Search Console quarterly: if a markup type never appears in reports, question its usefulness
• Prioritize content quality and classic E-E-A-T signals (backlinks, mentions, reputation) over isolated markup