viewport.not-scalable

What to change

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 viewport.not-scalable

Or from an assistant, with the MCP tool seo_audit_page:

{
  "url": "https://example.com",
  "rules": [
    "viewport.not-scalable"
  ]
}

To leave it out of an audit, pass --disable viewport.not-scalable on the command, or disableRules: ["viewport.not-scalable"] to a tool.

• Warninghtml.lang-missingThe <html> element has no lang attribute.
• Warninghtml.lang-invalidThe <html lang> value is not a valid BCP 47 language tag.
• Warningviewport.missingNo <meta name="viewport"> is present, so the page is not mobile-friendly.
• Infocharset.missingNo character encoding is declared, in the HTML or in the Content-Type header.
• Infodoctype.missingThe document does not start with <!DOCTYPE html>.
• Infodocument.html-too-largeThe HTML document is larger than 1.5 MB.
• Errorhead.closed-earlyAn element that does not belong in <head> (an <img>, <iframe>, <div>, stray text) ends it early, so search engines read the metadata after it as part of <body> and ignore it.
• Warninghead.metadata-in-bodyMetadata that search engines read only in <head> (title, meta description, viewport, canonical, hreflang) is written in <body> (warning). Metadata a framework streams into a hidden part of <body> and moves into <head> with JavaScript, as Next.js does for an async generateMetadata, is info. Robots meta tags are not reported: Google honours them in <body> too.