doit.com — AI Site Grade

Analysis

The Cold-Knowledge Gap

DoiT's site has undergone a complete rebrand that cold LLM knowledge has not caught up with. The model describes "DoiT Cloud Navigator" and "DoiT Cloud Management Platform (CMP)" — products that no longer exist on the live site. The site now exclusively brands around Cloud Intelligence with sub-products PerfectScale (Kubernetes, Commitments, Data Platforms), CloudFlow, and Agentic Cloud Operations. The model also references a NetApp acquisition in 2022 — no mention of this exists anywhere on the site, and the DNS TXT records show no NetApp affiliation. The site presents DoiT as an independent company founded in 2011, headquartered in Santa Clara, with 4,500+ customers and $20B+ in managed cloud spend. The cold knowledge is roughly 2-3 years stale.

Crawler Access

Every major AI crawler — GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, Applebot-Extended, Bytespider, anthropic-ai — receives a 200 with full HTML content (1.06 MB) identical to browser delivery. No UA-based blocking, no JS shell, no Cloudflare challenge. The robots.txt explicitly allows OAI-SearchBot, Claude-SearchBot, and Claude-User with Allow: /, and the wildcard rule blocks only /api/, /admin/, /settings/, /analytics/. The file even includes a comment pointing to /llms.txt as an "AI discovery aid." The llms.txt itself is a 155 KB file listing 665+ blog posts with markdown API endpoints — one of the most comprehensive llms.txt implementations observed. The sitemap index is well-structured with 5 sub-sitemaps (pages, blog, changelog, customers, team), last updated May 2026.

Schema Posture

The schema implementation is thin for a site of this sophistication. Every page fetched — homepage, about, pricing, product pages, blog — uses only a bare Organization schema with name and URL. No WebSite, WebPage, SoftwareApplication, Product, or FAQPage schemas are present despite the site having clear SaaS products, a pricing page with FAQ, and a blog with Article schema (only on individual blog posts). The pricing page has an FAQ section with real questions but zero FAQPage markup. The homepage has no WebSite or SoftwareApplication schema to tell AI engines what Cloud Intelligence actually is. This is a significant missed signal for AI-driven search and knowledge graph inclusion.

Content & Answer Signals

The homepage is a dense, well-written 968-word narrative with strong positioning: "Your infrastructure, always at its best." It uses a three-lever savings model (Usage Optimization, Rate Optimization, Forward Deployed Engineers) with percentage counters. The blog publishes frequently — 665 posts, with the most recent dated May 21, 2026 — covering FinOps, Kubernetes, AI cost optimization, and cloud pricing. The blog uses Article schema with datePublished, author, and publisher. The Agentic Cloud Operations product page has a genuine FAQ section with 5 questions and answers, but no FAQPage schema. The site has multi-language support (English, Spanish, Japanese, French, German, Portuguese, Italian) with hreflang annotations in the sitemap.

External Signals

The DNS TXT records reveal integrations with a wide SaaS stack: OpenAI (openai-domain-verification), Anthropic (anthropic-domain-verification), Cursor, Notion, Figma, 1Password, Slack, Stripe (3 verification records), Atlassian, Mixpanel, Segment, Pardot, and Apple. The site links to G2 reviews, LinkedIn, X (formerly Twitter), YouTube, Facebook, and GitHub. The blog references customer case studies (Rapyd, SNCF, PlayHQ, Fiverr, Current) with specific savings figures. The site claims 99.7% average customer satisfaction and SOC 2 / ISO 27001 certification.

Findings

1. Cold LLM knowledge references discontinued products and outdated acquisition High

   Cold knowledge describes 'DoiT Cloud Navigator' and 'DoiT Cloud Management Platform' which no longer exist on the live site, and mentions a NetApp acquisition in 2022 that is not referenced anywhere on the site. The site now exclusively brands around Cloud Intelligence with sub-products PerfectScale, CloudFlow, and Agentic Cloud Operations.

   What to change: Publish a press release or blog post about the rebranding and current product lineup, and ensure the site's structured data and sitemaps clearly reflect the new product names to help LLMs update their knowledge.

2. Minimal schema markup across key pages High

   Every page fetched uses only a bare Organization schema with name and URL. No WebSite, WebPage, SoftwareApplication, Product, or FAQPage schemas are present, despite the site having clear SaaS products, a pricing page with FAQ, and a blog with Article schema only on individual posts.

   What to change: Add WebSite schema to the homepage, SoftwareApplication schema to product pages, Product schema to pricing page, and FAQPage schema to pages with FAQ sections.

3. FAQ sections lack FAQPage schema markup Medium

   The pricing page and Agentic Cloud Operations product page have genuine FAQ sections with real questions and answers, but neither uses FAQPage schema, missing an opportunity for rich results in AI-driven search.

   What to change: Add FAQPage schema to the pricing page and Agentic Cloud Operations page.

4. Product pages missing SoftwareApplication schema Medium

   Product pages for PerfectScale and Agentic Cloud Operations do not include SoftwareApplication schema, which would help AI engines understand the software category, features, and pricing.

   What to change: Add SoftwareApplication schema to all product pages with properties like name, description, applicationCategory, offers, and operatingSystem.

5. Homepage missing WebSite schema Medium

   The homepage does not include WebSite schema, which would help search engines and AI understand the site's name, URL, and search action.

   What to change: Add WebSite schema to the homepage with potentialAction for search.

6. Sitemap fetch initially timed out Low

   The initial fetch of the sitemap timed out after 25 seconds, though subsequent fetches succeeded. This may indicate intermittent performance issues that could affect crawler efficiency.

   What to change: Investigate and resolve sitemap server response time to ensure reliable crawling.

7. No WebPage schema on any page Low

   None of the fetched pages include WebPage schema, which would provide metadata about page type, date modified, and breadcrumbs.

   What to change: Add WebPage schema to all pages with properties like dateModified, breadcrumb, and mainEntity.

What's working

• All major AI crawlers receive full HTML content — Every major AI crawler (GPTBot, ClaudeBot, PerplexityBot, Google-Extended, etc.) receives a 200 with full HTML content identical to browser delivery, with no UA-based blocking or JavaScript shells.
• Extensive llms.txt with 665+ blog posts — The llms.txt file is 155 KB and lists 665+ blog posts with markdown API endpoints, making it one of the most comprehensive implementations observed.
• Well-structured sitemap index with sub-sitemaps — The sitemap index is well-structured with 5 sub-sitemaps (pages, blog, changelog, customers, team) and includes hreflang annotations for multi-language support.
• robots.txt explicitly allows AI search bots — The robots.txt explicitly allows OAI-SearchBot, Claude-SearchBot, and Claude-User with Allow: /, and includes a comment pointing to llms.txt as an AI discovery aid.
• Dense, well-written homepage with strong positioning — The homepage is a 968-word narrative with clear positioning, a three-lever savings model, and percentage counters, providing rich content for AI understanding.
• Frequent blog with Article schema on individual posts — The blog publishes frequently (665 posts, latest May 21, 2026) covering relevant topics, and individual posts use Article schema with datePublished, author, and publisher.
• Strong external signals from integrations and social links — DNS TXT records show integrations with OpenAI, Anthropic, Cursor, Notion, Figma, and others. The site links to G2, LinkedIn, X, YouTube, Facebook, and GitHub, and references customer case studies with specific savings figures.