About Tracee

A technical audit service for online stores. We test what search engines and AI crawlers actually receive from your site, and we show the evidence before anything else.

stores audited
326
had at least one confirmed issue
189
clients tested on every page
6
hours to your report
24

Why Tracee exists

Most technical problems that keep a store out of AI answers and search results are invisible from the inside. The store loads, the dashboard looks normal, and nothing reports an error.

A firewall rule can turn away an AI crawler that your own robots.txt allows. A product page can look complete in a browser and arrive almost empty to a crawler that doesn't run JavaScript. Structured data can pass the usual testing tools and still never reach the systems that read it.

Tracee exists to find those gaps, prove them, and fix the ones that are real.

How we work

The rules every check follows.

  • Evidence before opinion

    Every finding comes with what we requested, what came back, and how we confirmed it. If we can't show it, we don't report it.

  • Test what happens, not what's declared

    Reading robots.txt tells you what a site says. We request the page as each crawler and record what it actually gets back.

  • Every block gets a control

    A block only counts if a normal browser visit to the same page succeeds. If the control fails too, we don't call it a block.

  • Recheck before reporting

    Access problems are confirmed with an independent second request before they go into a report.

  • Raw HTML matters

    We compare the raw HTML a crawler receives with the page a browser renders, because many AI crawlers never run JavaScript.

  • Nothing to fix, nothing to pay

    If a check comes back clean, we say so. You only pay a flat fee when there's a confirmed issue and we fix it.

The six layers we test

In the order a crawler meets them.

  1. Discovery

    Can crawlers find your pages? Sitemaps, internal links, and robots directives.

  2. Access

    Do they get in? Status codes for each crawler, plus firewall and CDN rules.

  3. Render

    Is the content there without JavaScript? The raw page compared with the rendered one.

  4. Extract

    Can the main content be pulled out cleanly? Headings, body text, and product details.

  5. Interpret

    Is it described in a way machines trust? Structured data, titles, and metadata.

  6. Index-readiness

    Is the right version eligible to show up? Canonicals, duplicates, and indexing directives.

What we won't do

  • Promise more traffic, sales, or AI mentions. Nobody can guarantee those honestly.
  • Lock you into a retainer or a monthly plan.
  • Ask for access to your store to run the check.
  • Report a problem we can't prove.

See what AI and search actually see on your site

The check is free, and your report lands in your inbox within 24 hours.