ethixbase360.com — AI Site Grade

Analysis

Ethixbase360's homepage and product pages serve rich, server-rendered HTML that all major AI crawlers (GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, ChatGPT-User) receive as full 200-byte-identical responses — yet the cold-knowledge model hallucinates a fundamentally different corporate history, including a fictional acquisition of "360factors" and "iComply" that never happened.

Crawler Access

All eleven AI bots tested return 200 with identical byte size (222,966 bytes) to the browser baseline. No UA-based blocking exists. The site runs on Cloudflare (CDN) with WP Engine hosting, serving fully server-rendered WordPress pages — no JS-rendering risk for AI crawlers. The robots.txt is a bare Yoast-generated file with a User-agent: * allow-all rule and no AI-bot-specific directives whatsoever. llms.txt returns a 404 — no AI content map exists. The sitemap (sitemap_index.xml) is present with 5 sub-sitemaps covering ~450+ URLs, well-structured.

Cold-Knowledge Gap

Asked cold, the LLM describes Ethixbase360 as founded in 2015 as "Ethixbase," headquartered in Singapore with offices in London, Dubai, and Austin, and claims it acquired 360factors (a GRC firm) in 2021 and iComply in 2021. The actual site tells a different story: the company is headquartered in London, UK (all press releases cite London), was originally called Ethixbase (no "360"), and acquired Tcompliance (formerly TRACE Inc.) in 2022 — not 360factors or iComply. The current CEO is Simon Wardle (appointed after Peter Sweetbaum, who succeeded Leas Bachatene in 2023), but the cold model lists no current CEO. The model also claims pricing starts in the "tens of thousands" — the site lists no pricing at all (marked as "Pricing on request"). The model names product lines ("Ethixbase360 Diligence," "Ethixbase360 Monitor") that do not appear anywhere on the actual site, which uses different product naming (Platform, Questionnaires, Risk-Based Due Diligence, Tcertification, TRAC).

Schema Posture

The homepage carries a minimal Organization schema with zero sameAs links — no LinkedIn, no Twitter, no G2 profile. The product pages (/product/platform/, /product/risk-based-due-diligence/, /product/independent-third-party-certification/) are stronger, carrying SoftwareApplication and Service schemas with detailed featureList, knowsAbout arrays (covering 18+ regulatory frameworks), and FAQPage markup. However, the About page (/about-us/) has no schema at all — no Organization, no Person schema for the six named executives. The Organization schema on the homepage lists sameAs: [] (empty array), which is functionally equivalent to having no social profile links in structured data.

External Signals

The site prominently displays G2 reviews (six embedded testimonials with named reviewers and company sizes) and links to its G2 profile, but the G2 page was not returned by search. The only external link in the Organization schema is LinkedIn. The site references customer logos including Pfizer, H&M, Unilever (on the About page meta description) and case studies for Mitsubishi Electric, Japan Aerospace Corp, Anglicare, and New Forests. Press releases reference a PR Newswire distribution. The DNS TXT records show HubSpot, Salesforce, Zendesk, and Paubox integrations — a typical enterprise SaaS stack. No negative press or scandals surfaced.

Surprising Details

The URL /product/tcert/ redirects to /product/independent-third-party-certification/ — a canonical redirect that is fine, but the old path remains in the sitemap and navigation. The blog is active and current (2026 posts referencing Anthropic, Epstein case, Iran conflict), suggesting strong content velocity. The site uses Yoast SEO Premium but the homepage Organization schema is missing critical fields (no logo URL in the homepage schema, though the logo URL exists in product page schemas). The knowsAbout array on product pages is impressively comprehensive (18 regulatory frameworks) but is only attached to the Organization node, not surfaced as SoftwareApplication keywords — a missed opportunity for AI crawlers indexing the product specifically.

Findings

1. Cold-knowledge model hallucinates fictional acquisitions and product lines High

   The LLM cold-knowledge response describes Ethixbase360 as having acquired 360factors and iComply, neither of which occurred; the actual acquisition was Tcompliance in 2022. The model also invents product names like 'Ethixbase360 Diligence' and 'Ethixbase360 Monitor' that do not appear on the site.

   What to change: Publish a comprehensive llms.txt file and enrich the site's structured data with accurate corporate history, acquisitions, and product names to ground AI models.

2. No llms.txt file published High

   The site returns a 404 for llms.txt, meaning there is no AI content map to guide language models to key pages and facts.

   What to change: Create an llms.txt file listing the most important pages (homepage, product pages, about, press releases) and key facts about the company.

3. Homepage Organization schema has empty sameAs array Medium

   The Organization schema on the homepage includes a sameAs field set to an empty array, providing no social profile links (LinkedIn, Twitter, G2) in structured data.

   What to change: Populate the sameAs array with URLs to the company's LinkedIn, Twitter, G2, and other official profiles.

4. About page lacks any structured data Medium

   The /about-us/ page has no Organization or Person schema, missing an opportunity to provide entity information for six named executives.

   What to change: Add Organization schema with founding date, headquarters, and Person schema for each executive listed on the page.

5. Homepage Organization schema missing logo URL Low

   The homepage Organization schema does not include a logo property, though product page schemas do reference a logo URL.

   What to change: Add the logo URL to the homepage Organization schema.

6. Regulatory framework keywords attached to Organization, not SoftwareApplication Medium

   The knowsAbout array listing 18 regulatory frameworks is placed on the Organization node, not on the SoftwareApplication schema for product pages, reducing relevance for AI crawlers indexing the product.

   What to change: Move or duplicate the knowsAbout array onto the SoftwareApplication schema for each product page.

7. Sitemap includes redirected URL /product/tcert/ Low

   The URL /product/tcert/ redirects to /product/independent-third-party-certification/ but remains in the sitemap and navigation, which may confuse crawlers.

   What to change: Remove the redirected URL from the sitemap and update internal navigation to point directly to the canonical URL.

8. No pricing information on site Low

   The site lists 'Pricing on request' and provides no pricing details, which the cold model hallucinates as 'tens of thousands'.

   What to change: Consider publishing indicative pricing tiers or a pricing page to ground AI models.

What's working

• All major AI crawlers receive full server-rendered HTML — Eleven AI bots tested return 200 with identical byte size to the browser baseline, with no UA-based blocking. The site uses server-rendered WordPress pages, eliminating JS-rendering risk.
• Robots.txt allows all bots with no AI-specific restrictions — The robots.txt file has a User-agent: * allow-all rule and no AI-bot-specific disallow directives, ensuring maximum crawler access.
• Well-structured sitemap with 5 sub-sitemaps covering 450+ URLs — The sitemap_index.xml is present and well-organized, helping crawlers discover all pages.
• Product pages carry detailed SoftwareApplication and Service schemas — Product pages like /product/platform/ include SoftwareApplication and Service schemas with featureList, knowsAbout (18 regulatory frameworks), and FAQPage markup.
• Active blog with current posts covering relevant topics — The blog is regularly updated with posts referencing current events (Anthropic, Epstein case, Iran conflict), demonstrating content velocity.
• G2 reviews prominently displayed on site — The site embeds six G2 testimonials with named reviewers and company sizes, providing social proof and external signals.
• DNS TXT records show enterprise SaaS integrations — TXT records indicate HubSpot, Salesforce, Zendesk, and Paubox integrations, typical of a credible enterprise software company.