pixelbuilders.com — AI Site Grade

Analysis

Pixelbuilders.com — AI-Visibility Audit

The cold-knowledge model describes Pixelbuilders as a "WordPress agency for SMEs" — but the site has never mentioned WordPress and serves enterprise clients like The Access Group, AG Barr, and The QHotels Collection on Umbraco and Kentico. This is the single largest AI-visibility gap: the brand's actual positioning is completely invisible to frontier models without live retrieval.

Crawler Access

All major AI crawlers (GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, Bytespider, Applebot-Extended) receive 200 status with identical byte payloads to browser traffic. Cloudflare sits in front but does not UA-block any AI bot. The robots.txt is a bare catch-all (User-agent: *) with only two disallow rules (/umbraco/ and a contractor-stockists path) and no AI-bot-specific directives. The /llms.txt returns 404 — no AI-friendly content map exists. The sitemap lives at /sitemap/ (not /sitemap.xml), which is non-standard but functional, listing 142 URLs.

Cold-Knowledge Gap

The LLM prior (no retrieval) states Pixelbuilders builds "custom WordPress websites" for "SMEs in Leeds and Yorkshire." The actual site: zero mentions of WordPress, Umbraco Platinum Partner status, Kentico Bronze Partner, clients like Everyday Blinds (national B2C ecommerce), The Access Group (enterprise SaaS), and AG Barr (FTSE-listed). The model also claims "no high-profile awards" — the site lists Winner: Best Agency Team (Small) at the National Digital Awards 2026 and multiple 2026 shortlists. The agency was founded in 2008 (notably absent from the cold knowledge) and employs 18 people.

Schema Posture

Only the homepage carries structured data — a minimal Organization schema with name, email, and phone. No LocalBusiness, no Service types, no FAQPage, no BreadcrumbList, no ItemList for the portfolio. Blog posts use NewsArticle schema with author and datePublished, which is correct. The work/portfolio pages, expertise pages, and agency pages have zero JSON-LD. The /work/ portfolio listing page returns only 52 words of visible text — it loads project cards via JavaScript, making it thin for crawlers despite the full HTML payload being present.

External Signals

The site has a near-zero external search footprint. DuckDuckGo searches for "Pixelbuilders" returned zero indexed results. No review sites, no press mentions, no Reddit threads surfaced. The brand's external authority relies entirely on its own domain and social profiles (Facebook, LinkedIn, Instagram, X, YouTube, TikTok). The Wayback Machine shows a snapshot from March 2026, confirming the site is live and current, but the lack of third-party citations means AI engines have almost no corroborating signals to cite.

Findings

1. Cold-knowledge profile describes Pixelbuilders as a WordPress SME agency, contradicting actual Umbraco/Kentico enterprise focus High

   Frontier LLMs without retrieval describe Pixelbuilders as a 'WordPress agency for SMEs' in Leeds, but the site never mentions WordPress and serves enterprise clients like The Access Group, AG Barr, and The QHotels Collection on Umbraco and Kentico. The brand's actual positioning is completely invisible to AI models.

   What to change: Publish an llms.txt file at /llms.txt with a factual summary of the agency's positioning, client base, and technology stack. Add structured data (Organization, Service) to key pages to reinforce the correct narrative.

2. No llms.txt file published, missing opportunity to guide AI crawlers High

   The /llms.txt endpoint returns a 404 error. This file would allow the site to provide a curated summary of its content for AI crawlers, helping correct the cold-knowledge gap.

   What to change: Create an llms.txt file at /llms.txt containing a brief overview of the agency, key pages, and technology stack.

3. Near-zero external search footprint with no indexed results on DuckDuckGo High

   Multiple web searches for 'Pixelbuilders' and related terms returned zero results. No review sites, press mentions, or third-party citations exist, meaning AI engines have no corroborating signals to cite.

   What to change: Invest in PR, guest posting, and directory listings to build external citations. Encourage client testimonials on third-party platforms.

4. Only homepage has structured data; portfolio, expertise, and agency pages lack JSON-LD High

   The homepage carries a minimal Organization schema. No LocalBusiness, Service, FAQPage, BreadcrumbList, or ItemList schema exists on portfolio, expertise, or agency pages. Blog posts correctly use NewsArticle schema.

   What to change: Add JSON-LD structured data (Organization, LocalBusiness, Service, ItemList) to all key pages, especially the portfolio listing and individual work pages.

5. Portfolio listing page has only 52 words of visible text, relying on JavaScript for project cards Medium

   The /work/ page returns only 52 words of visible text. Project cards are loaded via JavaScript, making the page content-thin for crawlers despite the full HTML payload being present.

   What to change: Include project titles and descriptions in the initial HTML to ensure crawlers can index portfolio content without JavaScript execution.

6. Sitemap located at /sitemap/ instead of standard /sitemap.xml Low

   The sitemap lives at /sitemap/ (a directory) rather than the conventional /sitemap.xml. While functional, this non-standard location may reduce discoverability by some crawlers.

   What to change: Add a symlink or redirect from /sitemap.xml to /sitemap/ to follow convention.

7. Awards and notable clients not mentioned in structured data or prominent page content Medium

   The site lists 'Winner: Best Agency Team (Small) at the National Digital Awards 2026' and clients like The Access Group, AG Barr, and The QHotels Collection, but these are not included in structured data or prominently featured on the homepage.

   What to change: Add award and client information to the Organization schema and consider featuring them more prominently on the homepage.

8. Robots.txt has no AI-bot-specific directives, missing opportunity to guide crawlers Low

   The robots.txt is a bare catch-all with only two disallow rules and no AI-bot-specific directives. While not blocking any bots, it does not provide guidance to AI crawlers about which content to prioritize.

   What to change: Add AI-bot-specific directives to robots.txt, such as allowing all AI bots and optionally pointing to the llms.txt file.

What's working

• All major AI crawlers receive full access with identical content to browser traffic — All tested AI crawlers (GPTBot, ClaudeBot, PerplexityBot, etc.) receive 200 status with identical byte payloads to browser traffic. Cloudflare does not UA-block any AI bot.
• Blog posts correctly implement NewsArticle schema with author and datePublished — Blog posts use NewsArticle structured data with author and datePublished properties, which is correct and helps AI crawlers understand content.
• Sitemap is functional and lists 142 URLs despite non-standard location — The sitemap at /sitemap/ returns 200 status and lists 142 URLs, ensuring crawlers can discover site content.
• Key pages like Umbraco agency page and blog posts contain substantial text content — Pages such as /agency/umbraco/ (1178 words) and blog posts (1022 words) provide rich, crawlable content that helps AI understand the agency's expertise.
• Cloudflare provides security without blocking AI crawlers — Cloudflare sits in front of the site but does not UA-block any AI bot, balancing security with accessibility.