dronedeploy.com — AI Site Grade

Analysis

The site's llms.txt is a rare, well-structured AI-facing asset — but the homepage's canonical points to www.dronedeploy.com while the bare domain serves identical content, creating a subtle split that AI crawlers indexing the non-www variant may treat as a separate entity from the canonical.

Crawler Access

All major AI crawlers (GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, ChatGPT-User, anthropic-ai) receive full 200 responses with identical byte-size content as a browser. Only Bytespider (ByteDance) gets a 403 from Cloudflare. The robots.txt contains no AI-bot-specific rules — only a catch-all * block on /api/, /tools/, and /test. The site runs on Cloudflare with HSTS preloaded, SOC 2 Type 2 and ISO 27001 certifications advertised. No JS-rendering risk: the homepage delivers 751 words of visible text on a plain GET.

llms.txt and Content Map

DroneDeploy is an outlier in having a live, comprehensive /llms.txt (3,727 bytes) that lists platform overview, products, industries, documentation, and legal pages with preferred citation instructions and a CC BY-NC 4.0 license. This is ahead of nearly all peers. The sitemap contains 685 URLs covering product pages, solutions, legal docs, and localized (ja-jp) content. The /news page carries a noindex meta tag — intentional, but means press releases and media coverage are invisible to AI crawlers.

Cold-Knowledge Gap

The LLM's cold knowledge describes DroneDeploy as a "cloud-based drone mapping and data analytics platform" focused on agriculture, construction, and mining — and notably references a 2023 data breach and 2024 layoffs. The actual site makes zero mention of either event. The site has pivoted hard toward "reality capture, robotics and AI agents" with products like Safety AI, Progress AI, and Dock Automation. The cold knowledge is 2-3 years stale: it omits the StructionSite acquisition (2022), the Rocos acquisition (2021), the shift to ground robotics, and the entire AI agent product line. The brand's current positioning as "robotics and AI platform used on 3 million sites" is entirely absent from the model's prior.

Schema Posture

Only the homepage carries structured data — a single SoftwareApplication schema with basic name/description/sameAs. The pricing page has a FAQPage schema with 12 Q&A entries (free trial, payment methods, integrations). All other key pages — product/safety-ai, product/progress-ai, product/ai-at-dronedeploy, solutions/construction, about — have zero JSON-LD. No BreadcrumbList, Product, Organization, or WebSite schema exists on those pages despite rich FAQ content and clear product hierarchies.

External Signals

The news page documents extensive press coverage: New York Times, MIT Technology Review, Fast Company, Forbes, VentureBeat, Financial Times, CNBC, TechCrunch, Construction Dive, ENR. Recent milestones include surpassing 20 trillion square feet of visual site data, a partnership with PCL Construction across 1,000+ projects, and a $15M raise (per AEC Magazine). The DNS TXT records show integrations with Anthropic, Atlassian, Calendly, Cursor, Figma, Miro, Mixpanel, MongoDB, Notion, Segment, Zendesk, Salesforce — a sophisticated enterprise tech stack. No Reddit threads or negative review signals surfaced in search.

Canonical Split

The homepage at https://dronedeploy.com (no-www) serves identical content to https://www.dronedeploy.com but declares its canonical as https://www.dronedeploy.com. Both resolve and return 200. AI crawlers hitting the bare domain will index content that points to a different canonical — a minor but unnecessary split that could dilute link equity and confuse entity resolution.

Findings

1. Homepage canonical split between www and non-www Medium

   The homepage at https://dronedeploy.com serves identical content to https://www.dronedeploy.com but declares its canonical as https://www.dronedeploy.com. Both resolve and return 200, creating a subtle split that may cause AI crawlers indexing the non-www variant to treat it as a separate entity.

   What to change: Redirect https://dronedeploy.com to https://www.dronedeploy.com with a 301 redirect to consolidate the canonical entity.

2. Missing JSON-LD schema on product and solution pages High

   Key pages such as /product/safety-ai, /product/progress-ai, /product/ai-at-dronedeploy, /solutions/construction, and /about have zero JSON-LD structured data. No BreadcrumbList, Product, Organization, or WebSite schema exists despite rich content and clear product hierarchies.

   What to change: Add appropriate JSON-LD schema (e.g., Product, BreadcrumbList, Organization) to all product and solution pages to improve AI entity understanding.

3. Stale cold knowledge about data breach and layoffs High

   LLM cold knowledge references a 2023 data breach and 2024 layoffs, but the site makes zero mention of either event. The brand's current positioning as a robotics and AI platform used on 3 million sites is entirely absent from the model's prior, creating a 2-3 year gap in AI perception.

   What to change: Publish a press release or blog post addressing the data breach and layoffs to update the public record, and ensure the site's content reflects the current product focus on robotics and AI agents.

4. News page blocked from AI crawlers via noindex Medium

   The /news page carries a noindex meta tag, making press releases and media coverage invisible to AI crawlers. This hides extensive positive coverage from outlets like New York Times, Forbes, and TechCrunch.

   What to change: Remove the noindex tag from the /news page to allow AI crawlers to index press coverage and improve external signal visibility.

5. llms.txt omits several key pages Medium

   The llms.txt lists platform overview, products, industries, documentation, and legal pages, but omits pages like /product/safety-ai, /product/progress-ai, /product/ai-at-dronedeploy, and /solutions/construction, which contain rich AI-relevant content.

   What to change: Add the missing product and solution pages to llms.txt to ensure AI crawlers have a complete content map.

6. Bytespider (ByteDance) blocked by Cloudflare Low

   The AI crawler Bytespider receives a 403 from Cloudflare, preventing ByteDance's AI models from indexing the site.

   What to change: Allow Bytespider access if coverage from ByteDance's AI products is desired.

7. Pricing page FAQ schema lacks product schema Low

   The pricing page has a FAQPage schema with 12 Q&A entries but no Product or Offer schema, missing an opportunity to provide structured pricing data to AI crawlers.

   What to change: Add Product and Offer schema to the pricing page to enable rich results and better AI understanding of pricing tiers.

What's working

• Comprehensive llms.txt with citation instructions — DroneDeploy has a live, 3,727-byte llms.txt listing platform overview, products, industries, documentation, and legal pages with preferred citation instructions and a CC BY-NC 4.0 license, ahead of nearly all peers.
• Full access for major AI crawlers — All major AI crawlers (GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, ChatGPT-User, anthropic-ai) receive full 200 responses with identical content as a browser, with no AI-bot-specific blocks in robots.txt.
• Homepage delivers full text without JavaScript — The homepage delivers 751 words of visible text on a plain GET request, with no JS-rendering risk for AI crawlers.
• Extensive press coverage from top-tier outlets — The news page documents coverage from New York Times, MIT Technology Review, Fast Company, Forbes, VentureBeat, Financial Times, CNBC, TechCrunch, and others, providing strong external signals.
• Enterprise integration ecosystem with major platforms — DNS TXT records show integrations with Anthropic, Atlassian, Calendly, Cursor, Figma, Miro, Mixpanel, MongoDB, Notion, Segment, Zendesk, Salesforce, indicating a sophisticated enterprise tech stack.
• Robots.txt does not block any AI bots — The robots.txt contains no AI-bot-specific rules, only a catch-all * block on /api/, /tools/, and /test, ensuring AI crawlers can access all public content.
• Pricing page has FAQPage schema with 12 entries — The pricing page includes a FAQPage schema with 12 Q&A entries covering free trial, payment methods, and integrations, providing structured data for AI crawlers.
• Homepage has SoftwareApplication schema — The homepage carries a SoftwareApplication schema with basic name, description, and sameAs, providing a foundation for AI entity understanding.