AI visibility report
Reading robots.txt, the sitemap, llms.txt and the homepage the way an AI crawler does, then a few of your pages. Usually a few seconds. A site that leaves us hanging gets twenty-five, then we show what we have.
AI visibility report
AI-ready
out of 100
AI readiness · www.salesarcsolutions.com
Assistants can crawl, read, verify and cite this site. The work now is content and measurement.
Every check passed. The score is the ceiling for this scale; what moves the needle now is being cited, and that is measured, not scanned.
Scanned Oct 22, 2026, 10:33 PM MST · 23 requests · https://www.salesarcsolutions.com/
Crawler access
Can the AI assistants get in?
Agent readability
Can an agent read you without a browser?
Answer content
Is there anything worth citing?
Identity
Can it tell who you are?
The next question
This site can be cited. Whether it is cited is a different measurement: we ask assistants the questions your buyers ask and count how often you are named.
See ArcClaw™ AEO · or read the answers we publish for ourselves.
We ask two assistants three of your buyers’ questions, three times each with web search on, and show you who they name. Right here, in about a minute.
Would rather not leave an email? Every price is on the pricing page, and you can build a plan without talking to anyone.
Everything we checked
Open any line to see exactly what we asked your site and what it answered. Nothing here is inferred.
A robots.txt file that returns 200 and contains at least one User-agent group.
Trusted by The Rock Group, Fasturtle and Phoenix Strategy Group — and we run our own outbound on SalesARC.
From $999 once · Basic and Standard check out online, no sales call first · Export your data on every tier
Trust
Who wrote it, and which page is the real one?
Explicit Allow rules in robots.txt for the crawlers behind ChatGPT, Claude, Perplexity, Gemini, Apple and Bing.
We request the homepage once as each of the nine AI crawlers and record the status code your server returns to each.
A Content-Signal line in robots.txt saying your content may be used for search and AI answers.
A sitemap.xml that parses, found from robots.txt or at the default path.
A /llms.txt file: a plain-text index of what the company does and where the important pages are.
A /llms-full.txt file with the full text of the pages worth citing.
An HTTP Link header on the homepage pointing at llms.txt (rel="llms-txt" or rel="describedby").
The homepage returns text/markdown when a request asks for it (Accept: text/markdown).
The homepage delivers its words in the HTML itself, not after JavaScript runs.
A <title>, a meta description and exactly one H1 on the homepage.
A self-referential <link rel="canonical"> on the homepage.
Organization JSON-LD (or Person, for a personal site) with the name, URL and at least a logo or photo, phone, email, address or social profile.
Pages that answer buyer questions directly, marked up as FAQPage, QAPage or Article, and findable from the sitemap.
og:title, og:description and og:image on the homepage.
http redirects to https, and the www and bare domain both resolve to one host.
An email, phone number or address on the Organization, Person or ContactPoint record, and a mailto: or tel: link on the homepage.
The articles we sample carry an author that resolves to a Person with a name, and that name appears on the page.
Every page we sample has a self-referential canonical, its own title and its own description, and no large group of sitemap URLs is the same page with one word swapped.
