Framework SEO guides
Most SEO advice is framework-agnostic, which is why it rarely helps. A canonical tag in Next.js is the Metadata API; in SvelteKit it is a load function; in Rails it is a helper in the layout. Same problem, three different fixes.
These are the 81 framework-specific checks RankCLI runs across 11 frameworks — each with the fix written in that framework's own idiom, taken from the recipes the tool actually uses.
Angular
Client-rendered by default · 4 known traps
Astro
Client-rendered by default
Django
Renders on the server by default
Laravel
Renders on the server by default
Next.js
Renders on the server by default
Nuxt
Renders on the server by default
React
Client-rendered by default · 5 known traps
Ruby on Rails
Renders on the server by default
SvelteKit
Renders on the server by default
Vue.js
Client-rendered by default · 4 known traps
WordPress
Renders on the server by default · 4 known traps
Detected but not yet given a recipe
Every audit identifies your framework and tells you which one it found — 32 of them. Detection weighs all the evidence on the page and answers "unknown" rather than guessing, so when it names one it is right. These are recognised and reported, but their fixes are generic rather than idiomatic:
Find out which of these apply to you
280+ checks, framework detected automatically. No signup.
npx @rankcli/cli audit -u https://your-site.dev