gusto.com — AI Site Grade

Analysis

I have a thorough picture. Let me compile the audit.

The llms.txt is a standout — but zero JSON-LD schema across every page probed is a critical gap for AI answer engines.

Crawler Access

All major AI crawlers — GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, Bytespider, Applebot-Extended — receive a 200 with full HTML content from the homepage. No UA-based blocking exists. The robots.txt has no AI-bot directives at all; it uses a non-standard Content-Signal: ai-train=yes, search=yes, ai-input=yes header that no major crawler recognizes. The site runs on Cloudflare with a Next.js stack (x-powered-by: Next.js), serving server-rendered HTML (477 words visible on homepage, no JS-shell risk). The llms.txt at /llms.txt is exceptional — 6,600+ bytes with canonical domains, preferred summaries, URL maps by user intent, and explicit guidance for AI assistants including disclaimers and forbidden behaviors. This is among the most mature llms.txt implementations observed.

Cold-Knowledge Gap

The LLM's prior knowledge describes Gusto as serving 300,000+ businesses and mentions a "Gusto for Enterprise" offering. The actual site claims 500,000+ businesses and makes no mention of an enterprise tier — the top plan is "Premium" at $180/mo. The model also references a "Gusto Wallet" earned-wage-access app and mentions 2023-2024 tax-filing complaints, neither of which appears anywhere on the current site. The site positions itself around "Payroll, HR, Benefits. Simplified." and emphasizes the all-in-one platform for SMBs, but the cold model still describes it primarily as a payroll company with add-on HR — a positioning gap of roughly 2-3 years.

Schema Posture

Zero JSON-LD schema was found on any page probed: homepage, pricing, product, about, press, blog, or Spanish product page. No Organization, Product, FAQPage, BreadcrumbList, SoftwareApplication, or WebSite schema exists. This is a severe deficiency for AI answer engines (Google SGE, ChatGPT Browse, Perplexity) that rely on structured data to extract entity relationships, pricing, and feature comparisons. The pricing page has 13 FAQ items rendered as plain H3 headings with no FAQPage markup. The compare page has a feature comparison table (Gusto vs ADP Run) with no Table or Comparison schema.

External Signals

Press coverage is strong and current: Fast Company named Gusto #1 Most Innovative Company in HR (2025), Forbes Cloud 100 (#17), Fortune confirmed cash-flow positivity (2024), and Bloomberg/TechCrunch/CNBC cover its AI strategy and small-business data insights. The DNS TXT records show OpenAI domain verification (openai-domain-verification=dv-...) and Anthropic domain verification (anthropic-domain-verification-...), confirming Gusto has proactively registered with both major AI platforms for potential crawler or API access — yet the robots.txt does not reflect any AI-bot rules. The /ai/gus-assistant URL redirects to the homepage with no dedicated AI assistant page, despite the llms.txt mentioning no AI product by that name.

Findings

1. Zero JSON-LD schema on any page probed High

   No Organization, Product, FAQPage, SoftwareApplication, or WebSite schema was found on the homepage, pricing, product, about, press, blog, or Spanish product page. This severely limits extraction by AI answer engines like Google SGE, ChatGPT Browse, and Perplexity.

   What to change: Add JSON-LD schema for Organization, WebSite, SoftwareApplication, FAQPage, and BreadcrumbList to all relevant pages. Ensure pricing and comparison pages include Product and Offer schema.

2. Pricing page FAQ items lack FAQPage schema High

   The pricing page contains 13 FAQ items rendered as plain H3 headings with no FAQPage markup, missing an opportunity for rich results in AI answer engines.

   What to change: Wrap the FAQ section in FAQPage schema with Question/Answer pairs.

3. Comparison page feature table lacks structured data Medium

   The compare page (Gusto vs ADP Run) has a feature comparison table with no Table or Comparison schema, reducing its visibility in AI-generated comparisons.

   What to change: Add Comparison or Table schema to the feature comparison table.

4. Robots.txt has no AI-bot directives despite domain verification Medium

   The robots.txt contains no rules for GPTBot, ClaudeBot, PerplexityBot, or other AI crawlers, even though DNS TXT records show OpenAI and Anthropic domain verification. The non-standard Content-Signal header is ignored by all major crawlers.

   What to change: Add explicit Allow/Disallow rules for GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, and other AI crawlers in robots.txt.

5. Cold LLM knowledge lags current site positioning by 2-3 years Medium

   The LLM's prior knowledge describes Gusto as serving 300,000+ businesses with a 'Gusto for Enterprise' offering, while the site claims 500,000+ businesses and offers only 'Premium' as the top plan. The model also references a 'Gusto Wallet' app and 2023-2024 tax-filing complaints not present on the site.

   What to change: Publish updated company facts (customer count, product tiers) in structured data and the llms.txt to correct AI knowledge.

6. AI assistant page redirects to homepage Medium

   The URL /ai/gus-assistant redirects to the homepage with no dedicated AI assistant page, despite the llms.txt mentioning no AI product by that name.

   What to change: Create a dedicated page for the AI assistant (Gus) with product details, capabilities, and schema markup.

7. Web search for reviews and complaints returned zero results Low

   Searches for 'Gusto payroll reviews 2024 2025 problems complaints' and 'Gusto payroll site:reddit.com' returned zero results, indicating poor external signal indexing or search limitations.

   What to change: Encourage customer reviews on third-party sites and ensure review pages are crawlable and indexed.

What's working

• Exceptional llms.txt implementation — The llms.txt at /llms.txt is 6,600+ bytes with canonical domains, preferred summaries, URL maps by user intent, and explicit guidance for AI assistants including disclaimers and forbidden behaviors. This is among the most mature implementations observed.
• Server-rendered HTML with no JS-shell risk — All pages probed return full HTML content (477+ words) with no JavaScript dependency for content, ensuring AI crawlers can extract text without rendering.
• All major AI crawlers receive 200 with full content — GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, Bytespider, and Applebot-Extended all receive a 200 status with full HTML from the homepage. No UA-based blocking exists.
• OpenAI and Anthropic domain verification in DNS — DNS TXT records show openai-domain-verification and anthropic-domain-verification entries, confirming proactive registration with both major AI platforms for potential crawler or API access.
• Strong and current press coverage — Fast Company named Gusto #1 Most Innovative Company in HR (2025), Forbes Cloud 100 (#17), Fortune confirmed cash-flow positivity (2024), and Bloomberg/TechCrunch/CNBC cover its AI strategy and small-business data insights.
• Spanish-language product page available — A fully translated Spanish product page exists at /es/product with 1007 words of content, expanding reach to Spanish-speaking audiences.