AI Site Grade
spendless.com.au — AI Site Grade
Spendless.com.au's entire product catalog is invisible to AI crawlers because every page returns zero visible text without JavaScript execution.
The site's JS-dependent rendering, combined with WAF blocks on ClaudeBot and GPTBot and a complete absence of structured data, makes it functionally invisible to the AI indexing ecosystem.
- Findings
- 10
- Evidence checks
- 28
- Completed
- 30 May 2026
Analysis
I have enough data now. Let me compile the audit.
Spendless.com.au — AI-Visibility Audit
The site's entire product catalog — homepage, category pages, sale pages, store locator — returns zero words of visible text to any HTTP client that does not execute JavaScript, meaning every AI crawler that gets past the WAF receives an empty shell. This is the single most consequential finding: the site is functionally invisible to the AI indexing ecosystem regardless of bot access policy.
Crawler Access
The robots.txt contains no AI-bot-specific rules — no mention of GPTBot, ClaudeBot, Google-Extended, PerplexityBot, or any other crawler. The wildcard (User-agent: *) rule disallows query-string URLs, checkout, customer account pages, and PHP files, but permits the homepage and category pages. However, compare_bot_access reveals that ClaudeBot and GPTBot receive HTTP 403 (blocked) while Google-Extended, OAI-SearchBot, PerplexityBot, ChatGPT-User, Bytespider, and Applebot-Extended all get HTTP 200 with the same byte payload as a browser. The blocking is not from robots.txt but from the edge infrastructure (Fastly CDN, based on X-Served-By and X-Cache headers) — likely a WAF rule targeting those specific user-agent strings. The site runs on Magento (evident from URL structure, X-Platform-Server header, and version1778041338 static asset path) behind Fastly. No llms.txt exists (404).
JS-Rendering Black Hole
Every product-facing page tested — homepage, women's, men's, sandals, sale, store locator — returns 0 words of extracted text from a plain GET. The <title> and <meta description> tags render server-side, but the <body> content is entirely populated by JavaScript. The only page that returns substantive text is /careers (957 words), which is a static content page. This means AI crawlers that do not execute JS (the vast majority) see a page with a title, a meta description, and zero product information, pricing, or inventory. The sitemap contains ~31,000 URLs across two sub-sitemaps, all pointing to JS-dependent pages that yield nothing to non-rendering crawlers.
Cold-Knowledge Gap
The LLM prior knows Spendless as "one of Australia's largest independent shoe retailers, with over 100 stores nationwide" — but the /careers page states 200+ stores and 1000+ employees, and the founding year is 1988. The cold knowledge underestimates store count by 2x and omits the founding year entirely. The model also references "house brands like 'Spendless' or 'Shoe Collection'" and "licensed kids' characters" — claims that cannot be verified from the site itself since no product pages render text. The site's own meta descriptions describe itself generically ("amazing range of Womens Shoes") without any distinctive brand positioning.
Schema & Structured Data
Zero JSON-LD schema of any type was found on any page tested — no Organization, WebSite, Product, BreadcrumbList, LocalBusiness, or FAQPage markup. The site has no canonical tags on any page tested. Despite having 200+ physical stores, there is no LocalBusiness or Store schema. The Zendesk help center contains FAQ content (e.g., "100 Day Everflex School Shoes Guarantee") that could be marked up as FAQPage but is not. The site has no og: Open Graph tags either.
External Signals
External search results for Spendless are surprisingly sparse — DuckDuckGo returned zero results for queries combining the brand name with "Australia", "reviews", "retailer", or "stores". The brand has active social media (Facebook, Instagram, Pinterest, YouTube, TikTok, LinkedIn) and uses Zendesk for customer support, but none of this off-domain content is linked back to the site in a way that search engines or AI crawlers can easily discover. The site's DNS is hosted on Fastly (Fastly IPs: 151.101.x.x) with DNSMadeEasy nameservers and Microsoft 365 for email.
Findings
All product pages render as empty JS shells with zero visible text High
Every product-facing page tested (homepage, category pages, sale pages, store locator) returns 0 words of extracted text from a plain GET. The body content is entirely populated by JavaScript, making the site invisible to AI crawlers that do not execute JS.
What to change: Implement server-side rendering (SSR) or dynamic rendering to serve HTML content to crawlers. Ensure product names, prices, descriptions, and inventory are visible in the initial HTML response.
ClaudeBot and GPTBot blocked by WAF despite robots.txt allowance High
ClaudeBot and GPTBot receive HTTP 403 responses from the edge infrastructure (Fastly CDN), likely due to WAF rules targeting those user-agent strings. Other AI crawlers (Google-Extended, OAI-SearchBot, PerplexityBot) are allowed.
What to change: Remove WAF rules that block ClaudeBot and GPTBot, or update them to allow these crawlers. Verify that robots.txt does not inadvertently disallow them.
No llms.txt file published Low
The site returns a 404 for /llms.txt, missing an opportunity to provide AI crawlers with a curated list of important URLs and context.
What to change: Create an llms.txt file at the root that lists key pages (homepage, category pages, about, careers) and provides a brief site description.
Zero JSON-LD structured data on any page High
No JSON-LD schema of any type was found on any tested page. Missing Organization, WebSite, Product, BreadcrumbList, LocalBusiness, and FAQPage markup. The site has 200+ physical stores but no LocalBusiness schema.
What to change: Add JSON-LD structured data across the site: Organization schema on the homepage, Product schema on product pages, BreadcrumbList on category pages, LocalBusiness schema referencing store locations, and FAQPage schema on the help center FAQ pages.
No canonical tags on any tested page Medium
None of the tested pages include a canonical link element, which can lead to duplicate content issues and dilute indexing signals.
What to change: Add self-referencing canonical tags to every page to consolidate indexing signals and prevent duplicate content issues.
No Open Graph tags on any tested page Low
The site lacks og:title, og:description, og:image, and other Open Graph meta tags, reducing shareability on social platforms and limiting visibility to social-media-based AI crawlers.
What to change: Add Open Graph tags (og:title, og:description, og:image, og:url) to all pages to improve social sharing and AI crawler understanding.
LLM cold knowledge underestimates store count and omits founding year Medium
The LLM prior states 'over 100 stores' while the careers page indicates 200+ stores. The founding year (1988) is absent from the prior. The site's own meta descriptions lack distinctive brand positioning.
What to change: Add Organization schema with founding date, number of stores, and a detailed description. Update meta descriptions to include key brand facts (e.g., '200+ stores across Australia, founded in 1988').
Near-zero external search results for the brand Medium
DuckDuckGo returned zero results for queries combining the brand name with 'Australia', 'reviews', 'retailer', or 'stores'. The brand has active social media but no backlinks from those platforms to the site are easily discoverable.
What to change: Improve off-site SEO by ensuring social media profiles link back to the site, encouraging customer reviews on third-party platforms, and building backlinks from relevant Australian retail directories.
Robots.txt lacks AI-bot-specific directives Low
The robots.txt file does not mention any AI crawler by name (GPTBot, ClaudeBot, Google-Extended, etc.), leaving their access to default rules. While the wildcard rule allows most pages, the lack of explicit guidance may lead to inconsistent crawling.
What to change: Add explicit directives for AI crawlers in robots.txt, e.g., allow GPTBot and ClaudeBot to access the site, and consider adding crawl-delay directives to manage load.
Zendesk FAQ content lacks FAQPage schema Low
The help center contains FAQ content (e.g., '100 Day Everflex School Shoes Guarantee') but no FAQPage structured data is present, missing an opportunity for rich results in AI-generated answers.
What to change: Add FAQPage JSON-LD schema to the help center FAQ pages, marking up each question and answer pair.
What's working
- Robots.txt allows crawling of homepage and category pages — The robots.txt file does not disallow the homepage or category pages, and the wildcard rule permits access to most content. This is a baseline positive for crawlers that are not blocked by the WAF.
- Sitemap published with ~31,000 URLs — The site has a sitemap index at /media/sitemap.xml containing two sub-sitemaps with approximately 31,000 URLs, providing a comprehensive list of pages for crawlers to discover.
- Careers page returns substantive text content — The /careers page returns 957 words of visible text, demonstrating that static content pages can be rendered server-side. This page provides useful context about the company (200+ stores, 1000+ employees, founded 1988).
- Zendesk help center is accessible and contains FAQ content — The help center at spendlessshoes.zendesk.com is accessible and contains FAQ categories (ORDER & DELIVERY INFORMATION, GENERAL QUERIES) with text content that could be leveraged for AI visibility.
- Site uses Fastly CDN for performance and security — The site is served via Fastly CDN, which provides edge caching and DDoS protection. This infrastructure can be leveraged for fast content delivery to crawlers if server-side rendering is implemented.
- Active social media profiles on multiple platforms — The brand has active profiles on Facebook, Instagram, Pinterest, YouTube, TikTok, and LinkedIn, providing channels for off-site visibility and potential backlinks.
Track spendless.com.au across AI search
This is one snapshot. Open the interactive report to inspect evidence, or grade another site free.