36 passed
41 failed
AI Readiness
Bot access, structured data, llms.txt, and content accessibility for AI/LLM crawlers.
15grade F
Bot Discoverability 30pt
50%
Structured Data 25pt
0%
LLM Communication 25pt
0%
Content Accessibility 15pt
0%
Cross-Signal Readiness 5pt
0%
Priority Fixes
19
critical
Self-referencing canonical tag: No <link rel="canonical"> tag found.
Jump to fix →
critical
Character encoding declared: No <meta charset> or Content-Type meta found -- encoding falls back to guesswork, risking mojibake on non-ASCII content.
Jump to fix →
critical
Page-appropriate JSON-LD schema present (e.g. Organization/WebSite/Product): No JSON-LD found.
Jump to fix →
critical
robots.txt reachable and does not block this page: HTTP 404
Jump to fix →
critical
Organization and/or Article JSON-LD present: Types found: none.
Jump to fix →
critical
llms.txt present: Not found -- see llmstxt.org for the emerging convention.
Jump to fix →
critical
Page content is readable without running JavaScript: Only 21 word(s) of text came through before any JavaScript runs -- bots and assistants that don't execute JS (most AI crawlers, many scrapers) see essentially a blank page, not the content a visitor sees in a browser.
Jump to fix →
critical
Strict-Transport-Security (HSTS) header present: Not present.
Jump to fix →
important
Meta description length is ~120-165 characters: No meta description found.
Jump to fix →
important
Mandatory Open Graph tags present (title/description/image/url/type): Missing: ['og:description', 'og:image', 'og:title', 'og:type', 'og:url'].
Jump to fix →
important
sitemap.xml exists and is well-formed: HTTP 404
Jump to fix →
important
Navigation signal present (breadcrumbs or SiteNavigationElement schema): No breadcrumb markup or SiteNavigationElement schema found.
Jump to fix →
important
Title/description are well-formed enough for an AI summary to quote directly: Meta description is missing or out of length range -- an AI assistant summarizing this page is more likely to paraphrase awkwardly or skip it.
Jump to fix →
important
Keyword density for "domain example domain" stays under the stuffing-risk threshold (<8%): ~14.3% density. Google's current spam policies explicitly list keyword stuffing (repeating a term or phrase unnaturally) as a violation -- well above the 3-5% rule-of-thumb range is a real ranking risk, not just a style issue.
Jump to fix →
important
Target keyword appears in the title tag: Title: "Example Domain"
Jump to fix →
important
Target keyword appears in the H1: H1: "Example Domain"
Jump to fix →
important
No phrase among the top 5 unigrams/bigrams/trigrams is stuffed (>8% density): 12 phrase(s) exceed 8% density: "domain" (14.3%); "example" (9.5%); "example domain" (19.0%); "domain example" (9.5%); "documentation examples" (9.5%); "examples without" (9.5%); "without needing" (9.5%); "example domain example" (14.3%); "domain example domain" (14.3%); "domain this domain" (14.3%); "use in documentation" (14.3%); "documentation examples without" (14.3%).
Jump to fix →
important
X-Content-Type-Options: nosniff present: Not present.
Jump to fix →
important
Clickjacking protection (X-Frame-Options or CSP frame-ancestors): Not present.
Jump to fix →
TEC
Technical
71
URL
URL Structure
100
CON
URL Consolidation
50
REL
Search Relevance
100
VAL
Validation
83
PRS
Search Presentation
0
IDX
Index Control
46
TPL
Template Structure
14
IMG
Images
N/A
TAX
Taxonomy
100
RDB
Readability
0
BOT
AI Readiness: Bot Discoverability
75
SCH
AI Readiness: Structured Data
0
LLM
AI Readiness: LLM Communication
0
ACC
AI Readiness: Content Accessibility
0
XSG
AI Readiness: Cross-Signal Readiness
0
KWD
Keyword Optimization
21
SEC
Security Headers
0
LNK
Link Health
71
AST
Performance & Assets
100
3PI
Third-Party Impact
100
CXN
Connection Timing
100
CWV
Core Web Vitals (field data)
100
BOT AI Readiness: Bot Discoverability 75%
FAIL
advisory
robots.txt has bot-specific rules (deliberate AI-crawler policy)
Only a blanket 'User-agent: *' rule (or none) found -- no evidence of a per-bot policy.
PASS
critical
Major AI crawlers (GPTBot, ClaudeBot, PerplexityBot, etc.) aren't blocked
All known AI crawlers allowed.
Evidence
GPTBot: allowed -- OpenAI (training / ChatGPT search grounding) ChatGPT-User: allowed -- OpenAI (live browsing agent) OAI-SearchBot: allowed -- OpenAI (ChatGPT search index) ClaudeBot: allowed -- Anthropic (crawler) anthropic-ai: allowed -- Anthropic (legacy crawler token) Claude-User: allowed -- Anthropic (live browsing agent) PerplexityBot: allowed -- Perplexity (search index) Google-Extended: allowed -- Google (Gemini/AI Overviews training opt-out control) CCBot: allowed -- Common Crawl (feeds many third-party LLM training sets)
ACC AI Readiness: Content Accessibility 0%
FAIL
critical
Page content is readable without running JavaScript
Only 21 word(s) of text came through before any JavaScript runs -- bots and assistants that don't execute JS (most AI crawlers, many scrapers) see essentially a blank page, not the content a visitor sees in a browser.
FAIL
important
Title/description are well-formed enough for an AI summary to quote directly
Meta description is missing or out of length range -- an AI assistant summarizing this page is more likely to paraphrase awkwardly or skip it.
XSG AI Readiness: Cross-Signal Readiness 0%
FAIL
advisory
Bot access, structured data, llms.txt, and SSR content all align
At least one of bot access / structured data / llms.txt / SSR content is missing.
LLM AI Readiness: LLM Communication 0%
FAIL
critical
llms.txt present
Not found -- see llmstxt.org for the emerging convention.
SCH AI Readiness: Structured Data 0%
FAIL
critical
Organization and/or Article JSON-LD present
Types found: none.
FAIL
important
Navigation signal present (breadcrumbs or SiteNavigationElement schema)
No breadcrumb markup or SiteNavigationElement schema found.
FAIL
advisory
At least one rich schema type present (FAQPage, HowTo, Product, etc.)
Rich types found: none.
CXN Connection Timing 100%
PASS
advisory
Connection chain (DNS + TCP + TLS) is fast (<=200ms)
DNS 1.3ms + TCP 2.9ms + TLS 70.4ms = 74.6ms before the first byte was requested.
CWV Core Web Vitals (field data) 100%
PASS
critical
LCP (Largest Contentful Paint) within budget (<= 2.50s)
Actual: 0.93s (category: FAST)
PASS
critical
CLS (Cumulative Layout Shift) within budget (<= 0.100)
Actual: 0.000 (category: FAST)
PASS
critical
INP (Interaction to Next Paint) within budget (<= 200ms)
Actual: 81ms (category: FAST)
IMG Images N/A
IDX Index Control 46%
FAIL
critical
robots.txt reachable and does not block this page
HTTP 404
FAIL
important
sitemap.xml exists and is well-formed
HTTP 404
FAIL
advisory
llms.txt present (emerging AI-crawler convention)
HTTP 404
FAIL
advisory
ai.txt present (emerging AI-crawler convention)
HTTP 404
PASS
critical
Page is not marked noindex
No noindex directive.
PASS
critical
No unintended snippet/archive/preview restrictions
No nosnippet/noarchive/max-snippet:0/max-image-preview:none/max-video-preview:0 found.
KWD Keyword Optimization 21%
FAIL
advisory
Keyword density for "domain example domain" is in the classic 3-5% range
"domain example domain" appears 1 time(s) across 21 words (~14.3% density). Treat this as a rough guideline, not a target to write toward -- natural, reader-first phrasing matters more than hitting an exact number (over-optimizing risks tripping Google's keyword-stuffing spam policy; too little risks the page not clearly signaling its topic).
FAIL
important
Keyword density for "domain example domain" stays under the stuffing-risk threshold (<8%)
~14.3% density. Google's current spam policies explicitly list keyword stuffing (repeating a term or phrase unnaturally) as a violation -- well above the 3-5% rule-of-thumb range is a real ranking risk, not just a style issue.
FAIL
important
Target keyword appears in the title tag
Title: "Example Domain"
FAIL
important
Target keyword appears in the H1
H1: "Example Domain"
FAIL
advisory
Target keyword appears in the meta description
No meta description found.
FAIL
advisory
Target keyword appears in the first paragraph
First paragraph: "This domain is for use in documentation examples without needing permission. Avoid use in operations."
FAIL
important
No phrase among the top 5 unigrams/bigrams/trigrams is stuffed (>8% density)
12 phrase(s) exceed 8% density: "domain" (14.3%); "example" (9.5%); "example domain" (19.0%); "domain example" (9.5%); "documentation examples" (9.5%); "examples without" (9.5%); "without needing" (9.5%); "example domain example" (14.3%); "domain example domain" (14.3%); "domain this domain" (14.3%); "use in documentation" (14.3%); "documentation examples without" (14.3%).
Evidence
1-gram "domain": 3x (14.29%) <-- ALARM 1-gram "example": 2x (9.52%) <-- ALARM 1-gram "documentation": 1x (4.76%) 1-gram "examples": 1x (4.76%) 1-gram "without": 1x (4.76%) 2-gram "example domain": 2x (19.05%) <-- ALARM 2-gram "domain example": 1x (9.52%) <-- ALARM 2-gram "documentation examples": 1x (9.52%) <-- ALARM 2-gram "examples without": 1x (9.52%) <-- ALARM 2-gram "without needing": 1x (9.52%) <-- ALARM 3-gram "example domain example": 1x (14.29%) <-- ALARM 3-gram "domain example domain": 1x (14.29%) <-- ALARM 3-gram "domain this domain": 1x (14.29%) <-- ALARM 3-gram "use in documentation": 1x (14.29%) <-- ALARM 3-gram "documentation examples without": 1x (14.29%) <-- ALARM
PASS
critical
Target keyword "domain example domain" appears in the body at all
Found 1 occurrence(s).
LNK Link Health 71%
FAIL
advisory
External links don't outnumber internal links
1 external vs. 0 internal. Heuristic, not an official standard -- flags the unusual case where citations outnumber your own internal linking.
FAIL
advisory
External link density is reasonable (<=5 per 1000 words)
1 external link(s) across 21 words (47.6 per 1000 words). Heuristic threshold, not an official standard.
PASS
important
No links with empty anchor text (and no aria-label)
0 of 1 navigable link(s) have no visible text, aria-label, or title (in-page anchors, mailto:, and tel: links excluded from this count).
PASS
advisory
Affiliate/ad-network links carry rel="sponsored" or "nofollow"
No links to known affiliate/ad domains found -- heuristic list, not exhaustive.
PASS
important
No broken links in sample of 1
Checked 1 of 1 unique link(s) (sample, not exhaustive). None broken.
AST Performance & Assets 100%
PASS
important
Total page weight is reasonable (<=2 MB)
1 request(s) totaling 0.5 KB across 1 domain(s).
Evidence
Weight by domain: example.com: 0.5 KB (1 req) Weight by content type: HTML: 0.5 KB (100.0%)
PASS
advisory
Total requests kept reasonable (<=50)
1 total request(s) discovered from static HTML (script/link/img/iframe/source tags).
Evidence
File request log: 200 HTML 0.5 KB https://example.com/
PASS
advisory
Server supports HTTP/2 or later (via ALPN)
ALPN negotiated: h2
RDB Readability 0%
FAIL
advisory
Flesch Reading Ease is reasonably accessible (>=50)
Score 30.5 (Difficult). 7.0 avg words/sentence across 3 sentences (21 words).
PRS Search Presentation 0%
FAIL
important
Meta description length is ~120-165 characters
No meta description found.
FAIL
important
Mandatory Open Graph tags present (title/description/image/url/type)
Missing: ['og:description', 'og:image', 'og:title', 'og:type', 'og:url'].
FAIL
advisory
twitter:card meta tag present
Not present.
REL Search Relevance 100%
PASS
important
Title tag length is 10-60 characters
14 characters: "Example Domain"
PASS
critical
Exactly one H1 on the page
Found 1 H1 element(s): ['Example Domain']
PASS
advisory
H1 and title tag share topical keywords
Word overlap ratio: 100%. H1: "Example Domain" | Title: "Example Domain"
SEC Security Headers 0%
FAIL
critical
Strict-Transport-Security (HSTS) header present
Not present.
FAIL
important
X-Content-Type-Options: nosniff present
Not present.
FAIL
important
Clickjacking protection (X-Frame-Options or CSP frame-ancestors)
Not present.
FAIL
advisory
Content-Security-Policy header present
Not present.
FAIL
advisory
Referrer-Policy header present
Not present.
FAIL
advisory
Permissions-Policy header present
Not present.
TAX Taxonomy 100%
PASS
advisory
Tag count is reasonable (not over-tagged)
0 distinct tag link(s) found via /tag/ URL pattern -- 0 may mean no tags, or that this site tags posts using a different URL convention this check doesn't recognize.
TEC Technical 71%
FAIL
advisory
Cache-Control or Expires header present
Cache-Control/Expires: (none)
FAIL
advisory
Privacy Policy link present on the page
No link matching "privacy" found on this page.
FAIL
advisory
Terms of Service link present on the page
No link matching "terms" found on this page.
FAIL
advisory
Cookie Policy link present on the page
No link matching "cookie" found on this page.
PASS
important
No unnecessary redirect chain
Loaded directly, no redirects.
Evidence
https://example.com/
PASS
critical
Served over HTTPS
Scheme is 'https'.
PASS
important
Response served with gzip/brotli compression
Content-Encoding: gzip
PASS
advisory
Favicon <link> tag present
Found: data:,
PASS
advisory
DMARC record present
v=DMARC1;p=reject;sp=reject;adkim=s;aspf=s
PASS
advisory
SPF record present
v=spf1 -all
TPL Template Structure 14%
FAIL
critical
Page-appropriate JSON-LD schema present (e.g. Organization/WebSite/Product)
No JSON-LD found.
Suggested fix
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Example Domain",
"url": "https://example.com/"
}
</script>
FAIL
advisory
First paragraph has enough substance (>=30 words)
15 words: "This domain is for use in documentation examples without needing permission. Avoid use in operations."
FAIL
advisory
3-7 contextual internal links in article body
0 internal link(s) found in article body.
FAIL
advisory
Article has substantial content (>=300 words)
21 words in the article body.
PASS
advisory
Heading levels don't skip (e.g. H1 straight to H3)
H1:1 H2:0 H3:0 H4:0 H5:0 H6:0 -- no skipped levels.
3PI Third-Party Impact 100%
PASS
advisory
Third-party categories kept to a reasonable number (<=5)
0 third-party categories detected across 0 domain(s): none.
Evidence
No third-party assets detected in static HTML.
CON URL Consolidation 50%
FAIL
critical
Self-referencing canonical tag
No <link rel="canonical"> tag found.
Suggested fix
<link rel="canonical" href="https://example.com/">
PASS
critical
At most one <link rel="canonical"> tag
0 canonical tag found.
URL URL Structure 100%
PASS
important
URL slug has no date segment
Path: /
PASS
important
URL uses hyphens, not underscores
Path: /
PASS
advisory
URL path is shallow (<=4 segments)
Path depth: 0 segment(s) -- /
VAL Validation 83%
FAIL
critical
Character encoding declared
No <meta charset> or Content-Type meta found -- encoding falls back to guesswork, risking mojibake on non-ASCII content.
Suggested fix
<meta charset="utf-8">
PASS
critical
At most one <title> tag
1 title tag found.
PASS
critical
At most one meta description tag
0 meta description tag found.
PASS
critical
Responsive viewport meta tag present
width=device-width, initial-scale=1
PASS
critical
Title/meta description/canonical are inside <head>
All present head-level tags are actually inside <head>.
PASS
advisory
Lang attribute declared on <html>
Declared: en
PASS
important
No empty src/href attributes
0 <img> with empty src; 0 <a> with empty href.
Script for your agent
Paste into Claude Code, Cursor, or another coding agent to apply every fix below.
Fix the following on-page SEO issues on https://example.com/.
Apply each fix directly in the page template/source, without changing unrelated content or design.
1. [Critical] Self-referencing canonical tag
Issue: No <link rel="canonical"> tag found.
Fix:
<link rel="canonical" href="https://example.com/">
2. [Critical] Character encoding declared
Issue: No <meta charset> or Content-Type meta found -- encoding falls back to guesswork, risking mojibake on non-ASCII content.
Fix:
<meta charset="utf-8">
3. [Critical] Page-appropriate JSON-LD schema present (e.g. Organization/WebSite/Product)
Issue: No JSON-LD found.
Fix:
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Example Domain",
"url": "https://example.com/"
}
</script>
4. [Critical] robots.txt reachable and does not block this page
Issue: HTTP 404
Fix: no fixed snippet available -- use judgment based on the issue above.
5. [Critical] Organization and/or Article JSON-LD present
Issue: Types found: none.
Fix: no fixed snippet available -- use judgment based on the issue above.
6. [Critical] llms.txt present
Issue: Not found -- see llmstxt.org for the emerging convention.
Fix: no fixed snippet available -- use judgment based on the issue above.
7. [Critical] Page content is readable without running JavaScript
Issue: Only 21 word(s) of text came through before any JavaScript runs -- bots and assistants that don't execute JS (most AI crawlers, many scrapers) see essentially a blank page, not the content a visitor sees in a browser.
Fix: no fixed snippet available -- use judgment based on the issue above.
8. [Critical] Strict-Transport-Security (HSTS) header present
Issue: Not present.
Fix: no fixed snippet available -- use judgment based on the issue above.
9. [Important] Meta description length is ~120-165 characters
Issue: No meta description found.
Fix: no fixed snippet available -- use judgment based on the issue above.
10. [Important] Mandatory Open Graph tags present (title/description/image/url/type)
Issue: Missing: ['og:description', 'og:image', 'og:title', 'og:type', 'og:url'].
Fix: no fixed snippet available -- use judgment based on the issue above.
11. [Important] sitemap.xml exists and is well-formed
Issue: HTTP 404
Fix: no fixed snippet available -- use judgment based on the issue above.
12. [Important] Navigation signal present (breadcrumbs or SiteNavigationElement schema)
Issue: No breadcrumb markup or SiteNavigationElement schema found.
Fix: no fixed snippet available -- use judgment based on the issue above.
13. [Important] Title/description are well-formed enough for an AI summary to quote directly
Issue: Meta description is missing or out of length range -- an AI assistant summarizing this page is more likely to paraphrase awkwardly or skip it.
Fix: no fixed snippet available -- use judgment based on the issue above.
14. [Important] Keyword density for "domain example domain" stays under the stuffing-risk threshold (<8%)
Issue: ~14.3% density. Google's current spam policies explicitly list keyword stuffing (repeating a term or phrase unnaturally) as a violation -- well above the 3-5% rule-of-thumb range is a real ranking risk, not just a style issue.
Fix: no fixed snippet available -- use judgment based on the issue above.
15. [Important] Target keyword appears in the title tag
Issue: Title: "Example Domain"
Fix: no fixed snippet available -- use judgment based on the issue above.
16. [Important] Target keyword appears in the H1
Issue: H1: "Example Domain"
Fix: no fixed snippet available -- use judgment based on the issue above.
17. [Important] No phrase among the top 5 unigrams/bigrams/trigrams is stuffed (>8% density)
Issue: 12 phrase(s) exceed 8% density: "domain" (14.3%); "example" (9.5%); "example domain" (19.0%); "domain example" (9.5%); "documentation examples" (9.5%); "examples without" (9.5%); "without needing" (9.5%); "example domain example" (14.3%); "domain example domain" (14.3%); "domain this domain" (14.3%); "use in documentation" (14.3%); "documentation examples without" (14.3%).
Fix: no fixed snippet available -- use judgment based on the issue above.
18. [Important] X-Content-Type-Options: nosniff present
Issue: Not present.
Fix: no fixed snippet available -- use judgment based on the issue above.
19. [Important] Clickjacking protection (X-Frame-Options or CSP frame-ancestors)
Issue: Not present.
Fix: no fixed snippet available -- use judgment based on the issue above.
20. [Advisory] twitter:card meta tag present
Issue: Not present.
Fix: no fixed snippet available -- use judgment based on the issue above.
21. [Advisory] First paragraph has enough substance (>=30 words)
Issue: 15 words: "This domain is for use in documentation examples without needing permission. Avoid use in operations."
Fix: no fixed snippet available -- use judgment based on the issue above.
22. [Advisory] 3-7 contextual internal links in article body
Issue: 0 internal link(s) found in article body.
Fix: no fixed snippet available -- use judgment based on the issue above.
23. [Advisory] Article has substantial content (>=300 words)
Issue: 21 words in the article body.
Fix: no fixed snippet available -- use judgment based on the issue above.
24. [Advisory] Flesch Reading Ease is reasonably accessible (>=50)
Issue: Score 30.5 (Difficult). 7.0 avg words/sentence across 3 sentences (21 words).
Fix: no fixed snippet available -- use judgment based on the issue above.
25. [Advisory] llms.txt present (emerging AI-crawler convention)
Issue: HTTP 404
Fix: no fixed snippet available -- use judgment based on the issue above.
26. [Advisory] ai.txt present (emerging AI-crawler convention)
Issue: HTTP 404
Fix: no fixed snippet available -- use judgment based on the issue above.
27. [Advisory] robots.txt has bot-specific rules (deliberate AI-crawler policy)
Issue: Only a blanket 'User-agent: *' rule (or none) found -- no evidence of a per-bot policy.
Fix: no fixed snippet available -- use judgment based on the issue above.
28. [Advisory] At least one rich schema type present (FAQPage, HowTo, Product, etc.)
Issue: Rich types found: none.
Fix: no fixed snippet available -- use judgment based on the issue above.
29. [Advisory] Bot access, structured data, llms.txt, and SSR content all align
Issue: At least one of bot access / structured data / llms.txt / SSR content is missing.
Fix: no fixed snippet available -- use judgment based on the issue above.
30. [Advisory] Keyword density for "domain example domain" is in the classic 3-5% range
Issue: "domain example domain" appears 1 time(s) across 21 words (~14.3% density). Treat this as a rough guideline, not a target to write toward -- natural, reader-first phrasing matters more than hitting an exact number (over-optimizing risks tripping Google's keyword-stuffing spam policy; too little risks the page not clearly signaling its topic).
Fix: no fixed snippet available -- use judgment based on the issue above.
31. [Advisory] Target keyword appears in the meta description
Issue: No meta description found.
Fix: no fixed snippet available -- use judgment based on the issue above.
32. [Advisory] Target keyword appears in the first paragraph
Issue: First paragraph: "This domain is for use in documentation examples without needing permission. Avoid use in operations."
Fix: no fixed snippet available -- use judgment based on the issue above.
33. [Advisory] Cache-Control or Expires header present
Issue: Cache-Control/Expires: (none)
Fix: no fixed snippet available -- use judgment based on the issue above.
34. [Advisory] Content-Security-Policy header present
Issue: Not present.
Fix: no fixed snippet available -- use judgment based on the issue above.
35. [Advisory] Referrer-Policy header present
Issue: Not present.
Fix: no fixed snippet available -- use judgment based on the issue above.
36. [Advisory] Permissions-Policy header present
Issue: Not present.
Fix: no fixed snippet available -- use judgment based on the issue above.
37. [Advisory] Privacy Policy link present on the page
Issue: No link matching "privacy" found on this page.
Fix: no fixed snippet available -- use judgment based on the issue above.
38. [Advisory] Terms of Service link present on the page
Issue: No link matching "terms" found on this page.
Fix: no fixed snippet available -- use judgment based on the issue above.
39. [Advisory] Cookie Policy link present on the page
Issue: No link matching "cookie" found on this page.
Fix: no fixed snippet available -- use judgment based on the issue above.
40. [Advisory] External links don't outnumber internal links
Issue: 1 external vs. 0 internal. Heuristic, not an official standard -- flags the unusual case where citations outnumber your own internal linking.
Fix: no fixed snippet available -- use judgment based on the issue above.
41. [Advisory] External link density is reasonable (<=5 per 1000 words)
Issue: 1 external link(s) across 21 words (47.6 per 1000 words). Heuristic threshold, not an official standard.
Fix: no fixed snippet available -- use judgment based on the issue above.
After applying the fixes, re-run the SEO page auditor against this URL to confirm each check now passes.
Scope note: this report only covers checks that can be evaluated deterministically
from a single fetched page (URL structure, metadata, schema, image attributes, template structure).
It does not and cannot evaluate content quality, genuine expertise/trustworthiness signals, whether
publishing volume constitutes scaled content abuse, or site-wide taxonomy health. Those
require human judgment or a full-site crawl.