pseo-metadata

pSEO Dynamic Metadata

Implement a metadata system that generates unique, accurate SEO tags for every programmatic page.

Core Principles

1. Every page gets unique metadata: No two pages share the same title or description
2. Data-driven generation: Metadata is constructed from structured content fields, not hardcoded
3. Canonical by default: Every page declares its canonical URL, in the <head> of the initial HTML
4. Social-ready: Open Graph and Twitter cards are complete on every page, with a page-specific or per-category image (never one site-wide placeholder)
5. Framework-native: Use the framework's built-in metadata API

Scope parameter

all (default) = everything. titles = section 2, descriptions = section 3, canonical = section 4 (and 8a), opengraph = section 5, twitter = section 6, robots = sections 7, 7a, 7b, export = sections 8 and 8a, i18n = section 9.

Implementation Steps

1. Create the Metadata Generator

Build a centralized function that constructs metadata from page data:

Next.js App Router pattern:

// lib/metadata.ts
import type { Metadata } from "next";

export function generatePageMetadata(data: PageData, baseUrl: string): Metadata {
  const title = buildTitle(data);
  const description = buildDescription(data);
  const canonicalUrl = `${baseUrl}${data.canonicalPath}`;

  return {
    title,
    description,
    alternates: { canonical: canonicalUrl },
    openGraph: {
      title,
      description,
      url: canonicalUrl,
      type: "article",
      siteName: "Site Name",
      // images: [{ url, width, height, alt }],
    },
    twitter: {
      card: "summary_large_image",
      title,
      description,
      // images: [url],
    },
  };
}

2. Build Title Construction Logic

Titles must be:

• Unique across all pages (validate with pseo-quality-guard)
• 50-60 characters target length (hard cap at 70)
• Front-loaded with the primary keyword
• Accurate to the page: Google may rewrite titles that are stuffed, boilerplate or do not describe the page. Do not fight rewrites with more keywords; make the title and H1 agree and describe the content.
• Multi-dimensional: Use 2+ data fields to construct, not just one variable