litigator.onescanned Aug 13, 2026 · 11:020.25s
Public AI visibility report

litigator.oneAI visibilityNeeds Work

This site has a useful foundation, but important gaps still limit AI readability.

Key strengths include sitemap and structured data, while plain-text page access and content signals need attention.

Recommended next step

add content negotiation for Accept: text/markdown on the homepage and return a markdown representation with Content-Type: text/markdown.

Keep the HTML response for regular browser requests.

Overall score

51/100
Needs Work

What happens next

Monitor this score as your site changes

Weekly checks catch robots, sitemap, schema, and content regressions before AI systems stop reusing your pages.

Monitor changes
Download PDF
Go to fixesOverall position916 out of 1,787Leaderboard

// score breakdown

Points by check

8 checks

Crawlability10/20
Robots.txt7.5/15
llms.txt7.5/15
Sitemap10/10
Markdown support0/15
Semantic HTML5.7/10
Structured data10/10
Content signals0/5
2pass4warn2fail

Public link

llmscan.dev/scan/vb95G7j9LpPiFPOLCIXlB

Signals checked

8 AI visibility signals

Fix bundle

4 copy-ready files

Share badge

Needs Work · 51/100

Add a polished proof badge

A compact badge for footer, press, or trust sections that links visitors to this public report.

Embed codellmscan.dev/scan/vb95G7j9LpPiFPOLCIXlB
<a href="https://www.llmscan.dev/scan/vb95G7j9LpPiFPOLCIXlB"
  target="_blank"
  rel="noopener"
>
  <img
    src="https://www.llmscan.dev/scan/vb95G7j9LpPiFPOLCIXlB/badge.png"
    alt="LLM Scan AI visibility score badge"
    width="460"
    height="120"
    style="width: 260px; max-width: 100%; height: auto;"
  />
</a>
Open badge
L
LLM Scan
Needs Work
Score
51/100

Share your score

Post the public report with: “We scored 51/100 for AI-readability.”

Download fixes

Grab generated files and implementation notes for the highest-impact gaps.

Rescan weekly

Save this domain to catch regressions after content, sitemap, or robots changes.

Monitor weekly

// signal breakdown

8 signals AI systems depend on

The homepage is reachable, but no canonical link tag was found and robots.txt contains AI crawler restrictions for GPTBot, ChatGPT-User, ClaudeBot, Claude-Web, PerplexityBot, and Google-Extended.

Signal weight

10/20
Warn

Evidence

url
https://litigator.one/
finalUrl
https://litigator.one/
status
200

Recommendation

Next step: Review AI crawler Disallow rules and keep only the paths that should be excluded from AI crawler access; serve a non-empty HTML homepage with a canonical link tag.

robots.txt contains AI-crawler path blocks for GPTBot, ChatGPT-User, ClaudeBot, Claude-Web, PerplexityBot, and Google-Extended.

Signal weight

8/15
Warn

Evidence

robotsTxtUrl
https://litigator.one/robots.txt
exists
true
rawRobotsTxt
User-agent: * Allow: / # Private, auth-gated application — the SPA rewrite serves the homepage shell # for these paths, so they carry no unique indexable content. Disallow keeps # crawl budget on the real marketing pages. (Note: a Disallowed URL is never # rendered, so a JS-injected noindex on it would never be seen — Disallow is # the correct single mechanism here.) Disallow: /app/ Disallow: /app$ Disallow: /api/ # Thin auth / utility routes (duplicate the homepage shell) Disallow: /signin Disallow: /signup Disallow: /forgot-password Disallow: /onboarding # /start renders the same component as /onboarding with the same <title>, and # resolvePageMeta emits a self-referential canonical for it. It exists as the # paid-acquisition entry — ads don't need the organic index, and letting Google # hold a thin near-duplicate of a page we deliberately excluded is the worst of # both. Added with the route, 2026-08-08. Disallow: /start Disallow: /styleguide # App/email utility surfaces (e.g. /apply/exam-week, /apply/weekly-brief) — not # marketing pages and no unique indexable content. These are still active # (some are email-CTA destinations); robots only gates CRAWLERS, so direct and # email access is unaffected. Do NOT read this as "delete these routes". Disallow: /apply/ Sitemap: https://litigator.one/sitemap.xml

Recommendation

Next step: Review AI crawler Disallow rules and keep only the paths that should be excluded from AI crawler access.

The llms.txt file exists but is missing one or more expected quality signals.

Signal weight

8/15
Warn

Evidence

llmsTxtUrl
https://litigator.one/llms.txt
present
true
accessible
true

Recommendation

Next step: Publish /llms.txt as text or markdown with more than 200 characters, markdown headings, and at least one absolute URL.

The sitemap.xml file is valid and contains URL entries.

Signal weight

10/10
Pass

Evidence

sitemapUrl
https://litigator.one/sitemap.xml
sitemapUrls
[https://litigator.one/sitemap.xml]
robotsSitemapUrls
[]

The homepage returned HTML when requested with Accept: text/markdown, so the server appears to ignore markdown content negotiation.

Signal weight

0/15
Fail

Evidence

url
https://litigator.one/
acceptHeader
text/markdown
status
200

Recommendation

Next step: Add content negotiation for Accept: text/markdown on the homepage and return a markdown representation with Content-Type: text/markdown. Keep the HTML response for regular browser requests.

The homepage has some semantic HTML signals, but one or more title, metadata, heading, landmark, content, or link text checks need improvement.

Signal weight

6/10
Warn

Evidence

url
https://litigator.one/
quality
partial
score
57

Recommendation

Next step: Add exactly one h1 element that describes the page topic. Add missing semantic elements: main, article, nav, footer. Add visible body copy after script and style removal so the page has at least 200 words.

Valid JSON-LD structured data was found with core Organization or WebSite schema.org types.

Signal weight

10/10
Pass

Evidence

url
https://litigator.one/
quality
good
hasStructuredData
true

Content-Signal directive not detected in headers, HTML metadata, or robots.txt.

Signal weight

0/5
Fail

Evidence

url
https://litigator.one/
hasContentSignals
false
hasContentSignalHeader
false

Recommendation

Next step: Add the standard directive 'Content-Signal: ai-train=no, search=yes, ai-input=yes' to robots.txt, HTML metadata, or HTTP headers so AI systems can discover content usage preferences.

What happens next

Keep watching this score

Scores move when sites and models change. This one was measured once, on Aug 13, 2026.

Watch weekly

// generated fixes

Downloadable fix files

Preview the generated files below. Enter your email to reveal the full fixes, download the bundle, or copy the agent-ready implementation prompt.

Done-for-you

Agency package

Not sure how to ship the technical fixes? Book a call and we can help turn this report into implemented updates.

Fix planning from your scan

Implementation guidance

AI visibility monitoring

llms.txtMarkdown
# Litigator One — AI Law School Admissions & Career Platform > Essay review, per-school admissions strategy, application tracking, and recruiting planning — one platform built for pre-law and law students. This llms.txt file summarizes the public, canonical resources that AI assistants and crawlers should use to understand this site. ## Site Overview - Canonical URL: https://litigator.one/- Site type: organization
robots.txtTXT
# robots.txt additions# Copy these blocks into the existing robots.txt file. Keep current rules unless a note calls out a conflicting Disallow. # AI crawler access# Add explicit Allow rules for blocked AI crawlers; remove or narrow conflicting Disallow rules if your crawler target requires precedence.User-agent: GPTBotAllow: / User-agent: ChatGPT-UserAllow: /
schema.jsonJSON
{  "@context": "https://schema.org",  "@graph": [    {      "@type": "Organization",      "@id": "https://litigator.one/#organization",      "name": "Litigator One — AI Law School Admissions & Career Platform",      "description": "Essay review, per-school admissions strategy, application tracking, and recruiting planning — one platform built for pre-law and law students.",      "url": "https://litigator.one/",
head metaHTML
# Content-Signal recommendations Use these directives to make AI-use preferences explicit for compliant crawlers and AI systems. They are advisory signals, so keep them aligned with robots.txt, terms, and access controls. ## Recommended values - ai-train=no: AI model training, fine-tuning, and dataset creation.- search=yes: AI search indexing, snippets, and discovery.- ai-input=yes: AI answer grounding, retrieval, and generated-response context.

What happens next

Monitor this score as your site changes

Weekly checks catch robots, sitemap, schema, and content regressions before AI systems stop reusing your pages.

Watch weekly

Related scans

Similar AI visibility reports

Browse leaderboard