Can ChatGPT and Perplexity actually see your store?

Most stores have at least one technical issue blocking AI or search. We find yours, with proof.

Free to check. Your report lands in your inbox within 24 hours.

Tracee report, sample store1 confirmed issue
Sample Tracee audit report: visibility score 58 of 100, six layers tested with Access failing, and one confirmed issue showing OAI-SearchBot and PerplexityBot returning 403 Blocked while a standard browser returns 200 OK.

What a test returns

One result from each of the six layers we check, taken from our sample reports.

Discovery
Pages missing from the sitemapLive product pages found in navigation, not listed.Warning
Access
403 for AI search botsOAI-SearchBot and PerplexityBot blocked. A browser gets 200.Issue
Render
8 words in raw HTML1,240 words appear only after JavaScript runs.Issue
Extract
Main content readableHeadings and body text come through cleanly.Passed
Interpret
Structured data fails to parseJSON-LD is present but invalid, so it's ignored.Warning
Index-readiness
No canonical on filtered URLsFilter and page 2 URLs compete with the original page.Opportunity

Why would AI, or Google, miss a store that looks perfectly fine?

A store can have great products and still be invisible to AI and search for a handful of separate reasons, and most owners never find out which one applies to them, because nothing in a normal dashboard shows it.

Sometimes it's that AI assistants and search engines simply can't find all your pages in the first place. Sometimes a security setting blocks their automated visits without anyone noticing. Sometimes the pages load fine for a person but show up empty or broken to an automated visitor. And sometimes the information is all there, but it's structured in a way that's hard for AI to read and trust.

Each of these is a different, specific fix, not one generic problem.

What we actually check

Four layers, each tested directly.

Discovery. Can they find your pages at all?

We check your sitemap and site structure for the discovery problems that keep pages hidden from both AI and search with no error message to point to.

  • sitemap.xml validity
  • orphan pages
  • internal link depth
  • robots directives

Access. Can they get in without being blocked?

We test your site the way real AI crawlers do, and catch the CDN or firewall rules that block them even when your own settings say they're allowed.

  • per-bot status codes
  • CDN and WAF rules
  • rate limiting
  • independent recheck

Rendering. Does the page actually show real content?

Some pages look fine to a person but load empty for an automated visitor. We check for that gap directly.

  • raw versus rendered word count
  • JavaScript-only content
  • lazy-loaded blocks

Structure. Is your content structured so AI can trust it?

Missing or broken technical details, like page metadata and structured data, can make correct information look unreliable to AI and search alike.

  • structured data validity
  • product and offer fields
  • titles and meta
  • canonicals
Runs on Shopify, WooCommerce, BigCommerce, Wix, Squarespace, Webflow, and custom-built sites alike. Read the full technical breakdown

How it works

Three steps, no retainer.

  1. We test your site

    A direct, verifiable check across discovery, access, rendering, and structure, not a guess based on your platform or theme.

  2. You see the evidence first

    Delivered to your inbox within 24 hours: what's happening, where, and how we confirmed it.

  3. You decide what happens next

    If there's nothing to fix, we tell you that too. If there is, we quote a flat one-time price to fix it, no subscription required.

What this fix does, and doesn't, guarantee

We can prove and fix a confirmed technical issue stopping AI or search from reading your site correctly. We cannot promise a specific increase in sales, traffic, or how often AI mentions your brand, anyone who guarantees that outcome is guessing. What we deliver is proof that the issue existed and proof that it's gone.

We don't just say it, we show it

Every finding comes with evidence.

326
stores audited
189
had at least one confirmed issue
Tracee report, sample store, domain redactedAccess layer failed
Sample report: AI recommendation bots blocked at the firewall even though robots.txt allows them, with per-bot status codes as evidence.
What we foundOAI-SearchBot and PerplexityBot get 403 on every sampled page.
The proofA normal browser gets 200 on the same URL, confirmed on a recheck 20 seconds later.
Why it mattersrobots.txt allows them, so the block is a firewall or CDN rule nobody intended.

Sample reports built from our real test format. Store details are redacted.

Who this helps

Owners who want proof before paying.

  • You're running ads, but you suspect AI-driven search is becoming a source you can't see or measure yet.
  • You've never checked whether ChatGPT, Claude, or Perplexity can actually reach your product pages.
  • You manage your own site, or a small team does, and nobody's specifically responsible for this.
  • You'd rather see one confirmed problem than pay for an ongoing service you can't evaluate.

You pay once, and only if something was wrong

One flat, one-time fee for a confirmed issue. No retainer, no monthly plan, no charge if we don't find anything worth fixing.

The check itself is free. You only pay the flat fee if we find and fix something.

The check
Free
Report in your inbox
Within 24 hours
Nothing found
No charge
Confirmed issue, fixed
Flat fee, quoted first
Contract or retainer
None
Check my site

No card required to start.

Want the specifics behind this?

We test six clients against every page, then compare access, rendering, and content extraction across all of them.

Common issues we find: a CDN or firewall blocking crawlers even though robots.txt allows them, broken or missing sitemaps, JavaScript-only content that never reaches an automated visitor, and structured data or basic page metadata that's missing or malformed.

The six clients we test against every page
ClientOperatorRole
OAI-SearchBotOpenAILive answers
Claude-SearchBotAnthropicLive answers
PerplexityBotPerplexityLive answers
GPTBotOpenAIModel training
ClaudeBotAnthropicModel training
Standard browserControlBaseline
Live answers.
These feed the answers assistants give in real time.
Model training.
These collect content for model training, not live answers.
Baseline.
A normal browser visit, so every result has something to compare against.

Questions people ask before booking

What is an AI crawler audit, and how is it different from SEO?

SEO affects your Google ranking. This checks a wider set of technical issues, including some that affect both search and AI, and some that are specific to how AI assistants read a page.

Is this just about blocked crawlers?

No. Blocking is one common issue we find, but we also check page discovery, whether content actually renders for automated visitors, and whether your structured data is set up correctly.

How is this different from a free robots.txt checker?

Free tools only read your site's declared rules. We test what actually happens, and check several other technical layers a robots.txt checker doesn't touch at all.

Will this get me cited more by ChatGPT?

It removes a confirmed barrier to being read correctly. It can't guarantee how often you're mentioned, no one can honestly promise that.

Do I need to give you access to my store?

No. The initial check only requires your public site.

Does this work for Shopify, WooCommerce, BigCommerce, Wix, Squarespace, Webflow, or a custom-built site?

Yes. The check works on any live website, regardless of platform.

What happens after you submit my site?

We run the check, then email you the specific finding within 24 hours, what's happening, where, and how we confirmed it. If there's something worth fixing, we quote a flat price before doing any work.

Is there a catch?

No. If we don't find a real, confirmed issue, we tell you that and there's nothing to pay.

See what AI and search actually see on your site

Best suited for small and mid-sized online stores. Running an enterprise site with an in-house dev team? Reach out directly instead.