Kaliber Group — Performance Marketing, Augmented by AI

How to Fix AI Readability on Shopify (2026)

19 May 2026

Why this matters for Shopify stores

Shopify is brilliant at the operational side — payments, inventory, shipping, multi-channel selling — and quiet on the SEO side. Two stores with the same theme can score 40 points apart on AI Readability based on whether someone installed an SEO app, edited theme.liquid, or filled in per-product SEO fields.

For ecommerce the stakes are sharper than for service businesses. When AI engines summarise a product category, they reach for the brands their training data linked to that category. A store with no Organization schema, weak Product schema, generic meta descriptions, and a default robots.txt is invisible to that process. The competitor with the same product range and explicit schema gets cited; you don't.

The fixes are ordered by how much each moves the audit score, not by where each setting lives in the admin.

What Google said in May 2026

Google published an updated AI Search guide on May 7, 2026. The headline: optimising for generative AI search is optimising for the search experience, and thus still SEO.

Three claims worth knowing:

• No special files needed. llms.txt and agents.md give no benefit for Google's AI surfaces. They may still help niche LLM tools that read them, but the broad-adoption case is dead.
• No content chunking needed. Markdown mirrors, sitemap.md, and similar parallel formats are unnecessary. Google's systems handle multi-topic pages natively.
• No special schema needed for AI. Schema still helps traditional rich results and is still consumed by ChatGPT, Claude, and Perplexity. But adding schema because of AI search is no longer the angle.

Google also stopped rendering FAQ rich results the same day. The markup still parses; the SERP feature is gone.

1. Allow AI crawlers in robots.txt

The single highest-impact fix. AI engines can't read what they can't fetch. Shopify's default robots.txt has no explicit allow rules for AI crawlers, and the admin UI gives you no way to edit it.

The workaround: create a theme template file called robots.txt.liquid that overrides the default while preserving Shopify's existing rules.

The robots.txt.liquid template to add

Create a new template called robots.txt.liquid. The Liquid below preserves Shopify's defaults and appends the AI-crawler allow lines.

{% for group in robots.default_groups %}
{{- group.user_agent }}

{% for rule in group.rules -%}
{{ rule }}
{% endfor -%}

{% if group.sitemap != blank -%}
{{ group.sitemap }}
{% endif -%}
{% endfor %}

User-agent: GPTBot
Allow: /

User-agent: ClaudeBot
Allow: /

User-agent: anthropic-ai
Allow: /

User-agent: CCBot
Allow: /

User-agent: Google-Extended
Allow: /

User-agent: PerplexityBot
Allow: /

User-agent: Applebot-Extended
Allow: /

User-agent: cohere-ai
Allow: /

User-agent: Bytespider
Allow: /

To allow search indexing but block AI training: set Disallow: / on Google-Extended and Applebot-Extended only. Those control training data without affecting search crawlers.

2. Add Organization schema

Organization schema is how AI engines link your domain to your brand. Without it, they often cite a competitor instead of you when answering questions in your category.

No Shopify theme adds it automatically. Two paths: install an SEO app that includes it (JSON-LD for SEO, Schema Plus, Smart SEO), or paste the JSON-LD into theme.liquid directly.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "{{ shop.name }}",
  "url": "{{ shop.url }}",
  "logo": "{{ 'logo.png' | asset_url }}",
  "sameAs": [
    "https://instagram.com/your-brand",
    "https://facebook.com/your-brand",
    "https://tiktok.com/@your-brand"
  ],
  "contactPoint": {
    "@type": "ContactPoint",
    "telephone": "+65-6000-0000",
    "contactType": "Customer Service"
  }
}
</script>

The Liquid variables ({{ shop.name }}, {{ shop.url }}) auto-fill from your Shopify settings, so you only edit them in one place.

3. Make sure Product schema is complete

Product schema is the second tier of entity recognition for ecommerce. Modern Shopify themes (Dawn and most theme-store themes from 2023 onwards) auto-render it on product pages. Older themes, custom themes, and heavily-modified themes often don't.

Even when it's present, it's usually incomplete. Required fields: name, image, offers. Highly recommended: description, brand, sku, and aggregateRating + review if you have reviews. Missing fields don't break the schema — they just reduce how AI engines summarise your products.

4. Write meta descriptions that say something

AI engines read meta descriptions to decide whether to surface a page in an answer summary. Two patterns fail on Shopify: descriptions auto-generated from product copy that opens with "Welcome to our store...", and homepage descriptions defaulting to "Shop the latest..." with no category, brand, or differentiator.

A description that passes names at least one of: a specific category, a named differentiator, or a location. "Handcrafted leather bags made in Singapore. Lifetime guarantee" passes. "Welcome to our store. We sell quality leather goods" fails.

5. Fix heading hierarchy

AI engines use headings to map the page. The audit flags pages with more than one H1, skipped levels, or fewer than five H2/H3 headings on a substantive page.

The Shopify-specific bug: many themes wrap the store logo in <h1>. Every product page then uses an H1 on the logo, leaving the actual product title at H2. AI engines see "Acme Store" as the H1 and "Premium Leather Wallet" as a subordinate heading — opposite of what you want for product discovery.

The fix

Online Store → Themes → Edit code → search for <h1. If the store name is wrapped in <h1> in header.liquid or theme.liquid, change it to <div> and let the page template handle the H1. Product title on product pages, collection name on collection pages, hero headline on the homepage.

6. FAQ schema after Google's May 2026 change

Short answer: keep using it on pages that are genuinely Q&A. Stop using it as a SERP-snippet hack on pages that aren't.

The SERP rich result is gone. The markup still parses cleanly. Non-Google LLMs (ChatGPT, Claude, Perplexity) appear to still consume FAQ schema when summarising — Google hasn't confirmed whether their own AI surfaces use it. For a product page with a real FAQ section ("How long does shipping take? Is the leather full-grain? What's the return window?"), FAQ schema is still a legitimate marker for non-Google AI.

7. Make your product content concrete enough to be cited

This is the check Google would say matters most. The audit scores three things on the actual content: specificity (does the page name real products, services, or methods?), differentiation (does it distinguish you from alternatives?), and credibility (does it name real proof — reviews, customer counts, awards?).

Shopify copy fails this more often than service-business copy. Three patterns specific to ecommerce:

Product descriptions that lead with mood. "You're going to fall in love with this scarf. The perfect addition to your wardrobe." Zero concrete claims, nothing to summarise. Rewrite to lead with material facts: "100% Mongolian cashmere scarf, 200 × 70cm, woven in Inner Mongolia. Weighs 220g. Available in eight colours including the bestselling Charcoal." Every clause is a citation hook.

Collection pages with no body copy. Most Shopify collection pages are a grid of products with a one-line title. AI engines reading the collection have nothing to extract about the category. Add 200-400 words per major collection — what defines it, who it's for, what differentiates the products. Admin → Products → Collections → Description field.

Homepage hero with no specifics. "New season collection now live" + "Shop now" teaches AI engines nothing. Replace with category, audience, differentiator. "Handcrafted leather bags made in Singapore since 2018. Lifetime repair guarantee" gives AI engines something to cite when someone asks about durable leather bags in Singapore.

8. Verify everything is actually working

Three free tools. Take five minutes per page.

Schema: paste any product or page URL into Google's Rich Results Test. Critical for Shopify — theme-code schema changes render immediately on the live site (no publish step needed), but app-based schema changes can take a few minutes to propagate.

Robots.txt: visit yourstore.com/robots.txt in incognito. You should see Shopify's default rules followed by your AI-bot block. If your additions are missing, the robots.txt.liquid template ended up in Sections or Snippets instead of Templates.

App conflicts: if you have more than one SEO app installed, view source on a product page and search for application/ld+json. You should see ONE Product block, not two or three. Duplicate Product schema from competing apps is the most common source of invalid markup.

End-to-end: re-run the AI Readability Checker. Each fix should move the score visibly.

What to fix first — a half-day order of operations

First (15 minutes). Create the robots.txt.liquid template and paste the Liquid block. Biggest score lift per minute spent.

Second (30 minutes). Add Organization schema to theme.liquid (or install an SEO app that handles it). Verify on the homepage with Rich Results Test.

Third (an hour). Audit Product schema on your top 5 best-sellers. Fix any product missing description, brand, or image fields. Wire up review schema if you have a reviews app.

Fourth (2 hours). Rewrite meta descriptions on top 20 products and top 5 collections — 120-160 characters, concrete claim each. Bulk via an SEO app if the catalogue is large.

Fifth (2 hours). Rewrite homepage hero, collection page bodies, and top 5 product descriptions. Lead with material facts.

The other fixes (heading hierarchy, FAQPage, canonical edge cases) are useful but smaller. The first five account for most of the score lift.

One pass, lasting effect

None of these fixes need ongoing maintenance once set up. The robots.txt.liquid template sits in your theme forever. Schema renders on every page via theme.liquid. Heading hierarchy stays fixed unless someone changes the theme. Meta descriptions, once written well, persist — though products you add later need their own.

That's why it's worth getting right on the first pass. Stores that scored poorly in March usually still score poorly in October — nothing changed.

If your audit surfaces fixes that need more than the admin can give you — heavy theme customisation that conflicts with schema, a catalogue that needs proper rewriting at scale, multi-market stores with locale-specific schema — that's the work we take on. Get in touch, or read about the GEO & AI Search service.

Frequently asked questions