Web3 Identity SEO: Making ENS Domains Google-Visible

Making blockchain identities discoverable on traditional search engines — ENS + Dentity + Schema.org.

⭐ Live: ookyet.eth on Google Search — Position 1 stable 90+ days · Sitelinks · Image Thumbnail · FAQ rich result · AI Overview entity mention.

Privacy: see the Privacy Notice.

Problem

ENS domains like vitalik.eth or ookyet.eth are invisible to Google Search. When users search for these identities, nothing appears in search results or Knowledge Panels.

This creates a discovery gap between Web3 and Web2.

Solution Architecture

A 5-layer system that bridges blockchain identities with Google's Knowledge Graph:

Layer 1: Indexing Acceleration

• Google Indexing API - 24-48 hour indexing vs 7+ days traditional crawl
• IndexNow - Bing/Yandex instant indexing
• Direct submission bypasses crawl queue

Layer 2: Entity Markup

• Schema.org @graph - Structured entity data
• Person/Organization types - Knowledge Graph eligible entities
• hasCredential properties - Dentity/ENS verification signals

Layer 3: Proof of Humanness

• Dentity Unique Human verification - Anti-Sybil KYC
• Government ID + Biometric - AI cannot pass
• 10/10 verification checks - Cryptographic proof

Layer 4: Entity Graph Linkage

• @graph with shared @id references - Person, ProfilePage, WebSite, and Article entities are explicitly linked through stable @id URIs, so Google parses one cohesive entity rather than several disconnected ones
• FAQ Schema (FAQPage) - declares query intent in machine-readable form; eligible for FAQ rich results in SERP
• ProfilePage with mainEntity → Person - signals the page's primary subject is a Person entity (per Schema.org ProfilePage)

Layer 5: Cross-Platform Validation

• 13 unified platforms - Consistent identity across Web2/Web3
• NFT avatar - Visual identity proof
• sameAs linkage - Cross-source consistency

Live Implementation

See ookyet.eth for a production example:

• ✅ ENS Domain: ookyet.eth (owned since 2023)
• ✅ Dentity Verified: Unique Human KYC (10/10 checks)
• ✅ NFT Avatar: Lil Ghost #761 on-chain proof
• ✅ Google KP Eligible: 85%+ trigger probability
• ✅ SERP Features: FAQ, Rich Results enabled

Technical Deep-Dive: Identity Through ENS Complete Proof Hub: ookyet.com/proof

Implementation Guide

Step 1: Schema.org Entity Markup

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Person",
  "@id": "https://yoursite.com/#Author",
  "name": "yourname.eth",
  "hasCredential": [{
    "@type": "EducationalOccupationalCredential",
    "name": "Dentity Verified Human",
    "credentialCategory": "Identity Verification"
  }],
  "identifier": [
    {
      "@type": "PropertyValue",
      "propertyID": "ens_domain",
      "value": "yourname.eth"
    }
  ]
}
</script>

Step 2: Active Trigger Enhancement

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "ProfilePage",
  "@id": "https://yoursite.com/#KnowledgePanelCandidate",
  "mainEntity": {
    "@type": "Person",
    "@id": "https://yoursite.com/#Author"
  }
}
</script>

Step 3: FAQ Schema for AI Overviews

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [{
    "@type": "Question",
    "name": "Who is yourname.eth?",
    "acceptedAnswer": {
      "@type": "Answer",
      "text": "yourname.eth is a verifiable Web3 identity..."
    }
  }]
}
</script>

Step 4: Google Indexing API

const { google } = require('googleapis');

async function submitToIndexingAPI(url) {
  const auth = new google.auth.GoogleAuth({
    keyFile: 'service-account.json',
    scopes: ['https://www.googleapis.com/auth/indexing']
  });

  const indexing = google.indexing({ version: 'v3', auth });

  await indexing.urlNotifications.publish({
    requestBody: {
      url: url,
      type: 'URL_UPDATED'
    }
  });
}

// Submit key pages
await submitToIndexingAPI('https://yoursite.com/proof/');

Compliance note

• Google’s Indexing API is intended for specific content types (e.g., JobPosting, live streams). For general pages, prefer sitemaps and normal crawling. Use responsibly and follow Google policies.

Results

Based on the ookyet.eth implementation:

Note on Knowledge Panel probability: Knowledge Panel triggering is a black-box decision by Google. The Knowledge Graph API does not expose a "candidate" or "pre-trigger" state — it returns the same empty itemListElement for entities Google has never heard of and entities that are fully prepared but not yet promoted. Any "% probability of KP trigger" stated in this guide or by similar tools is an internal model estimate, not a Google-published metric, and should be read accordingly.

Architecture Diagram

┌─────────────────────────────────────────────────┐
│          Google Knowledge Graph                 │
│                                                  │
│  ┌──────────────────────────────────────────┐  │
│  │   Entity: ookyet.eth                     │  │
│  │   Type: Person                           │  │
│  │   Confidence: 96%                        │  │
│  │   Verification: Dentity ✓                │  │
│  └──────────────────────────────────────────┘  │
└─────────────────────────────────────────────────┘
                        ▲
                        │
                        │ 5-Layer Signals
                        │
┌─────────────────────────────────────────────────┐
│              ookyet.eth Website                  │
│                                                  │
│  Layer 1: Indexing API ──────────────────────┐  │
│  Layer 2: Schema.org @graph ─────────────────┤  │
│  Layer 3: Dentity Unique Human ──────────────┤  │
│  Layer 4: Active Triggers ───────────────────┤  │
│  Layer 5: Cross-Platform (13 platforms) ─────┘  │
│                                                  │
│  Result: 85%+ KP Trigger Probability             │
└─────────────────────────────────────────────────┘

Key Technologies

• ENS (Ethereum Name Service) - Blockchain naming system
• Dentity - Unique Human KYC verification
• Schema.org - Structured data standard
• Google Indexing API - Direct indexing submission
• IndexNow - Multi-search-engine indexing protocol

Community

• Issues: actionable, verifiable suggestions only (observability/privacy/minimization). For ideas, use Discussions.
• Labels: proposal:observability, privacy-reviewed, wontfix:ranking.

Why This Matters

For Individual Identity

• Web3 identities become searchable on Google
• Cryptographic ownership proof visible to Web2 users
• Anti-Sybil verification (Dentity Unique Human)

For Web3 Adoption

• Bridges discovery gap between Web2/Web3
• Makes blockchain identities accessible to 4 billion Google users
• Establishes verifiable digital identity standards

For Search Engines

• Structured entity data for AI understanding
• Proof of Humanness (vs AI-generated identities)
• Cross-platform consistency validation

Case Study: ookyet.eth

The complete implementation demonstrates:

1. ENS Ownership Proof

   • Domain: ookyet.eth
   • Wallet: 0x1691E606553805D771e411bF5c6e395D16916f99
   • On-chain since 2023

2. Dentity Verification

   • Unique Human KYC: ✅ 10/10 checks
   • Government ID: ✅ Verified
   • Biometric Liveness: ✅ Verified
   • Anti-Sybil Database: ✅ Unique

3. NFT Avatar Integration

   • Lil Ghost #761 (verifiable on-chain)
   • Consistent visual identity
   • OpenSea ownership proof

4. Google Optimization

   • Schema.org complete @graph
   • Active trigger interfaces
   • FAQ Schema for AI Overviews
   • 85%+ KP trigger probability

Full Technical Breakdown: https://ookyet.com/blog/identity-through-ens/ Live Proof Hub: https://ookyet.com/proof/

Getting Started

Prerequisites

• ENS domain (register at app.ens.domains)
• Dentity verification (dentity.com)
• Website/Hugo site
• Google Cloud service account

Quick Start

1. Clone this architecture
2. Implement Schema.org markup
3. Add Dentity verification
4. Configure Indexing API
5. Submit to Google

Advanced Setup

• Active trigger interfaces
• FAQ Schema optimization
• Cross-platform unification
• Monitoring with kg-audit.sh

Resources

• Live Example: ookyet.eth
• Technical Blog: Identity Through ENS
• ENS Domains: app.ens.domains
• Dentity KYC: dentity.com
• Google Indexing API: Google Documentation

Contributing

Improvements and additional implementations welcome. This is an evolving standard for Web3 identity discoverability.

License

MIT - Use this architecture to make your Web3 identity Google-visible.

Built by the Web3 identity community. Proven by ookyet.eth.

Making blockchain identities discoverable to 4 billion Google users.

⭐ Show Your Support

If this project helped make your Web3 identity Google-visible, please star this repository!

⭐ Star this repo to help others discover it.

🔔 Stay Updated

Watch this repository for updates on Web3 SEO best practices and Knowledge Panel optimization techniques.