DIAGNOSE
Platform / Technical & Schema
All of your product data,
readable
by machines.
Searchpanel parses every product page the way an engine does, validates the structured data field by field, and reports the markup, canonical, and llms.txt problems that stop a product from being read at all.
✓ Parsed like an engine
✓ Validated field by field
✓ Re-checked daily
Technical & Schema
tekzone.com/waine89-black
PRODUCT-V2 TEMPLATE
CHECKS
Product schema
VALID
gtin13
MISSING
aggregateRating
INVALID
Canonical
OK
llms.txt entry
MISSING
Specs as fields
PROSE ONLY
JSON-LD AS PARSED
{ “@type”: “Product”,
“name”: “Waine89 Wireless Headphones”,
“brand”: “Tekzone”,
“gtin13”: — missing
“aggregateRating”: {
“ratingValue”: “4.6 stars” not a number
},
“offers”: { “price”: 179 } }
3 fields broken
Gemini
✦
ChatGPT
✦

Copilot
✦
AI Overviews
✦

Claude
✦
WHAT WE CHECK
Everything that decides whether a machine can read you.
Product schema, review markup, canonical tags, index status, llms.txt, and machine-readable specifications, checked on every tracked product page.
“@type”: “Product”
“name”: “Waine89 Headphones”
“gtin13”: missing
Product schema
Whether a Product block exists, validates, and carries the fields engines need to match a SKU to a real item.
ratingValue
“4.6 stars”
reviewCount
1,284
FIX
ratingValue must be 4.6
Review markup
Whether your ratings are expressed as valid aggregateRating markup rather than text a parser has to guess at.
Canonical
/waine89-black ✓
Variant URL
/waine89?c=sand ✗
Indexed
Yes
Canonical and indexing
Which URL you declare as canonical, and whether the page is indexed on the surfaces engines draw from.
# Tekzone
- Waine89 Headphones
- Pulse Mini Earbuds
14 PRODUCTS LEFT OUT
llms.txt
Whether engines have a machine-readable file describing your catalogue, and which products it leaves out.
WRITTEN AS
“Up to fifty hours on a single charge”
NEEDS
batteryLife: 50 h
Machine-readable specs
Specifications written in prose that no parser can extract into a field an engine could filter on.
HOW A PAGE IS READ
Tools to help you see the page the way an engine does.
Every page is fetched, parsed, and validated field by field, so a technical problem is a specific broken line with a location rather than a warning icon on a dashboard.
WHAT AI SEES
See your page the way an engine parses it.
Every product page is fetched and parsed the way an engine does, so you see the fields it actually extracted rather than the page a browser renders for a person.
✓
Parsed from the live page
✓
Extracted field by field
✓
Set against what the answer needed
name
Waine89 Wireless…
✓
price
179 USD
✓
batteryLife
not extracted
✗ needed
weight
not extracted
✗ needed
gtin13
not extracted
✗ needed
ratingValue
“4.6 stars”
4.6
All 5
gtin13
missing
13 digits
Gemini, AIO
availability
“in stock”
InStock URL
ChatGPT, AIO
line 42 “ratingValue”: “4.6 stars”
fix “ratingValue”: 4.6
VALIDATION
See exactly which field is broken, and why.
Each error names the field, the value found on your page, the value the specification requires, and where it sits, so a fix is a line change rather than an investigation.
✓
The field and its location
✓
Found value against required
✓
Which engines it affects
CATALOGUE COVERAGE
See which products are readable, and which are not.
The same checks run across your whole catalogue, so a template problem shows up as a count rather than as the one product you happened to open.
✓
Counts across every tracked SKU
✓
Grouped by page template
✓
Movement since your last deploy
312 tracked products
▲ 41 PASSING SINCE DEPLOY
PRODUCT-V2 · 184
92%
PRODUCT-V1 · 96
41%
BUNDLE · 32
63%
!
PRODUCT-V1 drops gtin13 on all 96 pages. One template fix clears them all.
5×
average lift in AI visibility within the first 90 days.
+32%
higher conversion on AI referral traffic.
2,847
buyer prompts tracked per brand, every day.
CUSTOMER STORY

How Green Llama expanded visibility while scaling its product range.
Green Llama had a strong sustainability story, but it wasn’t translating into enough digital discovery. Searchpanel revealed where the brand was missing from AI-generated recommendations, which competitors were appearing more often, and which product-page signals needed improvement.
Mathew Keasey
Green Llama

PRODUCT VISIBILITY
+120%
▼ 25% wasted spend
CONVERSION RATE
+25%
across 26 new launches
SALES GROWTH
2 ×
quarter on quarter
FAQ
What does Technical and Schema check?
Product schema, review markup, canonical tags, index status, llms.txt, and whether your specifications are stated in a form a parser can extract into a field.
What is llms.txt?
Do you check schema on every product?
Does Searchpanel fix the problems for me?
Is this the same as an SEO site audit?
Do you check the words on my listing too?
How often is it re-checked?
revenue.
Find out which of your products AI names, which it ignores, and what it would take to change that.
Run a free audit
takes 2 minutes
No card needed · Cancel anytime · Read only, always