netdocuments.com — AI Site Grade

Analysis

NetDocuments: AI-Visibility Audit

The site is technically wide open to AI crawlers but has zero structured data on any page — a striking gap for a company whose entire product is now about AI-powered context graphs and agentic workflows.

Crawler Access

All major AI bots — GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, ChatGPT-User, Applebot-Extended, anthropic-ai — receive a full 200 response with identical content to a browser baseline (270 KB). Only Bytespider is blocked (403 by Cloudflare). The robots.txt is minimal: a single wildcard rule disallowing /wp-admin/ with no AI-bot-specific directives whatsoever. The site runs on Cloudflare (CDN) + WP Engine (hosting), with nginx as the origin server. No JS-rendering risk exists — all pages serve rich HTML content on plain GET. /llms.txt returns 404, meaning no AI-friendly content map exists despite the company actively building MCP connectors for Claude and ChatGPT.

Schema Posture

Every page examined — homepage, solutions pages, blog posts, press releases — contains zero JSON-LD schema of any type. No Organization, WebSite, Article, FAQPage, Product, or SoftwareApplication schema is present. The FAQ section on the legal AI platform page (/solutions/legal-ai-platform/) uses plain HTML headings with no FAQPage markup. This is a critical miss: AI engines consuming this content via retrieval have no structured signals to classify NetDocuments as a software product, an organization, or an article publisher.

Cold-Knowledge Gap

The cold LLM knows NetDocuments as a cloud DMS for legal, founded 1999, acquired by Welsh Carson in 2020, with FedRAMP/SOC 2, products named ndOffice/ndMail/ndHub. It also recalls pricing scrutiny and migration complexity as reputational signals. The site itself, however, has completely moved past that narrative. The homepage and all key pages now lead with the "legal context graph" — a reimagined platform unveiled May 2026 — and emphasize AI agents, MCP integration with Anthropic, and the ndMAX Studio of 33 AI apps. The cold model knows nothing about the context graph, the Anthropic MCP collaboration, the reimagined platform, or the eDOCS acquisition from OpenText. The site's current positioning is roughly 6-12 months ahead of what AI engines would say without live retrieval.

Content & Answer Signals

The homepage and solution pages are text-rich (900-2,200 words each) with strong answer-format signals: FAQ sections, definition patterns ("What is a legal context graph?"), comparison language, and lists of features. Blog posts are substantive (2,200+ words on the context graph explainer). The site has 10 localized language versions (ES, PT, FR, NL, NO, SV, GB, BR). The company news page shows active press coverage from Artificial Lawyer, Forbes Tech Council, and legal trade outlets. However, the canonical and og:type are inconsistent — some pages use og:type: article for solution pages that are not articles.

External Signals

Web search returned zero indexed results for multiple queries about NetDocuments — a DuckDuckGo limitation rather than a site problem. The company news archive shows press pickup from Artificial Lawyer, Forbes Tech Council, and Legal IT Insider, plus a customer case study with Am Law 100 firm Akin (65M+ documents). The DNS TXT records reveal integrations with Pendo (product analytics), Notion, Canva, Carta, and Docker — a broader tech stack than the site's "150+ integrations" messaging suggests.

Findings

1. Zero JSON-LD schema on any page High

   Every page examined — homepage, solutions, blog, press releases — contains no JSON-LD schema of any type. No Organization, WebSite, Article, FAQPage, Product, or SoftwareApplication schema is present.

   What to change: Add JSON-LD schema for Organization, WebSite, Article, and SoftwareApplication on relevant pages. Mark up FAQ sections with FAQPage schema.

2. No /llms.txt file despite MCP integrations Medium

   The site returns 404 for /llms.txt, meaning no AI-friendly content map exists. This is a missed opportunity given the company's active MCP connector development for Claude and ChatGPT.

   What to change: Create an /llms.txt file that lists key pages and resources for AI crawlers.

3. Cold LLM unaware of context graph and MCP collaboration High

   The cold LLM knows NetDocuments only as a traditional cloud DMS. It has no knowledge of the legal context graph, the Anthropic MCP collaboration, the reimagined platform unveiled in May 2026, or the eDOCS acquisition. The site's current positioning is 6-12 months ahead of AI knowledge.

   What to change: Increase external signals (press, backlinks, social) about the context graph and MCP integrations. Ensure schema markup helps AI engines classify the new platform.

4. Inconsistent og:type on solution pages Low

   Some solution pages use og:type: article, which is inappropriate for non-article pages like product or solution pages.

   What to change: Set og:type to 'website' or 'product' for solution pages, reserving 'article' for blog posts and news.

5. FAQ sections lack FAQPage schema Medium

   The FAQ section on the legal AI platform page uses plain HTML headings with no FAQPage markup, reducing the chance of rich results in AI-driven search.

   What to change: Add FAQPage schema to all FAQ sections on the site.

6. Minimal robots.txt with no AI-bot directives Low

   The robots.txt only has a wildcard rule disallowing /wp-admin/. No AI-bot-specific directives exist, which is fine for access but misses the opportunity to guide crawlers to key pages.

   What to change: Consider adding Allow directives for important AI-accessible pages and a Sitemap directive.

7. Bytespider blocked by Cloudflare Low

   Bytespider receives a 403 response, which may limit visibility on certain AI platforms that use it.

   What to change: Allow Bytespider if it does not cause performance issues.

8. Blog posts missing Article schema Medium

   Blog posts and news articles lack Article schema, reducing their discoverability in AI-driven news and search features.

   What to change: Add Article schema with headline, datePublished, author, and image to all blog and news pages.

What's working

• All major AI bots allowed with full content access — GPTBot, ClaudeBot, PerplexityBot, Google-Extended, and others receive 200 responses with identical content to browser baseline. No JS rendering required.
• Text-rich pages with strong answer signals — Homepage and solution pages contain 900-2,200 words with FAQ sections, definition patterns, and comparison language, making them suitable for AI retrieval.
• Active press coverage from legal and tech outlets — Company news page shows press pickup from Artificial Lawyer, Forbes Tech Council, and Legal IT Insider, plus a customer case study with Am Law 100 firm Akin.
• Detailed MCP integration content published — A blog post details the collaboration with Anthropic on a legal industry MCP, providing rich content for AI crawlers interested in agentic workflows.
• Sitemap with 80 URLs covering key pages — The sitemap includes 80 URLs, ensuring crawlers can discover all important pages.
• 10 localized language versions available — The site offers content in 10 languages, expanding its reach to international AI crawlers and users.