The technology behind
AI-sourced pipeline
Nevisible sees both sides of an AI-sourced purchase. It serves your catalog, specs and certifications to 8 AI engines and procurement agents on ai.yourcompany.com, records which AI systems read them, and matches that research to the companies that visit next.
About 10 minutes of setup. No redesign, no change to your pages.
What manufacturers and distributors see
- +21.07%pipeline revenue within the first quarter
- +55%qualified leads from AI-referred buyers
- +312%AI bot and agent traffic to your catalog
Average results across 700+ customers, 90 days after implementing Nevisible.
Architecture
One platform, from an AI read to a rep's inbox
Nevisible is five layers that work as one. Your host and catalog feed the data layer. Human/agent behavioral matching ties AI research to the buyers who follow it. The decision layer scores and labels each company, and the right rep hears about it.
Sales outcomes
What your sales team gets
+21.07% pipeline revenue in the first quarter
- New buyers uncoveredCompanies AI sent you that never called or filled in a form+55% leads
- Briefed before the first callWhat the buyer read, what they want and why nowPeak intent
- Expansion for account ownersExisting customers researching a new product lineCross-sell
- Revenue you can traceEvery deal followed from the AI answer to revenue, AI-sourced kept apart from other inboundClosed-won
Proprietary buyer-intent model
Trained on B2B procurement behavior, it sees the full context before a rep hears a word: who the company is, where it is in its buying journey and what it wants.
- 1Researches the prospect
- 2Tracks intent across the journey
- 3Surfaces the highest-intent moment
- 4Tells the rep what the buyer wants
Qualified on both sides of the research
AI insightsWhich specs, certificates and products AI agents read, compared and shortlisted
Human insightsWhat people at the company read, how deep they went and how often they came back
Fit gate · 7 criteria
- Cert / spec match
- Product-line fit
- Capacity
- Not an existing customer
- Deal size
- Geography & lead time
- Owned and acted on fast
Routing
- Product line → rep
- Region → rep
- Below 55 · never billed
AI agent readHuman visitSignals compared
Proprietary matching model
Trained on millions of human and agent behavior signals, it scores how likely an AI read and a human visit are the same buying effort.
- 5signals weighed before a company is tied to AI research
- 2sides of every purchase, AI and human research, in one view
Attribution state
- Confirmed AI-sourced
- Likely AI-influenced · 71%
- Other inbound
- AI-readable catalogSpecs, SKUs and checked certificates on ai.yourcompany.com
- Verified AI readersSigned request or published IP list, never the name alone
- Human visitsThe script: source and pages, nothing stored on the device
- Main-site AI requestsThe read-only log feed from your host
Read by
ChatGPT
Claude
Gemini
Perplexity
Copilot
Google AI Overviews
Grok
Meta AI- + procurement agents: SAP Ariba Joule, Coupa Navi, Fairmarkit, Globality
- Cloudflare
- Vercel
- Netlify
- CloudFront
- Fastly
- Akamai
- Catalog & ERP files
- Customer list
- CRM (Enterprise)
Why it's built this way
A tracking script only sees people
AI crawlers and live AI fetchers download your pages without running JavaScript, so a tag on your site never loads for them. Seeing AI takes a server-side position. That's what the ai. subdomain and the log feed give Nevisible.
| Who reads your site | Tracking script alone | Nevisible Standard |
|---|---|---|
| A buyer browsing your main site | Yes | Yes |
| An AI crawler indexing your main site | No | Yes, via the log feed |
| An AI fetcher answering a buyer's question right now | No | Yes, via the log feed |
| Any AI reading your catalog on ai.yourcompany.com | No | Yes, at the edge |
| A procurement agent shortlisting suppliers | Seen, not recognised as AI | Yes, verified |
Setup
Four steps, about 10 minutes
Your team adds one DNS record, one robots.txt line, one script tag and a read-only log connection. Your main site isn't rebuilt or redesigned, and you're live in 48 hours.
-
1
Add one DNS record
Point a subdomain at Nevisible. The SSL certificate is issued automatically.
Type CNAME Host ai Value edge.nevisible.com
-
2
Add one robots.txt line
It tells AI crawlers where your AI-readable catalog lives.
Sitemap: https://ai.yourcompany.com/
sitemap.xml -
3
Add the script tag
A few kilobytes. It records human visits and their source, writes nothing to the device and never blocks page rendering.
<script src="…/nevisible-ai.js" async></script>
-
4
Connect your host's logs
Answer one question, "Where is your website hosted?", and grant read-only log access. Nevisible never touches your main domain's DNS.
Access read-only Keeps AI requests only IPs hashed at ingest
| Your site | Standard setup |
|---|---|
| Pages, design and CMS | Unchanged |
| Search rankings | Unchanged: canonical tags credit your main pages |
| Page speed | Unchanged: AI traffic is served off your site's render path |
| Cookie banner | No new cookies to declare |
| Removing Nevisible | Delete the DNS record, the robots.txt line and the script |
Two ways to connect
Standard by default, Full Edge by request
Standard keeps Nevisible beside your site. Full Edge puts Nevisible in front of it, for teams that want every AI request to the main site seen in real time.
Standard
"Deployed on a subdomain. Your main site's pages stay as they are."
Full Edge
"Your site is served exactly as it is today; Nevisible sits at the edge to see and answer AI agents."
| Standard | Full Edge | |
|---|---|---|
| DNS change | New ai. subdomain only | www points to Nevisible's edge |
| AI requests to your main site | Seen where your host shares logs | Always seen, in real time |
| Lighter version for AI | On ai.yourcompany.com | On your own URLs, when a verified agent asks |
| In your site's request path | No | Yes, built to add under 50 ms |
| Setup time | About 10 minutes | 1 to 3 days, with a tested cutover |
| Safety net | Nothing to roll back | Kill switch, plus DNS rollback in minutes |
Works with your host
Log feeds for the hosts manufacturers use
The log feed is read-only and copies AI requests only. Where a host shares no logs, Nevisible estimates AI reads of your main site and labels them as estimates in your dashboard.
| Your host or CDN | How it connects | Coverage |
|---|---|---|
| Cloudflare | Logpush, or a pass-through logging Worker that fails open | Full |
| Vercel · Netlify | Log drain in project settings | Full (Netlify by plan) |
| AWS CloudFront | Real-time logs or S3 log bucket, read-only role | Full |
| Fastly · Akamai | Real-time log streaming to Nevisible | Full |
| Self-hosted Nginx, Apache, IIS | Lightweight log shipping agent | Full |
| WordPress on managed hosting | Nevisible plugin or the host's CDN logs | Partial: cached pages are missed |
| Webflow · Wix · Squarespace · Shopify · HubSpot CMS | These hosts don't share request logs | Estimated, unless you use Cloudflare in front |
The data layer
Your catalog, structured once and served to every AI engine
Nevisible turns the files you already have into structured, machine-readable data, checks your certifications at the source, and keeps it all current when anything changes.
How AI readers are verified
A bot's name is never taken on trust
Anyone can call their scraper GPTBot. Nevisible counts an AI reader only when its identity is proven, and separates crawlers that index on a schedule from fetchers that act on a buyer's live question.
Crawlers
GPTBot, ClaudeBot, PerplexityBot. They index on their own schedule, about 80% of AI bot traffic. Used for coverage and freshness, never to match a company.
Fetchers
ChatGPT-User, Claude-User, Perplexity-User. Someone asked a question that sent the AI to your page. This is live demand.
Procurement agents
The sourcing agents inside the procurement platforms buyers already use: SAP Ariba Joule, Coupa Navi, Fairmarkit, Globality, GEP SMART, Ivalua IVA, Keelvar and Levelpath. They find, compare and shortlist suppliers. Counted only when verified by signed request or published IP list.
Human/agent behavioral matching
How an AI read is tied to the buyer who follows it
Buyers now send an AI agent to research suppliers before a person ever visits. Human/agent behavioral matching is how Nevisible connects the two.
Proprietary matching model
Trained on millions of human and agent behavior signals
Nevisible's algorithm compares what an AI agent read on your catalog with the human research that follows, and scores how likely it is that they're the same buying effort.
- 1Compares agent and human research
- 2Tests it against chance on your site
- 3Scores the match
-
1
The agent read is logged
A verified AI engine or procurement agent reads your pages on ai.yourcompany.com or your main site. Nevisible records which products, specs and certificates it read, in what order, and when. Scheduled crawlers are left out, because no buyer asked for them.
-
2
The human visit is resolved
A person arrives on your site. The script records the source and pages, and IP-to-company resolution names the company.
-
3
The two are matched
The algorithm compares the human research with the agent reads before it, tests the pattern against your site's normal chance of a coincidence, and gives the pair a confidence score from the signals below.
-
4
The company is labelled
A proven link is Confirmed AI-sourced. A strong pattern without proof is Likely AI-influenced, with its confidence. The rest is Other inbound.
What the confidence score weighs
Same research path
The person reads the same specific pages the agent read, in the same order, minutes later.
AI citation
The page they land on is one AI engines cite in answers to buyer questions.
Repeat visits
The company comes back to the same product line over several days.
Spec depth
They go deep into specifications and certificates, not just the homepage.
Self-identified
They download a file, ask a product question or send an RFQ. This is the strongest signal.
Only verified agents count: scheduled crawlers, bots that fail verification, and VPN or residential-proxy traffic never add to a score. A behavioral match on its own is never counted as Confirmed AI-sourced, and it never names a person. It names the company, and a person only when they identify themselves to you.
Methodology
How companies are matched, and how sure we are
Nevisible matches visits to companies with IP-to-company resolution, after removing consumer, VPN, proxy and cloud networks. Every match shows its confidence. No one in this category can match more than roughly 30–45% of business visits at the moment they happen, so Nevisible also credits earlier visits once a buyer identifies themselves. How AI reads are tied to those visits.
Confirmed AI-sourced
The AI source is on the record: a click from an AI answer, or an AI read of your catalog.
Likely AI-influenced
The pattern matches AI-led research, but the link isn't proven. Always shown separately, never counted as AI-sourced.
Other inbound
Search, social, referral and direct visits, still matched, scored and routed.
SEO, GEO, security and privacy
Built to pass your IT review
SEO and GEO safeguards
Search engines
- Your main-site pages are never changed based on who is asking
- Every ai. page carries a canonical tag to its main-site page
- The "AI-Ready by Nevisible" badge link is nofollow
AI engines (GEO)
- Your catalog is served as Markdown, JSON-LD and llms.txt that AI engines can read and quote
- Structured data points to your main URLs, so AI citations credit your domain
- The lighter version goes only to verified agents that ask for it
- Specs and certifications are kept current, so AI repeats today's facts
Security and privacy
Security
- SOC 2 Type II
- Read-only access to your host's logs; Nevisible never touches your main domain's DNS
- The log feed keeps AI requests only
Privacy
- Company-level matching: a person is named only when they identify themselves
- No cookies or device storage, no fingerprinting
- IP addresses kept only as a salted hash
- Deletion on request, cascading through every record
- Data stored in the EU for EU and UK customers, and in Canada and the US for North American customers
- Data Processing Addendum available on request at privacy@nevisible.co
More in Security and GDPR & data protection.
Technical questions about Nevisible
Nevisible serves your catalog, specs and certifications to AI engines and procurement agents on a subdomain of your site (ai.yourcompany.com), sees which AI systems read them, and matches that research to the companies that visit next. A lightweight script covers human visitors, and a read-only log feed from your host covers AI requests to your main site. Each matched company is scored for fit and sent to the right rep.
Human/agent behavioral matching is how Nevisible ties AI research to the human research that follows it. It compares what a verified AI engine or procurement agent read on your catalog with the visits that come after, using a proprietary algorithm trained on millions of human and agent behavior signals. It weighs five signals: the same research path in the same order, AI citations of the landing page, repeat visits, depth into specs and certificates, and whether the buyer identified themselves. Scheduled crawlers and unverified bots never count. IP-to-company resolution names the company. A proven link is labelled Confirmed AI-sourced, and a strong pattern without proof is labelled Likely AI-influenced with its confidence. It never names a person unless they identify themselves.
Yes. AI crawlers and live AI fetchers don't run JavaScript, so a tracking script never sees them. Nevisible sees them server-side: every request to ai.yourcompany.com is logged at the edge, and a read-only log feed from your host or CDN shows AI requests to your main site. A bot only counts when its IP address is on the AI operator's published list or it sends a signed request.
One CNAME record: ai.yourcompany.com pointing to edge.nevisible.com. The SSL certificate is issued automatically. You also add one line to robots.txt that points AI crawlers to the ai. sitemap. To remove Nevisible, delete the record.
In the Standard setup your main site's pages stay exactly as they are. Nevisible never changes your main-site pages based on who is asking, every page on ai.yourcompany.com carries a canonical tag pointing to its page on your main site, and structured data points to your main URLs, so search engines keep crediting your site.
No. The script stores nothing on the visitor's device: no cookies, no localStorage or sessionStorage, and no device fingerprinting. Return visits are linked on the server, and IP addresses are kept only as a salted hash.
Nevisible matches visits to companies with IP-to-company resolution, after removing consumer, VPN, proxy and cloud networks, and shows the confidence of every match. No one in this category can match more than roughly 30–45% of business visits at the moment they happen. When a buyer later identifies themselves, their earlier visits are credited back to the company.
No. Nevisible identifies companies. It names a person only when that person identified themselves to you, for example by downloading a certificate packet, asking a question in Ask Product Hub or sending an RFQ.
Full Edge is an optional setup in which your www hostname points to Nevisible's edge, which forwards every request to your existing host unchanged. It sees every AI request to your main site in real time and can serve the lighter version on your own URLs to verified agents that ask for it. It includes a tested cutover, a kill switch and rollback by switching DNS back.
Bring your IT team. We'll walk them through it.
A 20-minute technical walkthrough on your own domain: the DNS record, your host's log feed, and what AI is reading on your site today.
Standard setup: about 10 minutes · Live in 48 hours · SOC 2 Type II
Last updated