law.cornell.edu
AI Visibility Check · Free 82-point audit ·
law.cornell.edu scored 54/100 (Fair)on GeoCore AI's free AI visibility check (). Audited 82 checks: 23 passed, 36 warnings, 16 failures. law.cornell.edu passed 23/82 AI visibility checks. GEO score: 54/100. Free check powered by GeoCore AI.
GEO HealthAI Generative Engine Optimization▸▾ View 3450/100
SEO HealthTraditional Search Engine Score▸▾ View 1662/100
AEO HealthAnswer Engine Optimization▸▾ View 2157/100
Full Scan Results · 82 Checks
All 82 checks across 12 categories — including passed and skipped items.
AI Crawl Infrastructure
(11 checks 3 pass, 3 warn, 1 fail, 4 skip)sitemap.xml Exists
sitemap.xml not found (404)
Fix: Create a sitemap.xml and submit it to Google Search Console and Bing Webmaster Tools. 🔄 This fix boosts both SEO rankings and AI citation rates (locafy 2026: ~60% shared foundation).
Sitemap Declared in robots.txt
No Sitemap: directive in robots.txt
Fix: Add "Sitemap: https://yourdomain.com/sitemap.xml" to robots.txt 🔄 This fix boosts both SEO rankings and AI citation rates (locafy 2026: ~60% shared foundation).
llms.txt Present
llms.txt not found (optional but recommended)
Fix: Consider creating /llms.txt following llmstxt.org spec. Note: major AI platforms have not yet officially confirmed support — treat as a forward-looking signal, not a critical fix. 🔄 This fix boosts both SEO rankings and AI citation rates (locafy 2026: ~60% shared foundation).
humans.txt Present
humans.txt not found (optional but supports E-E-A-T)
Fix: Create /humans.txt with team info, contact details, and update date. Helps AI engines verify authorship and expertise signals.
sitemap.xml Format Valid
Cannot check — sitemap.xml not available
sitemap.xml Has <lastmod>
Cannot check — sitemap.xml not available
No Dead Links in Sitemap
Cannot check — sitemap.xml not available
llms.txt Consistency
llms.txt not present — consistency check skipped (non-critical)
robots.txt Exists
robots.txt found and accessible
robots.txt Format Valid
robots.txt has valid User-agent directives
AI Search Bots Allowed
AI search bots allowed (OAI-SearchBot, PerplexityBot, Google-Extended detected)
Discovery & Indexing
(4 checks 2 pass, 2 warn)IndexNow Enabled
IndexNow key file not found
Fix: Implement IndexNow to instantly notify Bing, Yandex, and other engines about new/updated pages.
Perplexity Hub Listed
No Perplexity Hub registration detected
Fix: Register your site on Perplexity Hub (hub.perplexity.ai) to improve AI search visibility.
Google Indexing Signal
Homepage is accessible (Google crawl likely possible)
Bing Indexing Signal
No Bingbot restrictions in robots.txt
Content & Schema
(14 checks 5 pass, 6 warn, 3 fail)Article Schema Markup
No Article schema markup detected on homepage or scanned content pages
Fix: Add JSON-LD Article schema to your content pages to help AI understand your content type. 🔄 This fix boosts both SEO rankings and AI citation rates (locafy 2026: ~60% shared foundation).
FAQ Schema Quality
No FAQ schema detected
Fix: Add FAQPage JSON-LD schema with 8-10 Q&As (each 100+ chars). FAQ schema is one of the strongest signals for AI answer extraction. 🔄 This fix boosts both SEO rankings and AI citation rates (locafy 2026: ~60% shared foundation).
Meta Description Quality
No meta description found
Fix: Add a compelling meta description (50-160 chars) to every page. 🔄 This fix boosts both SEO rankings and AI citation rates (locafy 2026: ~60% shared foundation).
Organization Schema
No Organization schema detected
Fix: Add Organization JSON-LD schema to establish entity recognition with AI systems. 🔄 This fix boosts both SEO rankings and AI citation rates (locafy 2026: ~60% shared foundation).
BreadcrumbList Schema
No BreadcrumbList schema detected
Fix: Add BreadcrumbList schema to improve content hierarchy understanding by AI crawlers. 🔄 This fix boosts both SEO rankings and AI citation rates (locafy 2026: ~60% shared foundation).
Answer Capsule Content
No clear answer capsule content detected (LLM, unified)
Fix: Add concise, direct answer paragraphs at the top of key pages to improve AI citation potential.
HowTo Schema Present
No HowTo schema detected
Fix: Add HowTo JSON-LD schema to tutorial/guide pages. AI engines prominently feature step-by-step content with HowTo markup. 🔄 This fix boosts both SEO rankings and AI citation rates (locafy 2026: ~60% shared foundation).
E-E-A-T Signals
3/4 E-E-A-T signals detected (Experience, Authority, Trust). Missing: Expertise
Fix: Google March 2026 Core Update strengthened E-E-A-T weighting. Add signals for: Expertise. AI engines (Perplexity, ChatGPT) prioritize citing E-E-A-T-strong content. 🔄 This fix boosts both SEO rankings and AI citation rates (locafy 2026: ~60% shared foundation).
High-Value AI Content Signals
Only 1/3 quality signals detected (LLM, unified)
Fix: Add statistics, expert citations, and clear definitions.
Article Content Identified
Article-like content detected (article, blog, post)
Internal Links (Outbound)
127 internal links found on homepage
Canonical Consistency
Canonical consistent and single (https://www.law.cornell.edu)
Inbound Link Quality (rule estimate)
Rule-based estimate: canonical present, 128 internal links found. Real backlink/referring-domain data requires FullScan (paid unlock).
Fix: 🔒 Unlock real backlink analysis (referring domains, spam score, broken links) with FullScan. 🔄 This fix boosts both SEO rankings and AI citation rates (locafy 2026: ~60% shared foundation).
Content Spam Compliance
No Google SpamBrain risk signals detected. Content appears compliant.
Technical Signals
(4 checks 2 pass, 1 warn)Product Schema Present
No Product schema detected
Fix: Add Product JSON-LD schema (with name, description, offers) to product/pricing pages to improve AI recommendation visibility. 🔄 This fix boosts both SEO rankings and AI citation rates (locafy 2026: ~60% shared foundation).
HTTPS Enabled
Site uses HTTPS: https://www.law.cornell.edu/
Title Consistency
Page title found: "Welcome to LII | Legal Information Institute"
AI Agent Visibility
(3 checks 2 warn, 1 fail)llms.txt Agent Navigation
No llms.txt — AI agents cannot efficiently discover your content
Fix: Create /llms.txt following llmstxt.org format. Only 19% of websites have AI agent-specific instructions; this is a key differentiator.
AI Agent Config
No AI agent configuration detected (ai-plugin.json, agent.json)
Fix: Create /.well-known/ai-plugin.json to make your service discoverable by AI agents (ChatGPT Plugins, OpenAI GPTs). 81% of companies still treat AI agents as generic bots — early movers gain significant visibility.
Agent-Readable Schema
No Agent-compatible Schema types found
Fix: Add Service/SoftwareApplication/Action JSON-LD schema. AI agents use structured data to understand your capabilities. AI Agent traffic now equals 88% of human organic search.
Multi-Platform Citation
(2 checks 2 fail)Turn-1 Content Optimization
No Turn-1 optimization signals found (LLM, unified)
Fix: Add a clear definition and question-style heading near the top of the page.
Multi-Platform Citation Fit
Only 1/5 AI platform signals — highly undifferentiated
Fix: Each AI platform cites different content types. ChatGPT→authority schema; Perplexity→fresh content; Gemini→YouTube; Grok→twitter:card; Claude→tech docs. Only 7% of content cited across all platforms universally. 🔄 This fix boosts both SEO rankings and AI citation rates (locafy 2026: ~60% shared foundation).
AI Discoverability
(4 checks 1 pass, 2 warn, 1 fail)Citation Readiness (5W)
Only 0/5 citation signals found (LLM, unified) — low citation probability
Fix: Add Who (author), What (description), When (date), Where (location), How (methodology) signals. AI engines prefer content with clear provenance and structure.
ai.txt Present
ai.txt not found — AI agents lack explicit permission/usage directives
Fix: Create /ai.txt to declare which AI agents can use your content, usage restrictions, and attribution requirements. Emerging standard adopted by major AI companies.
AI Plugin Manifest
No AI plugin manifest found at /.well-known/ai-plugin.json
Fix: Create an AI plugin manifest to enable GPT Actions and AI agent integrations. This allows AI assistants to discover and interact with your site's functionality. 🔄 This fix boosts both SEO rankings and AI citation rates (locafy 2026: ~60% shared foundation).
Brand Mention Consistency
Brand "law" appears 31x (55.0/1000 words) with consistent usage
Citation Enhancement (v3)
(16 checks 4 pass, 9 warn, 3 fail)Statistics Density
No quantitative data found (LLM, unified)
Fix: Include specific numbers, percentages, and statistical claims backed by sources.
Brand Knowledge Consolidation
0 official platform profile(s) — insufficient brand presence signals
Fix: Create official profiles on LinkedIn, Twitter/X, and industry-specific platforms. Add them as sameAs links in your Organization schema.
Freshness Signal (Enhanced)
No publication or update date found on page or in sitemap
Fix: Add <lastmod> to sitemap XML AND visible "Last Updated" date with article:modified_time meta tag. AI engines strongly prefer fresh content (50% citations from ≤13 weeks). 🔄 This fix boosts both SEO rankings and AI citation rates (locafy 2026: ~60% shared foundation).
Comparison Table
No comparison table found on page
Fix: Add a comparison table highlighting your advantages vs alternatives. AI engines heavily cite comparison data.
Calculator / Interactive Tool
No calculator or interactive tool detected — consider adding one for engagement
Fix: Public calculators and estimation tools get ~39% more AI citations in finance/health/saas categories.
Review / Rating Schema
No Review or AggregateRating schema detected
Fix: Add AggregateRating schema to product/service pages. AI engines use review data as a recommendation signal. 🔄 This fix boosts both SEO rankings and AI citation rates (locafy 2026: ~60% shared foundation).
Original Data Signal
No original/proprietary data signal detected (LLM, unified)
Fix: Publish original research, proprietary statistics, or a documented methodology.
Question Headings (Site-wide)
Only 2 question heading(s)
Fix: Structure more headings as questions users actually ask (e.g., "How much does X cost?" "What is the best Y for Z?"). AI models treat question headings as direct answer targets. 🔄 This fix boosts both SEO rankings and AI citation rates (locafy 2026: ~60% shared foundation).
Plain-Text Q&A Pairs
Only 2 Q&A pair(s)
Fix: Add more short Q&A sections: question heading + concise answer (<300 chars). AI models prefer bite-sized, self-contained answer chunks. 🔄 This fix boosts both SEO rankings and AI citation rates (locafy 2026: ~60% shared foundation).
Plain-Text Step Instructions
No step-by-step instructions found
Fix: Add numbered step-by-step guides for how-to content. AI models prefer procedural content with clear sequential steps.
Wikidata Entity Presence
No Wikidata/Wikipedia reference detected — add one to strengthen knowledge-graph entity recognition
Fix: Create a Wikidata entry for your brand and add the Q-item ID to Organization schema sameAs. Wikipedia is the #1 cited source by ChatGPT (~7.8% of all citations).
Sub-Intent Coverage
Only 4 sub-intent(s) covered (LLM, unified): access legal resources, find primary sources, get legal information, learn about legal topics
Fix: Add content covering missing user intent topics (pricing, comparisons, tutorials, FAQs, use cases, etc.).
Ranking / List Density
17 list(s) with 91 items across scanned pages — good density for AI scanning
Authoritative Outbound Links
33 links to authoritative sources (.gov/.edu/Wikipedia/arXiv) across scanned pages
Content Extractability
Substantial text in raw HTML (522 words) — AI crawlable without JS execution
Category-Specific Optimization
Category detected: legal (confidence 0.98) — category-aware checks active
Fix: Category identified; industry-specific optimization guidance will deepen after onboarding.
Image & Visual (E3)
(4 checks 1 pass, 2 warn, 1 fail)Image Performance (WebP/AVIF/srcset/lazy)
Images poorly optimized (4 missing: no WebP/AVIF; no srcset/sizes; no loading=lazy; no width/height (CLS risk))
Fix: Use WebP/AVIF, add srcset+sizes (picture fallback), loading=lazy + decoding=async, and explicit width/height to prevent CLS. Add ImageObject schema for AI/vision crawlers.
ImageObject Schema (E3)
ImageObject schema not found
Fix: Add ImageObject JSON-LD to richly describe key images for AI/vision crawlers (Google I/O 2026: AI can "see" images).
Core Web Vitals (E2) (local probe)
Local probe (TTFB): 34137ms — could be improved (CrUX/PSI unavailable, using scan-time avg TTFB)
Fix: Improve server response time (TTFB) — use CDN/edge caching and optimize backend. Real-user data will confirm after sufficient traffic.
Image Alt Quality
All 2 images have alt text (or empty alt for decorative) (2 images, 0 missing)
Site Quality (v5)
(7 checks 2 pass, 3 warn, 2 fail)Social Card (OG/Twitter)
Social Card incomplete (missing: og:description, og:image, og:title, og:title tag)
Fix: Add Open Graph tags: og:title (60-75 chars), og:description (150-200 chars), og:image (1200x630, absolute URL, <5MB). Add twitter:card=summary_large_image. These improve link previews on X/LinkedIn/WeChat and AI citation of page context.
Schema JSON-LD Validation (E1)
No JSON-LD structured data found
Fix: Add JSON-LD structured data (e.g. Organization, Website, Article) to help AI engines understand your content. Use https://validator.schema.org to validate.
Mobile Friendliness
Viewport OK; some touch targets may be too small for mobile
Fix: Add <meta name="viewport" content="width=device-width, initial-scale=1">, use font-size >= 16px, and ensure touch targets are >= 48x48px (WCAG 2.2 2.5.8). Full audit via Lighthouse mobile audit is recommended.
Voice Search Readiness
Voice Search not optimized (15/100) (LLM, unified) [Industry allowance: legal no typical use case for this item; downgraded to hint]
Fix: Add Speakable/FAQ schema, put a concise direct answer near the top (<=40 words), and use conversational phrasing. Voice/AI search favors short, quotable answers.
AI Overview Readiness (E4)
AI Overview readiness: 50/100 — partial [ai_crawl=20.0, answer_first=4.0, schema=4.0, citable=18.0, unique=4.0] (LLM, unified)
Fix: Opening lacks a direct answer. Lead your first 150 words with the core answer ("X is...", "Yes/No...") so AI Overview can quote it directly.<br>No AI-friendly structured data (FAQ/Article/HowTo/Product/Organization JSON-LD). Add schema.org markup so AI engines can extract and cite your content.<br>No original data points. AI Overviews prefer unique statistics, comparisons, or proprietary research as citation-worthy sources — add original numbers or a comparison table.
Accessibility (WCAG)
Accessibility base checks passed (labels, headings, contrast, ARIA)
Industry Detection (F3)
Industry detected: legal (LLM, confidence 0.98)
AI Readability (E5)
(2 checks 2 fail)AI Readability (E5) (LLM, unified)
Weak AI readability (E5 44.8/100) (LLM) (unified) — Macro 0.4 / Meso 0.7 / Micro 0.0 · cited-prob 45%
Fix: Restructure for AI scanning: put an answer-first opening under H1, use a strict H1→H2→H3 hierarchy with balanced paragraphs, add bulleted key points, a comparison table, an early stats block, bold signals, an FAQ section, and semantic tags (article/section/main).
Content Readability (LAURAE) (LLM, unified)
No readable text found on page — Flesch 0.0 — Fog 0.0 — ARI 0.0
Fix: Add actual readable content to the page.
Multi-Page Aggregation
(8 checks 2 pass, 4 warn)Answer Near the Top
No direct answer signal in first 30% of content
Fix: Lead with the core answer in the first 30%% of text. CXL research: 55%% of AI citations come from the first 30%% of content.
Factually Specific
Low factual density: 0.00 data points per 200 words (need >=1)
Fix: Add more specific facts, statistics, percentages, or concrete figures. Studies show content with data gets ~40%% more AI citations.
Content Length
Content length 522 words (decent, aim >=800 for in-depth)
Fix: Expand content to at least 800 words. Token-dense pages let an LLM extract a complete answer.
Preview Control
Partial preview control — missing: meta description (30-160 chars)
Fix: Meta description, first paragraph, and FAQ schema control what AI previews. Add the missing: meta description (30-160 chars).
Title Uniqueness (site-wide)
All page titles unique across 1 page(s)
Contradiction Risk
No contradiction/misleading signals detected (LLM, unified)
✅ 22 checks passed
AI Reputation & Platform Citation
Risk level: high
Limited visibility into maintenance or completeness of the legal database compared with larger free legal portals
AI systems typically describe LII as a trusted free legal research source, but note that users should verify whether the specific statute, case, or state resource is current and fully covered before relying on it for research.
Potential overlap and confusion with Justia and other free legal research sites
AI answers usually position LII and Justia as similar free-access legal research portals, with LII framed as Cornell’s nonprofit resource and Justia as a broader legal information site; they may be interchangeable for basic research but not identical in coverage or presentation.
Free-access legal resources can have funding and sustainability constraints
AI platforms often explain that LII is a nonprofit public-service project and that free access to law requires ongoing support, so long-term sustainability and resource expansion can depend on institutional funding and maintenance.
🤖 Platform Sentiment
LII is typically presented as a reputable nonprofit legal reference source with strong authority because it is affiliated with Cornell Law School. It is commonly framed as useful for statutes, case law, and legal explanations.
Legal Information Institute is generally described as a free legal information portal from Cornell Law School that provides access to legal materials and educational content. Descriptions are usually factual and comparative rather than promotional.
Legal Information Institute is usually described as a trusted Cornell Law School public-service site that provides free access to primary legal materials and explanatory resources. It is often recommended for general legal research and plain-language legal information.
LII is typically summarized as a reliable, no-cost legal research resource from Cornell Law School that offers access to laws, cases, and legal explanations. It is often mentioned alongside Justia as one of the main free legal information sites.
📡 5-Platform Crawler Access Radar
Robots.txt access permission per AI platform crawler (ChatGPT / Gemini / Perplexity / Grok / Claude). Citation-diversity dimension requires a full scan.
🛰 AI Overview Citation
Live Google AIO💬 Reddit Mentions
🔥 Trending Questions
❄️ Underserved Questions
About This Audit
Is law.cornell.edu visible to AI search engines?
law.cornell.edu scored 54/100 (Fair) on GeoCore AI's free AI visibility check as of August 22, 2026. Results: 23 passed, 36 warnings, 16 failures out of 82 checks. law.cornell.edu passed 23/82 AI visibility checks. GEO score: 54/100. Free check powered by GeoCore AI.
Does law.cornell.edu have llms.txt?
No — law.cornell.edu does not have a llms.txt file. Consider creating /llms.txt following llmstxt.org spec. Note: major AI platforms have not yet officially confirmed support — treat as a forward-looking signal, not a critical fix. 🔄 This fix boosts both SEO rankings and AI citation rates (locafy 2026: ~60% shared foundation).
How can law.cornell.edu improve its AI visibility?
- •Create a sitemap.xml and submit it to Google Search Console and Bing Webmaster Tools.
- •Add JSON-LD Article schema to your content pages to help AI understand your content type.
- •Add FAQPage JSON-LD schema with 8-10 Q&As (each 100+ chars). FAQ schema is one of the strongest signals for AI answer extraction.
- •Add a compelling meta description (50-160 chars) to every page.
- •Create /llms.txt following llmstxt.org format. Only 19% of websites have AI agent-specific instructions; this is a key differentiator.
- •Add a clear definition and question-style heading near the top of the page.
- •Each AI platform cites different content types. ChatGPT→authority schema; Perplexity→fresh content; Gemini→YouTube; Grok→twitter:card; Claude→tech docs. Only 7% of content cited across all platforms universally.
- •Add Who (author), What (description), When (date), Where (location), How (methodology) signals. AI engines prefer content with clear provenance and structure.
- •Include specific numbers, percentages, and statistical claims backed by sources.
- •Create official profiles on LinkedIn, Twitter/X, and industry-specific platforms. Add them as sameAs links in your Organization schema.
- •Add <lastmod> to sitemap XML AND visible "Last Updated" date with article:modified_time meta tag. AI engines strongly prefer fresh content (50% citations from ≤13 weeks).
- •Use WebP/AVIF, add srcset+sizes (picture fallback), loading=lazy + decoding=async, and explicit width/height to prevent CLS. Add ImageObject schema for AI/vision crawlers.
- •Add Open Graph tags: og:title (60-75 chars), og:description (150-200 chars), og:image (1200x630, absolute URL, <5MB). Add twitter:card=summary_large_image. These improve link previews on X/LinkedIn/WeChat and AI citation of page context.
- •Add JSON-LD structured data (e.g. Organization, Website, Article) to help AI engines understand your content. Use https://validator.schema.org to validate.
- •Restructure for AI scanning: put an answer-first opening under H1, use a strict H1→H2→H3 hierarchy with balanced paragraphs, add bulleted key points, a comparison table, an early stats block, bold signals, an FAQ section, and semantic tags (article/section/main).
- •Add actual readable content to the page.
What does this 82-point check cover?
82 checks across 12 dimensions: AI Crawl Infrastructure (11 checks); Discovery & Indexing (4 checks); Content & Schema (14 checks); Technical Signals (4 checks); AI Agent Visibility (3 checks); Multi-Platform Citation (2 checks); AI Discoverability (4 checks); Citation Enhancement (v3) (16 checks); Image & Visual (E3) (4 checks); Site Quality (v5) (7 checks); AI Readability (E5) (2 checks); Multi-Page Aggregation (4 checks).
How do I make my site get cited by ChatGPT, Perplexity, Claude, Grok & Google AI?
The best way to improve your AI visibility is with a continuous optimization loop: (1) run a free GeoCore AI check to find gaps like missing llms.txt or weak structured data, (2) fix the highest-impact issues, then (3) monitor how your citations change as AI engines index your site. GeoCore AI tracks this for you so you can see real progress toward being cited by ChatGPT, Perplexity, Claude, Grok, and Google AI Overview.
Get cited by ChatGPT, Perplexity, Claude & Google AI
Run a free AI visibility checkfor your own domain, fix the gaps, then track your citations climbing with GeoCore AI's full GEO platform.