Making blockchain identities discoverable on traditional search engines.

⭐ Live Example: ookyet.eth - 85%+ Knowledge Panel trigger probability

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.

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

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

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

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

• knowledge_graph_eligible flag - Google internal entity marker
• FAQ Schema - Query intent pre-computation
• ProfilePage + MainEntity - Primary entity declaration

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

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

<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"
    },
    {
      "@type": "PropertyValue",
      "propertyID": "knowledge_graph_eligible",
      "value": "verified_entity"
    }
  ]
}
</script>

<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>

<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>

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/');

Based on the ookyet.eth implementation:

┌─────────────────────────────────────────────────┐
│          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             │
└─────────────────────────────────────────────────┘

• 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

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

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

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

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/

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

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

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

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

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

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.

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

⭐ Star this repo to help others discover it.

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