flyscoot.com — AI Site Grade

Analysis

Akamai Bot Wall Blocks All AI Crawlers From Every Page

The entire flyscoot.com domain is locked behind an Akamai CDN bot-detection wall that returns HTTP 403 "Access Denied" to every request, including standard browsers, all major AI crawlers (GPTBot, ClaudeBot, PerplexityBot, Google-Extended, ChatGPT-User, OAI-SearchBot, Applebot-Extended, anthropic-ai, Bytespider), and even the Wayback Machine's archiver. No page — homepage, /en, /en/about, /en/destinations, /en/help, /en/blog, robots.txt, llms.txt, or sitemap.xml — returns any content. Every URL produces the same 15-word HTML error referencing errors.edgesuite.net (Akamai's error domain). The site has zero discoverable content for any automated agent.

Crawler Access

robots.txt and llms.txt both return HTTP 403, meaning no AI crawler can read access rules before attempting to crawl. The compare_bot_access test across 11 user-agents shows 100% block rate — every bot receives a 403 with identical byte-size response (~370 bytes). The cache-control header is set to max-age=0, no-cache, no-store, preventing any intermediary caching. DNS records point to AWS Route53 with Akamai IPs (18.245.218.x), confirming the CDN-layer blocking. The site uses strict-transport-security but no Content-Security-Policy or X-Frame-Options headers.

Cold-Knowledge Gap

The LLM knows Scoot as a Singapore Airlines low-cost subsidiary launched in 2012, operating Boeing 787 and Airbus A320 fleets to Asia-Pacific and European destinations, with products like ScootBiz and Scoot-Thru. This knowledge comes from pre-training data (news, Wikipedia, travel forums) — none of it originates from the live site. The site itself contributes zero signals: no schema markup, no structured data, no FAQ content, no heading hierarchy, no meta descriptions. The gap between what the LLM knows (detailed brand history, fleet, routes) and what the site serves (a 403 error page) is absolute.

Schema and Content Posture

No JSON-LD schema of any type was detected on any accessible URL. The homepage returns no <title>, no <meta name="description">, no Open Graph tags, no canonical URL, and no headings beyond the error message. The Wayback Machine snapshots from 2022 and 2023 also only captured the Akamai challenge page ("Pardon Our Interruption"), meaning the site's actual content has never been publicly archived. No FAQ, comparison tables, or answer-format signals exist on the live domain.

External Signals

DuckDuckGo web searches for "flyscoot.com", "Scoot airline Singapore", and related queries returned zero results — the domain appears to have no indexed external mentions in the search engine used. The Google cache for flyscoot.com returned no results. The site's DNS TXT records show verification tokens for Apple, Atlassian, Dropbox, Facebook, Zoom, LaunchDarkly, Miro, and over 60 GlobalSign SSL certificates, indicating a complex multi-vendor infrastructure but no AI-specific configuration.

Findings

1. Akamai bot wall blocks all AI crawlers from every page High

   The entire flyscoot.com domain returns HTTP 403 'Access Denied' to all requests, including standard browsers, all major AI crawlers (GPTBot, ClaudeBot, PerplexityBot, Google-Extended, ChatGPT-User, OAI-SearchBot, Applebot-Extended, anthropic-ai, Bytespider), and the Wayback Machine archiver. No page — homepage, /en, /en/about, /en/destinations, /en/help, /en/blog, robots.txt, llms.txt, or sitemap.xml — returns any content. Every URL produces the same 15-word HTML error referencing errors.edgesuite.net (Akamai's error domain).

   What to change: Remove or reconfigure the Akamai bot-detection wall to allow AI crawlers (e.g., GPTBot, ClaudeBot, Google-Extended) to access the site. Implement a robots.txt that permits crawling by AI bots and serves actual content instead of a 403 error.

2. Robots.txt and llms.txt return HTTP 403, blocking crawler directives High

   Both robots.txt and llms.txt return HTTP 403, meaning no AI crawler can read access rules before attempting to crawl. This prevents crawlers from discovering allowed paths or respecting any directives.

   What to change: Serve a valid robots.txt that allows AI crawlers to access the site, and create an llms.txt file with a summary of the site's content for LLM consumption.

3. Sitemap.xml returns HTTP 403, preventing content discovery High

   The sitemap.xml at https://www.flyscoot.com/sitemap.xml returns HTTP 403, so crawlers cannot discover the site's URL structure or prioritize content for indexing.

   What to change: Serve a valid sitemap.xml that lists all public URLs on the site, and ensure it is accessible to crawlers.

4. No JSON-LD schema or structured data detected on any page High

   No JSON-LD schema of any type was detected on any accessible URL. The homepage returns no <title>, no <meta name="description">, no Open Graph tags, no canonical URL, and no headings beyond the error message. This means AI crawlers cannot extract any structured information about the airline, flights, or destinations.

   What to change: Implement JSON-LD schema markup (e.g., Airline, Flight, FAQ, BreadcrumbList) on all relevant pages, and ensure proper HTML meta tags are present.

5. All URLs return identical 403 error page with no content High

   Every URL on flyscoot.com returns the same 15-word HTML error referencing errors.edgesuite.net. No page serves any actual content, including the homepage, about page, destinations, help, blog, or any subpage. The site has zero discoverable content for any automated agent.

   What to change: Remove the blanket bot wall and serve actual HTML content for all public pages, including proper meta tags, headings, and structured data.

6. Domain has zero indexed external mentions in search engines High

   DuckDuckGo web searches for 'flyscoot.com', 'Scoot airline Singapore', and related queries returned zero results. The Google cache for flyscoot.com returned no results. The domain appears to have no indexed external mentions in the search engine used, indicating a complete lack of visibility.

   What to change: Allow search engine crawlers to access the site and index its content. Implement proper SEO practices including meta tags, sitemaps, and structured data to improve search visibility.

7. Wayback Machine snapshots only capture Akamai challenge page Medium

   Wayback Machine snapshots from 2022, 2023, and 2025 only captured the Akamai challenge page ('Pardon Our Interruption'), meaning the site's actual content has never been publicly archived. This indicates the bot wall has been in place for years.

   What to change: Remove the bot wall to allow the Wayback Machine and other archivers to capture the site's actual content.

8. Cache-control headers prevent any intermediary caching Low

   The cache-control header is set to 'max-age=0, no-cache, no-store', preventing any intermediary caching. This further limits the site's ability to be served from caches or CDNs for legitimate crawlers.

   What to change: Adjust cache-control headers to allow caching of static assets and public content, while still respecting bot access rules.

9. DNS TXT records show no AI-specific configuration Low

   The site's DNS TXT records show verification tokens for Apple, Atlassian, Dropbox, Facebook, Zoom, LaunchDarkly, Miro, and over 60 GlobalSign SSL certificates, indicating a complex multi-vendor infrastructure but no AI-specific configuration such as AI crawler allowlists or verification tokens.

   What to change: Add DNS TXT records for AI crawler verification (e.g., Google, OpenAI, Anthropic) to facilitate authorized crawling.

What's working

• LLM has pre-training knowledge of Scoot airline — The LLM knows Scoot as a Singapore Airlines low-cost subsidiary launched in 2012, operating Boeing 787 and Airbus A320 fleets to Asia-Pacific and European destinations, with products like ScootBiz and Scoot-Thru. This knowledge comes from pre-training data (news, Wikipedia, travel forums), providing a baseline understanding of the brand despite the site being inaccessible.
• DNS infrastructure is robust with multiple records — DNS records point to AWS Route53 with Akamai IPs, and TXT records show verification tokens for many vendors, indicating a well-managed multi-vendor infrastructure.
• Strict-Transport-Security header is enabled — The site uses strict-transport-security header, ensuring HTTPS connections and protecting against downgrade attacks.