Magic Spoon
www.magicspoon.comLast scanned Jun 20, 2026, 6:19 AM
Verdict
Open to AI agents
ARC Score v1.0
86/100Open
Agent access50/50
Structured data14/25
Protocol files12/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.txtYes
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 magicspoon.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 sitemap.xmlshow prompt
My e-commerce site is magicspoon.com. A scan could not find a sitemap.xml, so crawlers and AI agents have no reliable way to discover our product pages. 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. Generate a sitemap.xml covering the homepage, category pages, and every product page, with <lastmod> from each product's updated-at where available.
2. If the catalog is large, split into a sitemap index with child sitemaps of ≤50,000 URLs.
3. Reference the sitemap from robots.txt ("Sitemap: https://magicspoon.com/sitemap.xml").
4. Make it regenerate automatically (build step or on-demand route) rather than a one-off static file, and show me the diff.Embed this score
HTML
<a href="https://www.arcreport.ai/brand/magic-spoon"><img src="https://www.arcreport.ai/badge/magic-spoon.svg" alt="ARC Score for Magic Spoon" height="22"></a>
Markdown
[](https://www.arcreport.ai/brand/magic-spoon)
Updates automatically with each daily scan.