تخطَّ إلى المحتوى

GEO

AI visibility audit

An AI visibility audit answers one question: when your buyers ask an engine who to hire, what happens? We test crawler access engine by engine, check whether your pages can be read at all, then run an agreed prompt set and record who gets named instead of you.

ثلاثون دقيقة. بلا عرض شرائح. تخرج بخطة مرتّبة حسب الأولوية.

Most companies have no idea what an answer engine says about them. They have rankings, they have traffic, and they have a blind spot exactly where the buying decision now starts. An AI visibility audit closes it. It is the first project in our GEO services, and everything else we plan comes out of it.

What does the audit look at?

Three layers, in the order they break.

Access. Can each engine's crawler reach your pages? We fetch live as each one by name rather than reading your robots file and assuming. Most failures we find are not robots rules at all, they are security presets switched on by someone who never connected them to marketing.

Readability. Once a page is fetched, is there anything to quote? We compare what the raw HTML contains with what a browser shows, check heading structure, check whether an answer exists near the top, and check that your markup matches the visible page instead of contradicting it.

Presence. When a buyer asks the engine directly, are you named? This is the part that decides the plan, and it is the part most audits leave out because it takes real work rather than a crawl.

Three layers, six engines, reported one engine at a time and never blended into a single score.
LayerWhat we testWhat comes back
AccessA live fetch as each engine's crawler by name, against your firewall rather than your robots filePass or fail per crawler, with the rule that blocks it
ReadabilityRaw HTML against the rendered page, heading structure, answer placement and markup accuracyThe pages an engine cannot use, and the reason
PresenceYour agreed prompt set, run on every engine in scope, in each language you sell inNamed, linked or absent per prompt, with the sources that appeared instead

Why do we test each engine separately?

Because they read different indexes and rarely agree.

About eleven percent of the domains cited by ChatGPT are also cited by Perplexity for the same question. Averaging six engines into one number hides exactly the information you need, which is which engine you are missing and why.

Which crawler belongs to which engine, and what each one tends to cite, is set out in full on the GEO services page.

How do you choose the prompts?

From your sales calls, not from a keyword tool.

We start with the questions your buyers already ask a person: what does this cost, who else does this, is this company any good, what should I ask a supplier before I sign. Then we add category questions in the words a stranger would use, comparison questions naming your competitors, and questions about your own brand by name.

The set is usually 20 to 40 prompts, agreed in writing before we run anything, and run in each language you sell in. We deliver in English and Arabic, and we report the two separately, because the pool of pages an engine can draw on differs by language and so do the answers.

What does the report tell you?

Where you stand, and who is standing there instead.

For every prompt and every engine we log three states: named, linked, or absent. Under each one we list the sources the engine actually used. That list is the plan. If the same review platform appears in nine answers and you have no profile on it, the first task writes itself.

26%

Share of brands that received no mentions at all in AI answers in a large study of AI visibility. Ahrefs

A first audit that comes back empty is normal, not a disaster. It is also the most useful result, because it means the gap is presence rather than something subtle, and presence work has a clear order to it.

How is this different from a free consultation?

Scope and depth.

A free 30-minute consultation is the quick version of the same thinking: we look at one page with you, check crawler rules for the major engines, look for server-rendered text and valid markup, and name the first three fixes. It costs nothing.

The paid audit adds what half an hour cannot: the full prompt set run across several engines in each language, the competing sources named, a read of your third-party profiles and review coverage, a live fetch test against your firewall rather than your robots file, and a ranked plan with an owner and a date on every task.

What happens, step by step?

  1. Week 1: scope and prompts

    We agree the engines, the languages and the prompt set, and get whatever read access is needed for Search Console and analytics.

  2. Week 1: access tests

    Live fetches as every major crawler by name, against the live site, so firewall behaviour shows up rather than being assumed from a config file.

  3. Week 1: page and markup review

    Raw HTML against rendered page, heading structure, answer placement, structured data accuracy, and a check on the technical basics underneath.

  4. Week 2: run the prompts

    Every prompt on every engine in scope, recorded with the full source list and screenshots, so the findings can be checked rather than trusted.

  5. Week 2: report and plan

    Findings ranked by what they cost and how hard they are to fix, with the first three tasks named. You get the raw logs as well as the summary.

What does not belong in an audit like this?

An llms.txt check scored as a finding. No answer engine uses the file to decide citations, Google said in June 2026 that it has no effect, and a study of 137,000 domains found 97 percent of them were never requested. We note whether you have one and we do not score it.

A points deduction for missing FAQ markup. Google retired FAQPage rich results in May 2026. Accurate markup that mirrors visible text is still worth having, and the visible questions were always the part that did the work.

A single blended score with no method, a list of 200 findings with no order, and any claim that a particular change will produce a citation. The engines do not work that way and neither do we.

What do you do with the findings?

Fix them in order, or hand them over.

Most engagements move straight into a retainer, where the access fixes ship in the first weeks, the page work runs in weekly batches, and the presence work starts early because it takes longest. The engine-specific detail lives on the ChatGPT optimization and Google AI Overviews and AI Mode pages.

You can equally take the report and run it with your own team. That is a fair outcome and the report is written to survive it: every finding names the page or template it touches and how to test the fix. The rendering and markup items usually land with whoever owns technical SEO on your side. To see how we run this for a team in one of our regional markets, our market page walks through the same process.

How do we start?

Book a free 30-minute consultation first. If we find blocked crawlers or a page with no readable text, you already know the first month of work without paying anyone.

If you want the full picture, book a call and we will scope the audit. Plans are flat monthly retainers with starting prices on the pricing page, month to month, and you can stop at the end of any month.

أسئلة تتكرر علينا

  • What does the audit actually test?

    Three things. Whether each engine's crawler can reach your pages, whether the pages can be read and quoted once fetched, and whether you are named or linked when a real buyer question is asked. The third is the part most reports skip.

  • How is this different from a free consultation?

    A free consultation is a 30-minute look at one page with you: crawler rules, markup, server-rendered text and speed. The paid audit adds a full prompt set across several engines in both languages, the competing sources by name, and a ranked plan.

  • Which engines do you test?

    ChatGPT, Perplexity, Claude, the Gemini app, Google AI Overviews and AI Mode, and Copilot. They read different indexes and rarely agree, so we report each one separately rather than averaging them into a single number.

  • How many prompts do you run?

    Usually 20 to 40, agreed with you before we start. They cover category questions, comparison questions, questions about competitors and questions about you by name, in each language you sell in.

  • Do you give us a single visibility score?

    No. Scores with no published method move for reasons nobody can explain. We report the share of your prompt set where you were named and where you were linked, per engine, and list the sources that appeared instead.

  • How long does the audit take?

    Usually one to two weeks from access to delivered report, depending on how many languages and engines are in scope and how fast we can get the fetch tests done against your firewall.

  • Is it a one-off or ongoing?

    The first audit is a project. After that the prompt set is re-run weekly as part of a retainer, because the answers change and a single snapshot goes stale within a month.

  • What if the audit says we are fine?

    Then we say so and you keep your money. It happens, usually with brands that already have strong review coverage. We would rather tell you that than sell a retainer against a problem you do not have.

ثلاثون دقيقة لتعرف أين يكون موقعك غائبًا.

احجز استشارة مجانية مع إبراهيم وجيريمي. ننظر في موقعك في البحث وإجابات الذكاء الاصطناعي والتحويل أثناء الحديث، وتخرج بخطة مرتّبة حسب الأولوية.

ثلاثون دقيقة. بلا عرض شرائح. تخرج بخطة مرتّبة حسب الأولوية.