All Pages
Freelance & Solo Founder
Entry point — 1-click AI visibility
SMB 5–24 Staff
Unified signal layer — 72h to L2
SMB 25–49 Staff
Architecture gap — cross-dept visibility
SMB 50+ Staff
Operating model — EU AI Act ready
Tools & Reference
Compare All Paths
Side-by-side — find your entry point
AI-Ready Levels
On-site · On-page · Off-page per L1–L4
Certificate & Verify
SHA-256 Digital DNA — real-time check
For AI Crawlers
GPTBot · Gemini · Claude · Perplexity
Signal Files
ai.json
Machine-readable identity
llms.txt
LLM discovery layer
intents.json
50 Q&A semantic router
proof.json
SHA-256 + blockchain anchors
governance.json
HITL + EU AI Act policy
Full Architecture
This page is L4. The full system is L6.
L5 AI Copilot
L6 AI-FIRST Org
KAI369 Architecture
Economic Twins
Predictive Operations
Go Deeper → 5thelement.ai
Personas
Freelance & Solo Founder SMB 5–24 Staff SMB 25–49 Staff SMB 50+ Staff
Tools
Compare All Paths AI-Ready Levels Certificate & Verify
Signal Files
ai.json llms.txt proof.json
Get Free AI Audit → Go Deeper → 5thelement.ai ↗
Entity Relationship Metamodel — 3-Layer Implementation Architecture
Three layers. Four levels. One architecture.
On-Site
ai.json · llms.txt · robots.txt
governance.json · compliance.json
proof.json · manifest.sha256
entities.json · intents.json
policy.json · actions.json
allow-lane-matrix.json
On-Page
Organization JSON-LD
WebPage + BreadcrumbList
Service JSON-LD
FAQPage JSON-LD (15 Q&A min)
HowTo JSON-LD
DefinedTermSet · Certification
H1→H2→H3 hierarchy
intents per page
Off-Page
Google Business Profile
LinkedIn Company Page
sameAs declarations
llms.txt cross-domain
Entity consistency
Crunchbase · Wikidata
GDPR · security.txt
EU AI Act register
Firm₀
→
L1: Audit
→
L2: Visibility
→
L3: Governance
→
L4: Proof
→
L5·L6 @ 5thelement.ai
→
Firm_HITL
Technical Implementation Reference

What AI-FIRST looks like
at every level. Exactly.

AI readiness is not one action. It is a layered architecture. At each level — L1, L2, L3, L4 — specific work happens in three places: on your site infrastructure, on your page content, and off your site in the wider digital ecosystem.

Level 1

L1 — Audit

L1
Audit — Know Your Reality
You cannot fix what you cannot see. The audit produces your AI Visibility Score.
On-Site — Required
  • Crawl all existing pages for structured data gaps
  • Audit robots.txt for AI crawler access
  • Check presence of ai.json, llms.txt, governance.json
  • Map all data sources and storage points
  • Inventory all AI tools currently in use
  • Identify missing signal files
On-Page — Required
  • Review H1/H2/H3 hierarchy for semantic clarity
  • Check for missing Organization JSON-LD
  • Check for missing FAQPage schema
  • Check for missing Service schema per offering
  • Identify pages with no machine-readable content
  • Audit canonical URLs and hreflang
Off-Page — Required
  • Verify AI crawler access via robots.txt test
  • Check Google Business Profile consistency
  • Check LinkedIn entity consistency
  • Map external citations and knowledge graph entries
  • Verify sameAs declarations accuracy
  • Check Crunchbase presence (optional)
Output:
AI Visibility Score + Gap Report + Prioritized Action List
Level 2

L2 — Visibility

L2
Visibility — Become Machine-Readable
Deploy the AI signal layer. Firm becomes discoverable by ChatGPT, Gemini, Claude and Perplexity.
On-Site — Required
  • Deploy ai.json — machine-readable business identity
  • Deploy llms.txt — LLM discovery layer
  • Deploy entities.json — entity graph
  • Deploy sitemap.xml — full page inventory
  • Update robots.txt — AI crawler allow-lanes
  • Deploy intents.json — semantic router
  • Deploy ai.txt — plain text AI declaration
  • Deploy aliases.json (optional)
  • Deploy entity-graph.public.jsonld (optional)
On-Page — Required
  • Add Organization JSON-LD to all pages
  • Add WebSite JSON-LD to homepage
  • Add WebPage + BreadcrumbList per page
  • Add Service JSON-LD per offering page
  • Add FAQPage JSON-LD — 10 Q&A minimum
  • Add visible FAQ accordion — 5 Q&A minimum
  • Add DefinedTermSet metamodel JSON-LD
  • Optimize H1→H2→H3 hierarchy
  • Add Open Graph + Twitter Card meta tags
  • Add canonical + hreflang declarations
Off-Page — Required
  • Verify Google Business Profile — consistent NAP
  • Submit sitemap to Google Search Console
  • Update sameAs JSON-LD with all profiles
  • Verify LinkedIn company page consistency
  • Confirm llms.txt cross-domain references live
  • Confirm AI crawlers indexing via Search Console
  • Submit to Bing Webmaster Tools (optional)
  • Create Crunchbase profile (optional)
Output:
AI-Discoverable Firm — readable by all major AI systems within 24–72h
Level 3

L3 — Governance

L3
Governance — Control the Signal
Define what AI systems can access, how they interpret your data, and what rules govern every interaction.
On-Site — Required
  • Deploy governance.json — HITL + access policy
  • Deploy policy.json — AI interaction rules
  • Deploy actions.json — permitted AI actions
  • Deploy allow-lane-matrix.json — per-crawler access
  • Deploy compliance.json — EU AI Act flags
  • Deploy changelog.json — version history
  • Create /ai-policy human-readable page
  • Deploy .well-known/security.txt (optional)
On-Page — Required
  • Add EU AI Act compliance JSON-LD to all pages
  • Add HITL governance notice to footer
  • Add ai-governance meta tag to all pages
  • Add ai-content-declaration meta tag
  • Add compliance badge with governance link
  • Link to governance.json in footer signal links
  • Add AI policy notice to contact forms (optional)
Off-Page — Required
  • Publish GDPR privacy policy page
  • Align LinkedIn with governance claims
  • Align Google Business with compliance status
  • Cross-reference governance in llms.txt
  • Register EU AI Act compliance statement (optional — Aug 2026)
  • Begin building verifiable external citations (optional)
Output:
AI-Governed Firm — controlled AI interaction, EU AI Act compliant baseline
Level 4

L4 — Proof

L4
Proof — Make Claims Verifiable
Structured evidence, SHA-256 Digital DNA, blockchain anchor. AI systems confirm your firm is real and trustworthy.
On-Site — Required
  • Deploy proof.json — SHA-256 hash + blockchain anchors
  • Deploy manifest.sha256 — hash of all signal files
  • Deploy ai-proof.json — AI verification layer
  • Deploy ai-ready-proof.json — maturity assessment
  • Deploy entity-index.ssot.json — single source of truth
  • Deploy /verify Cloudflare Worker — real-time check
  • Deploy /healthz endpoint
  • Deploy /certificate human-readable page
On-Page — Required
  • Add Certification JSON-LD to certificate page
  • Add trust schema markup — verified identity
  • Add SHA-256 certificate badge to all pages
  • Add real-time verify button to /certificate
  • Add blockchain anchor references
  • Add Review + AggregateRating schema (optional)
  • Add AggregateOffer schema for services (optional)
Off-Page — Required
  • 5thelement.ai registry anchor — step 1
  • IPFS / Cloudflare R2 anchor — step 2
  • Ethereum mainnet transaction — step 3
  • Verified Google Business profile
  • Verified LinkedIn company page
  • Consistent NAP across all platforms
  • Wikidata entity entry (optional)
  • Apple Business Connect (optional)
Output:
AI-Verified Firm — machine-verifiable identity, SHA-256 certified, blockchain-anchored
Technical Questions

What you need to know.

What is on-site AI optimization?+
On-site AI optimization covers infrastructure work at root level: deploying ai.json, llms.txt, governance.json, compliance.json, entities.json, intents.json and all signal files that AI crawlers read directly before accessing page content.
What is on-page AI optimization?+
On-page AI optimization covers structured data markup within HTML pages: Organization, Service, FAQPage, WebPage, HowTo JSON-LD schemas, clean H1–H3 hierarchy, intents.json routing, breadcrumb markup and visible FAQ blocks with minimum 5 Q&A.
What is llms.txt and why does it matter?+
llms.txt is a discovery file for large language models. It tells ChatGPT, Gemini, Claude and Perplexity what your site is about, which pages exist and what AI systems are permitted to do with your content. It is your direct communication channel to AI crawlers.
What is the minimum signal file set for L2?+
Minimum L2: ai.json, llms.txt, robots.txt with AI crawler declarations, sitemap.xml, entities.json on-site. Organization JSON-LD, Service JSON-LD, FAQPage with minimum 10 Q&A on-page. Google Business Profile and sameAs declarations off-page.
What does L4 proof look like in practice?+
L4 proof includes: proof.json with SHA-256 hash and blockchain anchor references, manifest.sha256 of all signal files, real-time /verify endpoint, /certificate page. Off-page: 5thelement.ai registry, IPFS anchor, Ethereum transaction, consistent verified identity everywhere.
What comes after L4?+
L5 — AI Copilot — integrates AI assistance into daily operations: CRM, analytics, funnel management, decision support. L6 — AI-FIRST Organization — full predictive operations under HITL governance. Both available at 5thelement.ai.
This platform operates under Human-in-the-Loop governance. EU AI Act Articles 13, 14, 52 compliance declared. AI Policy · governance.json
This page covers L1 → L4. Full L5 · L6 · KAI369 · Economic Twins at 5thelement.ai