kubixmedia.co.uk — AI Site Grade

Analysis

The site is a Shopify Platinum agency that does not run on Shopify — it runs on Webflow — and has no llms.txt despite publishing a blog post about Shopify launching llms.txt.

Crawler Access

All major AI crawlers — GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, ChatGPT-User, anthropic-ai — receive a full 200 response with identical content to a browser (456 KB). Only Bytespider gets a 403 from Cloudflare. The robots.txt is minimal: a single User-agent: * rule disallowing /service-categories/, with no AI-bot-specific directives. The site is hosted on Webflow (Cloudflare DNS, proxy-ssl.webflow.com TXT record), not Shopify — an ironic infrastructure choice for a "Shopify Platinum Agency." The llms.txt returns a 404 (serving a Webflow 404 page). The sitemap at /sitemap.xml is healthy with 344 URLs.

Cold-Knowledge Gap

A frontier LLM queried cold about "Kubix Media" describes it as a general digital marketing and web development agency serving SMBs, mentions a proprietary "Kubix CMS," references mixed Trustpilot reviews, and places it in the "UK Digital Growth Awards" context. The actual site positions itself as a Shopify Platinum Agency (the highest Shopify partner tier) with enterprise clients including Ted Baker, Scotch & Soda, Castle Fine Art, OKA, and Haws Watering Cans. The cold model knows nothing about the Shopify Platinum status, the Ted Baker case study, the Pulse eCommerce Awards recognition, or the Birmingham HQ. The "Kubix CMS" the model hallucinated does not exist — the site exclusively builds on Shopify. The model's "mixed reviews" signal is untraceable: web searches for Kubix Media reviews on Trustpilot or elsewhere returned zero results, suggesting the model is conflating this brand with another entity.

Schema Posture

Only the homepage carries structured data — a single Organization schema with name, address, and social links. Every other page audited (about-us, case-studies, case-study/ted-baker, services/shopify-design-development, services/discovery, faqs) has zero JSON-LD. The blog posts that do have schema use BlogPosting with author and publisher data, but the service pages, case studies, and FAQ page — the pages most likely to be surfaced by AI answer engines — are entirely unmarked. The FAQ page is explicitly noindex-tagged, preventing it from appearing in search results at all.

External Signals

Web searches for "Kubix Media" plus "reviews," "Trustpilot," or "Shopify Platinum agency" returned zero indexed results from any external source. The only external validation visible is the Shopify Partner directory link (shopify.com/uk/plus/partners/kubix), Google Partner badge, and Klaviyo Master Platinum badge — all linked from the site itself. The Pulse eCommerce Awards "Highly Commended" mention (May 2026) has no external press coverage discoverable via search. The site lists ~90+ case studies on the portfolio page, but only a handful have dedicated detail pages with metrics.

Surprising Artifacts

The sitemap includes 10+ placeholder team pages at /team/blank-2, /team/blank-3, etc., all returning live pages titled "Blank-2 - Blank" with noindex tags. These are Webflow CMS draft entries published to the live sitemap. The blog post titled "Shopify Launches llms.txt" (May 2026) discusses the importance of llms.txt for AI discovery while the agency's own llms.txt returns a 404. The copyright footer reads "2023" despite content being actively published in 2026.

Findings

1. llms.txt returns 404 despite blog post advocating its use High

   The site's llms.txt returns a 404 error, contradicting a blog post that promotes llms.txt for AI discovery. This prevents AI crawlers from efficiently discovering key content.

   What to change: Publish an llms.txt file at the root that lists key pages (services, case studies, about, blog) with brief descriptions.

2. Service and case study pages lack any structured data High

   Pages like /services/shopify-design-development, /services/discovery, /case-studies, and /case-study/ted-baker have zero JSON-LD markup. These are the pages most likely to be cited by AI answer engines.

   What to change: Add Service, Product, and Article schema to service pages and case studies. Use FAQ schema on the FAQ page after removing the noindex tag.

3. LLMs describe Kubix Media as a generic digital marketing agency, not a Shopify Platinum Partner High

   A cold query to a frontier LLM returned a description of Kubix Media as a general digital marketing agency with a non-existent 'Kubix CMS', missing the Shopify Platinum status, enterprise clients (Ted Baker, Scotch & Soda), and Pulse eCommerce Awards recognition.

   What to change: Publish an llms.txt and add structured data (Organization, Service, Article) to reinforce the Shopify Platinum positioning. Build external backlinks from authoritative sources like Shopify partner directory and industry awards.

4. FAQ page is noindexed, blocking AI crawlers from surfacing answers High

   The FAQ page at /faqs contains 5277 words of question-answer content but has a noindex meta tag, preventing it from appearing in search results and AI answer engines.

   What to change: Remove the noindex tag from the FAQ page and add FAQPage schema to enable rich results.

5. Sitemap includes placeholder team pages with blank content Medium

   The sitemap contains 10+ URLs like /team/blank-2 that return live pages titled 'Blank-2 - Blank' with noindex tags. These are Webflow CMS drafts published to the live sitemap, wasting crawl budget.

   What to change: Remove placeholder team pages from the sitemap and either delete or properly populate them.

6. No external reviews or press coverage discoverable via search Medium

   Web searches for 'Kubix Media reviews', 'Trustpilot', and 'Shopify Platinum agency' returned zero results. The Pulse eCommerce Awards mention has no external press coverage. This limits third-party validation for AI models.

   What to change: Encourage clients to leave reviews on Google, Trustpilot, and Clutch. Issue press releases for awards and partnerships to generate indexed coverage.

7. Copyright footer reads 2023 despite 2026 content Low

   The site footer displays '© 2023 Kubix Media' while blog posts and awards are dated 2026. This may reduce trustworthiness for AI models and users.

   What to change: Update the copyright year to 2026 or use dynamic year rendering.

8. robots.txt disallows /service-categories/ without clear reason Low

   The robots.txt has a single rule disallowing /service-categories/ for all user agents. If this path contains useful content, it is blocked from AI crawlers.

   What to change: Review the /service-categories/ path and either remove the disallow or ensure it does not contain important content.

What's working

• All major AI crawlers receive full access with identical content — GPTBot, ClaudeBot, PerplexityBot, Google-Extended, and others get a 200 response with the same content as a browser. Only Bytespider is blocked by Cloudflare.
• Homepage includes Organization schema with name, address, and social links — The homepage has a single Organization JSON-LD block providing basic business information, which helps AI models correctly identify the entity.
• Blog posts use BlogPosting schema with author and publisher data — Blog articles include proper BlogPosting structured data, aiding AI crawlers in understanding article content and authorship.
• Sitemap is healthy with 344 URLs and no errors — The sitemap at /sitemap.xml returns 200 and contains 344 URLs, providing a comprehensive index for crawlers.
• Blog post discusses llms.txt importance for AI discovery — The article 'Shopify Launches llms.txt' shows awareness of AI visibility best practices, even though the site itself does not implement it.
• Case study detail pages include metrics and client logos — Pages like /case-study/ted-baker provide specific results and client branding, which can be used for rich snippets and AI citations.
• Cloudflare blocks Bytespider, preventing aggressive scraping — Bytespider receives a 403, which may protect against excessive crawling from a bot known for ignoring robots.txt.