This repository houses the v0.1.1 standard (backward-compatible with v0.1), reference tooling, and outreach material for the AI Domain Data initiative — the open, vendor-neutral format for authoritative domain data consumed by AI systems, search, and other automated agents. Publishers self-host their JSON record at https://<domain>/.well-known/domain-profile.json and optionally mirror it via _ai.<domain> TXT (ai-json=<base64(JSON)>).
site/ React/Vite workspace for generator + visibility checker
checker/ Checker-specific UI + logic
components/ Shared React components
generator/ Generator-specific UI + logic
src/ App shell + routing/entry files
styles/ Global CSS + tokens
index.html Vite template
package.json Workspace manifest
spec/ Human-readable spec, schema, and outreach content
docs/ Intro, guides, adoption resources
spec/ Canonical spec markdown + JSON schema
tests/ Automated test suites (schema validation, examples, edge cases, backward compatibility)
packages/
cli/ `aidd` CLI for init/validate/emit workflows
resolver/ Node/TypeScript resolver SDK
nextjs/ Next.js integration package (@ai-domain-data/nextjs)
LICENSE MIT License
npm install
npm run dev --workspace @ai-domain-data/siteVisit http://localhost:5173 (default Vite port) to use the generator and checker locally.
npm run build --workspace @ai-domain-data/cli
npx @ai-domain-data/cli aidd --help
npm run build --workspace @ai-domain-data/resolver
npm run test:spec
Runs all test suites in spec/tests/:
- Schema validation tests
- Example validation tests
- Backward compatibility tests
- Edge case tests
spec/spec/spec-v0.1.md– Normative spec text for the v0.1.1 release (backward-compatible with v0.1), including schema.org interoperability mapping and precedence rules.spec/spec/schema-v0.1.json– Canonical JSON schema (with optionallogo,entity_type, andjsonld). Also available athttps://ai-domain-data.org/spec/schema-v0.1.json.spec/examples/basic.json– Minimal valid record with only required fields.spec/examples/with-jsonld.json– Complete record demonstrating all optional fields includinglogo,entity_type, and embeddedjsonld.spec/docs/introduction.md– Plain-language overview of why the standard exists.spec/docs/technical-guide-v0.1.md– Implementation details for publishers and integrators, including schema.org integration guidance.spec/docs/adoption-guide.md– Rollout and governance checklist for domain owners.spec/docs/implementation-overview.md– Summary of the included tooling.spec/docs/aidd-vs-ai-txt.md– Comparison of AIDD and ai.txt, explaining their complementary purposes.
If you're building a plugin, CMS integration, or platform feature that adds one-click support for domain-profile.json, see:
spec/docs/integrator-quickstart.md– Practical guide for plugin authors covering required/optional fields, error handling, validation, and versioning policy. Start here for implementation details.
Add AI Domain Data support to your site in minutes with our official integrations. Each package handles validation, generation, and deployment automatically.
@ai-domain-data/nextjs – Add domain-profile.json to your Next.js site with zero configuration. Supports both App Router and Pages Router.
npm install @ai-domain-data/nextjsFeatures:
- Automatic route generation for
/.well-known/domain-profile.json - Environment variable support with smart defaults
- Full TypeScript support with type-safe configuration
- Built-in schema validation
- Works with Next.js 13+ (App Router) and Next.js 12 (Pages Router)
Quick Start:
// app/.well-known/domain-profile.json/route.ts
import { createAIDomainDataRoute } from "@ai-domain-data/nextjs/app-router";
export const GET = createAIDomainDataRoute({ useEnv: true });Install on npm | Full Documentation | 🔗 GitHub
jekyll-ai-domain-data – Automatically generate and validate domain-profile.json during Jekyll site builds. Zero manual file management required.
gem "jekyll-ai-domain-data"Features:
- Automatic file generation during site build
- Validates against the official schema before publishing
- Liquid tags for embedding domain data in templates
- Smart fallbacks to existing Jekyll configuration
- Works with Jekyll 3.8+ and 4.x
Quick Start:
# _config.yml
plugins:
- jekyll-ai-domain-data
ai_domain_data:
contact: "[email protected]"
entity_type: "Organization"Install on RubyGems | Full Documentation | 🔗 GitHub
- WordPress Plugin – One-click installation for WordPress sites
- Cloudflare Worker – Edge-computed domain profiles
- GitHub Pages Action – Automated deployment for static sites
Have a platform you'd like to see supported? Open an issue or contribute an integration.
This working repo covers everything required for Phases 1–3:
- Brand + Spec + Proof – Docs, schema, generator, checker.
- Distribution + Influencers – Clarity and outreach resources for getting the spec adopted.
- Minimal Implementation – CLI and resolver packages for self-hosted workflows.
Future integrations (e.g., WordPress plugin, GitHub Action, Cloudflare Worker) will also land here once they are ready for public testing.