On Mastodon, verified accounts have green checkmarks next to their profile links — not because they paid for verification, but because they proved ownership through a simple HTML attribute called rel="me". It is the most honest verification system on any social platform: you prove you own a domain by adding a link, and the platform verifies it automatically.

But rel="me" does more than generate green checkmarks. It creates machine-readable identity connections between your website and your social profiles. Search engines, AI systems, and other platforms use these connections to build a unified picture of your identity across the web — which directly supports Google's E-E-A-T evaluation of your expertise and authority.

I implemented rel="me" links across every site and profile in our 52-site network. The implementation took 20 minutes per site and created a web of verified identity connections that strengthens both fediverse credibility and search engine authority signals.

How rel="me" Works

The rel="me" attribute is an HTML microformat that declares: "This link points to another representation of me." When two pages link to each other with rel="me", they establish a bidirectional identity claim — each page is saying "that page is also me."

On your website:

<a href="https://mastodon.social/@yourhandle" rel="me">Mastodon</a>
<a href="https://github.com/yourusername" rel="me">GitHub</a>
<a href="https://www.linkedin.com/in/yourprofile" rel="me">LinkedIn</a>

On your Mastodon profile, add your website URL as a profile link. Mastodon checks your website for a rel="me" link pointing back to your Mastodon profile. If it finds one, it displays a green checkmark next to the link, confirming you own that domain.

The verification is automatic, free, and based on actual ownership proof — not payment or celebrity status.

Platforms That Support rel="me"

Mastodon (Green Checkmark)

Mastodon is the most visible implementation. Profile links verified through rel="me" get a green background and checkmark icon. This is the primary trust signal on Mastodon, equivalent to a blue checkmark on other platforms but based on domain ownership rather than payment.

To set up:

  1. Add your Mastodon URL to your website with rel="me"
  2. Add your website URL to your Mastodon profile's "Profile metadata" fields
  3. Mastodon verifies the bidirectional link and displays the green checkmark

GitHub

GitHub profile pages include a website field. When your website links back to your GitHub profile with rel="me", search engines can connect the two identities. GitHub does not display a visual indicator, but the machine-readable connection strengthens entity signals.

IndieWeb Ecosystem

The broader IndieWeb community uses rel="me" extensively for identity consolidation. Platforms like IndieLogin.com use rel="me" chains for authentication — you can log into IndieWeb services using just your domain name, verified through rel="me" links.

Search Engines

Google has acknowledged using cross-platform identity signals for E-E-A-T evaluation. While Google does not explicitly state that it follows rel="me" links, the sameAs property in Schema.org structured data serves the same purpose — and rel="me" links complement schema markup by providing an additional, standards-based identity connection.

Implementation for E-E-A-T

Website Footer Links

Add rel="me" to every social profile link in your website footer:

<footer>
  <nav aria-label="Social profiles">
    <a href="https://mastodon.social/@jawatte" rel="me">Mastodon</a>
    <a href="https://github.com/jawatte" rel="me">GitHub</a>
    <a href="https://www.linkedin.com/in/jawatte" rel="me">LinkedIn</a>
    <a href="https://bsky.app/profile/jawatte.bsky.social" rel="me">Bluesky</a>
  </nav>
</footer>

Head Link Elements

For profiles that you want to verify without displaying visible links, add <link> elements in the HTML <head>:

<head>
  <link rel="me" href="https://mastodon.social/@jawatte">
  <link rel="me" href="https://github.com/jawatte">
</head>

This method is invisible to visitors but readable by machines.

Author Pages

If your site has an author or about page, add rel="me" links alongside your bio. This page becomes your canonical identity hub — the single URL that connects to all your other profiles.

Schema.org Complement

Combine rel="me" links with Schema.org sameAs properties for maximum identity signal strength:

{
  "@context": "https://schema.org",
  "@type": "Person",
  "name": "J.A. Watte",
  "url": "https://theresaletrap.com",
  "sameAs": [
    "https://mastodon.social/@jawatte",
    "https://github.com/jawatte",
    "https://www.linkedin.com/in/jawatte",
    "https://www.amazon.com/author/jawatte"
  ]
}

The sameAs array tells Google explicitly: all of these profiles represent the same entity. Combined with rel="me" links, this creates redundant identity verification that strengthens entity resolution in Google's Knowledge Graph.

The E-E-A-T Connection

Google's E-E-A-T guidelines evaluate whether a content creator is a real, credible person with relevant expertise. Cross-platform identity verification directly supports this evaluation:

Experience

Profiles on platforms like GitHub (code contributions), LinkedIn (work history), and Mastodon (community participation) demonstrate active engagement with your topic area. A verified identity across these platforms signals real-world experience.

Expertise

LinkedIn credentials, GitHub repositories, and published works on Amazon — all connected through rel="me" and sameAs — create a verifiable expertise trail. Google can evaluate whether the author has credentials relevant to the content they are publishing.

Authoritativeness

A consistent identity across high-authority platforms (GitHub DA 95, LinkedIn DA 98, Amazon DA 96) creates authority signals through association. The verified bidirectional connections prove that the same person controls all these profiles.

Trustworthiness

Verified identity reduces the risk of impersonation and content misattribution. A content creator who can be verified across multiple platforms is more trustworthy than an anonymous author with no verifiable identity.

Cross-Network Implementation

For our 52-site network, I implemented rel="me" links in three layers:

Layer 1: Each site links to the author's social profiles. Every site footer includes rel="me" links to Mastodon, GitHub, LinkedIn, and Bluesky.

Layer 2: Each site links to the other network sites. This creates a visible connection between all sites in the network, demonstrating that they are operated by the same entity.

Layer 3: All social profiles link back to the primary website. The primary domain (jwatte.com) serves as the identity hub, with all social profiles pointing back to it.

The result is a web of verified identity connections that a search engine or AI system can traverse to build a complete picture of the author entity.

Verification Checklist

For each platform:

  1. Add the platform URL to your website with rel="me"
  2. Add your website URL to the platform profile
  3. Verify the bidirectional link is working (Mastodon shows green checkmark, use browser DevTools to verify rel="me" on other platforms)
  4. Add the platform URL to your Schema.org sameAs array

Platforms to connect:

Results

After implementing rel="me" across the entire network:

Implementation time: 20 minutes per site for rel="me" links, plus 30 minutes for Schema.org sameAs updates across the network.

Identity verification is not glamorous work. But in a web increasingly populated by AI-generated content from faceless sources, proving that you are a real person with verifiable credentials across multiple platforms is a trust signal that compounds over time.

For the complete identity and authority building strategy, see The Resale Trap and The $100 Dollar Network.

Want the Full Data?

This article draws from The Resale Trap — 395 pages of sourced research covering total cost of ownership, all 50 states ranked, insurance mechanics, and more.

Buy on Amazon Preview Chapter 1

Part of The Trap Series

The W-2 Trap → The $97 Launch → The Condo Trap → The Resale Trap