acenda.com.au — AI Site Grade

Analysis

Excellent. Now I have a comprehensive picture. Let me write the audit.

Acenda.com.au — AI-Visibility Audit

The cold LLM knowledge about Acenda is entirely wrong: the model describes Acenda as a NobleOak direct-to-consumer digital insurer, when the site reveals Acenda is actually the post-merger brand for the former MLC Life Insurance, Resolution Life Australasia, and Asteron Life — a major institutional life insurer owned by Nippon Life with 2 million customers and 175+ years of combined heritage. This identity gap means every AI engine that retrieves cold knowledge will misrepresent the brand.

Crawler Access

All major AI crawlers — GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, Bytespider, Applebot-Extended — receive 200 status with full HTML content on the homepage, identical in byte size to a browser baseline (~60KB). No UA-based blocking, no JS shell, no WAF challenge. The robots.txt exists but contains only User-agent: * with no rules at all — no disallow, no allow, no AI-bot directives. The llms.txt returns 404. The sitemap at /sitemap.xml returns HTTP 500 with empty body, making it impossible for crawlers to discover the full site structure programmatically.

Schema Posture

Every page examined — homepage, about-us, how-insurance-works, support, acenda-group, guaranteed-income — contains zero JSON-LD schema of any type. No Organization, InsuranceProduct, FAQPage, WebSite, BreadcrumbList, or LocalBusiness markup. The only structured data signals are HTML meta tags (description, robots, Open Graph). For a financial services brand with multiple product lines (life insurance, TPD, income protection, critical illness, annuities), this is a critical gap for AI answer engines that rely on schema for entity extraction.

Cold-Knowledge Gap

The frontier model queried cold describes Acenda as "a specialist Australian insurer" that is "a brand of NobleOak" offering "term-based life cover" with "no medical exam policies" targeting "younger Australians." The actual site describes Acenda as the brand of the Acenda Group — formed in 2025 from the merger of MLC Life Insurance, Resolution Life Australasia, and Asteron Life, owned by Nippon Life (a Japanese giant with AU$990 billion in assets). The site serves 2 million customers through advisers, super funds, and employers — not direct-to-consumer digital sales. The NobleOak association is entirely absent from the site. The model also claims "positive customer feedback" and "efficient claims handling" as known facts, but no external review signals, Reddit threads, or press mentions were discoverable on the open web for this brand.

Content and Structure

The site has approximately 25 discoverable URLs, all server-rendered HTML with good visible text (200–680 words per page). Content is well-written educational insurance copy organized under /how-insurance-works/ (8 sub-pages), /using-your-insurance/ (3 sub-pages), and /acenda-group. However, the /support page is a thin JS-dependent gateway (42 words extracted) that requires a user to click "I am a Customer" or "I am an Adviser" — AI crawlers hitting this page get almost no content. The retirement page redirects from /retirement to /guaranteed-income and references Resolution Life as the product issuer, not Acenda, creating brand fragmentation. No FAQ schema, comparison tables, or answer-format signals exist anywhere on the site.

Findings

1. AI models fabricate Acenda's brand identity as a NobleOak digital insurer High

   Cold LLM knowledge describes Acenda as a NobleOak direct-to-consumer insurer, but the site reveals Acenda is the post-merger brand for MLC Life Insurance, Resolution Life Australasia, and Asteron Life, owned by Nippon Life with 2 million customers. This identity gap causes every AI engine to misrepresent the brand.

   What to change: Publish an llms.txt file with accurate brand description and entity definitions. Add Organization and InsuranceProduct schema to all pages to ground AI knowledge.

2. No JSON-LD schema on any page High

   Every page examined lacks any JSON-LD structured data. No Organization, InsuranceProduct, FAQPage, WebSite, or BreadcrumbList markup exists. For a financial services brand with multiple product lines, this is a critical gap for AI answer engines.

   What to change: Add JSON-LD schema for Organization, InsuranceProduct, WebSite, BreadcrumbList, and FAQPage across all relevant pages.

3. Sitemap returns HTTP 500 with empty body High

   The sitemap at /sitemap.xml returns a 500 error with an empty body, preventing crawlers from discovering the full site structure programmatically.

   What to change: Fix the sitemap generation to return a valid XML sitemap listing all public URLs.

4. llms.txt returns 404 High

   The llms.txt file, which provides AI crawlers with a curated overview of the site, returns a 404 error. This is a missed opportunity to correct the cold-knowledge gap.

   What to change: Create an llms.txt file with accurate brand description, key pages, and entity definitions.

5. Support page is a thin JS-dependent gateway Medium

   The /support page extracts only 42 words of visible text and requires user interaction (clicking 'I am a Customer' or 'I am an Adviser') to reveal content. AI crawlers receive almost no content from this page.

   What to change: Provide server-rendered content for both customer and adviser sections, or use progressive enhancement so crawlers see the full content.

6. Retirement page references Resolution Life, not Acenda Medium

   The /retirement page redirects to /guaranteed-income and references Resolution Life as the product issuer, creating brand fragmentation and confusing AI crawlers about the brand's product ownership.

   What to change: Update the retirement page to clearly brand the product under Acenda and add schema indicating the issuer relationship.

7. No external review signals or press mentions discoverable Medium

   Web searches for Acenda reviews, Reddit discussions, and press mentions returned zero results. The brand has no visible third-party validation, which limits AI trust signals.

   What to change: Encourage customer reviews on independent platforms and pursue press coverage to build external signals.

8. No FAQ schema or answer-format signals anywhere Medium

   The site lacks FAQPage schema, comparison tables, or any answer-format signals that AI engines use to extract direct answers. This limits the site's ability to appear in AI-generated answers.

   What to change: Add FAQPage schema to educational pages and create comparison tables with structured data.

9. Robots.txt has no AI-bot directives Low

   The robots.txt file contains only a User-agent: * rule with no disallow, allow, or AI-bot-specific directives. While this allows all crawlers, it misses the opportunity to guide AI bots to important pages.

   What to change: Add specific directives for AI bots, such as allowing access to key pages and disallowing thin or duplicate content.

What's working

• All major AI crawlers receive full HTML content — All tested AI crawlers (GPTBot, ClaudeBot, PerplexityBot, etc.) receive 200 status with full HTML content on the homepage, identical to a browser baseline. No UA-based blocking or JS shell issues.
• Pages are server-rendered with good visible text — All discovered pages are server-rendered HTML with 200–680 words of visible text, providing substantial content for AI crawlers to index.
• Well-organized educational content under clear paths — Content is organized under logical paths like /how-insurance-works/ and /using-your-insurance/, with educational copy that helps AI understand the site's domain.
• HTML meta tags provide basic SEO signals — Pages include meta description, robots, and Open Graph tags, providing basic structured signals for search engines and social previews.