AI Layer gives your WordPress site a structured data layer: clean, typed, connected, and queryable. Stop AI systems guessing from your pages. Give them authoritative answers, directly.
Every business website contains the same core information: services, prices, locations, FAQs, contact details. But it's buried in page copy, scattered across templates, and formatted for a human eye. AI has to guess.
An AI reading your site has to crawl multiple pages, interpret unstructured HTML, infer relationships between your services and locations, and piece together an answer across your about page, services page, and contact page.
The result: slow, token-heavy crawls, outdated or incorrect answers, hallucinated pricing, and no structured way to attach trust signals or next actions.
Every page visit costs tokens. Every ambiguous sentence risks a wrong answer. There's no source of truth, just an AI doing its best with a website built for humans.
One request to the /answers endpoint. The engine detects which service and location the question relates to, finds the best matching FAQ, and returns a structured response: answer, confidence level, proof, and next actions.
No scraping. No inference. No hallucination from ambiguous page copy. Just clean, typed data that you control, updated in one place, served to any consumer.
One API call. Fewer tokens consumed. Higher accuracy. A response you can trust.
AI Layer sits alongside your existing theme and content as a pure data and API layer. It doesn't touch your front-end (unless you want it to). It just makes your business data structured, connected, and machine-readable.
Add your services, locations, FAQs, trust signals, and calls-to-action through the WordPress admin. Relationships are wired automatically: a service knows its related FAQs, locations, proof, and next actions.
Every entity type gets its own endpoint: /profile, /services, /locations, /faqs, /proof, /actions. All public, typed, and consistent. AI systems, agents, and integrations query directly.
Ask a plain English question. The engine detects the service and location, finds the best FAQ match, assembles a structured response, and attaches actions and proof. No external AI call. Runs on your server.
A complete intelligence layer from raw data endpoints to natural language answers, discovery signals, and AI agent tooling.
Six typed entity types: Services, Locations, FAQs, Proof & Trust, Actions, and Answers. Each has proper fields, relationships, and metadata. Not pages. Not posts. Actual business objects with meaning.
Clean endpoints at /wp-json/ai-layer/v1/. Every route returns exactly what an AI consumer needs typed summaries, full detail with relationships, and natural language answers with confidence scoring.
33 WordPress Abilities registered under ai-layer/. The WordPress MCP Adapter exposes them automatically. Claude, Cursor, and other MCP clients can read and manage all your AI Layer content without touching the admin UI.
Dynamically generated /llms.txt, a machine-readable /.well-known/ai-layer discovery document, and rel="ai-layer" link tags in every page head. AI systems can find and understand your data from any entry point.
Optional Organization, LocalBusiness, and FAQPage structured data output in <head>. Works alongside Yoast SEO and Rank Math with conflict detection built in.
Auto-populate your Business Profile from existing data in WordPress, Yoast SEO, Rank Math, and WooCommerce. Every suggestion requires explicit approval. Nothing is written without confirmation. Run it again any time.
Publish a dynamic /ai.txt file that declares your crawling, training, and attribution preferences to AI systems. Set global rules and agent-specific overrides for named crawlers. Conflict detection flags any existing physical file or plain-permalink clash.
Embed the full answer engine query console on any page or post with [wpail_answer_console]. Visitors type a natural language question and see the structured response — confidence, source, matched FAQ, actions, and proof — without accessing the admin.
Built-in analytics track every request to your AI Layer endpoints automatically — no configuration needed. The moment AI systems start querying your data, you start seeing exactly what they're asking and where your answers are falling short.
Configurable data retention (default 365 days) with automatic daily cleanup. No IP addresses or personal data stored.
Top questions AI is asking
Ranked table of the most frequent queries sent to the answer engine, with ask count and per-question answer rate.
Missing intents — unanswered queries
Questions the engine couldn't answer, ranked by frequency. Direct links to add a FAQ or Authored Answer for each gap.
Endpoint hit breakdown
Per-endpoint hit counts with an inline bar chart showing relative share across all active endpoints.
Period filtering
Switch between Last 7 days, 30 days, 90 days, and All time. Stats and all tables update instantly.
Send a plain English question like "Do you offer SEO in London?" or "How much does web design cost?" and the engine assembles a complete, sourced response. No external AI. No API keys. Runs entirely on your server.
The pipeline
Each step scores available data and builds the best possible response:
{ "answer_short": "Yes, we offer SEO audits in London.", "answer_long": "Our London SEO audit covers...", "confidence": "high", "source": "faq", "services": [{ "id": 12, "slug": "seo-audit", "name": "SEO Audit" }], "locations": [{ "id": 5, "slug": "london", "name": "London" }], "actions": [ { "id": 3, "type": "book", "label": "Book a Free Consultation", "url": "https://example.com/book", "phone": null, "method": "get" }, { "id": 7, "type": "call", "label": "Call Us Now", "url": null, "phone": "+44 161 123 4567", "method": "get" } ], "source_faqs": [{ "id": 42, "question": "Do you offer SEO audits in London?", "short_answer": "Yes, we offer SEO audits in London." }], "supporting_data": [ { "id": 8, "type": "statistic", "headline": "214% avg organic traffic increase" }, { "id": 11, "type": "accreditation", "headline": "Certified Google Partner since 2019" } ] }
Every entity type has proper fields, relationships, and metadata. A service knows its FAQs. A FAQ knows its service. Proof attaches to both. Everything connects.
Canonical name, contact, address, hours, social links, and brand tone. The authoritative identity of your business served at /profile.
What you offer, with keywords, synonyms, pricing signals, benefits, and customer types. Powers intent matching in the answer engine.
Physical or virtual locations with postcodes, regions, and service radius. Linked to services for geographic intent detection.
Questions and answers linked to specific services. The primary source for the answer engine's dynamic responses. Short and long answer variants.
Testimonials, statistics, accreditations, case studies, and awards. Attached to answers as supporting evidence not just social proof copy.
Calls-to-action returned with every answer book, call, email, quote, download. Linked to services so the right action surfaces for the right query.
Using WooCommerce?
Enable the optional /products endpoint to expose your live product catalogue as structured, queryable data. AI systems can retrieve product details, pricing, categories, and descriptions in a single request. Your WooCommerce products are not duplicated or re-entered — AI Layer reads directly from your existing catalogue. Learn more →
Three complementary discovery signals ensure AI crawlers, agents, and search tools know exactly where to find your structured data whatever their preferred protocol.
A machine-readable JSON discovery document listing all active endpoints. The authoritative source of truth for agents and tools that query programmatically.
/.well-known/ai-layer
A human-readable text file following the emerging llms.txt standard. In recommended mode, it links to the well-known document as a signpost for AI systems reading your site.
/llms.txt
rel="ai-layer" and rel="llms-txt" injected into every page head. AI crawlers can discover your structured data layer from any page on your site.
<link rel="ai-layer">
From solo site owners to development agencies: if you want AI systems to give accurate answers about your business, AI Layer is the missing piece.
/productsAI Layer reads from your existing plugins during setup and operates alongside them without conflict. No rip-and-replace required.
AI Layer sits alongside REST, schema markup, and MCP. It doesn't replace them. Here's how it fits with what you already know.
WordPress REST gives you general-purpose data access: posts, users, blocks. AI Layer adds purpose-built surfaces: a single business profile, typed entities with explicit relationships, and a natural-language answer engine built on top of that model.
Generic REST answers "what records exist?" AI Layer answers "what should an agent do with this business when someone asks a question" in one structured step, with confidence scoring and next actions attached.
They can until layout changes, JavaScript gets in the way, or the answer depends on information scattered across three pages. Crawling is slow, token-heavy, and error-prone. Every page visit costs tokens. Every ambiguous sentence risks a wrong answer.
AI Layer offers stable, explicit inputs instead of best-effort scraping. That's the same reason you prefer a database over parsing HTML when reliability counts.
Schema markup is page-level metadata for search engines, great for rich results, but not a full operational model of your business. It doesn't replace a connected graph of services, locations, FAQs, and actions. It doesn't drive query-shaped responses.
When you enable JSON-LD output in AI Layer, it generates schema from your structured data. The two work together: AI Layer is the model, schema is one output format from it.
MCP describes how an agent talks to tools. It doesn't define what your business objects are or how they relate. AI Layer is the data and behaviour model behind the tools; MCP is how clients reach it. They fit together, not against each other.
With the WordPress MCP Adapter, all 33 AI Layer abilities are exposed as MCP tools automatically. AI Layer provides the domain model; MCP provides the transport.
The data AI Layer asks you to maintain your services, locations, FAQs, proof, and contact details is data you'd manage for a serious site anyway. AI Layer just structures it properly and wires the relationships for you.
The Setup Wizard auto-populates from your existing WordPress, Yoast SEO, Rank Math, and WooCommerce data. And once it's in, every AI integration benefits from it: not just one chatbot, but any consumer that queries your endpoints.
Yes. AI Layer operates as a pure data and API layer. It doesn't modify your front-end, doesn't touch your theme, and doesn't conflict with page builders. It works alongside Yoast SEO and Rank Math with built-in conflict detection for schema and llms.txt.
WooCommerce users get an optional /products endpoint that proxies your live product catalogue. Requires WordPress 6.0+ and PHP 8.1+.
Free to install. No external accounts. No API keys. Works with your existing setup.
WordPress 6.0+ · PHP 8.1+ · No external services required