unitedlex.com — AI Site Grade

Analysis

UnitedLex: A Technically Open Site with a Cold-Knowledge Gap and a Phantom Product Problem

The homepage's JSON-LD dateModified field reads "2026-05-29" — a date over a year in the future — while the site's oldest news articles date to 2020 and the Wayback Machine holds no snapshot at all, creating a temporal contradiction that AI crawlers ingest as structured metadata.

Crawler Access

All major AI crawlers — GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, Applebot-Extended, Bytespider, anthropic-ai — receive a full 200 response with identical byte payload (~421 KB) to a browser baseline. No UA-based blocking exists. The robots.txt is a bare Yoast-generated file (User-agent: * Disallow:) with zero AI-specific directives. No llms.txt exists (404). The site runs on Cloudflare (CDN) proxying to Kinsta (hosting, via ki-cache-tag and ki-edge headers), with DNS on AWS Route53 and email via Microsoft 365. No JS-rendering risk: the homepage delivers ~945 words of visible text on plain GET.

Cold-Knowledge Gap

The LLM's prior knowledge describes UnitedLex as having a "Legal Operating System" (LOS) platform integrating AI, contract analytics, and workflow automation — and mentions a 2023 lawsuit from a former client alleging breach of contract and data security issues. Neither of these facts appears anywhere on the live site. The site makes zero mention of an "LOS" platform. The closest named products are Vantage for IP, Digital First Draft, RAPID Review, RAPID PrivLog, Digital Fact Binder, First Look, and LexLoan. The alleged lawsuit could not be verified through any search or on-site reference. The gap between what the model "knows" and what the site actually presents is wide and potentially damaging: an AI engine citing a phantom product name and unverified litigation risk.

Schema Posture

The homepage carries a well-structured WebPage / WebSite / Organization schema graph with logo, breadcrumb, and search action. The AI services page adds a Service schema with OfferCatalog. However, no FAQPage, Product, SoftwareApplication, or HowTo schema exists anywhere — surprising for a company that sells named AI tools and data platforms. The Organization schema lacks foundingDate, foundingLocation, numberOfEmployees, sameAs links, or knowsAbout fields that would help AI engines contextualize the brand.

External Signals

DuckDuckGo returned zero search results for queries about UnitedLex — no press, no reviews, no Reddit threads, no news. This is an extreme signal of low external citation density. The site's own news section (80+ articles) covers acquisitions (Paul Hastings DSAI team, iRunway, Blackstone Discovery), partnerships (Polsinelli, DXC Technology, GE, Credit Suisse), and awards (Chambers, Legalweek, ACC Value Champions), but none of these stories appear to have generated indexed external coverage visible to the search tool used. The careers page links to Oracle Cloud for job applications.

Structural Issues

The /about-us/ URL returns a 404; the actual about page lives at /about-unitedlex/ (with a 301 redirect from /company/). The /technology/ URL redirects to /technology-industry/ — a page about serving the technology sector, not about UnitedLex's own technology stack. The site's navigation menu is duplicated three times in the HTML body (header, mobile menu, footer), bloating every page's text payload for AI crawlers. The "Insights" section contains substantive white papers and articles, but none carry Article schema with full author, date, or estimated reading time — only the Yoast-generated graph.

Findings

1. Homepage JSON-LD contains a future date (2026-05-29) Medium

   The homepage's JSON-LD `dateModified` field is set to 2026-05-29, over a year in the future, creating a temporal contradiction that AI crawlers ingest as structured metadata.

   What to change: Update the `dateModified` field in the JSON-LD to reflect the actual last modification date of the page.

2. LLM prior knowledge includes a 'Legal Operating System' platform not found on the site High

   The LLM's prior knowledge describes UnitedLex as having a 'Legal Operating System' (LOS) platform, but the live site makes no mention of LOS. The closest named products are Vantage, Digital First Draft, RAPID Review, etc. This gap may cause AI engines to cite a phantom product name.

   What to change: Ensure the site prominently features all current product names and platforms, and consider adding a product page or schema for each named offering.

3. LLM prior knowledge references an unverified 2023 lawsuit High

   The LLM's prior knowledge mentions a 2023 lawsuit from a former client alleging breach of contract and data security issues. No evidence of this lawsuit was found on the site or through web searches. This unverified litigation risk could be cited by AI engines.

   What to change: If the lawsuit is resolved or irrelevant, consider publishing a statement or press release to clarify the situation. If it is ongoing, ensure the site addresses it transparently.

4. /about-us/ returns a 404 error Medium

   The URL /about-us/ returns a 404 page. The actual about page is at /about-unitedlex/ (with a 301 redirect from /company/). This broken link may confuse crawlers and users.

   What to change: Implement a 301 redirect from /about-us/ to /about-unitedlex/ or create a proper page at /about-us/.

5. /technology/ redirects to a page about serving the technology sector, not UnitedLex's own tech stack Medium

   The URL /technology/ redirects to /technology-industry/, which describes how UnitedLex serves technology companies, not the company's own technology platform. This misdirects crawlers and users seeking information about UnitedLex's technology.

   What to change: Create a dedicated page at /technology/ that describes UnitedLex's own technology stack, platforms, and AI capabilities.

6. Navigation menu duplicated three times in HTML body Low

   The site's navigation menu appears three times in the HTML body (header, mobile menu, footer), bloating every page's text payload for AI crawlers and potentially diluting content relevance.

   What to change: Consolidate navigation menus into a single semantic structure using CSS to show/hide for different viewports.

7. Insights pages lack Article schema with author, date, and reading time Medium

   The Insights section contains substantive white papers and articles, but none carry Article schema with full author, date, or estimated reading time. Only the Yoast-generated graph is present, which may limit rich snippet eligibility.

   What to change: Add Article schema markup to each insight page, including author, datePublished, dateModified, and estimated reading time.

8. No llms.txt file exists Low

   The site returns a 404 for /llms.txt, missing an opportunity to guide AI crawlers to key pages and provide a structured summary of the site's content.

   What to change: Create an llms.txt file that lists important pages and provides a brief description of the site's content for AI crawlers.

9. DuckDuckGo returns zero search results for UnitedLex High

   DuckDuckGo returned zero results for queries about UnitedLex, indicating extremely low external citation density. This may limit the site's visibility in AI-generated answers that rely on web signals.

   What to change: Investigate the cause of low search engine indexing and consider improving off-site SEO through press releases, backlinks, and social media presence.

10. Organization schema lacks founding date, location, employee count, and sameAs links Medium

    The Organization schema on the homepage is missing fields like foundingDate, foundingLocation, numberOfEmployees, sameAs, and knowsAbout, which would help AI engines contextualize the brand.

    What to change: Add the missing fields to the Organization schema, including foundingDate, foundingLocation, numberOfEmployees, sameAs links to social profiles, and knowsAbout for key topics.

11. No FAQPage, Product, or SoftwareApplication schema on product pages Medium

    Despite selling named AI tools and data platforms, the site does not use FAQPage, Product, or SoftwareApplication schema on relevant pages, missing opportunities for rich results.

    What to change: Add Product or SoftwareApplication schema to pages describing specific tools, and consider FAQPage schema for common questions.

What's working

• All major AI crawlers receive full 200 response with identical content — All tested AI crawlers (GPTBot, ClaudeBot, PerplexityBot, etc.) receive a full 200 response with the same byte payload as a browser, with no UA-based blocking.
• Homepage carries well-structured WebPage/WebSite/Organization schema graph — The homepage includes a comprehensive schema graph with WebPage, WebSite, and Organization types, including logo, breadcrumb, and search action.
• AI services page includes Service schema with OfferCatalog — The /ai-legal-services/ page includes a Service schema with OfferCatalog, helping AI engines understand the services offered.
• Sitemap index file exists with 80 URLs — The sitemap index at /sitemap_index.xml contains 80 URLs, providing a clear map of the site for crawlers.
• Homepage delivers ~945 words of visible text on plain GET without JavaScript — The homepage serves substantial text content without requiring JavaScript rendering, ensuring AI crawlers can access the content easily.
• News section contains 80+ articles covering acquisitions and partnerships — The site's news section has over 80 articles detailing acquisitions, partnerships, and awards, providing rich content for AI crawlers.