Chubbies
www.chubbiesshorts.comLast scanned Jun 20, 2026, 6:19 AM
Verdict
Open to AI agents
ARC Score v1.0
81/100Mostly open
Agent access50/50
Structured data18/25
Protocol files3/15
Scan stability10/10
Agent access
| Agent | Status | Source |
|---|---|---|
| GPTBot | Allowed | robots.txt: Allow |
| ChatGPT-User | Allowed | robots.txt: Allow |
| ClaudeBot | Allowed | robots.txt: Allow |
| Claude-Web | Allowed | robots.txt: Allow |
| PerplexityBot | Allowed | robots.txt: Allow |
| Google-Extended | Allowed | robots.txt: Allow |
| Amazonbot | Allowed | robots.txt: Allow |
| Bingbot | Allowed | robots.txt: Allow |
| CCBot | Allowed | robots.txt: Allow |
Infrastructure
PlatformmagentoCDNcloudflareWAFnone
Data signals
- JSON-LDDetected
- Schema.org ProductNot detected
- Open GraphYes
- Product feedYes
- llms.txtNo
Change history · last 90 days
0 changesNo confirmed changes in the last 90 days — this brand's agent access posture has been stable.
The free public window is 90 days. Multi-year history, watchlists, and change alerts are part of Pro.
Fix it with Claude Code
Each failed check below has a ready-made prompt tailored to this scan's findings. Run it in Claude Code from your site's repository.
✗No Schema.org Product markupshow prompt
My e-commerce site is chubbiesshorts.com. A scan found JSON-LD on the site but no Schema.org Product markup, so AI shopping agents can't reliably read our product names, prices, availability, or images. The site runs on magento, so prefer that platform's idiomatic way of serving these files/markup (theme templates, app settings, or metafields) over hand-rolled middleware where it exists. In this repository: 1. Find the product page template/component and add a JSON-LD <script type="application/ld+json"> block with Schema.org Product markup: name, description, image, sku, brand, and an Offer with price, priceCurrency, availability (use schema.org/InStock | OutOfStock), and url. Populate every field from our real product data — no placeholders. 2. Add an Organization JSON-LD block to the base layout (name, url, logo) if missing. 3. If we have category/listing pages, add ItemList markup referencing the product URLs. 4. Show me one fully rendered example of the JSON-LD for a real product, then validate the shape against Google's Rich Results requirements for Product and fix any warnings you can detect statically. Verify after deploy with https://search.google.com/test/rich-results on a product URL.
✗No llms.txtshow prompt
My e-commerce site is chubbiesshorts.com. We don't publish an llms.txt file yet — the emerging convention (llmstxt.org) that gives language models a concise, curated guide to a site. In this repository: 1. Create /llms.txt (served at https://chubbiesshorts.com/llms.txt as text/plain or text/markdown) following the llms.txt format: - H1 with our brand name, - a one-paragraph blockquote summary of what we sell and who we serve, - sections linking to our most useful pages for an AI agent: bestsellers/category pages, shipping & returns policy, size guides, FAQ/support, and store locator if any. 2. Write the summary from this repository's real content (README, about page, homepage copy) — keep it factual, no marketing superlatives. 3. Keep it under ~200 lines, every link absolute. 4. Show me the full file content and where you wired it to be served. Verify after deploy: curl https://chubbiesshorts.com/llms.txt
Embed this score
HTML
<a href="https://www.arcreport.ai/brand/chubbies"><img src="https://www.arcreport.ai/badge/chubbies.svg" alt="ARC Score for Chubbies" height="22"></a>
Markdown
[](https://www.arcreport.ai/brand/chubbies)
Updates automatically with each daily scan.