magnals.com — AI Site Grade

Analysis

The Cloudflare JS challenge on magnals.com returns a 403 to every AI crawler tested — GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, and Applebot-Extended all hit the same "Just a moment..." wall with zero content delivered.

Crawler Access

Every AI crawler tested against https://magnals.com receives a 403 status from Cloudflare's JS challenge page. The compare_bot_access scan across GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, ChatGPT-User, Bytespider, Applebot-Extended, and anthropic-ai returned identical results: all blocked, all served the Cloudflare challenge HTML shell (5.5-5.7 KB), zero visible page content. The robots.txt (archived snapshot from Jan 2026) contains only User-Agent: * Disallow: with no AI-bot-specific rules — but the file is inaccessible live behind the same 403. No llms.txt exists. The sitemap is also 403'd. The site runs on Cloudflare (A records point to 104.18.28.2/29.2) with Cloudflare nameservers and a managed challenge configuration.

Cold-Knowledge Gap

A frontier LLM queried cold about magnals.com returned: "I do not have specific, verifiable information about magnals.com." The model has zero prior knowledge — no awareness of the brand name, its services, or its industry. This is a complete knowledge vacuum. The site itself (via Wayback archive) identifies as Magna Legal Services, a nationwide litigation support provider offering court reporting, record retrieval, jury consulting, trial presentation, legal translation, and investigative services from a Philadelphia headquarters with offices in 10+ US states. The gap between what the site claims ("nationwide leader in litigation support") and what AI models know (nothing) is total.

Schema Posture

The archived homepage carries a solid JSON-LD schema block with WebPage, WebSite, Organization, and BreadcrumbList types. The Organization schema includes name, logo URL, URL, and a Facebook sameAs link. However, the schema is missing LocalBusiness or LegalService subtypes, has no @id references to service pages, no hasOfferCatalog for the extensive service list, and no aggregateRating or review schema despite prominently featuring testimonials and "Industry Recognition" sections. The sameAs array contains only Facebook — no LinkedIn, Twitter/X, YouTube, or other platforms.

External Signals

DuckDuckGo web search returned zero indexed results for "magnals.com", "Magna Legal Services", or any combination of the brand name with its service keywords. No reviews, no Reddit threads, no press mentions, no LinkedIn company page surfaced. The DNS TXT records reveal a sophisticated tech stack — Mimecast email security, Zoom verification, Atlassian, Box, Monday.com, Pardot, Intacct, Duo SSO, and an OpenAI domain verification token (openai-domain-verification=dv-rR3atSvUTxODBttBVWfhaMPD), indicating the organization has engaged with OpenAI's business tools. Yet none of this infrastructure translates into AI-visible web presence. The site has been on the web since at least 2008 (Wayback captures begin then) and runs WordPress with Yoast SEO, but the Cloudflare challenge blocks all crawler access, effectively making the site invisible to both search engines and AI training pipelines.

Findings

1. Cloudflare JS challenge blocks all AI crawlers with 403 High

   Every AI crawler tested (GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, Applebot-Extended, and others) receives a 403 status from Cloudflare's JS challenge page. No visible page content is delivered to any crawler.

   What to change: Configure Cloudflare to allow AI crawler user agents (e.g., GPTBot, ClaudeBot) through the JS challenge, or serve a static HTML version to known bots.

2. Robots.txt inaccessible behind Cloudflare 403 High

   The live robots.txt returns a 403 error, making it impossible for crawlers to read crawl directives. An archived snapshot shows only a default allow-all rule with no AI-bot-specific instructions.

   What to change: Ensure robots.txt is publicly accessible and includes explicit rules for AI crawlers (e.g., allow GPTBot, ClaudeBot).

3. Sitemap returns 403, blocking crawler discovery High

   The sitemap at /sitemap_index.xml is also behind the Cloudflare 403, preventing crawlers from discovering site pages.

   What to change: Make the sitemap publicly accessible and submit it to search engines.

4. No llms.txt file published Medium

   The site does not serve an llms.txt file, missing an opportunity to provide AI crawlers with a structured overview of available content.

   What to change: Create an llms.txt file listing key pages and a brief site description for AI crawlers.

5. Zero indexed pages in search engines High

   Web searches for 'magnals.com', 'Magna Legal Services', and related terms return zero results. The site is completely absent from search engine indexes.

   What to change: Resolve Cloudflare blocking for search engine bots and submit the sitemap to Google Search Console and Bing Webmaster Tools.

6. AI models have zero knowledge of magnals.com High

   A frontier LLM queried cold about magnals.com returned no verifiable information. The brand and its services are completely unknown to AI models.

   What to change: Allow AI crawlers to access the site and publish structured data to build AI knowledge graph presence.

7. Organization schema missing LocalBusiness or LegalService subtype Medium

   The JSON-LD schema uses Organization but does not include LocalBusiness or LegalService subtypes, which would help AI models understand the site's business category.

   What to change: Add LocalBusiness or LegalService schema with appropriate subtypes to the Organization schema.

8. No @id references or hasOfferCatalog for service pages Medium

   The schema lacks @id references to individual service pages and has no hasOfferCatalog to enumerate the extensive list of litigation support services.

   What to change: Add @id properties to each service page and include a hasOfferCatalog in the Organization schema listing all services.

9. Testimonials and recognition not marked up with review schema Medium

   The site features testimonials and an 'Industry Recognition' section but does not use aggregateRating or review schema, missing an opportunity to enhance credibility signals.

   What to change: Add AggregateRating and Review schema markup to testimonial and recognition sections.

10. SameAs array contains only Facebook Low

    The Organization schema's sameAs array includes only a Facebook URL, missing LinkedIn, Twitter/X, YouTube, and other platforms that could build external signals.

    What to change: Add LinkedIn, Twitter/X, YouTube, and other relevant social profiles to the sameAs array.

11. No external mentions or backlinks found High

    Web searches for the brand name and services returned zero results, indicating no press mentions, reviews, or backlinks from other sites.

    What to change: Build external signals through PR, directory listings, and social media presence to improve AI visibility.

What's working

• JSON-LD schema with WebPage, WebSite, Organization, and BreadcrumbList — The archived homepage includes a solid JSON-LD schema block with multiple types, providing a foundation for AI understanding.
• OpenAI domain verification token present in DNS — The DNS TXT records include an OpenAI domain verification token, indicating engagement with OpenAI's business tools and potential for future AI integration.
• WordPress with Yoast SEO plugin — The site runs on WordPress with Yoast SEO, providing a solid technical foundation for SEO and structured data management.
• Archived homepage contains detailed service descriptions — The Wayback Machine snapshot shows a content-rich homepage with detailed descriptions of litigation support services, which can be leveraged once crawler access is restored.