LiveOpenAI Ads, now in Cresva.See how
Skip to content
Cresva for Chrome

Can AI agents read this store?

One click, about three seconds: see whether AI agents can find, understand, and buy from this store. No account, no setup.

Available in the Chrome Web StoreComing soon
What a person seescresva.ai, rendered

The growth system for brands

selling to humans and AI agents.

Cresva is the marketing and commerce platform for ecommerce brands selling to humans and AI agents.

What an agent seesthe same page, as it is served

Structured data on the page

@type
Organization
name
Cresva
url
https://cresva.ai
description
Cresva is the marketing and commerce platform for ecommerce brands selling to humans and AI agents.

Crawlers allowed in robots.txt

GPTBotOAI-SearchBotClaudeBotPerplexityBot

Green means allowed

Both panes are cresva.ai, read from what the site publishes about itself. A store where the right pane is empty is a store an agent cannot describe, whatever the left pane looks like.

How it runs

One click, and the answer is the panel

Open any storeyours or a competitor's
Click the iconone tab, granted by that click
Read the verdictabout three seconds

No account, no setup and no model call in the loop. The scan reads the page in front of you and the panel opens beside it.

Three axes

What one click tells you

Every scan answers the same three questions in the same order, because they fail in that order. A store nobody is allowed to crawl cannot be understood, and a store that cannot be understood cannot be bought from.

Can they find it

Are the assistants allowed in at all?

Whether robots.txt admits the crawlers behind ChatGPT, Claude and Perplexity, or quietly turns them away. A single disallow line is the difference between being considered and being invisible, and it is the most common reason a good store never comes up.

robots.txt rules, deprecated directives, CDN level bot rules

Can they understand it

Is the page readable without running your JavaScript?

Most agents read what the server sends, not what the browser assembles. The extension compares the two and tells you which of your product details exist only after JavaScript runs, and whether the page carries product structured data at all.

content in served HTML, product schema, served versus rendered

Can they buy from it

Is there enough to complete a purchase decision?

Price, availability, currency and where you ship. An agent that can read your page but cannot find a price will describe you and then recommend somebody else. This is the axis that fails most often, and usually on one field.

offer completeness, ships-to, agentic commerce descriptor

Where we could not establish something, the panel says so instead of marking you down for it. Our failure to look is never rendered as your failure to publish.

Privacy

What it never reads

An extension that can look at any page you open has to be specific about what it does not look at. Here is the short version. The full policy is linked below and every claim in it names the file that makes it true.

Never touched

  • Cookies. The extension does not hold the permission needed to read them.
  • Local storage, session storage and IndexedDB on any page you visit.
  • Credentials of any kind. There is no sign in and no account.
  • Form fields. Inputs, textareas, selects and editable regions are removed before any text is read.
  • Other tabs. Access is granted one tab at a time, by your click.

Refused outright

On an admin panel, a checkout, a cart, an account page or any page carrying a password field, no request leaves your browser at all. Not a redacted one. Nothing.

The refusal fires before the page is touched, because the address by itself gives something away. It fires a second time after the page has been looked at, for the password field, and anything already read is discarded unsent.

When you do turn on the browser view, emails, card shaped numbers and phone shaped strings are removed in the page, before the request exists. The text sample is never stored and never logged.

When one page is not enough

The panel is the first look. The audit is the whole store.

A scan reads the page in front of you, in about three seconds, with no model calls and nothing to sign up for. That is the right size for checking a fix. It is the wrong size for planning one.

The extension

One page, one verdict, in seconds. Where the three axes stand, the specific rows that failed, quoted evidence from your own page, and a snippet to paste where a fix is a snippet. Re-scan after you ship and watch a row change.

The growth audit

The whole store rather than one page: catalogue health across your products, tracking and schema coverage, and whether assistants actually mention you when somebody asks for what you sell. Enter one URL, no signup.

Run the full growth auditFree, one URL, no account.

One click. On whatever store you are on.

No account and no setup. The panel opens beside the page you are already looking at.

Available in the Chrome Web StoreComing soon