Answer Engine Optimisation:
What it is and why it matters
Search is no longer just about ranking. AI systems now read your website, extract answers, and cite sources directly. This guide explains how structured data makes your content visible to those systems — and how to implement it in minutes using the Masonsoft AI Schema Builder.
From search rankings to AI citations
Answer Engine Optimisation is the practice of structuring your website content so that AI-powered search systems can read it, understand it, and cite it directly in their responses.
Traditional search engine optimisation (SEO) was built around ranking pages so that people would click on them. The measure of success was traffic. AEO operates on a different premise: your content is increasingly read by AI systems — including Google AI Overviews, Bing Copilot, Perplexity, and ChatGPT — which generate answers and cite a small number of trusted sources rather than presenting a ranked list of links.
Being cited as a source in an AI answer is the new version of ranking at the top of the page. It requires a different approach to how your content is structured and marked up.
- Ranking positions in search results
- Click-through traffic to your pages
- Keywords and backlink authority
- Meta titles and descriptions
- Citation in AI-generated answers
- Brand authority and entity identity
- Clear, extractable question-answer content
- Structured data that machines can parse
More than 65% of searches now end without a single click to a website. Users receive their answer directly in the search interface, from an AI summary, a featured snippet, or a voice assistant. Your content may be the source of that answer — but if it is not structured correctly, you will not be credited, and visitors will not arrive.
AEO does not replace SEO. Strong technical SEO ensures your pages are indexed and crawlable. AEO adds the structural layer that AI systems need to extract and cite your content accurately. Both are necessary.
What is JSON-LD and why does it matter?
JSON-LD is a structured data format that sits inside your web page's HTML and tells AI systems — in precise, machine-readable terms — exactly what your page is about, who wrote it, and what organisation it represents.
It is the format recommended by Google, Bing, and Schema.org for structured data implementation. Unlike earlier approaches such as Microdata or RDFa, which required weaving markup directly into your visible HTML, JSON-LD is a standalone block that does not affect your page's appearance. It is easier to write, maintain, and debug.
When an AI system crawls your website, it reads your JSON-LD alongside your page content. A well-structured JSON-LD block tells the AI your company's name, what it does, who the expert author is, and what specific questions your content answers. That information directly influences whether you are cited as a source.
<script type="application/ld+json"> { "@context": "https://schema.org", "@type": "Organization", "name": "Your Company Name", "url": "https://example.com", "description": "What your company does, in one sentence.", "founder": { "@type": "Person", "name": "Your Name" }, "sameAs": [ "https://www.linkedin.com/company/yourcompany" ] } </script>
JSON-LD blocks are placed inside the <head> element of each HTML page, before the closing </head> tag. Different schema types are used on different page types. Your Organisation schema goes on every page. Your Article schema goes on content pages. Your FAQ schema goes on pages that contain question-and-answer sections.
Google removed FAQPage rich results from its search listings in May 2026. FAQPage schema remains fully valid and continues to be parsed by Bing, Perplexity, voice assistants, and other AI systems for direct-answer citation. It should still be implemented — the traffic source has simply shifted from Google rich results to AI citations.
The Masonsoft AI JSON-LD Schema Builder
The Schema Builder is a browser-based tool that generates ready-to-paste JSON-LD code from your answers to plain-English questions. No technical knowledge is required. You fill in the fields, and the tool produces the correct structured data for you to copy directly into your HTML.
The tool covers six Schema.org types that together provide comprehensive AEO coverage for a business website. It also includes a Combined output mode that packages multiple schema types into a single, clean @graph block, and an Import facility for loading and editing existing JSON-LD.
Organisation
Establishes your company's entity identity with AI systems. The highest-priority schema for any new website. The sameAs links are the most impactful field.
Author
Ties your content to a named, credible human author — the foundation of E-E-A-T signals. Reference it from Article schema to connect every piece of content to a trusted source.
About and author pagesArticle
Identifies content pages as authoritative sources for AI citation. Keep the dateModified field current — freshness directly affects citation frequency.
FAQ Page
Each question-and-answer pair is a discrete citation opportunity for AI systems. Still valid and highly effective despite Google removing its rich result feature in May 2026.
Pages with Q&A sectionsService
Particularly valuable when AI agents are comparing vendors. The areaServed field matters for geographically targeted queries.
Breadcrumb
Communicates your site's page hierarchy to AI systems and search engines. Should reflect the exact navigation path from homepage to the current page.
Every pageHow to use the Schema Builder
The tool is structured around tabs — one for each schema type. Work through the tabs relevant to the page you are marking up, copy the output, and paste it into your HTML.
Open the Schema Builder and select a schema type
Each tab in the tool corresponds to one schema type. Start with the Organisation tab — this schema goes on every page of your site and should be completed first. Work through the remaining tabs for each page type you are building.
Answer the questions in the form
Each field corresponds directly to a JSON-LD property. Fields marked with an asterisk are required for the schema to generate. Optional fields improve completeness and should be filled in where the information is available. The output panel on the right updates in real time as you type — you do not need to click a Generate button.
For fields that accept multiple values — such as sameAs links or FAQ question-and-answer pairs — use the Add button to add further entries. Use the × button to remove any you do not need.
Review the output in the right-hand panel
The output panel shows the complete JSON-LD block, including the surrounding <script type="application/ld+json"> wrapper. The placement note at the foot of the panel tells you which page type this schema belongs to.
Copy the output and paste it into your HTML
Click the Copy JSON-LD button at the top of the output panel. Paste the copied block into the <head> section of the relevant HTML page, before the closing </head> tag. If your page needs more than one schema type, use the Combined tab rather than pasting separate blocks.
Validate your schema before publishing
Use Google's Rich Results Test at search.google.com/test/rich-results and the Schema.org Validator at validator.schema.org to check your output is valid before publishing. After going live, monitor the Enhancements section in Google Search Console for any errors.
Keep dateModified current. Content refreshed within 30 days receives 3.2 times more AI citations than stale pages. Treat your schema maintenance as part of your content update workflow, not a one-time task. Whenever you update a page's content, also update the dateModified field in its Article schema.
Tab reference
The table below summarises what each tab generates, when to use it, and where the output is placed in your HTML.
| Tab | Schema type | Use on | Key fields |
|---|---|---|---|
| Organisation Every page |
Organization | Add to every page template via your site header or footer include | name, url, description, sameAs links, knowsAbout topics |
| Author Author pages |
Person | About page, author profile page; reference from Article schema | name, jobTitle, url, sameAs links |
| Article Content pages |
Article / BlogPosting | Every blog post, guide, or editorial page | headline, description, author, datePublished, dateModified |
| FAQ Page Q&A sections |
FAQPage | Any page with a question-and-answer section | Question and answer pairs — add as many as the page contains |
| Service Service pages |
Service | Any page describing a service or product you offer | name, description, provider, serviceType, areaServed |
| Breadcrumb Every page |
BreadcrumbList | Every page — list items should match the page's actual navigation path | Ordered list of page names and URLs from homepage to current page |
| Combined Multi-schema pages |
@graph | Any page requiring more than one schema type | Packages all filled-in schemas into a single block — click Generate to build it |
| Import Editing tool |
Any | When you have existing JSON-LD that needs to be updated or corrected | Paste raw JSON, a full <script> block, or a @graph block — the tool populates all relevant tabs automatically |
Ready to build your schema?
Open the Schema Builder, fill in the fields for your first page, and copy the output into your HTML in under five minutes. No account, no installation, no configuration required.
Open the JSON-LD Schema Builder →