eoma

Docs › Screens

Web presence

A scan of your website from an AI crawler's point of view — what it can read, what it cannot, and what is missing. Weekly, plus a re-check button you can press once a day.

In 10 seconds

Before you start

Steps

1 — Open AI Provider Visibility and find the audit strip

This page has no sidebar entry of its own. It is reached from the card near the bottom of the AI Provider Visibility screen.

┌─ AI Provider Visibility ─────────────────────────────┐
│  …                                                   │
│  WEB PRESENCE AUDIT                                  │
│  See your web presence technical checklist           │
│  21 of 32 checks complete · 6 partial · 5 missing    │
│                            [Needs attention]         │
│                              View audit  →   ← click │
└──────────────────────────────────────────────────────┘

2 — Read the badge, then the group counts

The badge is a verdict on the foundational group only. The three counts above each column tell you where the work is.

3 — Start with anything Missing in the first column

Work left to right. A missing item in "Foundational technical" can stop an AI engine reading your site at all, which makes everything in the other columns unreadable too.

What you'll see

"Web presence audit" and "Web presence signals"

The eyebrow label with an information icon, then the heading. The icon explains what the scan covers.

The health badge and "Last checked date and time"

Top right. The badge reads Healthy, Needs attention, Critical or Scan failed. Beside it, the exact moment the scan ran.

"Checked N days ago" and the re-check button

Page header, top right. How old this audit is, in days, and the button that retakes it. One press per day; when you have used it, the line beneath names the hour your next one opens. The scan takes about a minute and the page updates on its own — you do not have to reload.

"Your work is not in these numbers yet"

A banner above the checks, and it only appears when it has rows to point at. It means you closed an EOMA action for one of the checks below after this scan was taken, so those rows describe your site as it was before your fix. They carry a Not re-measured chip. The chip does not claim the check now passes — we do not know that until the site is read again.

"Foundational technical"

The first column — the checks that decide whether an AI crawler can reach and parse your site at all: llms.txt, robots.txt, AI crawler access, sitemap.xml, Organization schema, sameAs links, Wikipedia, Wikidata, canonical URL, OpenGraph tags, and three graded checks on your schema and llms.txt quality.

"Authority + entity"

The second column — the checks that decide whether AI treats you as a credible, specific business: FAQ, Article, Breadcrumb and LocalBusiness schema, mainEntityOfPage, HTTPS, homepage response time, JS render requirement, hreflang, favicon, RSS/Atom feed, security headers, and the graded content checks (E-E-A-T signals, BLUF answer quality, topic cluster coverage, differentiator visibility, page intent taxonomy, conversational query coverage, content freshness).

The count line above each column

"18 complete · 6 partial · 5 missing", with "· 3 other" added when checks came back N/A or errored.

Each check row

The check name on the left, its state on the right with a matching icon. States are Complete, Partial, Minimal, Outdated, Missing, Blocked, Error and N/A.

"Scanned: your site · N pages crawled"

The footer. The exact address that was visited, and how many pages were read.

Reading the numbers

"21 of 32 checks complete · 6 partial · 5 missing". Eleven of the things AI engines look for on a website are absent or half-done on yours. Partial usually costs less to fix than Missing — the thing exists and needs finishing.

The badge, "Needs attention". One or more foundational checks are not Complete. That is the whole rule: Healthy requires every foundational check to be Complete or not applicable, and Critical appears once three or more of the essential ones are missing or blocked outright. A badge stuck on Needs attention with only one missing item is not the same problem as one with eight — read the column, not the badge.

"AI crawler access — Missing". Your robots.txt is turning away the crawlers that ChatGPT, Claude and Perplexity use. Nothing else on this page matters until that is fixed: an engine that cannot fetch your pages will describe you from other people's sites instead. This is the single highest-cost failure in the list.

"Organization schema — Missing". Your site never states, in a form a machine reads, what your business is called, where it is, and how to contact it. AI then guesses from your page text, and guesses inconsistently.

"Wikidata — Missing". No structured entity exists for your brand. Wikidata feeds Google's Knowledge Graph, which is what produces the brand card on Your brand on Google. Missing here and a missing brand card there are usually the same problem.

"llms.txt — Missing". A short file that tells AI engines which of your pages matter and how to describe you. It is new, cheap to add, and almost nobody in most categories has one.

"· 45 pages crawled". The scanner read 45 pages of your site to reach these answers. A low number on a large site can mean pages are not linked from anywhere the crawler could follow — which means AI is not finding them either.

When it goes wrong

You see Why What to do
"No web presence audit yet — one will appear after the next scan." Your brand has not been scanned. The first scan runs during setup. If setup finished more than a week ago, contact support.
"Couldn't load the web presence audit. Refresh to try again." The read failed. It does not mean the scan failed. Refresh. If it repeats, contact support.
The badge reads "Scan failed" and there are no check rows The scanner could not read your site at all — usually an unreachable address, a redirect loop, or a firewall blocking automated visitors. Open the address in the footer in a private browser window. If it loads for you but not for the scanner, your host or security service is blocking it.
Only two columns, no "Content quality" group The audit defines a third group, but no check is currently filed under it, so it does not render. The content-quality checks themselves still run — they appear inside the two columns you can see. Nothing to fix, and nothing is missing from your results.
The count in the entry card says 26, the page shows more The tooltip text predates six checks added in July. Trust the column counts on this page.
A check reads "Error" That one check could not complete — often a timeout on a slow page. Press Fixed it? Check again. A single Error does not change the badge, so the weekly scan will also clear it on its own.
"One re-check a day" under the button You have already re-checked in the last 24 hours. The line names the exact time your next one opens. The weekly scan still runs regardless.
A row is marked Not re-measured You completed an EOMA action for that check after this scan ran, so the state beside it describes your site before your fix. Press Fixed it? Check again. Until you do, treat that row as unknown rather than as a finding.
Reading this as a machine? The same page in Markdown: /docs/pages/web-presence.md

On this page