SEO, GEO and AEO Audit: Visibility in Google and AI Assistants
encorp.ai runs SEO, GEO and AEO audits of company websites in Bulgaria — a check of how Google, Bing and the AI assistants ChatGPT, Gemini, Copilot, Perplexity and Claude see, rank, cite and recommend your site. The audit scores representative page templates, tests real queries live and ends with a PDF report and an action plan ordered by impact, so that AI systems cite you more often.
| Who it is for | Companies whose customers search Google and ask AI assistants — especially sites with many pages built from one template |
|---|---|
| Scope | Representative page templates chosen with you, plus real queries by intent in your customers’ languages |
| Systems | Google, AI Overview, AI Mode, Bing and ChatGPT live; the sources behind Gemini, Copilot, Perplexity and Claude |
| Scores | Two scores out of 10 per template — SEO and GEO/AEO |
| Deliverable | PDF report: findings with exact fixes, action plan, recommended template and schema, measurement plan |
| Re-check | After the fixes; the live test is repeated after 4–6 weeks |
| Duration | Depends on the number of templates and queries — set out in the proposal |
| Price | On request |
What is an SEO, GEO and AEO audit?
An SEO, GEO and AEO audit checks how Google, Bing and the AI assistants see, rank, cite and recommend your website — and what to change so they cite you more often. SEO is classic search engine optimisation. GEO (generative engine optimisation) optimises for generated answers, and AEO (answer engine optimisation) for systems that answer the question directly instead of showing a list of links.
The three are not separate disciplines. Every AI search draws on the classic indexes — Google, Bing or Brave. A page that is not well indexed and does not contain the answer as text cannot be cited, however "AI-optimised" it is. Google says so explicitly in its guide to generative AI features of 10.07.2026: AI Overviews and AI Mode rely on the search engine’s core ranking systems.
That is why the audit starts with the technical base and the content, and only then moves on to how AI systems choose whom to recommend and whom to cite as a source.
Where do AI assistants get their information?
Every AI assistant searches the web through a specific index or its own crawler. If your site is invisible to that index, the assistant has no way to learn about you. The table shows where each system draws from and its share in Bulgaria according to StatCounter for September 2026.
The two kinds of share are not directly comparable: for Google it is the share of searches, for the others the share of AI chatbot use. The practical conclusion is that good visibility in Google and Bing covers almost the whole market, because Google feeds AI Overviews, AI Mode and Gemini, and Bing feeds ChatGPT and Copilot.
AI Overviews are shown in Bulgarian, and AI Mode has supported Bulgarian since 7.10.2025. The crawlers of OpenAI, Perplexity and Anthropic have their own names in robots.txt, and Google uses the separate Google-Extended token. If one of them is blocked by mistake, that assistant cannot read your pages.
| System | Draws from | Share in Bulgaria |
|---|---|---|
| Google AI Overviews and AI Mode | Google’s index (Googlebot) | ~96% of search |
| ChatGPT | OAI-SearchBot and Bing’s index | 80.9% of AI chatbot use |
| Gemini | Google’s index; the Google-Extended token in robots.txt | 14.5% of AI chatbot use |
| Perplexity | PerplexityBot | 2.9% of AI chatbot use |
| Copilot | Bing’s index | 1.0% of AI chatbot use |
| Claude | Brave Search and Claude-SearchBot | 0.7% of AI chatbot use |
What does the audit cover?
The audit does not check every page one by one, but representative templates that we choose together with you — for example the homepage, a category or listing page, a service page, a product or detail page and an article. Most sites are built from a few templates repeated many times, so one fix in a shared template affects hundreds of pages at once.
For comparison we also check the contact, about, FAQ, team and blog pages. They carry the data that search engines and AI systems use to recognise the company: name, address, phone, people and expertise.
The second element is a set of real queries, grouped by intent and written in your customers’ languages. The same queries are used in the technical part, in the live test and in the measurement plan, so the results before and after the fixes can be compared directly.
| Intent | What the user is looking for | What we check |
|---|---|---|
| Buyer | To choose a product, service or supplier | Who is recommended first and whether you are among those recommended |
| Seller or lead | To ask for a quote, hand over a task or become your partner | Whether the right page shows up and leads to an inquiry |
| Informational | An explanation, comparison or advice | Whether your content is a source of the answer |
| Brand | The company by name | What AI systems say about you and whether the data is correct |
What do we check technically?
The technical part answers one question: what exactly does the crawler get when it visits the page. So we compare the source HTML a bot receives without JavaScript with the rendered mobile page. Google renders JavaScript, but most other AI crawlers do not — if the main text appears only after JavaScript runs, they simply do not see it.
The check runs through the tools the search engines use themselves, not through proprietary "scores". Every conclusion in the report is backed by a result you can reproduce yourself in the same tool.
We check structured data (schema) as a connected system rather than page by page: the organisation with its @id, the offices or locations, WebSite, breadcrumbs and the type of each page must all describe the same company. We also check the content templates — whether the intro, facts, questions and answers, authors and dates are in the HTML, where crawlers can read them.
- Source HTML without JavaScript vs the rendered mobile page
- Google Rich Results Test with Googlebot smartphone — rendered HTML and blocked resources
- PageSpeed Insights — real Chrome user data and Lighthouse
- robots.txt for the site, the API hosts and the image hosts
- Sitemaps and llms.txt
- hreflang and canonicals, duplicate URLs and redirects
- Structured data: Organization with @id, offices and locations, WebSite, breadcrumbs, page types
- Core Web Vitals (INP, LCP) and third-party scripts
- Content templates: intro, facts, questions and answers in HTML, authors, dates
How do we test visibility live?
We run the same queries in Google (organic results), Google AI Overviews, Google AI Mode, Bing and ChatGPT. The test runs without logging in, with cookies declined and from Bulgaria, with Bulgarian language and region settings (hl=bg, gl=bg). That way we see what an ordinary user sees, not personalised results.
For each query we record who is recommended first, who is cited as a source and where the company is missing even though it has a suitable page. Every result is documented with a screenshot as evidence.
AI answers change, sometimes from one day to the next. That is why the test is a snapshot on a specific date, not a permanent score, and the date is shown next to every result in the report. After the fixes the test is repeated after 4–6 weeks with the same queries to show the change. The live test also shows something the technical check cannot: whom AI systems prefer today for your topics.
| System | What we record |
|---|---|
| Google (organic) | The position of the right page and which sites rank above it |
| Google AI Overviews | Whether one is shown and which sources it cites |
| Google AI Mode | Whom it recommends and which pages it cites |
| Bing | The position of the page — Bing feeds ChatGPT and Copilot |
| ChatGPT | Whom it recommends and which pages it cites as sources |
How are templates and findings scored?
Every template gets two scores out of 10. The SEO score measures the technical base, the titles and the rankings. The GEO/AEO score measures how readily AI systems can take the content and cite it — whether the answer is in the text, whether the facts are clearly set out and whether there are questions with answers.
The two scores sit side by side, because a page can rank well and still not be cited — or the other way round. Comparing the templates shows where a single fix will have the biggest effect.
Every finding has a severity — critical, high, medium, low or "check" — and an exact fix: what to change, in which template and how to verify it afterwards. At the re-check every finding is marked as fixed, partially fixed or unchanged, so progress is visible without interpretation.
| Element | Values |
|---|---|
| SEO score | Out of 10 per template: technical base, titles, rankings |
| GEO/AEO score | Out of 10 per template: how readily AI takes and cites the content |
| Finding severity | Critical, high, medium, low, check |
| Status at the re-check | Fixed, partially fixed, unchanged |
How is the action plan ordered?
The plan is ordered by impact: first come the fixes that affect the whole site or many pages at once, then the slower and more labour-intensive ones. Every step points to the findings it resolves and to how we will verify the result.
Brand data sits high in the plan, because AI systems first have to recognise the company before they can recommend it. Content templates come next: one change to a template updates hundreds of pages, but it takes more work than the technical fixes.
The last group is off-site. ChatGPT and Copilot rely on Bing, so Bing Webmaster Tools and IndexNow are a quick way to get new and changed pages to them. Company profiles, Wikidata, media mentions and YouTube help AI systems connect the brand with the topics you want to be cited for. The order lets you start with the first groups and measure the effect before investing in the next ones.
- Immediate technical fixes — for the whole site
- Immediate brand data — in Google and in AI systems
- Content templates — affecting hundreds of pages
- Speed — Core Web Vitals
- Off-site — Bing Webmaster Tools and IndexNow, profiles, Wikidata, media mentions, YouTube
What does a page that AI can cite look like?
As part of the report you get a recommended template — the structure of a page that AI systems read and cite easily. It starts with breadcrumbs and an H1 that names the topic and, where it matters, the location. Then comes an intro of 120–180 words in which the facts come first, followed by facts with an update date and the list or offer itself.
There are 6 to 10 questions with answers, in the HTML inside a details element, which stays in the DOM even when it is closed. Contextual links with exact anchor texts lead to the related pages, and a real expert with a profile shows who stands behind the content.
The template comes with a structured-data blueprint: one organisation with an @id that every template references. That way Google and AI systems connect every page with the same company instead of seeing dozens of unconnected descriptions. This page is built on the same template.
- Breadcrumbs
- An H1 with the topic and the location
- An intro of 120–180 words — facts first
- Facts with an update date
- The list or the offer
- Contextual links with exact anchor texts
- 6–10 questions with answers in the HTML
- A real expert with a profile
- Related pages
What do Google and the AI platforms require in 2026?
The requirements are no secret — Google and the AI platforms describe them in their documentation. The audit checks the site against them, and the report’s appendix gathers them in one place with the sources. What they have in common is that clear, original and consistent pages win, not tricks.
Indexing comes first: according to Google, only indexed pages that are allowed to show a snippet can appear in AI Overviews. The resources needed for rendering, including content APIs, must not be blocked.
The second is the text. Google renders JavaScript, but most other AI crawlers do not, so the main content has to be in the HTML and early in the document — Googlebot reads the first 2 MB of HTML. Then come consistent data, language versions, real dates and trust, as set out in the table.
| Requirement | What it means in practice |
|---|---|
| Indexing and access | Only indexed pages with snippets allowed appear in AI Overviews; resources needed for rendering, including content APIs, are not blocked |
| The text is in the HTML | Google renders JavaScript; most other AI crawlers do not |
| Size | Googlebot reads the first 2 MB of HTML — the main content comes early |
| Original content | Your own data and experience, not a retelling of other pages |
| Clear structure | Headings, parameter tables, questions and answers, facts first |
| The same data everywhere | Name, address and phone match on the site, in the schema and in Google Business Profile |
| Language versions | hreflang to the exact equivalent, a self-referencing canonical, one protocol |
| Real dates | The visible "Updated" date equals dateModified; no date bumps without changes |
| Author and trust | A real author with a profile and verifiable credentials |
| No mass-generated pages | No page for every combination without unique content |
What does research show about AI citations?
Research gives direction, but it shows correlations, not causation. That is why we treat it as hypotheses that we verify with the live test, not as a guarantee of results.
The most cited study is GEO by Aggarwal et al. (Princeton, KDD 2024): quotations, statistics and cited sources raise visibility in AI answers, while keyword stuffing lowers it. Pages outside the top three results gain the most. SE Ranking’s analysis of 216,000 pages links more ChatGPT citations with short sections, recent updates and concrete data.
Ahrefs data shows that AI Overviews increasingly cite pages outside the top ten results and that brand mentions matter more than backlinks. That is why the audit also looks beyond the site — profiles, media, YouTube and Wikipedia, on which ChatGPT relies heavily according to Profound. According to Seer Interactive, organic CTR drops when an AI Overview is shown, but brands cited in it get more clicks.
| Study | Finding |
|---|---|
| GEO — Aggarwal et al., Princeton, KDD 2024 | Quotations +41%, statistics +31%, cited sources +28%; keyword stuffing −8%; pages outside the top 3 gain most |
| SE Ranking — 216,000 pages | Sections of 120–180 words, updates within the last 3 months and concrete data go with more ChatGPT citations |
| Ahrefs — March 2026 | About 38% of AI Overview citations come from the top 10, vs 76% a year earlier |
| Ahrefs — brand mentions | Correlate more strongly with AI Overview visibility than backlinks (0.664 vs 0.218) |
| Ahrefs; Profound | YouTube is 5.6% of AI Overview citations; ChatGPT leans heavily on Wikipedia |
| Seer Interactive | Organic CTR drops when an AI Overview shows, but brands cited in it get more clicks |
What no longer works in 2026?
Some advice that still circulates no longer helps or even hurts. The audit flags it explicitly, so you do not spend resources on it.
The most common misunderstanding concerns questions and answers. Google stopped showing FAQ rich results on 7.05.2026 and removed their documentation on 15.06.2026. The questions still matter as visible text on the page, though, because that is exactly where AI systems take their answers from.
The second is llms.txt. Google does not use it — according to the company the file neither helps nor hurts, so it is not a priority and does not replace indexing and text in the HTML. Mass-generating a page for every query variation, changing dates without changes and serving different content to bots are risks, not tactics: the first breaks Google’s spam policies, the second is a manipulation signal, the third is cloaking.
| Practice | Why |
|---|---|
| FAQ rich results | Not shown by Google since 7.05.2026; documentation removed on 15.06.2026. Questions still matter as visible text |
| llms.txt for Google | Google ignores it — "neither helps nor hurts"; not a priority |
| A page for every query variation | Mass-generated pages break Google’s spam policies |
| Changing dates without changes | A manipulation signal |
| Different content for bots | Cloaking — a policy violation |
| Blocks with dozens of links | "Popular searches" do not help AI; contextual links with exact anchors do |
How do we measure visibility in AI search?
The measurement plan combines the data the platforms provide with a manual check. Google Search Console shows whether pages are indexed and how Google sees each of them, and the generative AI report shows impressions in AI Overviews and AI Mode per page. Bing Webmaster Tools shows citations in Copilot and Bing.
In GA4 we set up a segment for traffic from AI assistants. Because not every AI answer leads to a click, every month we manually ask 20–30 real customer questions in ChatGPT, Gemini and AI Mode — in Bulgarian and English — and record who is recommended and who is cited.
Success is not measured in clicks alone. Success means the company is cited for the key queries, the right page ranks and inquiries come in. That is why the plan ties every metric to a concrete action: what we check, how often and what we do if the number does not move.
- Google Search Console: URL Inspection, page indexing, settings for generative AI in search, performance in AI Overviews and AI Mode per page
- Google Business Profile
- Bing Webmaster Tools: AI Performance — citations in Copilot and Bing
- GA4: a segment for traffic from chatgpt.com, perplexity.ai, gemini.google.com, copilot.microsoft.com and claude.ai
- A monthly manual panel: 20–30 real questions in ChatGPT, Gemini and AI Mode in Bulgarian and English
What do you get and what comes after the audit?
The deliverable is a PDF report with a summary, the live visibility test, the technical findings, a scorecard per template, the action plan, the recommended template and structured-data blueprint, the measurement plan and an appendix with the 2026 requirements and research, the methodology and the sources.
The report is written so that your team or an external developer can carry out the fixes. After the fixes we re-check, and the live test is repeated after 4–6 weeks to see whether the company is now recommended and cited.
encorp.ai can also take on the implementation — the fixes, the new templates, the content and the re-test. When the content of many pages has to be kept up to date regularly, that can be done with AI business process automation. If the audit is part of a wider change in the company, it runs through AI transformation for companies · the Encorp AIM method. The audit is priced on request — contact us for a quote.
Frequently asked questions
What are GEO and AEO?
GEO (generative engine optimisation) is optimising a website so that generative AI systems such as ChatGPT, Gemini and Google AI Overviews use and cite it in their answers. AEO (answer engine optimisation) is optimising for systems that answer the question directly instead of showing a list of links. Both build on classic SEO.
How is GEO different from SEO?
GEO does not replace SEO; it builds on it. AI search draws on the classic indexes of Google, Bing and Brave, so a page that is not indexed and does not contain the answer as text cannot be cited. The difference is the goal: SEO aims for a position in the results, GEO for a place in the answer itself, as a recommendation or a source.
Which AI systems do you check?
In the live test we check Google (organic results), Google AI Overviews, Google AI Mode, Bing and ChatGPT. The technical part also covers the sources behind Gemini, Copilot, Perplexity and Claude — the Google, Bing and Brave indexes and crawlers such as OAI-SearchBot, PerplexityBot and Claude-SearchBot. That covers the systems used most in Bulgaria.
What do we get at the end of the audit?
A PDF report with a summary, a live test with screenshots, technical findings with a severity and an exact fix, two scores out of 10 per template, an action plan ordered by impact, a recommended template and structured-data blueprint, a measurement plan and an appendix with the 2026 requirements, the research and the sources.
How long does the audit take and what does it cost?
Duration and price are on request. They depend on the number of templates we check, the number of queries and languages in the live test and whether you want a re-check after the fixes. Describe your site and markets through the contact form and you will get a proposal with scope, timeline and price.
Do we need to change our CMS?
Not necessarily. The audit checks what the crawler gets from your current platform, and the fixes are described in the templates, settings and content that are changed in the same system. We recommend a change only if the platform cannot do the basics — for example, the content is loaded only with JavaScript and cannot be served to crawlers as HTML.
Do we need an llms.txt file?
It is not a priority. Google ignores llms.txt — according to the company the file neither helps nor hurts. The audit checks whether you have one, but it does not replace indexing, text in the HTML and structured data. If the basics are in place, llms.txt is easy to add, but it will not make up for problems in them.
How do you measure AI visibility?
With the generative AI report in Google Search Console (impressions in AI Overviews and AI Mode per page), AI Performance in Bing Webmaster Tools (citations in Copilot and Bing), a GA4 segment for traffic from AI assistants and a monthly manual panel of 20–30 real questions in ChatGPT, Gemini and AI Mode. Success means being cited and getting inquiries, not just clicks.
Can encorp.ai implement the fixes?
Yes. encorp.ai can take on the fixes, the new templates, the content and the re-test — all of it or only the part you have no capacity for. The report is written so that your own team or another developer can also carry it out, so implementation is a separate decision after the audit.
How often should the test be repeated?
The live test is repeated 4–6 weeks after the fixes to show the effect. AI answers change often, so every test is a snapshot on a specific date. For ongoing monitoring there is the monthly manual panel of 20–30 questions and the reports in Search Console and Bing Webmaster Tools.
Sources
- Optimizing for generative AI features — Google Search Central, accessed 30 October 2026
- AI features and your website — Google Search Central, accessed 30 October 2026
- Google common crawlers — Google for Developers, accessed 30 October 2026
- Spam policies for Google web search — Google Search Central, accessed 30 October 2026
- Overview of OpenAI crawlers — OpenAI, accessed 30 October 2026
- Anthropic crawlers and robots.txt — Anthropic (Claude Help Center), accessed 30 October 2026
- Perplexity crawlers — Perplexity, accessed 30 October 2026
- IndexNow — IndexNow.org, accessed 30 October 2026
- GEO: Generative Engine Optimization (Aggarwal et al., KDD 2024) — arXiv / ACM SIGKDD 2024, accessed 30 October 2026
- StatCounter Global Stats — search engine and AI chatbot market share, Bulgaria, September 2026 — StatCounter, accessed 30 October 2026
Request an SEO, GEO and AEO audit
Describe your site, markets and languages — we will propose scope, timeline and price on request.