ninjatrader.com — AI Site Grade

Analysis

NinjaTrader.com: Zero Structured Data on a 1.9M-User Platform

Every page examined across the NinjaTrader domain — the homepage, pricing, trading platform, futures, blog, support, and contact pages — returns zero JSON-LD schema of any type. A site claiming 1.9 million users, displaying award badges ("2026 Best Futures Broker", "2024 Best Trading Software"), and offering tiered subscription plans ($0, $99/mo, $1,499 lifetime) has no Organization, Product, FAQPage, SoftwareApplication, or BreadcrumbList schema on any fetched page. This is the single most consequential finding: AI crawlers and knowledge panels receive no structured signal about what NinjaTrader is, what it sells, or how it is organized.

Crawler Access

All major AI crawlers — GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, Bytespider, Applebot-Extended, anthropic-ai, ChatGPT-User — receive a full 200 response with identical byte content (100,156 bytes) to a browser. Cloudflare serves the site with no UA-based blocking. The robots.txt uses a single User-agent: * rule blocking only admin/development paths (/cmsctx/, /webnew/, /Advisory/, etc.) and contains no AI-bot-specific directives. The llms.txt returns a 404. The sitemap at /sitemapindex.xml (actually a single flat sitemap) contains ~1,020 URLs with extensive hreflang alternates across 8+ language variants, but the robots.txt references it as sitemapindex.xml while the actual file is sitemap.xml — a minor but detectable inconsistency.

Cold-Knowledge Gap

The LLM's cold knowledge of NinjaTrader is surprisingly detailed and partially negative: it recalls a 2023 class-action lawsuit alleging unauthorized trading, user complaints about customer support, and platform stability issues during high volatility. The site itself makes zero mention of any lawsuit, legal action, or regulatory event. The site presents NinjaTrader as "the #1 rated futures broker" with "award-winning" platforms and "24/5 support" — a starkly sanitized version that does not acknowledge the reputational signals the model already holds. The model also knows about a "lifetime license" pricing model, but the current site shows the Lifetime plan at $1,499 (a one-time fee), which the model does not cite with a specific price.

Schema Posture

The complete absence of structured data is the critical gap. The pricing page has a clear three-tier plan comparison (Free / $0.39 micro, Monthly / $0.29 micro, Lifetime / $0.09 micro) with FAQ content, yet no FAQPage schema. The blog post on stop-loss strategies contains an FAQ section with four questions and no FAQPage markup. The homepage lists awards (BrokerChooser 2026, Stocks & Commodities 2024, Benzinga 2024) with no Award schema. The /about-us/ page 404s — there is no company information page at all, meaning no Organization schema with founding date, founding location (Chicago, IL — present on the contact page but not in schema), or leadership details.

External Signals

DNS records reveal an anthropic-domain-verification TXT record and an openai-domain-verification TXT record, confirming NinjaTrader has proactively verified its domain with both Anthropic and OpenAI for AI-related services. Yet the site does not surface an llms.txt or any AI-friendly content map. The domain also has google-site-verification records, stripe-verification, and numerous SaaS verification tokens (Slack, Atlassian, Figma, Calendly, etc.), indicating a broad third-party tool stack but no corresponding structured data output on the public site.

Findings

1. Zero JSON-LD schema on all pages High

   Every page examined (homepage, pricing, trading platform, futures, blog, support, contact) returns no JSON-LD schema of any type. No Organization, Product, FAQPage, SoftwareApplication, or BreadcrumbList schema exists, preventing AI crawlers from extracting structured information about the company, products, or content.

   What to change: Add JSON-LD schema for Organization (with name, founding date, location, awards), SoftwareApplication (for the trading platform), Product (for subscription plans), FAQPage (for FAQ sections), and BreadcrumbList on all pages.

2. About page returns 404 High

   The /about-us/ page returns a 404 error, meaning there is no company information page. This prevents AI crawlers from finding official details about NinjaTrader's history, leadership, or mission, and blocks the placement of Organization schema.

   What to change: Create an /about-us/ page with company history, leadership, founding date (2003), location (Chicago, IL), and mission, and include Organization schema.

3. Negative LLM knowledge unaddressed on site Medium

   The LLM's cold knowledge includes a 2023 class-action lawsuit, user complaints about customer support, and platform stability issues. The site makes no mention of any legal or regulatory matters, presenting a sanitized image that does not align with external signals.

   What to change: Consider publishing a legal or transparency page that addresses the lawsuit and regulatory status, or at minimum ensure the site's narrative is consistent with public records.

4. No llms.txt file Medium

   The /llms.txt endpoint returns a 404. This file is used by AI crawlers to discover key content and context about the site. Its absence means AI crawlers have no machine-readable guide to the site's structure or important pages.

   What to change: Create an llms.txt file listing key pages (homepage, pricing, platform, futures, blog, support, contact) with brief descriptions.

5. Sitemap URL mismatch in robots.txt Low

   The robots.txt references sitemapindex.xml, but the actual sitemap is at sitemap.xml. While both resolve, this inconsistency may confuse some crawlers.

   What to change: Update robots.txt to point to the correct sitemap URL: sitemap.xml.

6. FAQ content without FAQPage schema Medium

   The pricing page and a blog post contain FAQ sections with multiple questions and answers, but neither has FAQPage schema markup. This misses an opportunity for rich results in AI-generated answers.

   What to change: Add FAQPage schema to any page with FAQ content, marking up each question and answer.

7. Award badges without Award schema Low

   The homepage displays award badges (BrokerChooser 2026, Stocks & Commodities 2024, Benzinga 2024) but no Award schema is present. This prevents AI crawlers from understanding the awards as structured data.

   What to change: Add Award schema for each award badge, including the awarding organization, year, and category.

8. Trading platform page lacks SoftwareApplication schema Medium

   The trading platform page describes the NinjaTrader platform (desktop, web, mobile) but has no SoftwareApplication schema. This would help AI crawlers understand the platform's features, operating systems, and pricing.

   What to change: Add SoftwareApplication schema to the trading platform page with properties like name, applicationCategory, operatingSystem, offers, and description.

9. Pricing page lacks Product schema for plans Medium

   The pricing page lists three subscription plans (Free, Monthly, Lifetime) with prices and features, but no Product schema is used. This prevents AI crawlers from understanding the pricing structure.

   What to change: Add Product schema for each plan with properties like name, description, offers (price, priceCurrency), and possibly category.

10. No BreadcrumbList schema on any page Low

    No page uses BreadcrumbList schema, which helps AI crawlers understand site hierarchy and navigation context.

    What to change: Add BreadcrumbList schema to all pages, reflecting the site's navigation structure.

11. No Organization schema on any page High

    Despite having a contact page with address and phone, and awards on the homepage, no Organization schema is present. This is a critical missing signal for knowledge panels.

    What to change: Add Organization schema to the homepage and contact page with name, url, logo, foundingDate, foundingLocation, address, contactPoint, and awards.

12. Domain verification tokens not leveraged for AI content Medium

    DNS records show anthropic-domain-verification and openai-domain-verification TXT records, indicating proactive verification with AI companies. However, the site does not provide an llms.txt or any AI-friendly content map to take advantage of this access.

    What to change: Create an llms.txt file and consider adding an AI-specific sitemap or content guide to help AI crawlers discover key pages.

What's working

• All major AI crawlers allowed with full content access — All 11 tested AI crawlers (GPTBot, ClaudeBot, PerplexityBot, etc.) receive a 200 response with identical content to a browser. No UA-based blocking or AI-specific restrictions exist.
• Robots.txt blocks only admin paths, no AI bot restrictions — The robots.txt uses a single User-agent: * rule blocking only internal paths (/cmsctx/, /webnew/, /Advisory/). No AI-bot-specific directives are present, ensuring all AI crawlers can access public content.
• Sitemap contains ~1,020 URLs with hreflang alternates — The sitemap includes a large number of URLs with hreflang tags for 8+ languages, helping international crawlers discover localized content.
• Domain verified with Anthropic and OpenAI — DNS records contain anthropic-domain-verification and openai-domain-verification TXT records, showing proactive verification for AI services.
• Cloudflare serves site with no UA-based blocking — The site uses Cloudflare but does not block or alter content based on user-agent, ensuring AI crawlers receive the same content as users.
• Key pages have substantial text content — Pages like pricing (1503 words), futures vs stocks (921 words), and blog posts (1992 words) contain detailed, informative text that AI crawlers can index.
• Contact page provides physical address and phone — The contact page lists a Chicago, IL address and phone number, which can be used for local SEO and Organization schema (though currently missing).
• Blog includes FAQ sections with useful Q&A — A blog post on stop-loss strategies contains a four-question FAQ section, providing content that could be marked up with FAQPage schema.