tpgtelecom.com.au — AI Site Grade

Analysis

---

The site's business-product pages — the pages most relevant to an AI engine researching TPG Telecom's B2B offerings — return 403 to every crawler including browsers, yet they are listed in the sitemap.xml and linked from the homepage.

Crawler Access

All major AI crawlers (GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, Bytespider, Applebot-Extended) receive a 200 with full HTML content on the homepage and all public pages. No UA-based blocking, no JS shell, no CDN/WAF interference. The site runs on Apache with Drupal 8 (PHP 7.4.33), served from an AWS EC2 instance (52.64.118.113) with no Cloudflare or other reverse proxy. However, the robots.txt is a stock Drupal template with zero AI-bot-specific rules — no User-agent: GPTBot or Disallow: for any AI crawler. The llms.txt returns 404.

Content & Schema Posture

The homepage contains zero JSON-LD schema of any type — no Organization, WebSite, BreadcrumbList, or FAQPage markup. The same is true across every page examined (about-us, our-brands, our-network, investor-relations, sustainability, executive-team). The site has no FAQ pages, no comparison tables, and no structured answer-format signals. The homepage H1 reads "Connecting Australia for the better" — a tagline that does not match the brand's actual market position (Australia's third-largest telco). The "Our Strategy" page is only 157 words and the "Our Network" page is 151 words — thin content for a top-100 ASX company.

Cold-Knowledge Gap

The LLM prior knows TPG Telecom as "Australia's third-largest telco behind Telstra and Optus," formed by the 2020 TPG-Vodafone merger, with brands including TPG, Vodafone, iiNet, Internode, and AAPT. The site itself never uses the phrase "third-largest" anywhere. It describes itself as "a top 100 ASX listed company" and "home to some of Australia's most-loved brands" — a softer positioning. The prior also recalls regulatory battles (2022 ACCC case) and customer service complaints; the site contains zero mention of any regulatory or reputational challenges. The site's media releases do cover the Triple Zero incident (November 2025) and a Vodafone-Telstra coverage dispute, but these are not surfaced in the cold knowledge.

Broken Business Pages

The sitemap.xml lists URLs like /business-solutions/enterprise-ethernet (404), /small-business/fast-reliable-business-broadband (403), and /enterprise/high-bandwidth-business-connectivity (403). These are the pages an AI engine would most want to retrieve when answering "what B2B services does TPG Telecom offer?" — and they are inaccessible to all crawlers and browsers alike. The 403 pages use canonical https://www.tpgtelecom.com.au/node/95, suggesting they are unpublished or access-restricted Drupal nodes that should have been removed from the sitemap. The /business-solutions/ directory appears to be a dead section of the site.

External Signals

The site has no external backlink profile visible through standard search — DuckDuckGo returns zero results for site-specific queries and brand-reputation queries. The only external links on the site point to its own consumer brand sites (vodafone.com.au, tpg.com.au, iinet.net.au) and LinkedIn. The DNS TXT records reveal integrations with Pardot, Salesforce, Oracle Cloud, Mimecast, and Mandrill — a marketing automation stack that is not reflected in any structured data on the public site.

Findings

1. Business product pages return 403 to all crawlers High

   Key B2B pages like /small-business/fast-reliable-business-broadband and /enterprise/high-bandwidth-business-connectivity return 403 Forbidden to all 11 tested bots, including browsers. These pages are listed in the sitemap and linked from the homepage, misleading crawlers.

   What to change: Remove these URLs from the sitemap and homepage links, or make them publicly accessible. If the pages are intentionally restricted, ensure they are not indexed.

2. Zero JSON-LD schema on any page High

   The homepage and all examined pages lack any JSON-LD structured data, including Organization, WebSite, BreadcrumbList, or FAQPage markup. This prevents AI engines from extracting entity information.

   What to change: Add Organization schema to the homepage with name, url, logo, and description. Add WebSite schema with searchAction. Add BreadcrumbList to interior pages.

3. Robots.txt has no AI-bot-specific rules Medium

   The robots.txt is a stock Drupal template with only generic User-agent: * rules. No AI crawlers (GPTBot, ClaudeBot, etc.) are explicitly allowed or disallowed, leaving their access to default behavior.

   What to change: Add explicit Allow rules for AI crawlers to key pages, or at minimum add a comment acknowledging them.

4. llms.txt file returns 404 Medium

   The site does not provide an llms.txt file, which is a recommended standard for AI crawlers to discover key content.

   What to change: Create an llms.txt file listing the most important pages for AI consumption, such as about, strategy, network, and investor relations.

5. Key pages have thin content Medium

   The 'Our Strategy' page contains only 157 words and 'Our Network' page 151 words. For a top-100 ASX company, these pages lack depth and detail, reducing their value for AI extraction.

   What to change: Expand these pages with more substantive content, including specific strategic initiatives, network details, and relevant data.

6. Site omits 'third-largest telco' positioning Medium

   The site never uses the phrase 'third-largest' to describe its market position, despite that being the most common LLM prior. The homepage tagline 'Connecting Australia for the better' is vague and does not convey the company's scale.

   What to change: Add a clear statement like 'Australia's third-largest telecommunications company' to the homepage and about page.

7. Enterprise Ethernet page returns 404 Medium

   The sitemap includes /business-solutions/enterprise-ethernet which returns a 404 error. This is a dead link that wastes crawler budget.

   What to change: Remove this URL from the sitemap and fix or redirect it to a relevant page.

8. No external backlink profile visible in search Medium

   DuckDuckGo returns zero results for site-specific queries and brand-reputation queries, indicating very low external visibility and backlink profile.

   What to change: Invest in SEO and PR to build backlinks from reputable sources. Ensure the site is indexed by major search engines.

9. No FAQ or comparison pages for AI answer extraction Low

   The site lacks FAQ pages, comparison tables, or any structured answer-format content that AI engines can easily extract for featured snippets or direct answers.

   What to change: Create FAQ pages for common questions about services, coverage, and plans. Use FAQPage schema.

10. Site omits regulatory and reputational context Low

    The site contains no mention of the 2022 ACCC case or customer service complaints, which are part of the LLM cold knowledge. This creates a gap between external perception and site content.

    What to change: Consider adding a corporate governance or regulatory compliance page that addresses these topics transparently.

What's working

• Homepage and public pages accessible to all AI crawlers — All major AI crawlers receive a 200 with full HTML content on the homepage and public pages. No UA-based blocking or JS shell issues.
• Sitemap.xml published with 80 URLs — The site has a sitemap.xml listing 80 URLs, which helps crawlers discover content.
• Executive team page with detailed biographies — The /about-us/our-executive-team page contains 788 words with detailed biographies of leadership, useful for entity extraction.
• Investor relations page with financial data — The investor relations page contains 567 words with financial highlights and links to reports, providing valuable structured information.
• Media releases page with recent news — The media release page contains 551 words covering recent events like the Triple Zero incident and Vodafone-Telstra dispute, providing timely content.
• Sustainability page with strategy overview — The sustainability page provides a 173-word overview of the company's sustainability strategy, a positive signal for ESG-conscious AI queries.
• Brands page lists all subsidiary brands — The /about-us/our-brands page lists TPG, Vodafone, iiNet, Internode, and AAPT, helping AI engines understand the corporate structure.
• DNS TXT records indicate marketing automation integrations — The DNS TXT records show integrations with Pardot, Salesforce, Oracle Cloud, Mimecast, and Mandrill, suggesting a sophisticated marketing stack that could be leveraged for structured data.