Will It Vibe?App Router page defines no metadata
Part of Documentation, UX & Accessibility, which counts for 15% of the overall score. When this check fires it deducts 4 points from that category, once per scan, no matter how many places it turns up.
What it detects
A server page.tsx exports neither a metadata object nor a generateMetadata function, so it inherits only the layout defaults. Pages that skip per-route title and description get weaker search snippets and social previews. Heuristic: a shared layout may set metadata deliberately.
Why it matters
An App Router server page that exports neither a metadata object nor a generateMetadata function relies entirely on whatever the layout sets, so it gets no route-specific title, description, or social preview. Search engines and link unfurlers then show a generic or duplicated snippet for that page. This is a heuristic: a shared layout may set appropriate metadata on purpose.
How to fix it
Export a static metadata object with a title and description from the page when they are known at build time, or export an async generateMetadata function when the values depend on route params or fetched data. Keep layout metadata for shared defaults and override per page where it matters.
The paid report includes a ready-to-paste prompt for your AI coding agent for every check it finds, pointed at the exact findings from your scan. See pricing
Does your repo trip this check?
Paste a GitHub URL or drop a project folder. Scans run in your browser and take seconds.
Scan your repo