rendering.canonical-client-only

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 with --render, on the command or the local server. A warning is a problem that costs a page ranking, clicks or citations. Each finding takes 5 points 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 --render --rule rendering.canonical-client-only

Or from an assistant, with the MCP tool seo_audit_page:

{
  "url": "https://example.com",
  "render": true,
  "rules": [
    "rendering.canonical-client-only"
  ]
}

To leave it out of an audit, pass --disable rendering.canonical-client-only on the command, or disableRules: ["rendering.canonical-client-only"] to a tool.

• Warningrendering.title-client-onlyThe <title> only exists after JavaScript runs.
• Inforendering.title-changedJavaScript changes the <title> after load.
• Warningrendering.description-client-onlyThe meta description only exists after JavaScript runs.
• Warningrendering.canonical-changedJavaScript changes the canonical URL after load, sending conflicting signals.
• Errorrendering.noindex-client-onlyA noindex directive is injected by JavaScript. Google applies it when it renders the page, which removes the page from the index.
• Warningrendering.noindex-removed-by-jsThe server HTML says noindex but JavaScript removes it. Google honours the server noindex and skips rendering, so the page stays out of the index.
• Warningrendering.h1-client-onlyThe <h1> only exists after JavaScript runs.
• Warningrendering.content-client-onlyMost of the body text only exists after JavaScript runs.