Skip to content

Metadata · Next.js (Pages Router)

Every page needs a title tag in Next.js (Pages Router)

The title is the clickable line in every search result and the label on every browser tab. Without one, search engines invent something from your page content and you have no control over the first thing anyone reads about you.

The fix for Next.js (Pages Router)

13x detects your framework from the response and hands you this version rather than the generic one — below 50% confidence it hedges and gives you the generic one instead.

Use next/head in each page component:

tsx code
import Head from "next/head";

export default function PricingPage() {
  return (
    <>
      <Head>
        <title>Pricing — example.com</title>
      </Head>
      {/* ... */}
    </>
  );
}

On a different stack? The general version of this fix explains what 13x checks and why it matters, without assuming a framework.

Check your Next.js (Pages Router) site

113 deterministic checks against your live URL, in about 30 seconds. Framework detected from the response, so every fix comes back in the form your stack actually uses.

No signup. Results in 30 seconds.

The same fix, other stacks