Audit report — example-store.com | StoreCheck Visibility

example-store.com

AI bots are stopped at your site's edge. Even when robots.txt allows them, the bot-protection layer returns 403/challenge to some bots — site owners usually have no idea. Verify it yourself:

curl -s -o /dev/null -w "%{http_code}" -A "OAI-SearchBot"
        https://example-store.com/

Application scope score: 68 (C)

6 failures · 4 warnings — each finding comes with a fix and a check you can run yourself.

Fix these first

Average score across 146 scanned stores is 63 — this store does better than 42% of them.

This is a technical measurement report; it does not claim AI citation or ranking guarantees. Rule pack: rulepack_tr_2026.10.0 — platform: shopify

AI & SEO visibility

This layer measures technical readability by search engines and AI answer systems — not a citation guarantee; it checks edge behavior with real bot user-agents and robots.txt policy separately.

Check	Result	Severity	Observation & fix
AI bot access — edge/WAF AI-EDGE-PROBE	Fail	high	Why it matters: even when robots.txt allows bots, the edge layer can return 403 — AI visibility quietly dies without the owner knowing. How to fix: in Cloudflare, turn off the AI bot block under Security → Bots, or add an allow rule for search bots. Check guide → Verify yourself: `curl -s -o /dev/null -w "%{http_code}" -A "OAI-SearchBot" https://example-store.com/` — if it returns 403/503 instead of 200, the block is at the edge. Technical observation `{"probes":[{"bot":"googlebot","status":200},{"bot":"oai-searchbot","status":403},{"bot":"chatgpt-user","status":403},{"bot":"claudebot","status":200},{"bot":"perplexitybot","status":200}]}`
robots.txt — AI search bots AI-ROBOTS-SEARCH	Pass	high	Technical observation `{"blocked":[]}`
robots.txt — AI training bots AI-ROBOTS-TRAINING	Warn	low	Why it matters: no policy defined for GPTBot/ClaudeBot/CCBot — unclear whether that's a deliberate choice. How to fix: add an explicit Allow or Disallow line for training bots in robots.txt; blocking is a legitimate licensing choice. Check guide → Verify yourself: look for an explicit policy line for GPTBot / ClaudeBot / CCBot in `https://example-store.com/robots.txt`. Technical observation `{"undefined":["gptbot","claudebot","ccbot"]}`
llms.txt AI-LLMS-TXT	Pass	low	Technical observation `{"found":true,"contentType":"text/markdown"}`
First-HTML content density AI-SSR-CONTENT	Pass	medium	Technical observation `{"textBytes":4120,"htmlBytes":184210,"ratio":0.022}`
noindex check SEO-INDEXABLE	Pass	high	Technical observation `{"noindex":false}`
Sitemap reachability SEO-SITEMAP	Pass	medium	Technical observation `{"url":"https://example-store.com/sitemap.xml","urls":412}`
Structured data (JSON-LD) SEO-JSONLD	Fail	medium	Why it matters: without JSON-LD machines struggle to classify the page — lower odds of rich results and AI citations. How to fix: add Organization schema on the homepage and Product schema on product pages. Check guide → Verify yourself: search the source for `application/ld+json` — or paste the URL into validator.schema.org. Technical observation `{"jsonLdTypes":[]}`
Product schema SEO-PRODUCT-SCHEMA	Warn	medium	Why it matters: Product/Offer schema on product pages is missing or its fields are incomplete. How to fix: add a JSON-LD Product block to the theme template; verify with the rich-results test. Check guide → Verify yourself: test a product page with `search.google.com/test/rich-results` — a Product result should appear. Technical observation `{"hasProduct":false,"hasOffer":true}`
Title tag SEO-TITLE	Warn	medium	Why it matters: title is 89 characters — it gets truncated in the SERP; ideal is 30–60. How to fix: shorten it with the main keyword up front. Check guide → Verify yourself: check the `<title>` tag in the source — should be 30–60 characters and unique. Technical observation `{"title":"Example Store — Handmade Natural and Organic Home Textiles \| Free Shipping","len":89}`
Meta description SEO-META-DESC	Fail	medium	Why it matters: no meta description — Google picks the snippet itself, CTR drops. How to fix: add a unique 70–160 character description. Check guide → Verify yourself: search the source for `name="description"` — should hold a 70–160 character summary. Technical observation `{"metaDesc":null}`
H1 heading SEO-H1	Pass	low	Technical observation `{"h1Count":1}`
Canonical SEO-CANONICAL	Pass	low	Technical observation `{"canonical":"https://example-store.com/"}`
Open Graph cards SEO-OG-TAGS	Pass	low	Technical observation `{"og":["og:title","og:description","og:image","og:url"]}`
Mobile viewport SEO-VIEWPORT	Pass	low	Technical observation `{"viewport":"width=device-width,initial-scale=1"}`

Check

Result

Severity

Observation & fix

AI bot access — edge/WAF
AI-EDGE-PROBE

Fail

high

Why it matters: even when robots.txt allows bots, the edge layer can return 403 — AI visibility quietly dies without the owner knowing.
How to fix: in Cloudflare, turn off the AI bot block under Security → Bots, or add an allow rule for search bots.
Check guide →

Verify yourself:

curl -s -o /dev/null -w "%{http_code}" -A "OAI-SearchBot"
                https://example-store.com/

— if it returns 403/503 instead of 200, the block is at the edge.

Technical observation

{"probes":[{"bot":"googlebot","status":200},{"bot":"oai-searchbot","status":403},{"bot":"chatgpt-user","status":403},{"bot":"claudebot","status":200},{"bot":"perplexitybot","status":200}]}

robots.txt — AI search bots
AI-ROBOTS-SEARCH

Pass

high

Technical observation

{"blocked":[]}

robots.txt — AI training bots
AI-ROBOTS-TRAINING

Warn

low

Why it matters: no policy defined for GPTBot/ClaudeBot/CCBot — unclear whether that's a deliberate choice.
How to fix: add an explicit Allow or Disallow line for training bots in robots.txt; blocking is a legitimate licensing choice.
Check guide →

Verify yourself: look for an explicit policy line for GPTBot / ClaudeBot / CCBot in https://example-store.com/robots.txt.

Technical observation

{"undefined":["gptbot","claudebot","ccbot"]}

llms.txt
AI-LLMS-TXT

Pass

low

Technical observation

{"found":true,"contentType":"text/markdown"}

First-HTML content density
AI-SSR-CONTENT

Pass

medium

Technical observation

{"textBytes":4120,"htmlBytes":184210,"ratio":0.022}

noindex check
SEO-INDEXABLE

Pass

high

Technical observation

{"noindex":false}

Sitemap reachability
SEO-SITEMAP

Pass

medium

Technical observation

{"url":"https://example-store.com/sitemap.xml","urls":412}

Structured data (JSON-LD)
SEO-JSONLD

Fail

medium

Why it matters: without JSON-LD machines struggle to classify the page — lower odds of rich results and AI citations.
How to fix: add Organization schema on the homepage and Product schema on product pages.
Check guide →

Verify yourself: search the source for application/ld+json — or paste the URL into validator.schema.org.

Technical observation

{"jsonLdTypes":[]}

Product schema
SEO-PRODUCT-SCHEMA

Warn

medium

Why it matters: Product/Offer schema on product pages is missing or its fields are incomplete.
How to fix: add a JSON-LD Product block to the theme template; verify with the rich-results test.
Check guide →

Verify yourself: test a product page with search.google.com/test/rich-results — a Product result should appear.

Technical observation

{"hasProduct":false,"hasOffer":true}

Title tag
SEO-TITLE

Warn

medium

Why it matters: title is 89 characters — it gets truncated in the SERP; ideal is 30–60.
How to fix: shorten it with the main keyword up front.
Check guide →

Verify yourself: check the <title> tag in the source — should be 30–60 characters and unique.

Technical observation

{"title":"Example Store — Handmade Natural and
                Organic Home Textiles | Free
                Shipping","len":89}

Meta description
SEO-META-DESC

Fail

medium

Why it matters: no meta description — Google picks the snippet itself, CTR drops.
How to fix: add a unique 70–160 character description.
Check guide →

Verify yourself: search the source for name="description" — should hold a 70–160 character summary.

Technical observation

{"metaDesc":null}

H1 heading
SEO-H1

Pass

low

Technical observation

{"h1Count":1}

Canonical
SEO-CANONICAL

Pass

low

Technical observation

{"canonical":"https://example-store.com/"}

Open Graph cards
SEO-OG-TAGS

Pass

low

Technical observation

{"og":["og:title","og:description","og:image","og:url"]}

Mobile viewport
SEO-VIEWPORT

Pass

low

Technical observation

{"viewport":"width=device-width,initial-scale=1"}

Compliance checks (Shopify)

When a site is detected as Shopify, the report additionally includes the Turkish e-commerce compliance layer — pre-consent cookies/trackers, distance sales, KVKK, ETBİS, İYS.

Check	Result	Severity	Observation & fix
Pre-consent tracker requests TR-TRACKER-BEFORE-CONSENT	Fail	high	Why it matters: requests went out to 3 tracker domains before consent — pre-consent tracking is a technical violation. How to fix: enable the CMP's prior-consent blocking setting. Technical observation `{"trackerRequests":["www.google-analytics.com/g/collect","connect.facebook.net/tr/fbevents.js"]}`
Pre-consent cookie writes TR-COOKIE-NONESSENTIAL-BEFORE-CONSENT	Fail	high	Why it matters: 4 non-essential cookies were written before consent. How to fix: move cookie writes to after consent. Technical observation `{"beforeConsentCookies":["_ga","_fbp","_gid","_uetsid"]}`
ETBİS registration TR-ETBIS-REGISTRATION	Pass	high	Technical observation `{"registered":true}`
Distance sales contract TR-POLICY-DISTANCE-SALE	Pass	high	Technical observation `{"found":["https://example-store.com/pages/distance-sales"]}`

Check

Result

Severity

Observation & fix

Pre-consent tracker requests
TR-TRACKER-BEFORE-CONSENT

Fail

high

Why it matters: requests went out to 3 tracker domains before consent — pre-consent tracking is a technical violation.
How to fix: enable the CMP's prior-consent blocking setting.

Technical observation

{"trackerRequests":["www.google-analytics.com/g/collect","connect.facebook.net/tr/fbevents.js"]}

Pre-consent cookie writes
TR-COOKIE-NONESSENTIAL-BEFORE-CONSENT

Fail

high

Why it matters: 4 non-essential cookies were written before consent.
How to fix: move cookie writes to after consent.

Technical observation

{"beforeConsentCookies":["_ga","_fbp","_gid","_uetsid"]}

ETBİS registration
TR-ETBIS-REGISTRATION

Pass

high

Technical observation

{"registered":true}

Distance sales contract
TR-POLICY-DISTANCE-SALE

Pass

high

Technical observation

{"found":["https://example-store.com/pages/distance-sales"]}

Sample report — real scans list all 53 checks. This page is shortened for demonstration.

This scan is from the StoreCheckKit family

Compliance and AI visibility checks stay free — other checks live on the Shopify App Store:

PStoreCheck Promos

Test discount campaigns in a real cart before customers do.

Install on App Store MStoreCheck Markets

See currency and total glitches per country before your customers do.

Install on App Store RStoreCheck Reconcile

Reconciles iyzico payout reports against Shopify orders.

Coming soon