reech.agency — AI Site Grade

Analysis

I have enough data to write the audit. Let me compile the findings.

Cold-Knowledge Gap

A frontier LLM queried cold about "Reech Agency" returned zero verifiable facts — no services, no awards, no clients, no location. The model explicitly stated it could not confirm the agency exists as a known entity. This is the central AI-visibility problem: the site is technically open to all crawlers, but the brand has virtually no footprint in the training data of the models that would cite it.

Crawler Access

Every major AI crawler — GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, Applebot-Extended, Bytespider — receives a 200 status with identical byte payload (190,370 bytes) as a browser. No UA-based blocking, no Cloudflare challenge, no JS shell. The robots.txt contains no AI-bot rules at all; only a generic Disallow: /wp-admin/ and a sitemap directive. The site runs on Cloudflare (DNS via chin.ns.cloudflare.com / mitch.ns.cloudflare.com) with PHP 8.2 and WordPress. An llms.txt exists at /llms.txt (200, 4,538 bytes) with a well-structured content map, AI guidance, and a note claiming all metrics are "verified as current for 2026." This is an unusually mature AI-readiness signal for a mid-size regional agency.

Schema Posture

The homepage and all subpages carry WebPage, WebSite, Organization, BreadcrumbList, and SearchAction schema via Yoast SEO. The homepage also embeds a FAQPage schema with five questions about services, location, Drum accreditation, B Corp status, and growth approach. However, no Article schema appears on blog posts, no CaseStudy or Product schema on results pages, and no LocalBusiness schema despite having a physical Shrewsbury address. The Organization schema uses the name "Reech Media" (the old brand name), while the site itself uses "Reech Agency" — a brand-name inconsistency in the structured data.

External Signals

Web searches for "Reech Agency" combined with "Shrewsbury," "The Drum recommended," "reviews," and "B Corp" returned zero results across multiple queries. The site claims a "9 rating on The Drum Recommends" and "Top 20 agencies outside of London," but no independent third-party pages corroborating these claims surfaced in search. The only external links found on the site are to Instagram, LinkedIn, WhatsApp, and a Google Maps directions URL. The brand has a near-zero off-domain citation footprint, which explains the cold-knowledge gap: LLMs have no training-data sources to draw from.

Content & Structure

The site is a well-designed WordPress build with 263+ indexed URLs across blog posts, case studies, solutions pages, and events. The homepage (867 words) uses clear H1/H2 hierarchy and an FAQ accordion. The /method/ page explains the "360 method" and "Spark" initiative. The /results/ page lists case studies with metrics (e.g., "400% increase in enquiries," "20% growth in organic clicks YoY"). The /insights-and-events/ page is noindexed (robots: noindex, nofollow), which hides the blog and event content from search engines entirely — a significant gap given the blog is the primary vehicle for topical authority signals.

Findings

1. Brand absent from LLM training data High

   A frontier LLM queried cold about 'Reech Agency' returned zero verifiable facts — no services, awards, clients, or location. The model explicitly stated it could not confirm the agency exists as a known entity.

   What to change: Build a strong off-domain citation footprint by earning mentions on reputable directories, industry publications, and review platforms. Publish authoritative content that LLMs can index and cite.

2. Near-zero off-domain citation footprint High

   Web searches for 'Reech Agency' combined with 'Shrewsbury,' 'The Drum recommended,' 'reviews,' and 'B Corp' returned zero results. The only external links found on the site are to Instagram, LinkedIn, WhatsApp, and a Google Maps directions URL.

   What to change: Earn backlinks and mentions from reputable local and industry directories, review platforms, and publications. Claim and verify profiles on Google Business Profile, The Drum Recommends, and B Corp directory.

3. Blog and events page noindexed High

   The /insights-and-events/ page is noindexed (robots: noindex, nofollow), hiding all blog and event content from search engines and AI crawlers. This eliminates a primary source of topical authority signals.

   What to change: Remove the noindex directive from the insights-and-events page and ensure individual blog posts are indexable.

4. Organization schema uses old brand name 'Reech Media' Medium

   The Organization schema on the homepage uses the name 'Reech Media' while the site itself uses 'Reech Agency'. This inconsistency can confuse AI parsers and dilute brand identity in structured data.

   What to change: Update the Organization schema name to 'Reech Agency' to match the site branding.

5. No LocalBusiness schema despite physical address Medium

   The site has a physical Shrewsbury address but does not include LocalBusiness schema. This reduces local AI visibility and the chance of being cited for location-based queries.

   What to change: Add LocalBusiness schema with the Shrewsbury address, phone number, and opening hours.

6. No Article schema on blog posts Medium

   Blog posts lack Article schema, which helps AI crawlers understand and cite content as news or articles. This limits the discoverability of the blog's topical authority.

   What to change: Add Article schema to all blog posts via Yoast SEO or custom implementation.

7. No CaseStudy or Product schema on results pages Medium

   The /results/ page lists case studies with metrics but lacks CaseStudy or Product schema. This prevents AI crawlers from extracting structured success stories.

   What to change: Add CaseStudy schema to each case study entry with properties for metrics, client name, and outcome.

8. Robots.txt lacks AI-bot directives Low

   The robots.txt file contains no rules for AI crawlers like GPTBot, ClaudeBot, or PerplexityBot. While this means they are allowed, it also means no guidance is provided for crawl rate or allowed paths.

   What to change: Add explicit allow/disallow rules for AI crawlers and consider setting a crawl-delay to manage load.

What's working

• llms.txt file with structured content map — The site hosts an llms.txt file (4,538 bytes) with a well-structured content map, AI guidance, and a note claiming all metrics are verified for 2026. This is an unusually mature AI-readiness signal for a mid-size regional agency.
• All major AI crawlers receive 200 status — Every major AI crawler (GPTBot, ClaudeBot, PerplexityBot, Google-Extended, etc.) receives a 200 status with the same HTML as a browser. No UA-based blocking or Cloudflare challenges are applied.
• FAQPage schema on homepage with five questions — The homepage embeds a FAQPage schema with five questions covering services, location, Drum accreditation, B Corp status, and growth approach. This helps AI assistants extract quick answers.
• Core schema types present via Yoast SEO — The homepage and subpages carry WebPage, WebSite, Organization, BreadcrumbList, and SearchAction schema via Yoast SEO, providing a solid structured data foundation.
• Well-structured content with clear H1/H2 hierarchy — The homepage (867 words) uses clear H1/H2 hierarchy and an FAQ accordion. The /method/ and /results/ pages provide detailed, metric-rich content that is easy for crawlers to parse.
• Sitemap with 80 URLs and index enabled — A sitemap is available with 80 URLs and index enabled, helping crawlers discover all pages efficiently.