sydneysymphony.com — AI Site Grade

Analysis

The robots.txt contains commented-out AI-bot block rules that are not enforced — every major AI crawler receives a full 200 with identical content to a browser, yet the site has no llms.txt, no Organization or MusicGroup schema, and the cold-knowledge model already knows more about the orchestra's history and controversies than the site itself communicates.

Crawler Access

All eleven tested AI bots (GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, ChatGPT-User, anthropic-ai, Bytespider, Applebot-Extended, Perplexity-User) receive a 200 OK with identical 341KB payload as a browser. No UA-based blocking, no JS-gating, no Cloudflare challenge. The robots.txt has AI-bot Disallow: / rules commented out — they exist only as inert comments. The Crawl-delay: 1 directive is the only active AI-relevant rule. The site runs on Cloudflare DNS + AWS CloudFront CDN via the Basker CMS platform.

Schema Posture

Every page uses only two schema types: WebSite and WebPage in a @graph container. There is no Organization schema, no MusicGroup, no Event, no MusicEvent, no FAQPage (despite a rich FAQ page with 20+ Q&A pairs), no BreadcrumbList, no Article on blog pages, and no VideoObject on the On Demand page which lists 20+ embedded Brightcove videos. The FAQ page uses plain <h3> headings for questions with no FAQPage markup — a significant missed opportunity for AI answer extraction.

Cold-Knowledge Gap

The LLM cold-knowledge prior knows the Sydney Symphony Orchestra was founded in 1932, names Simone Young as Chief Conductor (appointed 2022), mentions ARIA Award wins, and recalls a 2023 controversy over cancelling a Russian pianist's concert. The site itself does not mention the founding year on the homepage, does not reference ARIA awards anywhere on the pages inspected, and makes no mention of the 2023 controversy. The "Who We Are" page provides a detailed history narrative but buries the 1932 founding in paragraph text rather than surfacing it as a structured fact.

Content & Answer Signals

The homepage is a JS-rendered navigation shell with ~1,000 words of visible text, dominated by navigation links. The "What's On" page organizes concerts into four categories (Timeless Classics, Star Soloists, Sydney Symphony Presents, Family Adventures) with clear H3 headings — a structure AI crawlers can parse, but no Event schema attaches dates, venues, or ticket URLs. The blog (Backstage News) uses a Blog schema type but individual posts lack Article or NewsArticle markup. The "Sydney Symphony On Demand" page lists 16 concert videos and 15 musician profiles but has no VideoObject or Person schema.

External Signals

External search results for the domain returned zero indexed results from DuckDuckGo for brand queries — an anomaly that may indicate low external citation density or indexing issues. The DNS TXT records show verification tokens for Apple, Facebook, Google, Canva, Zoom, Smartsheet, and Microsoft, indicating a broad but fragmented third-party integration stack. No press mentions, Reddit threads, or review aggregator references were surfaced in search.

Findings

1. No llms.txt file published Medium

   The site does not serve an llms.txt file, missing an opportunity to guide AI crawlers to key content.

   What to change: Publish an llms.txt file listing important pages like /about-us/who-we-are, /concert-tickets/whats-on, and /read-watch/backstage-news.

2. Missing Organization and MusicGroup schema High

   Every page only includes WebSite and WebPage schema. No Organization, MusicGroup, or Event schema is present, despite the site representing a major orchestra.

   What to change: Add Organization schema with name, founding date, and URL to the homepage; add MusicGroup schema to the about page; add Event schema to concert pages.

3. Concert listings lack Event schema High

   The What's On page lists concerts with clear headings but no Event or MusicEvent schema, preventing AI from extracting dates, venues, and ticket links.

   What to change: Add MusicEvent schema to each concert listing with startDate, location, and offers.

4. FAQ page uses plain HTML instead of FAQPage schema High

   The FAQ page contains over 20 Q&A pairs marked up with h3 headings, but no FAQPage or Question/Answer schema, missing a prime opportunity for AI answer extraction.

   What to change: Wrap the FAQ content in FAQPage schema with Question and Answer properties.

5. On Demand page missing VideoObject schema Medium

   The Sydney Symphony On Demand page lists 16 concert videos and 15 musician profiles but has no VideoObject or Person schema, reducing discoverability of video content.

   What to change: Add VideoObject schema to each video entry with name, description, thumbnailUrl, and embedUrl.

6. Blog posts lack Article or NewsArticle schema Medium

   The Backstage News page uses Blog schema but individual posts do not have Article or NewsArticle markup, limiting their visibility in AI-generated news summaries.

   What to change: Add Article schema to each blog post with headline, datePublished, and author.

7. Founding year not surfaced as structured fact Medium

   The site's history narrative mentions the 1932 founding in paragraph text but does not surface it in schema or prominent homepage copy, while LLMs already know this fact.

   What to change: Add the founding year to Organization schema and consider a homepage hero section highlighting the orchestra's heritage.

8. ARIA Award wins not mentioned on site Low

   LLMs know the orchestra has won ARIA Awards, but the site's inspected pages do not reference any awards, missing a credibility signal.

   What to change: Add an awards section or mention ARIA wins in the about page with supporting schema.

9. No external search results for brand queries High

   DuckDuckGo searches for the domain and brand returned zero indexed results, indicating low external citation density or indexing issues.

   What to change: Investigate indexing status via Google Search Console, build backlinks from reputable arts and culture sites, and ensure sitemap is submitted to search engines.

10. Robots.txt contains inert AI-bot block rules Low

    The robots.txt file has commented-out Disallow rules for AI bots, which are not enforced. All AI crawlers receive full access, but the commented rules may confuse crawlers.

    What to change: Remove the commented-out rules to avoid confusion, or uncomment them if blocking is intended.

What's working

• All AI crawlers receive full access with identical content — All 11 tested AI bots receive a 200 OK with the same HTML as a browser, ensuring no content is hidden from AI crawlers.
• Concert listings organized with clear headings — The What's On page categorizes concerts into four groups with descriptive H3 headings, aiding crawler parsing of content structure.
• FAQ page contains 20+ detailed Q&A pairs — The FAQ page provides comprehensive answers to common questions, which could be leveraged for AI answer extraction if schema were added.
• On Demand page offers 16 concert videos and 15 musician profiles — The Sydney Symphony On Demand page provides a rich library of video content and musician profiles, valuable for AI training and user engagement.
• Blog page uses Blog schema type — The Backstage News page correctly uses Blog schema, providing a structural signal for the blog section.
• Site delivered via AWS CloudFront CDN — The site uses AWS CloudFront for content delivery, ensuring fast load times for crawlers and users.