axappphealthcare.co.uk — AI Site Grade

Analysis

Excellent. Now I have the full picture. Let me write the audit.

The domain axappphealthcare.co.uk is a dead redirect — it no longer hosts any content and silently forwards all traffic (including all AI crawlers) to www.axahealth.co.uk, but the redirect is invisible to most AI crawlers because the bare domain times out on HTTPS while HTTP succeeds, creating a fractured crawl path.

Crawler Access

The HTTPS version of axappphealthcare.co.uk (and www.axappphealthcare.co.uk) times out entirely for every AI bot tested — GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, and all others return status 0 with zero bytes. The HTTP version (port 80) does redirect to https://www.axahealth.co.uk/ with a 301/302 chain, but AI crawlers defaulting to HTTPS hit a dead end. The destination site (www.axahealth.co.uk) serves all AI bots a full 200 response with real content from Cloudflare — no UA-based blocking detected. However, the robots.txt on axahealth.co.uk contains zero AI-bot-specific rules; the wildcard User-agent: * blocks only /microsites/, /extranets2/, and CMS paths. No llms.txt exists (returns 404).

Cold-Knowledge Gap

The LLM knows AXA PPP Healthcare as a UK PMI provider founded in 1940 as PPP, acquired by AXA in 2008, with a strong cancer-care focus and a 2023 Financial Ombudsman criticism for poor claims handling. The live site at axahealth.co.uk has completely erased the "PPP" brand — no mention of PPP anywhere on the homepage, about page, or news section. The site brands itself solely as "AXA Health" and "AXA's health and wellbeing specialists." The cold model still references the old brand name and the Ombudsman controversy, neither of which the current site acknowledges or addresses. The site's "About us" timeline traces history back to 1940 but never names "PPP" — a deliberate omission that creates a gap between what AI engines recall and what the site presents.

Schema Posture

The homepage and key pages carry InsuranceAgency JSON-LD with full address, opening hours, and social profiles. The Product schema includes a Trustpilot Review with a 4.1 rating. The health insurance page adds FAQPage schema with five well-structured Q&A pairs. However, the schema @id values are empty strings ("") rather than absolute URLs, and the sameAs array still references twitter.com/AXAHealth (now X) and instagram.com/axahealth/ — correct for the new brand but the old AXAPPPhealth social handles from the Wayback snapshot are abandoned.

External Signals

The old AXAPPPhealth Twitter/X account and AXAPPP Facebook page are no longer active; the current site links to @AXAHealth and AXAHealth across all social platforms. Trustpilot reviews reference axahealth.co.uk, not the old domain. The news section shows active PR (2024-2025) under the AXA Health name only, with research reports on the sandwich generation, self-diagnosis, and workplace health — but none of these articles bridge the brand transition. The Wayback Machine shows the last snapshot of the old axappphealthcare.co.uk site was September 2020, meaning the domain has been a redirect shell for over four years with no content of its own.

Findings

1. HTTPS timeout on old domain — https://axappphealthcare.co.uk and https://www.axappphealthcare.co.uk both time out for all user-agents (status 0). AI crawlers that default to HTTPS never reach the redirect. Only HTTP (port 80) successfully forwards to axahealth.co.uk.

2. No AI-bot rules in robots.txt — The destination site's robots.txt has zero directives for GPTBot, ClaudeBot, PerplexityBot, Google-Extended, or any other AI crawler. They are implicitly allowed everywhere except CMS paths.

3. llms.txt missing — Returns a 404 error page. No AI-friendly content map exists.

4. Brand name erased from live site — The "PPP" heritage is completely absent from all crawled pages. The cold LLM still knows the brand as "AXA PPP Healthcare" and recalls the 2023 Ombudsman criticism, but the site offers no rebuttal or acknowledgment.

5. Empty @id values in JSON-LD — Schema @id fields are set to "" instead of absolute URLs, which can cause entity resolution issues for knowledge graphs.

6. Old social handles abandoned — The sameAs schema on the current site correctly points to @AXAHealth handles, but the Wayback snapshot shows the old brand used @AXAPPPhealth, AXAPPPhealthcare YouTube, and AXAPPP Facebook — all now dead or redirecting.

7. No redirect chain for HTTPS — The HTTPS endpoint on the old domain simply drops connections. This means any AI crawler or link graph pointing to https://axappphealthcare.co.uk (or any subpage) gets a connection timeout, not a 301 to the new site, losing link equity and brand continuity.

Findings

1. HTTPS timeout on old domain blocks AI crawlers High

   The HTTPS versions of axappphealthcare.co.uk and www.axappphealthcare.co.uk time out for all user-agents, including all AI bots tested. Only HTTP (port 80) successfully redirects to axahealth.co.uk, but AI crawlers defaulting to HTTPS never reach the redirect.

   What to change: Configure the HTTPS endpoint on axappphealthcare.co.uk to issue a 301 redirect to https://www.axahealth.co.uk/ instead of timing out.

2. No AI-bot rules in robots.txt on destination site Medium

   The robots.txt on axahealth.co.uk contains zero directives for GPTBot, ClaudeBot, PerplexityBot, Google-Extended, or any other AI crawler. They are implicitly allowed everywhere except CMS paths, but the lack of explicit rules means no crawl budget management or access restrictions for AI bots.

   What to change: Add explicit allow/disallow rules for AI crawlers in robots.txt to manage crawl budget and signal AI-friendly content.

3. llms.txt file missing on destination site Medium

   The llms.txt file at axahealth.co.uk returns a 404 error. No AI-friendly content map exists to guide language models to key pages.

   What to change: Create an llms.txt file listing key pages for AI consumption, such as health insurance, about us, and FAQ pages.

4. PPP brand heritage erased from live site Medium

   The live site at axahealth.co.uk makes no mention of the 'PPP' brand anywhere on the homepage, about page, or news section. The cold LLM still knows the brand as 'AXA PPP Healthcare' and recalls the 2023 Ombudsman criticism, but the site offers no acknowledgment or rebuttal, creating a gap between AI knowledge and site content.

   What to change: Add a section on the about page or a dedicated page explaining the brand transition from AXA PPP to AXA Health, addressing the heritage and any past controversies.

5. Empty @id values in JSON-LD schema Low

   The JSON-LD schema on the homepage and key pages contains empty @id fields ("") instead of absolute URLs, which can cause entity resolution issues for knowledge graphs.

   What to change: Populate @id fields with absolute URLs (e.g., https://www.axahealth.co.uk/#organization) to improve entity resolution.

6. Old social handles abandoned and not redirected Low

   The old brand used social handles @AXAPPPhealth, AXAPPPhealthcare YouTube, and AXAPPP Facebook, all now dead or redirecting. The current site's sameAs schema correctly points to @AXAHealth handles, but the old handles are not redirected, losing social signals.

   What to change: Set up redirects from old social handles to the new ones, or at least post a final message directing followers to the new accounts.

7. No redirect chain for HTTPS on old domain High

   The HTTPS endpoint on axappphealthcare.co.uk drops connections instead of issuing a 301 redirect. Any AI crawler or link graph pointing to https://axappphealthcare.co.uk gets a connection timeout, losing link equity and brand continuity.

   What to change: Implement a 301 redirect from https://axappphealthcare.co.uk to https://www.axahealth.co.uk/ to preserve link equity.

What's working

• Destination site serves all AI bots with full content — The destination site www.axahealth.co.uk serves all 11 AI bots tested a full 200 response with real content from Cloudflare, with no UA-based blocking detected.
• JSON-LD schema present on homepage and key pages — The homepage and health insurance page carry InsuranceAgency and Product JSON-LD with full address, opening hours, social profiles, and a Trustpilot review with 4.1 rating.
• FAQPage schema on health insurance page — The health insurance page includes FAQPage schema with five well-structured Q&A pairs, which can be used by AI assistants to answer common questions.
• Active news section with recent PR content — The news section shows active PR from 2024-2025 under the AXA Health name, with research reports and articles that can serve as fresh content for AI indexing.
• SameAs schema points to current social handles — The sameAs array in JSON-LD correctly references @AXAHealth on Twitter/X and axahealth on Instagram, matching the current brand identity.