# AEO, plainly explained | Plyo

> How answer engines like ChatGPT, Perplexity and Google’s AI Overviews read your site, and the practical changes that help them quote you.

Source: https://plyo.studio/blog/aeo-plainly-explained

1.  [Home](/)
2.  [Blog](/blog)
3.  AEO, plainly explained

# AEO, plainly explained

How answer engines like ChatGPT, Perplexity and Google’s AI Overviews read your site, and the practical changes that help them quote you.

Plyo Studio 23 March 2024 7 min read

On this page

[How it differs from SEO](#how-it-differs-from-seo)[What answer engines look for](#what-answer-engines-look-for)[Practical changes you can make](#practical-changes-you-can-make)[What not to bother with](#what-not-to-bother-with)[How to tell if it’s working](#how-to-tell-if-its-working) [Common questions](#common-questions)

Related service

[Website speed & SEO audit](/services/website-audit)

More people now ask a question and read an answer, rather than scanning ten blue links. That answer might come from Google’s AI Overviews, ChatGPT, Perplexity or Copilot. AEO, answer engine optimisation, is the work of making your site easy for those tools to understand, trust and cite.

## How it differs from SEO

It is less different than the acronym suggests. Good SEO is still the foundation: answer engines lean heavily on pages that already rank, load properly and are clearly written.

The shift is in what gets rewarded. A traditional search result sends someone to your page to find the answer. An answer engine pulls the answer out of your page and shows it directly, often with a link back. So the content that wins is content that states things clearly enough to be lifted out and quoted.

## What answer engines look for

-   **A direct answer near the top.** The question, then the answer in a sentence or two, then the detail.
-   **Clear structure.** Headings that read like the questions people ask. Short paragraphs. Lists and tables where they fit.
-   **Specific facts.** Prices, service areas, timeframes, steps. Vague copy gives them nothing to quote.
-   **Signs of trust.** Who wrote it, who the business is, where it operates, and consistent details across the web.
-   **Pages they can actually read.** Content in the HTML, not hidden behind scripts, tabs that never load or images of text.

## Practical changes you can make

### 1\. Rewrite key pages around real questions

Look at what customers ask you on calls and in emails. Turn the common ones into headings, and answer each in the first sentence underneath. Your services page can do this as well as your blog.

### 2\. Add an honest FAQ

Not a list of sales lines dressed as questions. Real questions, with plain answers: how long does it take, what does it cost to start, do you work with businesses outside your city.

### 3\. Use structured data

Schema markup tells machines what a page is: an organisation, a service, an article, a product, a local business. It doesn’t guarantee anything, but it removes guesswork. We add it as standard on every build.

### 4\. Check you aren’t blocking the crawlers

Your site’s `robots.txt` file controls which bots can read it. Some sites block AI crawlers by accident, through a default setting or a plugin. Decide deliberately which ones you allow.

### 5\. Make sure Bing knows about you

Google isn’t the only index that matters. Some AI search tools draw on Bing’s index, so it is worth verifying your site in Bing Webmaster Tools and submitting your sitemap there too.

### 6\. Keep your business details consistent

Name, address, phone number, hours and services should match across your site, Google Business Profile, directories and social profiles. Conflicting details make an answer engine less confident about quoting you.

> If a stranger couldn’t answer the question from your page in ten seconds, neither can an answer engine.

## What not to bother with

-   **Writing for robots.** Stuffed keywords and awkward phrasing read badly for people and don’t help machines either.
-   **Mass-produced pages.** Hundreds of thin, near-identical pages targeting slight keyword variations tend to be filtered out.
-   **Chasing every new file format.** Proposals like `llms.txt` are worth watching, but clear, well-structured pages matter far more today.

## How to tell if it’s working

AEO is harder to measure than rankings. A few useful signals:

-   Referral traffic from chatgpt.com, perplexity.ai and similar in your analytics
-   Asking the tools directly about your business or services and seeing what they say
-   Enquiries mentioning that someone “found you through ChatGPT”

Our free website audit includes an AEO check alongside speed, SEO, accessibility and mobile. It is a quick way to see where your site stands.

## Keep reading.

[All posts](/blog)

-   [
    
    Search & AEO What to do when your website traffic drops 8 min read](/blog/when-website-traffic-drops)
-   [
    
    Search & AEO Google Business Profile and your website 7 min read](/blog/google-business-profile-and-your-website)
-   [
    
    Search & AEO robots.txt and AI crawlers: what to allow 7 min read](/blog/robots-txt-and-ai-crawlers)

Updated 23 March 2024

FAQ

## Common questions

[Ask a question](/contact)

### What is AEO?

Answer engine optimisation: making your website easy for AI tools like ChatGPT, Perplexity and Google's AI Overviews to understand, trust and cite.

### Is AEO different from SEO?

It builds on SEO. Good SEO is the foundation, and AEO adds a focus on clear, quotable answers, structure and consistent business details.

### How do I know if AI tools mention my business?

Ask them directly about your services and location, and check your analytics for referral traffic from sites like chatgpt.com and perplexity.ai.

About Plyo Studio

## Custom Astro websites. Built on Cloudflare.

Plyo Studio is an independent web studio that designs and builds fast, search-ready websites, web apps and interactive maps. Sites are custom-built in Astro and hosted on Cloudflare, so they load quickly and are easy for search engines and AI answer engines to read.

Founded by Chloe Nixon, a full stack developer and UI/UX designer from Australia, and Micky, a software engineer from New Zealand. Clients work directly with the founders from the first call to launch. Typical work: custom websites, migrations off Webflow, WordPress, Wix and Squarespace, web apps, and interactive maps and GIS. Projects are quoted at a fixed price before work starts.

[Start a project](/contact) [hello@plyo.studio](mailto:hello@plyo.studio) [About us](/about)

## Related pages

-   [Blog Read practical notes on designing, building and moving websites.](/blog)
-   [Website speed & SEO audit A clear report on what is slowing your site down and costing you rankings.](/services/website-audit)

Start a conversation

## Ready for a website that works harder?

[Start a project](/contact) [Free website audit](/audit)
