workwave.com — AI Site Grade

Analysis

Cold-Knowledge Gap: IFS Acquisition Misdated by Four Years

The LLM cold knowledge states WorkWave was "acquired by IFS in 2021." The actual press release on workwave.com/newsroom/ifs-extends-leadership-in-service-management-with-the-acquisition-of-workwave confirms the acquisition closed September 28, 2017 — a four-year error. The cold knowledge also lists "WorkWave Service" and "WorkWave Route Manager" as core products, but the site's product portfolio has evolved significantly: the current lineup centers on PestPac, RealGreen, WinTeam, Lighthouse, RouteManager, and Wavelytics, with no mention of a product called "WorkWave Service." The cold knowledge names Chris Sullens as CEO-era context, but the site's leadership page shows Kevin Kemmerer as CEO and a board chaired by Jesper Andersen.

Crawler Access

All major AI crawlers — GPTBot, ClaudeBot, PerplexityBot, Google-Extended, ChatGPT-User, OAI-SearchBot, Applebot-Extended — receive a 200 status with full HTML content on the homepage. The robots.txt is a minimal User-agent: * Allow: / with no AI-specific rules. Only Bytespider is blocked (403). The site runs on Cloudflare with AWS DNS, serves server-rendered HTML (no JS shell), and includes an anthropic-domain-verification TXT record, indicating proactive AI-ecosystem engagement. The llms.txt is a standout: comprehensive, well-structured, covering company info, all product brands, industries, and key pages with direct URLs.

Schema Posture

The homepage carries a single Organization schema with correct name, address, contact point, and social links. It lists RealGreen, PestPac, and TEAM Software as sub-organizations. However, every other page fetched — /company, /leadership, /blog, /wavelytics, /fintech, /industries, /private-equity — contains zero JSON-LD schema. The /newsroom press release page is the only subpage with schema, using NewsArticle. The blog has no Article or BlogPosting schema. The /leadership page has no Person schema for any executive. The /private-equity page has no Organization or Service schema.

Content and Answer Signals

The homepage delivers 376 words of visible text with a clear H1, multiple H2s, and comparison language ("No other field service software comes close"). No FAQ schema, no tables, no definition lists. The /fintech page is the richest at 3,112 words with an embedded interview transcript and a FAQ section — but no FAQPage schema. Blog posts like the AI article (1,166 words) have strong heading structure but no schema. The /insights page lists a press release titled "IFS Extends Leadership in Service Management with the Acquisition of WorkWave" — confirming the 2017 date — but the linked blog post "Why WorkWave's Doubling Down on Data & AI" returns a 404.

External Signals

The site's DNS includes verification tokens for Anthropic, Apple, Google, Facebook, Canva, Atlassian, DocuSign, KnowBe4, and Virtru — an unusually broad set of third-party verifications indicating active multi-platform presence management. The llms.txt references a Marketplace at marketplace.workwave.com, a Private Equity partner program, and a Sustainability commitment with SBTi targets. The newsroom shows active press coverage through April 2026, including product launches for Wavelytics and WAIve AI.

Findings

1. IFS acquisition misdated by four years in LLM cold knowledge High

   LLM cold knowledge states WorkWave was acquired by IFS in 2021, but the actual press release confirms the acquisition closed September 28, 2017. This four-year error may cause AI-generated answers to misrepresent the company's timeline.

   What to change: Ensure the acquisition date is prominently and consistently mentioned on the site, especially on the newsroom page and in structured data, to correct the LLM knowledge gap.

2. Missing JSON-LD schema on most subpages High

   Only the homepage and the newsroom press release page contain JSON-LD schema. All other fetched pages — including /company, /leadership, /blog, /wavelytics, /fintech, /industries, and /private-equity — have zero schema markup. This limits AI understanding of page content and entity relationships.

   What to change: Add appropriate JSON-LD schema to all subpages: Organization or WebSite for company pages, Person for leadership, Article or BlogPosting for blog posts, FAQPage for FAQ sections, and Service for product pages.

3. FAQ section on /fintech page lacks FAQPage schema Medium

   The /fintech page contains a FAQ section with questions and answers, but no FAQPage schema is present. This prevents AI crawlers from directly extracting Q&A pairs for rich results.

   What to change: Add FAQPage schema markup to the FAQ section on the /fintech page.

4. Leadership page missing Person schema for executives Medium

   The /leadership page lists executives including CEO Kevin Kemmerer and board chair Jesper Andersen, but no Person schema is present. This limits AI understanding of key people associated with the company.

   What to change: Add Person schema for each executive listed on the leadership page, including name, job title, and image.

5. Blog posts missing Article or BlogPosting schema Medium

   The blog page and individual blog posts lack Article or BlogPosting schema, reducing the likelihood of appearing in Google's rich results and limiting AI extraction of article metadata.

   What to change: Add Article or BlogPosting schema to all blog posts, including headline, datePublished, author, and image.

6. Blog post link in /insights returns 404 Medium

   The /insights page links to a blog post titled 'Why WorkWave's Doubling Down on Data & AI', but the URL returns a 404 error. This creates a dead end for users and crawlers.

   What to change: Restore the blog post or remove the broken link from the /insights page.

7. LLM cold knowledge lists outdated product names Medium

   LLM cold knowledge mentions 'WorkWave Service' and 'WorkWave Route Manager' as core products, but the current site portfolio centers on PestPac, RealGreen, WinTeam, Lighthouse, RouteManager, and Wavelytics. This mismatch may cause AI to reference discontinued or renamed products.

   What to change: Ensure the site clearly lists current product names and descriptions, and consider updating external knowledge sources or using structured data to reinforce the correct product lineup.

8. LLM cold knowledge names outdated CEO Medium

   LLM cold knowledge references Chris Sullens as CEO-era context, but the site's leadership page shows Kevin Kemmerer as CEO. This discrepancy may lead AI to provide incorrect executive information.

   What to change: Prominently display the current CEO and leadership team on the site, and consider adding Person schema to reinforce accurate information.

9. Homepage lacks FAQ schema despite comparison language Low

   The homepage uses comparison language ('No other field service software comes close') but has no FAQ schema, tables, or definition lists that could help AI extract key differentiators.

   What to change: Consider adding FAQ schema or a comparison table with structured data to highlight differentiators.

10. Bytespider crawler blocked with 403 Low

    The Bytespider crawler receives a 403 Forbidden response, preventing it from indexing the site. While this may be intentional, it limits visibility on certain AI platforms.

    What to change: If Bytespider access is desired, update server configuration to allow it.

What's working

• Comprehensive llms.txt file with detailed site structure — The llms.txt file is well-structured, covering company info, all product brands, industries, and key pages with direct URLs. This provides AI crawlers with a clear map of the site's content.
• All major AI crawlers receive full HTML content — GPTBot, ClaudeBot, PerplexityBot, Google-Extended, ChatGPT-User, OAI-SearchBot, and Applebot-Extended all receive 200 status with full HTML content on the homepage. The robots.txt has no AI-specific blocks.
• Server-rendered HTML with no JavaScript shell — The site serves server-rendered HTML, ensuring all content is immediately accessible to crawlers without requiring JavaScript execution.
• Anthropic domain verification TXT record present — The DNS includes an anthropic-domain-verification TXT record, indicating proactive engagement with the AI ecosystem and enabling potential use of Claude's extended features.
• Broad set of third-party verification tokens in DNS — DNS includes verification tokens for Anthropic, Apple, Google, Facebook, Canva, Atlassian, DocuSign, KnowBe4, and Virtru, indicating active multi-platform presence management.
• Homepage includes Organization schema with sub-organizations — The homepage carries a single Organization schema with correct name, address, contact point, social links, and lists RealGreen, PestPac, and TEAM Software as sub-organizations.
• Newsroom press release page uses NewsArticle schema — The /newsroom press release page includes NewsArticle schema, helping AI understand the article's headline, date, and publisher.
• Active press coverage through April 2026 — The newsroom shows recent press releases including product launches for Wavelytics and WAIve AI, demonstrating ongoing communication and content freshness.