response.truncated
The page is larger than the audit reads (5 MB; 2 MB on the hosted server), so only its first part was audited.
What to change
Findings about the rest of the page are missing, and counts such as words, links and images cover only the part that was read. HTML this large is slow for crawlers too: make it smaller (document.html-too-large says how). On the hosted server, the local server reads up to 5 MB.
A finding of this rule on a page carries the exact edits for that page: the markup it quotes, and what to write instead.
When it runs
Runs on every SEO audit: of a page, a crawl, a build directory or HTML. Info is a best practice: worth doing, rarely urgent, and --no-info leaves it out. Each finding takes 1 point off the page's score.
The severity here is the rule's usual one: a finding can be raised or lowered when the page gives a reason.
Run it, or skip it
Check a page for this rule alone, after a fix for instance:
npx @rivi-software/agentic-seo-check audit https://example.com --rule response.truncated
Or from an assistant, with the MCP tool seo_audit_page:
{
"url": "https://example.com",
"rules": [
"response.truncated"
]
}
To leave it out of an audit, pass --disable response.truncated on the command, or disableRules: ["response.truncated"] to a tool.
More in The HTTP response
All 7 rules- Error
response.error-statusThe URL returned a 4xx or 5xx status code. - Info
response.redirectedThe requested URL redirected to another URL. - Warning
response.redirect-chainThe URL goes through two or more redirects before reaching the final page. - Warning
response.slowThe HTML response took longer than the configured threshold (default 2000 ms). - Warning
response.not-htmlThe response Content-Type is not HTML. - Warning
response.not-httpsThe final URL is served over plain http.