Gemini Didn’t Mention Our Business. Here’s How We’d Audit One Service Page

Gemini Didn’t Mention Our Business. Here’s How We’d Audit One Service Page

When Gemini leaves your business out of an agency shortlist, the useful response is not to add “best agency” to every heading. Start with the page a buyer would use to decide whether you belong on the shortlist at all. We applied that test to Byte Digital’s own AI SEO and GEO service page.

On 2 November 2026, we asked Gemini: “Which UK AI SEO agencies would you shortlist?” Byte was not named in that single answer. That observation does not diagnose the cause. It gives us a buyer question we can use to audit the page.

The five questions behind the audit

A prospective customer should be able to answer:

1. Who will do the work?
2. Who is the service for?
3. What will they receive?
4. What evidence can they inspect?
5. How do they start?

This is a buyer-clarity audit, not an attempt to reverse-engineer Gemini. Google’s guidance for generative AI features in Search (opens in a new tab) emphasises useful, original and people-first content. Although the consumer Gemini app is a separate surface, improving a page for real buyers is a sounder decision than manufacturing copy for an unseen model.

We reviewed the live Byte Digital AI SEO and GEO service page as it stood on 2 November.

What the page already does well

The page names the service clearly: “AI SEO & Generative Engine Optimisation”. It defines both terms near the top, connects AI search work with SEO foundations and gives visitors routes into eight practical guides.

It also shows a real implementation. The page links to Byte’s public knowledge base, an implementation case study and a publication record. That is stronger than making an unsupported claim that the agency “understands AI”.

Finally, the starting route is visible. The page offers a complimentary initial assessment and carefully distinguishes it from detailed standalone audits, which are scoped and priced separately. We would not blur that boundary to make the free offer sound larger.

Finding 1: the delivery ownership is present, but dispersed

Current evidence: The page says Byte brings together search expertise, content and website development. It identifies Gareth Allen as founder and Managing Director, describes the service as founder-led, and explains that Byte can implement agreed content and website changes or work with an existing developer.

Consequence for a buyer: The answer exists, but somebody comparing several agencies has to join it together from different sections. They may still wonder who leads the audit, who writes the proposed content and who changes the website.

Proposed action: Add one compact delivery statement beside the engagement section, using only responsibilities Byte can support publicly.

Current passage:

We handle agreed content and website changes directly. We can also work alongside your existing developer or agency.

Proposed addition, not live copy:

Your work is led by Byte Digital founder Gareth Allen, with the agreed audit, content and website implementation handled by Byte or coordinated with your existing developer. Your proposal will state who owns each action before work begins.

That wording should only be published after checking it against the actual delivery model for the engagement.

Finding 2: the initial review boundary could be closer to the button

Current evidence: The page says the complimentary initial assessment covers objectives, current business information and useful next steps. It also says detailed standalone audits are scoped and priced separately.

Consequence for a buyer: The distinction is responsible, but a visitor may click “Request your free AI visibility review” before reading the later scope explanation. If the visible offer beside the first button does not say what will be tested, expectations may form too early.

Proposed action: Add a one-sentence scope cue beside the first call to action: an initial discussion and high-level review of priority questions and pages, with detailed implementation or a standalone audit quoted separately. This must not promise platform-wide testing or a written deliverable unless Byte has agreed to provide it.

The page should make the next step easier to understand, not make the free step sound more extensive.

Finding 3: the evidence is credible, but the buyer has to choose the route

Current evidence: The page links to the knowledge base, implementation case study, technical method, publication record, measurement guide and relevant service pages.

Consequence for a buyer: That depth is valuable, but a first-time visitor may not know which proof answers their immediate concern. An implementation case study, observation log and method page do different jobs.

Proposed action: Introduce a short “Check our work” sequence:

This is not a request for more proof. It is a request to label the proof already available.

One change we would deliberately leave alone

We would keep the page’s refusal to guarantee rankings or recommendations.

The temptation after an absence is to sound more certain. That would be the wrong lesson. Gemini’s source guidance (opens in a new tab) explains that not all responses include related links or sources. Byte cannot control whether an independent product recommends the company on a particular run.

A useful service page should explain controllable work—technical access, content, evidence and implementation—without selling control over an external answer.

The order we would make and test changes

1. Record the page before editing. Save the current copy, date and baseline questions.
2. Clarify delivery ownership. Add the smallest supportable statement about who leads and implements the work.
3. Tighten the initial-review scope cue. Put it beside the first relevant call to action without expanding the offer.
4. Label the evidence route. Connect build, observation and measurement records in a short sequence.
5. Check the rendered page. Review the new copy on desktop and mobile, including headings, links and calls to action.
6. Repeat the original question later. Use the same wording and record the answer once.
7. Keep commercial outcomes separate. Track identifiable visits and qualified enquiries independently from shortlist appearances.

The first test after an edit is whether the page gives a buyer a clearer answer. A later Gemini observation is useful evidence, but not proof that one sentence caused the result.

Apply the same method to your service page

Choose one real buying question and one priority page. Avoid auditing the whole site at once.

For each of the five questions—who, fit, deliverables, proof and next step—copy the exact passage that answers it. If you cannot find one, record the gap. If the answer is already strong, leave it alone.

Then turn each genuine gap into a proposal with three parts:

That format makes it harder to invent problems merely to fill a checklist. It also gives an editor or developer something concrete to review.

Our AI visibility audit page explains how Byte connects question testing with technical and content review. The wider AI SEO and GEO service remains the commercial destination.

FAQs