veriforce.com — AI Site Grade

Analysis

I have enough to write a thorough audit. Let me compile it.

Veriforce's homepage JSON-LD declares a dateModified of 2026-05-26 -- a date over a year in the future -- which is a schema integrity failure that undermines the temporal credibility AI engines rely on for freshness signals.

Crawler Access

All major AI crawlers -- GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, ChatGPT-User, Applebot-Extended, anthropic-ai, Perplexity-User -- receive a 200 with full HTML content identical to browser delivery. No UA-based blocking, no JS shell, no Cloudflare challenge. The site runs on nginx behind WP Engine hosting with AWS DNS, and returns a full ~83KB page to every bot tested. The robots.txt is a bare Yoast-generated file with a User-agent: * Disallow: (empty disallow, i.e., allow all) and no AI-specific directives whatsoever. No llms.txt exists (404). The sitemap index is present and well-formed with 13 sub-sitemaps covering ~1,000+ URLs.

Cold-Knowledge Gap

The LLM's cold knowledge describes Veriforce as an oil-and-gas-focused safety training firm founded in 1999, mentioning the "Veriforce OQSG" standard and an acquisition of ISNetworld's contractor management business in 2019. The actual site tells a different story: Veriforce was founded in 1993 (not 1999), positions itself as a supply chain risk management (SCRM) platform, and its recent acquisitions are ComplyWorks (2020), CHAS UK, and Highwire (October 2025) -- not ISNetworld. The model's prior is stale by roughly 5 years, anchored to an older industry identity. The site now emphasizes "3,200 hiring clients, 140,000+ contractors, 140+ countries" and a platform called VeriforceONE, none of which appear in the cold knowledge.

Schema Posture

Every page carries the same three-schema graph: WebPage, BreadcrumbList, WebSite, and Organization. The Organization block includes sameAs links to Facebook, X, and LinkedIn but no description, foundingDate, foundingLocation, or numberOfEmployees properties. The homepage WebPage schema has a dateModified of 2026-05-26 -- a future date that will trigger freshness skepticism in any AI engine parsing it. No FAQPage, Product, SoftwareApplication, or HowTo schema exists anywhere on the site, despite the site offering a SaaS platform with subscription tiers and feature comparisons. The contractor subscription page describes four distinct plans (Compliance Pro, ComplyWorks Global, VeriSource, CHAS UK) with pricing tiers, yet uses zero structured data to represent them.

External Signals

The press room reveals an aggressive acquisition strategy: ComplyWorks (2020), CHAS UK, Global Worker Pass, and most recently Highwire (October 2025). The Highwire acquisition extends Veriforce into construction and capital projects (data centers, life sciences, healthcare). The site also references a psychological safety study and partnerships with WithU (workplace wellness) and SiteDocs (safety management). However, web search for external coverage (G2 reviews, news articles, Reddit threads) returned zero results -- the brand has minimal third-party digital footprint discoverable via search, which limits the external signals AI engines can triangulate.

Structural Surprises

The /company/about-us URL returns a 404, while the actual about page lives at /company/about with a redirect from /company. The newsroom lives at /company/newsroom but the sitemap references /company/press-room URLs. The site has no FAQ pages, no comparison tables, and no pricing page -- critical gaps for an AI engine trying to answer "how does Veriforce compare to ISNetworld or Avetta?" or "what does it cost?" The homepage claims "40 years of Contractor Management" (implying founding ~1985) while the about page says "since 1993" -- a contradictory founding narrative across two core pages.

Findings

1. Homepage JSON-LD dateModified set to future date 2026-05-26 High

   The homepage WebPage schema declares a dateModified of 2026-05-26, over a year in the future. This schema integrity failure undermines temporal credibility signals for AI engines.

   What to change: Update the dateModified property to the actual last modification date or remove it if not maintained.

2. LLM cold knowledge is 5+ years out of date High

   The LLM's prior knowledge describes Veriforce as an oil-and-gas safety training firm founded in 1999, with an acquisition of ISNetworld's contractor management business in 2019. The actual site shows a founding in 1993, a supply chain risk management platform, and acquisitions of ComplyWorks, CHAS UK, and Highwire. This gap means AI engines may serve incorrect information about the company.

   What to change: Publish a comprehensive llms.txt file and ensure key facts (founding date, acquisitions, platform name) are consistently marked up in schema and visible on the site.

3. No SoftwareApplication or Product schema for SaaS platform High

   Despite offering a SaaS platform (VeriforceONE) with subscription tiers and feature comparisons, the site uses no SoftwareApplication, Product, or FAQPage schema. This prevents AI engines from understanding the product offering and answering comparison or pricing queries.

   What to change: Add SoftwareApplication schema to product pages, including applicationCategory, offers, and feature list. Consider FAQPage for common questions.

4. Contradictory founding dates across homepage and about page Medium

   The homepage claims '40 years of Contractor Management' (implying founding ~1985) while the about page states 'since 1993'. This inconsistency confuses AI engines and erodes trust.

   What to change: Align the founding year across all pages. Update the homepage tagline to match the about page's 'since 1993'.

5. No external search results for brand reviews or news Medium

   Web searches for Veriforce reviews on G2, news articles, and Reddit threads returned zero results. This minimal third-party digital footprint limits the external signals AI engines can use to validate the brand.

   What to change: Encourage customers to leave reviews on G2, Capterra, and other platforms. Issue press releases to news outlets to generate coverage.

6. No llms.txt file for AI crawlers Medium

   The site returns a 404 for llms.txt, missing an opportunity to provide AI engines with a curated summary of key facts and resources.

   What to change: Create an llms.txt file with a brief company description, key pages, and structured data hints.

7. /company/about-us returns 404 Low

   The URL /company/about-us returns a 404 page, while the actual about page is at /company/about. This broken link may confuse crawlers and users.

   What to change: Redirect /company/about-us to /company/about or add a proper page at that URL.

8. No FAQ, comparison, or pricing pages Medium

   The site lacks FAQ pages, comparison tables against competitors, and a pricing page. These are critical for AI engines to answer common queries about the product.

   What to change: Create FAQ pages for common questions, a pricing page, and comparison pages against competitors like ISNetworld and Avetta.

9. Organization schema missing description and foundingDate Medium

   The Organization schema on every page includes sameAs links but lacks description, foundingDate, foundingLocation, and numberOfEmployees properties, reducing its usefulness for knowledge panels.

   What to change: Add description, foundingDate, foundingLocation, and numberOfEmployees to the Organization schema.

10. Sitemap references /company/press-room but actual page is at /company/newsroom Low

    The sitemap lists URLs under /company/press-room, but the actual press room page is at /company/newsroom. This mismatch may cause crawl errors.

    What to change: Update the sitemap to use the correct /company/newsroom URLs or set up redirects from /company/press-room to /company/newsroom.

What's working

• All major AI crawlers receive full HTML content — Every tested AI crawler (GPTBot, ClaudeBot, PerplexityBot, etc.) receives a 200 response with full HTML, identical to browser delivery. No blocking, JS shells, or challenges.
• Sitemap index is present and well-formed with 13 sub-sitemaps — The sitemap index at /sitemap_index.xml is accessible and contains 13 sub-sitemaps covering ~1,000+ URLs, aiding crawler discovery.
• Every page includes a consistent three-schema graph — All pages carry WebPage, BreadcrumbList, WebSite, and Organization schema, providing a baseline structured data foundation.
• Press room documents recent acquisitions and partnerships — The press room contains detailed press releases about acquisitions (ComplyWorks, CHAS UK, Highwire) and partnerships (WithU, SiteDocs), providing rich content for AI engines.
• robots.txt allows all crawlers with no AI-specific blocks — The robots.txt file has a User-agent: * with empty disallow, meaning all crawlers are allowed. No AI-specific directives block any bot.