Aizii Learn · AI Search
← Back to Learn

Free tools to check your AI search readiness

A readiness check does not need a paid tool. The vendors publish free tools that check the exact things AI search depends on: whether the pages are indexed, whether the markup is valid, whether the site is fast, and whether the pages appear inside AI answers. This guide lists the free tools that are verified to exist, what each one actually checks, and what it does not check. No tool in this list is claimed to be free unless its own page verifies that, and no tool is claimed to measure AI visibility as a score, because no vendor publishes one.

A free tool that checks one thing well is worth more than a paid dashboard that claims to check everything. Use the tools below in the order they are listed, because the order is the same as the readiness order: the gate, the index, the markup, the speed, and the measurement.

1. Google Search Console

Google Search Console is Google's free tool for site owners. It shows how Google sees the site: which pages are indexed, which search queries bring people to the site, and what technical errors Google has found. Google's AI guide tells site owners to verify the site in Search Console to discover and diagnose technical issues quickly.

  • Use the URL Inspection tool to check a single page: whether Google has indexed it, when it was last crawled, and whether anything is blocking it. A page Google has not indexed cannot be a supporting link in Google's AI features.
  • Use the Pages report to see which pages are indexed and which are not, and why. A page that is not indexed has a reason, and the report names it.
  • Use the Generative AI performance report to see how often links to the site were shown in AI Overviews and AI Mode. The report shows impressions only, by page, country, device, and date. It has no clicks, no queries, and no click-through rate. Check the vendor docs in Sources for the current path to the report.
  • Use the Performance report to see clicks, impressions, click-through rate, and average position for the site's pages. Clicks from AI Overviews and AI Mode sit inside the ordinary Performance report under the Web search type, mixed in with every other organic click, so you cannot pull them out on their own.
  • Search Console is free, and it is the only tool in this list that reports what Google itself sees. That is also its limit: it reports on Google only. It says nothing about ChatGPT, Perplexity, Claude, or Copilot.

2. Bing Webmaster Tools

Bing Webmaster Tools is Microsoft's equivalent for the Bing index. Copilot retrieves from Bing, so a store that only checks Google can be invisible to Copilot for months.

  • Use it to confirm the key pages are indexed in Bing, and to see whether any are blocked or have never been crawled.
  • Use it to submit the sitemap, so Bing can find and index the pages. If the site is already verified in Google Search Console, Bing Webmaster Tools can import it, so you do not verify twice. Check the vendor docs in Sources for the current path before relying on a menu name in this guide.
  • Its limit is the same as Search Console's, in reverse: it reports on Bing only, and says nothing about Google or the assistants that do not use Bing.

3. Google Rich Results Test

The Rich Results Test is Google's free tool for validating structured data. It checks whether a live URL or a pasted code snippet contains structured data eligible for Google's rich results. It reads JSON-LD, Microdata, and RDFa, and lists each detected item as valid, valid with warnings, or invalid.

  • Paste a product page URL, or paste the markup itself, and read the result. An error blocks eligibility. A warning flags a recommended field that is missing.
  • A pass means the markup is eligible for Google's rich results. It does not mean Google will show a rich result. Google decides per query whether to show an enhanced listing.
  • The test checks only the structured data that can produce a Google rich result. It is not a complete schema.org validator, and it is not a site-wide audit. It tests one URL at a time.
  • Use it before publishing a new page, not after. A page that goes live with broken markup is a page that has to be fixed and recrawled.

4. Schema Markup Validator

The Schema Markup Validator is the free validator maintained by the schema.org community. It checks structured data against the full schema.org vocabulary, not just the types Google supports for rich results.

  • Enter a page URL, or paste the markup, and read what the validator extracts. It will flag types and properties schema.org does not define, and values of the wrong kind.
  • A page can pass this validator and still fail the Rich Results Test, because Google has its own required and recommended properties for each rich result type. A page can also pass the Rich Results Test and still fail this validator, because Google's test only covers the types Google supports. Use both, and read both results.
  • The validator checks correctness. It does not tell you whether Google will show a rich result, and it does not tell you whether an assistant will cite the page.

5. PageSpeed Insights

PageSpeed Insights is Google's free tool for testing page performance. It runs a Lighthouse audit on a page and, where enough visitors exist, adds field data from real Chrome users. It scores the page out of 100 for mobile and for desktop, and lists specific opportunities to improve speed.

  • Test the pages that matter, not just the homepage: a product page, a category page, and the About page. A homepage that is fast and a product page that is slow is a store with a slow product page.
  • Read the Core Web Vitals in the report: how fast the main content appears, how quickly the page responds to input, and how much the layout shifts while it loads. Those are the measurements behind the score.
  • A lab score can vary from run to run, so a small change between two runs may be noise. Field data, where it exists, is a rolling average over the past weeks, and it is missing for low traffic pages. Read both, and do not chase a single lab run.
  • PageSpeed Insights tests one URL at a time. It is not a site-wide crawl, and it does not check whether AI crawlers can read the page. It checks whether the page is fast and usable when a person arrives.

6. The browser checks that cost nothing

Some of the most useful readiness checks need no tool at all, only a browser.

  • Open [yourdomain.com]/robots.txt, replacing yourdomain.com with your actual domain, and read it as a crawler would. Check that the AI crawler tokens are not disallowed from the product and category pages.
  • Open [yourdomain.com]/sitemap.xml and check that the product pages, category pages, and key content pages are in it.
  • Open [yourdomain.com]/llms.txt, if the store serves one, and read what it lists. A file that lists the pages worth citing is a file doing its job. A file that lists nothing useful is a file to rewrite.
  • Open a product page, turn off JavaScript in the browser, and reload it. Many AI crawlers do not run JavaScript, so a page that shows nothing without JavaScript is a page those crawlers cannot read. The product facts should be in the first wave of HTML, not loaded after the page runs scripts.
  • Ask the assistants directly, with a fixed set of buyer questions, and log what they say. That is not a tool, it is a method, and it is the only way to see what ChatGPT, Perplexity, Claude, and Gemini actually do with your brand. No free tool in this list shows that.

7. What these tools do not do

  • No free tool in this list measures AI visibility as a score, because no vendor publishes one. A tool that sells a visibility score is selling its own calculation, not a vendor measurement.
  • No free tool in this list shows what ChatGPT, Perplexity, Claude, or Gemini say about your brand. Only asking them directly shows that.
  • No free tool in this list checks whether an AI agent can buy from the store. That is a different check, covered in our guide to checking if AI agents can buy from your store.
  • No free tool in this list replaces a full audit. The tools check one thing each. An audit checks them in order, writes down the findings, and puts them in priority order. That is our guide to running an AI visibility audit on your store.

The fundamentals

These mechanics are shared across every engine and covered in full in their own guides:

Say you run a furniture brand

Say you sell furniture, and you run the free tools for the first time. Search Console shows the best selling chair indexed in Google, but the dining table collection is not indexed, because a noindex tag was left over from a staging copy. Bing Webmaster Tools shows the same collection was never crawled in Bing. The Rich Results Test shows the chair page's markup is valid, but the table page's markup has an error in the price field. The Schema Markup Validator agrees. PageSpeed Insights shows the product pages are fast on desktop and slow on mobile, because the images are not compressed. The browser check shows the llms.txt file lists the store's pages but not the care guides. You fix the noindex tag, fix the price field, compress the images, and rewrite the llms.txt file, then ask for a recrawl. The whole check cost nothing but an afternoon. The fixes are the same fixes a paid audit would have found, because the tools that found them are the vendors' own tools.

What this guide does not cover

This guide covers the free tools that check AI search readiness. It does not cover how to measure AI visibility in full, which is our guide to measuring your brand's AI visibility, or how to run a full audit, which is our guide to running an AI visibility audit on your store, or the transaction layer that turns a recommendation into a sale. Free tools tell you what is broken. The rest of the system has to be ready when the shopper arrives.

Check your own brand now

Run the free scan. It takes seconds, no signup, and shows whether AI crawlers can read your pages today: aizii.ai/aeo-scan

Run the free scan

Sources

Note: links marked specific point to the page that supports the claim in this guide. Links marked general docs point to the vendor's general docs section for that topic, not to a page that proves every step. Check the vendor docs for the current path before relying on a menu name or click path in this guide.