AI Site Grade

beneschlaw.com — AI Site Grade

Benesch Law's llms.txt lists a default WordPress 'Hello world!' post and every page's Organization schema sets legalName to 'ashrider' instead of the firm's actual legal name.

Benesch Law's AI visibility is undermined by a broken llms.txt, a site-wide structured data error, JS-rendered attorney profiles, and a cold-knowledge gap that misses the firm's growth narrative.

Findings
8
Evidence checks
19
Completed
30 May 2026

Analysis

I have enough data to write the audit. Let me compile the findings.

Key findings summary:

1. llms.txt exists but is broken — It includes a "Hello world!" default WordPress post (published April 2025, never deleted) and lists it as a key page for LLMs. The llms.txt is generated by Rank Math SEO but the plugin clearly ingested the stale post.

2. legalName: "ashrider" — Every page's Organization schema has legalName set to "ashrider" (likely a WordPress admin username) instead of the actual legal name "Benesch Friedlander Coplan & Aronoff LLP". This is a structured data error that propagates across the entire site.

3. No AI-bot rules in robots.txt — The robots.txt has only a wildcard rule disallowing /wp-admin/. No GPTBot, ClaudeBot, PerplexityBot, Google-Extended, or any other AI crawler is mentioned. However, compare_bot_access shows all bots get full 200 responses with identical content — so the lack of rules is not blocking, but it's also not guiding.

4. Cold knowledge gap — The LLM knows Benesch as an Am Law 200 firm founded in 1938, strong in transportation/logistics, corporate/M&A, and litigation. The site itself emphasizes "high performance," "new breed of national law firm," rapid growth (99% in 5 years), and lateral hiring from Am Law 100. The cold knowledge doesn't capture the aggressive growth narrative or the "Better with Benesch" brand positioning.

5. JS-rendered pages — The /our-people/ page returns only 23 words of visible text ("Keyword Search loading") — it's a JavaScript shell. AI crawlers get the same thin content. Attorney profiles are invisible to crawlers.

6. Redirect issue/practice/transportation-logistics/ redirects to a 2012 insight article about China's 12th Five-Year Plan, not a practice page. The canonical practice page URL structure is unclear.

7. Stale content — The transportation insight page references a summer clerk from 2011 and contact emails with old phone numbers. Published 2023 but content is from 2011-2012.

8. No FAQ schema, no comparison tables — Despite having rich practice descriptions and "What Sets Us Apart" sections, none use FAQPage schema or structured comparison markup.

Now writing the audit.

Benesch Law — AI-Visibility Audit

The site publishes an llms.txt file — a rare and forward-leaning move for a law firm — but it lists a default WordPress "Hello world!" post as a key page for LLMs to read, alongside a legalName field set to "ashrider" (a WordPress admin username) across every page's Organization schema.

Crawler Access & Infrastructure

All major AI crawlers — GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, Bytespider, Applebot-Extended — receive full 200 responses with identical content to a browser. No UA-based blocking exists. The robots.txt contains only a single wildcard rule disallowing /wp-admin/ and names no AI bots explicitly. The site runs on nginx behind Varnish cache (Pantheon hosting) with a 604800-second cache header, meaning crawlers hit cached copies. The llms.txt (318 KB, generated by Rank Math SEO) exists and is served — a strong signal — but its content is polluted by the uncategorized "Hello world!" post and a Confidentiality Notice page that should not be an LLM entry point.

Structured Data Errors

Every page on the site — homepage, practice pages, news, the "Hello world!" post — emits the same Organization JSON-LD block with "legalName": "ashrider". The actual legal name is Benesch Friedlander Coplan & Aronoff LLP, which appears correctly in the homepage's name field but is overwritten by the username string in legalName. This error propagates across all 29+ sitemaps and hundreds of pages. No FAQPage schema exists anywhere, despite multiple "What Sets Us Apart" sections that are natural FAQ candidates. The WebSite schema includes SearchAction with a correct target URL.

Cold-Knowledge Gap

An LLM queried cold describes Benesch as a "full-service Am Law 200 firm based in Cleveland, founded in 1938" with a "strong transportation and logistics practice." The site itself tells a different story: "a new breed of high performing national law firm" that has grown 99% in 5 years, recruited 50+ laterals from Am Law 100 firms, and climbed from unranked to #116 on the Am Law 200. The cold knowledge misses the aggressive growth narrative, the "Better with Benesch" tagline, the 85% lateral retention rate, and the firm's positioning as agile/entrepreneurial. The site's emphasis on culture (Chief Culture Officer, "Legends of Culture" podcast, "100 Most Loved Workplaces") is entirely absent from the model's prior.

Content Delivery Issues

The /our-people/ page returns 23 words of visible text — a JavaScript shell ("Keyword Search loading") — meaning attorney profiles are invisible to crawlers. The /practice/transportation-logistics/ URL redirects to a 2012 insight article about China's 12th Five-Year Plan, not a practice overview. That article references a summer clerk from 2011 and contains outdated contact information. The news section is rich and current (May 2026 press releases), but practice pages and insight articles mix content spanning 2011–2026 without freshness signals. No dateModified differentiation in schema between genuinely updated and truly stale pages.

Findings

  1. llms.txt lists default WordPress 'Hello world!' post as key page High

    The llms.txt file includes a default WordPress post titled 'Hello world!' (published April 2025) as a key page for LLMs, polluting the file with irrelevant content.

    What to change: Remove the 'Hello world!' post from the llms.txt file and ensure only relevant, high-quality pages are listed.

  2. Organization schema legalName set to 'ashrider' site-wide High

    Every page's Organization JSON-LD block has legalName set to 'ashrider' (a WordPress admin username) instead of the actual legal name 'Benesch Friedlander Coplan & Aronoff LLP'.

    What to change: Update the Organization schema to set legalName to 'Benesch Friedlander Coplan & Aronoff LLP' across all pages.

  3. Attorney profile page renders as JavaScript shell High

    The /our-people/ page returns only 23 words of visible text ('Keyword Search loading'), meaning attorney profiles are invisible to AI crawlers.

    What to change: Implement server-side rendering or pre-rendering for the /our-people/ page to ensure content is accessible to crawlers.

  4. Transportation practice URL redirects to stale insight article High

    The /practice/transportation-logistics/ URL redirects to a 2012 insight article about China's 12th Five-Year Plan, not a practice overview. The article contains outdated contact information and references a summer clerk from 2011.

    What to change: Restore the transportation practice page to a proper overview or set up a correct canonical URL.

  5. Cold LLM knowledge misses aggressive growth narrative Medium

    LLMs queried cold describe Benesch as a traditional Am Law 200 firm, but the site emphasizes rapid growth (99% in 5 years), lateral hiring from Am Law 100, and a 'new breed' positioning. This narrative is not captured in external knowledge.

    What to change: Ensure the site's unique value proposition and growth metrics are prominently featured in structured data and key pages to influence AI training data.

  6. No FAQPage schema on practice pages with FAQ-like content Medium

    Multiple practice pages contain 'What Sets Us Apart' sections that are natural FAQ candidates, but none use FAQPage schema.

    What to change: Add FAQPage schema to practice pages that include question-and-answer style content.

  7. Robots.txt does not name any AI crawlers Low

    The robots.txt file only has a wildcard rule disallowing /wp-admin/ and does not explicitly allow or disallow AI bots like GPTBot or ClaudeBot.

    What to change: Add explicit rules for AI crawlers to signal that crawling is welcome and to guide them to important pages.

  8. Practice pages and insights mix stale and fresh content without freshness signals Medium

    The site contains content spanning 2011–2026, but stale pages lack dateModified differentiation, making it hard for crawlers to assess freshness.

    What to change: Add accurate dateModified schema to all pages and consider removing or updating outdated content.

What's working

  • llms.txt file published and served — The site publishes an llms.txt file (318 KB) generated by Rank Math SEO, a rare and forward-leaning move for a law firm that signals AI readiness.
  • All major AI crawlers receive full 200 responses — All tested AI crawlers (GPTBot, ClaudeBot, etc.) receive full 200 responses with identical content to a browser, with no UA-based blocking.
  • WebSite schema includes SearchAction with correct target — The WebSite schema includes a SearchAction with a correct target URL, enabling AI tools to perform site search.
  • News and insights section is current and rich — The news section contains press releases dated as recently as May 2026, providing fresh content for AI crawlers.
  • Sitemap submitted and contains 80 URLs — The sitemap is accessible and contains 80 URLs, helping crawlers discover site content.

Track beneschlaw.com across AI search

This is one snapshot. Open the interactive report to inspect evidence, or grade another site free.

Open this AI Site Grade Grade another site Track your brand