Official statement
Other statements from this video 1 ▾
Google permits the addition of the ?rel="author" parameter in profile URLs to circumvent the inability to modify a site's HTML. This workaround targets authors publishing on third-party platforms without access to the code. In practice, it offers a technical alternative, but raises questions about the reliability of the signal and its actual processing by algorithms.
What you need to understand
Why does Google offer this alternative to the traditional rel="author"?
The traditional rel="author" attribute is embedded directly in a page's HTML to create a link between content and the author's Google profile. The issue is that not all authors have access to the source code of their sites, especially on third-party blogging platforms, multi-author news sites, or locked CMS.
Therefore, Google introduced an alternative method via a URL parameter. The author adds ?rel=author to their Google profile URL when sharing or referencing it. This technical trick allows for signaling authorship without modifying the HTML.
How does this URL parameter technically work?
The mechanism relies on server-side detection by Google. When a user visits a profile URL containing ?rel=author, Google records this authorship intention. The search engine then associates the contents linked to this profile in its knowledge graph.
Specifically, the author shares their Google+ profile URL (back in the day) or Google Business Profile with this parameter on their articles. Google's crawlers follow these links and establish the author-content match. It is an indirect signal, less reliable than HTML rel="author", but functional in constrained environments.
What are the limitations of this approach compared to native HTML?
The primary weakness lies in the verifiability of the signal. An HTML attribute in the source code is explicit, easily crawlable, and difficult to manipulate. A URL parameter, on the other hand, depends on the presence of an external link and its discovery by bots.
Moreover, this method relies on a proprietary Google infrastructure (Google profiles). If the author deletes their profile or if Google alters its processing rules, the signal disappears. Finally, there is no guarantee on the actual weight attributed to this parameter versus the HTML attribute.
- The ?rel="author" is a workaround for authors without HTML access
- The signal relies on the detection of a URL parameter during the crawling of Google profiles
- This method is less reliable than a native HTML attribute for establishing authorship
- Google can modify or discontinue this processing without notice
- No guarantees exist regarding the real impact on rankings or SERP display
SEO Expert opinion
Does this statement still reflect an operational reality today?
Let’s be honest: Google officially abandoned the authorship feature in 2014, removing the display of author photos in SERPs. This statement regarding the ?rel="author" parameter dates back to the Google+ era and has no direct relevance to the search engine's current public features. [To verify] if this signal continues to feed internal knowledge graphs or expertise scoring systems.
Field observations indicate that Google now prioritizes other authority signals: Author schema in structured data, repeated mentions of an author associated with an area of expertise (EAT), verified social profiles. The traditional rel="author" or its parametric equivalent no longer generates visible advantages in search results.
Is the URL parameter still a relevant signal for EAT?
Google has gradually shifted to a multifactor evaluation of author expertise. The Quality Raters Guidelines value detailed biographies, external references, publications on recognized sites. A simple URL parameter is insufficient to establish this credibility.
However, in YMYL verticals (health, finance), some indications suggest that Google crawls and stores author-content relationships to feed its understanding models. It is impossible to assert that ?rel="author" still plays a role, but Author structured data (JSON-LD) is actively utilized. Prefer this standardized and documented method.
What risks does this approach pose for a professional site?
Relying on a proprietary and outdated Google mechanism creates a fragile technical dependency. If you build your authorship strategy solely on this parameter, you have no recourse or visibility on its actual processing. Web standards (schema.org) offer a sustainable and verifiable alternative.
Moreover, this method requires that each author maintain an up-to-date and public Google profile. In a GDPR and data protection context, forcing contributors to expose a Google profile can pose compliance or acceptability issues. Opt for a decentralized and controllable implementation via JSON-LD on the site.
Practical impact and recommendations
Should this parameter still be implemented in your content?
The short answer is: no, it's no longer a priority. Google has disabled authorship display in SERPs and no longer officially documents this parameter in its current guidelines. Investing time in this method diverts resources from more impactful optimizations.
Instead, focus on implementing Author schema in JSON-LD, with properties name, url, sameAs linking to verified social profiles. This approach is standardized, crawlable, and utilized by Google Discover, Google News, and rich features. It also meets the needs of other engines (Bing, Yandex) that respect schema.org.
How to migrate from a rel="author" strategy to modern structured data?
Audit your pages to identify old rel="author" attributes in the HTML. Remove them or leave them in place (they are simply ignored), but do not rely on them anymore. Then deploy a Person schema for each author in your CMS, with detailed properties: name, bio, canonical author URL, links to LinkedIn, Twitter, ORCID if applicable.
Integrate this schema into each article through an Article object with author property. Google will explicitly associate the content with an author entity, feeding its EAT understanding models. Test the implementation with the Rich Results Test and Search Console to validate the correct interpretation of the data.
What alternatives can be offered to authors without HTML access?
If your contributors publish on third-party platforms, prioritize rich author biographies hosted on your own domain. Create /author/first-last-name pages with complete Person schema, a list of publications, and social links. These pages become reference hubs for Google, associating the author with topical expertise.
On external platforms (Medium, LinkedIn), ensure that the author consistently mentions a backlink to their author page on your main site. This signal of coherence helps Google consolidate the digital identity. Complement with a Google Business Profile or Knowledge Panel if the author is a recognized personality in their field.
These technical optimizations around authorship and EAT require in-depth SEO expertise and rigorous monitoring. Poorly configured schema.org implementations can create crawl errors or contradictory signals. For a robust and scalable author authority strategy, partnering with a specialized SEO agency helps secure the investment and adapt tactics to algorithmic changes.
- Replace any HTML rel="author" attribute with a complete JSON-LD Author schema
- Create dedicated author pages with Person schema and list of publications
- Validate the implementation via Rich Results Test and Search Console
- Establish verified social profiles and reference them in sameAs
- Regularly audit the consistency of cross-platform author identity signals
- Document author expertise through detailed biographies and external references
❓ Frequently Asked Questions
Le paramètre ?rel="author" fonctionne-t-il encore en 2025 ?
Quelle est la différence entre rel="author" HTML et le paramètre d'URL ?
Dois-je supprimer les anciens attributs rel="author" de mon site ?
Les données structurées schema.org Author remplacent-elles rel="author" ?
Comment prouver l'expertise d'un auteur pour l'EAT sans authorship visible ?
🎥 From the same video 1
Other SEO insights extracted from this same Google Search Central video · duration 3 min · published on 09/08/2011
🎥 Watch the full video on YouTube →
💬 Comments (0)
Be the first to comment.