On-page improvements

Start with the actual page, reader's question, current metadata, rendered headings, and useful destination links. Keep the page's promise consistent with what the product delivers.

Review

• Write a distinctive, descriptive title. Character counts are preview heuristics, not ranking thresholds. Check title templates for duplicate brand suffixes.
• Summarize the page honestly in its description. Google may select a different snippet; no mandatory 150–160 character rule or blanket ban on quotes applies.
• Use headings that explain the page hierarchy. Prefer one clear main heading for readability without inventing a one-H1 ranking penalty.
• Confirm canonical policy from the content. Preserve meaningful filters/pagination; keep tracking cleanup explicit. Align canonical, internal links, redirects, and sitemap with the chosen URLs.
• Add links where they help the reader continue. Use descriptive anchor text and crawlable anchors, not arbitrary link quotas or click-depth limits.
• Use an accurate social preview with readable text and image dimensions suitable for the destination. A dynamic OG image does not guarantee a CTR gain.

Deliver

Provide existing → proposed text, its rationale, and a verification step. If code changes are authorized, inspect the real framework conventions and render the route after changing it. Validate schema only when it describes visible content and meets the intended feature's requirements.

References: Next.js metadata, links, social images. Primary sources: titles, snippets.