Independent technical audit

courtrules.app

Overall AI readiness score

A combined result across all audit signals.

Average

AI readiness audit: 10/29/2026Public technical data

About the site

Court Rules is a free reference for U.S. federal and state court rules, covering local rules, individual judge standing orders, court holidays and a filing-deadline calculator. It includes over 600 federal judges' standing orders across 20 federal districts plus a state-court beta, with each rule linked to its source document. A public API and remote MCP server are available for developers and assistants.

Category:: Public sector and non-profit
Platform:: Drupal

Written by AI from the site’s llms.txt and homepage.

Overall AI readiness assessment

How ready courtrules.app is for AI systems

67/100

Court Rules was independently audited by llmsmap. courtrules.app currently scores 67/100 for AI readiness. The result combines AI-specific files, crawler policy, sitemap discovery, structured homepage data, and—when available—the mobile Google Lighthouse technical profile.

Audit context

llms.txt is accessible and contains 603 tokens. No accessible llms-full.txt was detected, so deeper context still has to be assembled from regular pages. No separate ai.txt policy was detected; it is optional, but can clarify training, retrieval, and attribution preferences.

robots.txt is available. 11 of 11 tracked AI bots are not blocked. Declared sitemaps: 2. No Schema.org type was detected on the homepage. 0 OpenGraph tags were found and markup completeness is 0%, leaving more entity interpretation to crawlers.

The mobile Lighthouse profile adds Performance 79/100, Accessibility 100/100, Best Practices 100/100, SEO 100/100, and experimental Agentic Browsing 100/100. These signals have a limited weight: they complement rather than replace llms.txt, robots.txt, and structured-data checks.

Confirmed strengths

Accessible llms.txt
2 sitemap declarations
Strong Google agentic signals

Priority improvements

1Add llms-full.txt for richer first-party context.
2Add JSON-LD for the organisation, website, and core entities.
3Complete OpenGraph and canonical homepage metadata.
4Reduce mobile rendering delay and main-thread work.

llms.txt tokens603

llms-full.txt tokens—

ai.txt

sitemap.xml

Google Lighthouse technical profile

A mobile Lighthouse measurement. Google’s experimental Agentic Browsing category is explained separately and does not replace the broader llmsmap AI-readiness score.

Mobile · Lighthouse

Performance

100

Accessibility

100

Best Practices

100

Technical SEO

100

Agentic Browsing

What these results mean

Mobile performance is 79/100, with the largest visible content block appearing in 3.9 s and the browser main thread blocked for 60 ms. Layout shift was 0. The main thread is where the browser runs JavaScript, calculates layout, and paints the page; long work there delays both user input and browser-agent actions.

Accessibility scored 100/100, Best Practices 100/100, and technical SEO 100/100. The experimental Agentic Browsing category scored 100/100. It measures signals Google currently tests for software agents and is shown separately from the llmsmap AI-readiness score.

Free the main thread and accelerate the first view

Split long JavaScript tasks, defer non-critical scripts and styles, and shorten blocking request chains. This helps the primary content appear sooner and makes controls usable earlier.

Reduce code that loads without helping the page

Remove unused CSS and JavaScript, load heavy widgets on demand, and limit third-party scripts. Less code means less parsing and background work on the device.

Reduce network delay

Improve server response time, remove unnecessary redirects and repeat downloads, and use compression, caching, and selective preconnect hints.

FCP3.1 s

First content

LCP3.9 s

Main content

CLS0

Layout stability

TBT60 ms

Blocking time

SI4.9 s

Visual speed

Metric glossary

FCP · First content: When the first text or image appeared on screen.
LCP · Main content: When the largest visible element in the first viewport rendered.
CLS · Layout stability: How much content shifted unexpectedly while loading; lower is better.
TBT · Blocking time: How long the browser main thread could not respond quickly to input.
SI · Visual speed: How quickly the visible viewport filled with content.

10/29/2026Lighthouse 13.5.0Mobile profile

AI readiness checks

Machine-readable files, crawler policy, discovery, and homepage markup.

llms.txt

File found and accessible

https://www.courtrules.app/llms.txt

llms-full.txt

Full version was not found

ai.txt

ai.txt file was not found

robots.txt

File found

https://courtrules.app/robots.txt

Sitemap in robots.txt2

2 sitemaps found

Schema.org (JSON-LD)

Schema.org markup was not found on the homepage

OpenGraph

OpenGraph tags were not found on the homepage

AI bot access

Based on robots.txt analysis

GPTBotAllowed

OAI-SearchBotAllowed

ChatGPT-UserAllowed

Google-ExtendedAllowed

ClaudeBotAllowed

Claude-SearchBotAllowed

Claude-UserAllowed

BytespiderAllowed

CCBotAllowed

PerplexityBotAllowed

Perplexity-UserAllowed

Sitemaps

Declared discovery routes for crawlers and agents.

https://www.courtrules.app/sitemap.xml https://www.courtrules.app/sitemaps/rulebooks.xml

# Court Rules

> Court Rules is a free reference for U.S. federal and state court rules: local rules, individual judge standing orders, court holidays and a filing-deadline calculator, with a public API and a remote MCP server. Every rule links back to its source order.

Court Rules reads each judge's order, pulls out the requirements that affect a filing (page limits, courtesy copies, pre-motion letters, AI disclosure, hearing procedures), keeps every version and flags real changes. Coverage is over 600 federal judges' standing orders across 20 federal districts, plus a state-court beta. Read the order itself before relying on a summary.

## Tools

- [Deadline calculator](https://www.courtrules.app/calculator): counts calendar, business and court days and applies each district's holidays
- [Federal court deadline calculator](https://www.courtrules.app/federal-court-deadline-calculator): time computation under the Federal Rules
- [Court holidays](https://www.courtrules.app/holidays): federal and court-specific closures

## Rules by topic

- [All topics](https://www.courtrules.app/rules)
- [Page limits](https://www.courtrules.app/rules/page-limits)
- [Courtesy copies](https://www.courtrules.app/rules/courtesy-copies)
- [Pre-motion conferences](https://www.courtrules.app/rules/pre-motion-conferences)
- [Electronic filing](https://www.courtrules.app/rules/electronic-filing)
- [Filing timing](https://www.courtrules.app/rules/filing-timing)
- [Service rules](https://www.courtrules.app/rules/service-rules)

## Courts

- [Federal courts](https://www.courtrules.app/federal-courts): every district with its judges and local rules
- [Federal local rules](https://www.courtrules.app/federal-courts/local-rules)
- [State courts (beta)](https://www.courtrules.app/state-courts)

## Developers

- [API](https://www.courtrules.app/api): JSON API with a free developer tier
- [API documentation](https://docs.courtrules.app)
- [Coverage and licensing](https://www.courtrules.app/coverage): courts, states and judges covered, how often sources are read again, and the kinds of license
- [MCP server](https://www.courtrules.app/mcp): remote MCP endpoint at https://mcp.courtrules.app/mcp for assistants that need cited court-rule answers

## Optional

- [About](https://www.courtrules.app/about)
- [Blog](https://www.courtrules.app/blog)
- [Enforcement actions](https://www.courtrules.app/enforcement)

Share or continue the analysis

Share this audit