HUB · 8 GUIDES

AI visibility

What search engines and AI assistants return and state about a business, measured every week as a record the business owns, and the engineering on the site that the record directs.

Quick answer: AI visibility is what search engines and AI assistants return and state about a business, measured weekly across seven dimensions as a record the business owns; each finding names a site mechanism and the engineering acts on it without promising outcomes.

Last updated

Jump to section
  1. What AI visibility is
  2. The dimensions of the record
  3. What the engineering looks like
  4. Common questions about AI visibility

Quick answer

What is AI visibility and how is it measured?

High confidenceVerified 15 Oct 2026

AI visibility is what search engines and AI assistants return and state about a business when a customer asks. It is measured by putting a fixed set of customer questions to the assistants and the results page every week, keeping the answers and sources, and reading the series as a record.

Additional Context

The record is a series the business owns. Each finding in it names a mechanism on the site or a surface the business controls, and the engineering that follows is done on the client's own platform.

Sources

The record

What AI visibility is

A customer asks an assistant which clinic, lender, resort or supplier to use, what it costs, whether it is licensed, and whether it serves their suburb. The assistant answers in a paragraph, cites a few pages, and the customer acts on it. The business never sees the question or the answer, and finds out when a caller quotes a fee it has not charged for a year. AI visibility is the name for what those answers contain, and for the search results page that often opens with an AI Overview above the links. Both can be measured, and the measurement is what makes the rest of this practice possible.

Measurement here means a fixed set of customer questions put to each assistant on the same day each week, with the full answer and its cited sources kept; the full results page pulled for a fixed list of search terms from a fixed location; a scripted assistant set the same customer tasks on the site and on comparable sites; and the site's own crawl, Search Console, analytics, Business Profile and Bing data pulled into the same file. Each pull is a row. The rows are a series. The series is the record, and every row of it belongs to the business as plain CSV.

The dimensions of the record

Each dimension has its own page in this section, and each one ends in the same place: a finding that names something on the site or on a surface the business controls. Recording what AI assistants say covers the question set, the weekly ask and the claim-by-claim check against the business's own pages. The sources assistants cite covers whose pages the assistants trust, and why a business goes missing from its own answers. Testing whether an agent can use your website covers the scripted assistant, the benchmark sites and the transcript.

On the search side, measuring your place in AI Overviews reads the whole results page, and Search Console as a weekly record keeps what Google reports as a series the console itself forgets. Business Profile, Bing and your site is the entity record, the short list of facts that drift between surfaces. Crawl health and Core Web Vitals is what the site actually served that week. Turning findings into engineering tickets is where all of it goes.

Key Takeaways

What AI visibility work consists of

  • One answer is an anecdote and a weekly series is a measurementCritical

    Assistants compose each answer from the pages they can read at that moment, so only fixed questions on a fixed cadence, with answers and sources kept, can show whether anything changed.

  • The record has seven dimensions and they are read togetherImportant

    Assistant answers, cited sources, the agent test, the results page, Search Console, the entity record and the weekly crawl each explain the others, which is why they live in one file.

  • Every finding names a mechanism the business controlsCritical

    A PDF fee table, a script-only tab, a blocked fetcher, two copies of the hours, a wrong canonical. Each becomes a ticket on the client's codebase or a correction on a surface it owns.

  • Outcomes are recorded and never promisedImportant

    A ticket closes when the next measurement shows the mechanism works. Whether an assistant's answer changes afterwards is written on the series with a date, because the assistants change for reasons nobody controls.

  • The practice measures and engineers, and it does not write the messageCritical

    What the business should say, which terms to target and where to get links are marketing decisions the record informs and the engineering does not make.

AI visibility is measured as a weekly record with seven dimensions, owned by the business, in which every finding names a mechanism on the site or a surface the business controls. The engineering acts on those mechanisms and records what happens next without promising it.

The engineering

What the engineering looks like

The same kinds of finding recur. A fee is quoted wrongly because the schedule is a PDF. A tab renders from script, so the fetched page is empty where the answer should be. A retrieval agent is blocked by a rule written for a training crawler. Opening hours differ between the Business Profile and the contact page. A canonical points at a staging host after a plugin update. Each is a ticket on the client's codebase or a correction on a surface the client controls: publish the fact as HTML, render the tab on the server, allow the agent, generate every copy of the hours from one record, fix the template. The agent-readable side of that work is described under machine-readable delivery, and the access-log view of which agents reach the site under the omnichannel content delivery page on auditing AI bot traffic.

The engineering closes a ticket when the next measurement shows the mechanism works: the fetch returns the fact, the agent completes the task, the surfaces agree. Whether an assistant's answer then changes is recorded on the same series with the date marked. It is never promised, because the assistants and the pages they read change for reasons nobody controls. Google says AI Overviews use the same eligibility as Search and need no special markup, which is why the engineering is the ordinary work of being crawlable, readable and consistent, done with the record open.

What this practice does not do

It does not advise on what the business should say about itself, which words to target, or where to get links. Those are marketing decisions. The record informs them, because it shows which questions are answered from other people's pages, and the business makes them however it chooses. When a fact a customer asks about has never been published, the finding says so and hands the question back; publishing the fact is the business's call, and publishing it in a form a machine can read is the ticket that follows. The managed form of the whole practice, with the engineering days attached, is AI Visibility Management.

Talk to National Digital about what the assistants say about you

Tell us the questions your customers ask and the sites they would also ask about, and we will run the first week's record and read it with you.

Optional

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Common questions about AI visibility

Is AI visibility the same as SEO?

They share the site. Technical SEO is the work of being crawlable, indexable and readable, and assistants read the same HTML that search crawlers do, so that work is inside AI visibility. The marketing side of SEO, deciding what to say and which terms to chase, is a separate discipline that this practice measures around and does not do.

Which assistants should be measured?

The ones Australian customers reach for, asked with web access on where the product offers it, because that is how a customer asking about a fee or an opening hour is answered. The record names which assistants are asked, so a change in the set is visible.

Can the measurement be done without the engineering?

It can be run on its own, and on its own it is a report. A report with no one assigned to act on it is the thing this practice exists to replace, so the record is sold with committed engineering days.

Does this tell us what to put on our website?

It tells you which facts customers ask about that your site does not state in a form a machine can read, and which pages the assistants trust ahead of yours. Whether to publish a fact, and how to describe your business, stays with you. Publishing what you have decided in HTML with structured data is the engineering.

How long before the record is useful?

The first week's rows already show what the assistants say and whose pages they cite. The series becomes useful for reading change after several weeks, and the crawl and Search Console pulls are useful from the first diff.

In this hub · every guide

ADVANCED