luxeo.team — AI Site Grade

Analysis

Luxeo.team: An SEO Agency Whose Own Site Has a Broken Sitemap, No Robots.txt, and Vanishing Blog Posts

The site's sitemap.xml returns a full HTML WordPress page (497KB of CSS/JS) instead of XML — meaning search engines and AI crawlers cannot discover the site's URL structure through the standard protocol.

Crawler Access

All 11 AI bots tested (GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, ChatGPT-User, Bytespider, Applebot-Extended, anthropic-ai, Perplexity-User, and a browser baseline) receive 200 OK with identical 625KB payloads from Cloudflare. No UA-based blocking exists. However, robots.txt at /robots.txt does not serve a robots file — it redirects internally to the blog listing page (title: "SEO Blog | Articles & SEO Cases"), meaning no crawler directives of any kind are published. The llms.txt file exists and is well-structured with 30+ curated links across English, Russian, and Ukrainian content — a rare and forward-looking asset.

Broken Content Architecture

Individual blog post URLs that are listed in llms.txt (e.g., /how-often-does-chatgpt-update-its-information-sources/, /the-real-meaning-of-the-llms-txt-file-for-llm-systems/) redirect to the blog listing page rather than serving the article content. Only case study URLs (e.g., /seo-for-a-crypto-exchanger-the-lets-exchange-case-traffic-increased-by-130-times/) and some guide URLs (e.g., /on-page-seo-factors/, /best-fractional-ctos/) resolve to actual content. The /about-us/ page also redirects to the blog. This means roughly half the URLs in llms.txt point to dead-end redirects — an AI crawler following those links gets the blog index, not the promised article.

Cold-Knowledge Gap

A frontier LLM queried cold about "Luxeo Team SEO outsourcing" returned: "I do not have specific, verifiable information about a company called Luxeo Team... It is possible this is a very small, local, or newly formed business." The site itself claims 6+ years of operation, 300+ projects, clients like Luxoft and Proofy, and a 4.9 rating from 108+ reviews. The gap between the brand's self-presentation and what AI models know about it cold is near-total. The site's blog contains an extensive series of "Independent AI Response Tests" (10 experiments on ChatGPT output, llms.txt efficacy, AI Overview behavior) — content that should make the brand highly discoverable to LLMs, but the broken URL structure undermines that.

Schema and External Signals

The homepage has Organization schema with two addresses (Kyiv, Ukraine and Liverpool, UK), social profiles, and contact details. Case study pages have Article schema with AggregateRating (ratings of 4.8-5.0). However, the AggregateRating schema uses itemReviewed of type Book rather than Article or Service — a semantic mismatch. External review platforms (Clutch, Goodfirms, DesignRush) are linked in the footer but return 403 errors when accessed directly. No external press, Reddit threads, or independent reviews surfaced in search — the brand's off-domain footprint is minimal.

Findings

1. Sitemap returns HTML instead of XML High

   The sitemap.xml URL returns a full HTML WordPress page (497KB of CSS/JS) instead of valid XML, preventing search engines and AI crawlers from discovering the site's URL structure.

   What to change: Replace the sitemap.xml endpoint with a properly generated XML sitemap that lists all canonical URLs.

2. Robots.txt serves blog page instead of directives High

   The /robots.txt URL returns the blog listing page (title: 'SEO Blog | Articles & SEO Cases') rather than a robots.txt file, meaning no crawler directives are published.

   What to change: Serve a proper robots.txt file with directives for all crawlers, including AI bots.

3. Blog posts listed in llms.txt redirect to blog index High

   Individual blog post URLs such as /how-often-does-chatgpt-update-its-information-sources/ and /the-real-meaning-of-the-llms-txt-file-for-llm-systems/ redirect to the blog listing page instead of serving the article content, making them inaccessible to AI crawlers.

   What to change: Ensure each blog post URL serves its unique content and does not redirect to the blog index.

4. About Us page redirects to blog Medium

   The /about-us/ page redirects to the blog listing page, preventing crawlers and users from accessing company information.

   What to change: Restore the About Us page to serve its intended content.

5. Frontier LLM has no knowledge of Luxeo Team High

   A cold query to a frontier LLM returned no verifiable information about Luxeo Team, despite the site claiming 6+ years of operation and 300+ projects. The brand is effectively invisible to AI models.

   What to change: Improve AI visibility by fixing the sitemap, robots.txt, and blog redirects, and by building external signals such as reviews and press mentions.

6. AggregateRating schema uses incorrect itemReviewed type Medium

   Case study pages use AggregateRating schema with itemReviewed of type Book instead of Article or Service, which may confuse AI parsers and reduce schema effectiveness.

   What to change: Change the itemReviewed type in AggregateRating schema from Book to Article or Service.

7. External review platforms return 403 errors Medium

   Links to Clutch and Goodfirms profiles in the footer return 403 errors when accessed, indicating the profiles may be blocked or non-existent, undermining trust signals.

   What to change: Ensure external review profiles are publicly accessible and linked correctly.

8. Minimal off-domain presence and no independent reviews Medium

   Web searches for Luxeo Team reviews on Clutch, Goodfirms, and general web returned zero results, indicating a lack of external signals such as press, reviews, or backlinks.

   What to change: Build external signals by earning reviews on reputable platforms, publishing guest posts, and engaging in industry forums.

9. Sitemap URL not referenced in robots.txt Low

   Since robots.txt is non-functional, the sitemap URL is not declared, further hindering crawler discovery.

   What to change: Include a Sitemap directive in the robots.txt file pointing to the correct XML sitemap.

What's working

• Well-structured llms.txt with 30+ curated links — The site hosts a comprehensive llms.txt file with curated links across English, Russian, and Ukrainian content, a forward-looking asset for AI discoverability.
• All 11 AI bots receive 200 OK with no blocking — No AI bot is blocked by user-agent rules or server configuration; all receive full content, ensuring baseline access.
• Organization schema present on homepage — The homepage includes Organization schema with addresses, social profiles, and contact details, aiding AI understanding of the business.
• Case study pages have Article schema with ratings — Case study pages include Article schema and AggregateRating, providing structured data for AI parsers despite the type mismatch.
• Blog contains extensive content on AI visibility topics — The blog features a series of 'Independent AI Response Tests' covering ChatGPT output, llms.txt efficacy, and AI Overview behavior, positioning the site as a knowledgeable resource.