pseo-templates

pSEO Page Templates

Build page templates that produce unique, intent-matched content at scale through dynamic routing and structured data rendering.

Core Principles

1. One template, many unique pages: Templates are content-agnostic shells that render data
2. No thin pages: Every generated page must have substantial, differentiated content that adds real, unique value. Do not create pages for query variations.
3. Intent matching: Each page targets a specific search intent derived from its data
4. Semantic HTML: Use correct heading hierarchy, landmarks, and elements
5. Progressive enhancement: Pages work without JavaScript

Scope parameter

page-type names the template to build. Scope: routes = section 1, structure = sections 2 and 4-5, content = sections 3 and 3a, status = sections 6, 6a and 6b, hubs = section 7, eeat = section 8, images = section 9, all (default) = everything.

Implementation Steps

1. Set Up Dynamic Routes

Create dynamic route segments using the framework's routing system:

Next.js App Router:

app/
  [category]/
    page.tsx                    # category hub page
    [slug]/
      page.tsx                  # individual pSEO page

Next.js Pages Router:

pages/
  [category]/
    index.tsx
    [slug].tsx

Implement generateStaticParams (App Router) or getStaticPaths (Pages Router) using the data layer's getAllSlugs().

Next.js 16.4.x notes (>= 16.4.1 for security fixes; current stable 16.4.3):

• params and searchParams are Promises; always await them.
• middleware.ts is renamed proxy.ts (Node.js runtime) in Next.js 16.
• Cache Components (cacheComponents: true in next config, "use cache" directive): caching is opt-in and dynamic is the default. It is recommended for all apps and on by default in create-next-app from 16.4; Next.js 17 is announced to make it the default.
• With Cache Components, generateStaticParams must return at least one param; an empty array is a build error. Return a few seed params and let the rest render on demand. A placeholder param plus notFound() is the documented workaround when you have none.
• Without Cache Components, generateStaticParams can return [] for runtime ISR of all paths, and dynamicParams = false makes unlisted params 404. It is not re-run during ISR revalidation.
• export const ensureStatic = 'navigation' | 'prefetch' | 'shell' (16.4) requires cacheComponents. Only 'navigation' adds build validation (fails the build on dynamic content) and it requires generateStaticParams to return every param. 'shell' and 'prefetch' add no build validation. With seeded params (rest on demand), do not claim it validates anything.
• Do not prerender huge sets at build: Vercel build time is capped at 45 minutes per deployment. Prerender seed pages and use ISR or on-demand rendering for the rest.