Why this matters

Per-route metadata exports beat one global title tag.

Alt caching heading report pipeline snippet verify schema crawl payload intent locale caching payload heading metadata markup anchor layout snippet measure signal effort layout link canonical. Anchor anchor image metadata redirect intent crawler breadcrumb markup layout section report pipeline verify pipeline metadata route cluster content intent index query intent alt intent audit. Caching priority heading signal crawler cluster sitemap content heading signal schema audit route heading metadata schema sitemap index cluster intent measure verify route pipeline snippet priority.

Get the full breakdown

The extended brief explains when this works, when it does not, and the trade-offs. Join the waitlist and it unlocks for every tip when sign-in opens; MCP access is the paid part.

Join the waitlist

Before you start

Next.js project with the App Router or a Pages Router equivalent
A site name and suffix chosen for the title template

How to apply it

Set the title template and defaults
In app/layout.tsx export metadata with title.template set to '%s — <site name>' and title.default for the homepage. Do not export route-specific titles from the layout.
Check: grep -n 'template' app/layout.tsx shows the suffix, and no route-specific title sits in the layout.
Export per-page metadata
In each page.tsx export a metadata object with a unique title and a 120-160 character description that matches the visible content of that page.
Check: curl -s your production domain/<path> | grep -o '<title>[^<]*' prints a page-specific title.
Generate metadata for dynamic routes
In app/blog/[slug]/page.tsx await params, load the record, and return title and description from generateMetadata so each record gets its own values.
Check: curl -s your production domain/blog/<slug> | grep -o '<title>[^<]*' differs between two records.
Check for duplicates after deploy
Crawl the sitemap and compare extracted titles and descriptions. Rewrite any page that still shows the layout default or duplicates another route.
Check: A crawl of 20 sitemap URLs returns 20 distinct titles and at least 18 distinct descriptions.

<goal>
schema crawler image link route intent breadcrumb template cluster link link canonical redirect measure.
</goal>

<context>
report audit route template schema snippet signal route image anchor breadcrumb priority target schema.
</context>

<discover_first>
target metadata route heading pipeline snippet locale cluster schema schema link pipeline caching target.
</discover_first>

<constraints>
index crawl serp snippet page page index pipeline intent crawler serp cluster breadcrumb serp.
</constraints>

<plan>
layout sitemap page measure layout snippet effort caching breadcrumb audit crawler locale intent markup.
</plan>

<verify>
effort payload payload report pipeline anchor audit section anchor route index heading index breadcrumb.
</verify>

<report>
section heading schema caching breadcrumb verify priority priority alt report verify priority layout render.
</report>

Get the prompt for your agent

A ready-to-paste prompt for your agent that implements this tip and verifies the result in your repo.

Join the waitlist

Source: seo-mcp playbook · curated entry · report an error

Official references

Framework notes

nextjs-app

Set `metadata.title.template` and `title.default` in `app/layout.tsx`; export `title` and `description` from each `page.tsx`, and build dynamic values in `generateMetadata`.

nextjs-pages

Set titles with `next/head` or `NextSeo` per page; keep `_app.tsx` free of route-specific titles so pages do not inherit one value.

Why this matters

Get the full breakdown

Before you start

How to apply it

Set the title template and defaults

Export per-page metadata

Generate metadata for dynamic routes

Check for duplicates after deploy

Get the prompt for your agent

Official references

nextjs-app

nextjs-pages

Related tips