angelcity.com — AI Site Grade

Analysis

Angel City FC — AI-Visibility Audit

The homepage delivers 10 words of visible text to AI crawlers despite all bots returning HTTP 200 — a JavaScript-rendering shell that leaves GPTBot, ClaudeBot, PerplexityBot, Google-Extended, and every other major AI crawler staring at an empty page.

Crawler Access

All 11 tested AI user-agents (GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, anthropic-ai, PerplexityBot, Perplexity-User, Google-Extended, Bytespider, Applebot-Extended, and a browser baseline) receive HTTP 200 with identical byte payloads (~460KB) from Cloudflare. No UA-based blocking exists. The robots.txt is a bare HubSpot default — it disallows only CMS preview and cache-buster paths, with zero AI-bot-specific rules. No llms.txt exists (404). The sitemap.xml is present and contains 1,456 URLs, but the homepage itself is a JS shell that yields almost no parseable content.

JS-Rendering Risk

The homepage, tickets page, and several other top-level pages render near-zero visible text from a plain GET. The homepage extracts only "Angel City FC 2024 Unisex Sol Jersey $95.00 SHOP NOW" — a single product card. The tickets page yields 17 words. Most AI crawlers do not execute JavaScript, meaning they see a <div id="app"> shell with no substantive content. Deeper pages like acfc-post/ articles (e.g., the roster announcement, SOAR internship) render full text and carry BlogPosting schema, but the highest-value pages — homepage, tickets, club info — are effectively invisible to AI crawlers.

Schema Posture

The site carries zero JSON-LD schema on the homepage, tickets page, roster page, or partners page. Only blog articles (/acfc-post/) include BlogPosting schema with author, publisher, and date fields. No SportsTeam, Organization, Event, FAQPage, Product, or BreadcrumbList schema exists anywhere. The tickets FAQ page has a rich Q&A structure (2,700+ words of natural FAQ content) but no FAQPage markup to signal this to AI engines.

Cold-Knowledge Gap

The LLM prior knows Angel City FC as an NWSL expansion team (2022) with a celebrity ownership group (Natalie Portman, Serena Williams, Eva Longoria), a progressive sponsorship model, and a 2023 toxic workplace culture scandal that led to leadership changes. The site itself contains zero mention of the ownership group, zero mention of the founding story, zero mention of the workplace controversy, and zero mention of the "equity" or "progressive business model" positioning that the model associates with the brand. The gap is stark: the model knows the brand for its celebrity founders and a reputational crisis; the site presents a generic sports-team template with tickets, roster, and partners.

External Signals

The site is built on HubSpot CMS behind Cloudflare (NS: cloudflare.com). Google Workspace handles email. No Wayback Machine snapshot exists for the homepage. External search for press coverage, Reddit threads, and reviews returned no results — the site has no discoverable off-domain citation footprint in the search results sampled, which is unusual for a major-market NWSL team with celebrity backing.

Findings

1. Homepage renders as empty JS shell to AI crawlers High

   The homepage delivers only 10 words of visible text to AI crawlers despite all bots returning HTTP 200. Most AI crawlers do not execute JavaScript, leaving them with a blank page.

   What to change: Implement server-side rendering (SSR) or static prerendering for the homepage and other key pages so AI crawlers receive meaningful HTML content.

2. Tickets page renders only 17 words to AI crawlers High

   The tickets page yields only 17 words of visible text from a plain GET, making it effectively invisible to AI crawlers that do not execute JavaScript.

   What to change: Apply SSR or static prerendering to the tickets page to expose ticket information and pricing to AI crawlers.

3. Homepage lacks any JSON-LD schema markup High

   The homepage carries zero JSON-LD schema, missing opportunities to signal SportsTeam, Organization, or Event data to AI engines.

   What to change: Add JSON-LD schema for SportsTeam, Organization, and upcoming events on the homepage.

4. Tickets and tickets FAQ pages lack schema markup High

   The tickets page and tickets FAQ page have no JSON-LD schema. The FAQ page contains 2,700+ words of natural Q&A content but no FAQPage markup.

   What to change: Add FAQPage schema to the tickets FAQ page and Event/Product schema to the tickets page.

5. Roster page lacks SportsTeam or Person schema Medium

   The roster page contains 850 words of player information but has no JSON-LD schema for SportsTeam or Person.

   What to change: Add SportsTeam and Person schema to the roster page to help AI engines understand team composition.

6. Partners page lacks Organization or Sponsor schema Medium

   The partners page lists sponsors but has no schema markup to signal organizational relationships.

   What to change: Add Organization or Sponsor schema to the partners page.

7. Site omits celebrity ownership and founding story Medium

   The site contains zero mention of the celebrity ownership group (Natalie Portman, Serena Williams, Eva Longoria) or the progressive sponsorship model that the LLM prior associates with the brand.

   What to change: Add an 'About' or 'Our Story' page detailing the founding, ownership, and mission of the club.

8. Site omits workplace culture controversy Medium

   The LLM prior knows about a 2023 toxic workplace culture scandal that led to leadership changes, but the site makes no mention of it or any subsequent reforms.

   What to change: Consider adding a page or statement addressing the club's commitment to workplace culture and any changes made.

9. No llms.txt file for AI crawler guidance Low

   The site returns a 404 for llms.txt, missing an opportunity to provide AI crawlers with a curated list of important pages and context.

   What to change: Create an llms.txt file listing key pages (homepage, roster, tickets, FAQ) and a brief description of the club.

10. Robots.txt has no AI-bot-specific rules Low

    The robots.txt is a bare HubSpot default with no directives for AI user-agents, leaving them unrestricted but also unguided.

    What to change: Add specific rules for AI bots to allow crawling of key pages and disallow low-value paths.

11. No discoverable off-domain citations in search results Medium

    Searches for press coverage, Reddit threads, and reviews returned no results, indicating a weak external signal footprint.

    What to change: Encourage media coverage, partnerships, and community engagement to build a stronger off-domain citation profile.

12. No Wayback Machine snapshot for homepage Low

    The Wayback Machine has no snapshot of the homepage, which may hinder historical context for AI models.

    What to change: Ensure the site is accessible to the Wayback Machine by allowing archive.org crawlers.

What's working

• All major AI crawlers receive HTTP 200 — All 11 tested AI user-agents receive HTTP 200 with no UA-based blocking, ensuring no crawler is outright denied access.
• Blog articles render full text and carry BlogPosting schema — Deeper pages like acfc-post/ articles render full text and include BlogPosting schema with author, publisher, and date fields.
• Sitemap.xml is present and contains 1,456 URLs — The sitemap.xml is accessible and lists a large number of URLs, aiding crawler discovery.
• Tickets FAQ page has rich natural Q&A content — The tickets FAQ page contains 2,700+ words of natural Q&A content, which is valuable for AI understanding if properly marked up.
• Roster page contains 850 words of player information — The roster page provides substantial text content about players, which is useful for AI crawlers that can parse it.
• Partners page lists sponsors with text content — The partners page contains 551 words listing sponsors, providing useful organizational information.
• Site uses Cloudflare for performance and security — Cloudflare provides CDN and DDoS protection, which helps with site reliability and performance.
• DNS records are well-configured with multiple records — The domain has multiple A, NS, and TXT records, indicating proper DNS setup.