Metadata API for SEO in NextJS - Performance & Optimization

Performance: Metadata API for SEO

MEDIUM IMPACT

This affects the page load speed and SEO by controlling how metadata is rendered and delivered to browsers and search engines.

Setting SEO metadata for a Next.js page

NextJS

import { Metadata } from 'next';

export const metadata: Metadata = {
  title: 'Static or dynamic title',
  description: 'Page description for SEO',
};

export default function Page() {
  return <main>Page content</main>;
}

Metadata is rendered server-side during SSR, reducing render blocking and making SEO tags immediately available.

📈 Performance GainImproves LCP by reducing client-side JS dependency; metadata is in initial HTML.

Setting SEO metadata for a Next.js page

NextJS

export default function Page() {
  return (
    <>
      <Head>
        <title>{dynamicTitle}</title>
        <meta name="description" content={dynamicDescription} />
      </Head>
      <main>Page content</main>
    </>
  )
}

Using <Head> inside the component causes metadata to be injected client-side, delaying metadata availability and increasing render blocking.

📉 Performance CostBlocks rendering until client JS loads; delays LCP and SEO metadata visibility.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Client-side <Head> injection	Adds extra DOM nodes after initial load	Triggers reflow on metadata injection	Increases paint cost due to delayed metadata	[X] Bad
Next.js Metadata API server-side	Metadata included in initial DOM	No extra reflows for metadata	Minimal paint cost, metadata ready on first paint	[OK] Good

Rendering Pipeline

Metadata API integrates metadata generation into the server rendering phase, embedding SEO tags directly into the HTML before sending to the browser.

→Server Rendering

→HTML Parsing

→Style Calculation

⚠️ BottleneckClient-side injection of metadata delays HTML completeness and blocks LCP.

Core Web Vital Affected

LCP

This affects the page load speed and SEO by controlling how metadata is rendered and delivered to browsers and search engines.

Optimization Tips

1Always use Next.js Metadata API to define SEO metadata server-side.

2Avoid client-side metadata injection to prevent render blocking and reflows.

3Check initial HTML to ensure metadata is present for best SEO and LCP.

Performance Quiz - 3 Questions

How does using Next.js Metadata API affect Largest Contentful Paint (LCP)?

A It has no effect on LCP because metadata is not visible content.

B It improves LCP by rendering metadata server-side, reducing render blocking.

C It delays LCP by adding client-side JavaScript for metadata injection.

D It worsens LCP by increasing bundle size significantly.

DevTools: Performance

How to check: Record page load and look for when metadata tags appear in the HTML. Check if metadata is present in initial HTML or injected later.

What to look for: Early presence of <title> and <meta> tags in the HTML source indicates good performance; delayed injection shows client-side overhead.

Practice

1. What is the main purpose of the metadata export in a Next.js page?

easy

A. To define the page's layout and styling

B. To provide SEO information like title and description for the page

C. To handle user authentication on the page

D. To manage API routes for the page

Solution

1. Step 1: Understand the role of metadata in Next.js

   The metadata export is used to set SEO-related information such as the page title and description.

2. Step 2: Differentiate from other page features

   Layout, styling, authentication, and API routes are handled differently and not via metadata.

3. Final Answer:

   To provide SEO information like title and description for the page -> Option B

4. Quick Check:

   Metadata = SEO info [OK]

Hint: Metadata sets SEO info like title and description [OK]

Common Mistakes:

• Confusing metadata with layout or styling
• Thinking metadata handles API routes
• Assuming metadata manages authentication

2. Which of the following is the correct way to export metadata in a Next.js page file?

easy

A. export const metadata = { title: 'Home' }

B. export default metadata = { title: 'Home' }

C. const metadata = { title: 'Home' }; export metadata

D. export metadata = { title: 'Home' }

Solution

1. Step 1: Recall correct export syntax for named exports

   In Next.js, metadata is exported as a named export using export const metadata = {...}.

2. Step 2: Identify syntax errors in other options

   Options A, B, and C use invalid export syntax or missing keywords.

3. Final Answer:

   export const metadata = { title: 'Home' } -> Option A

4. Quick Check:

   Named export with const = export const metadata = { title: 'Home' } [OK]

Hint: Use 'export const metadata = {...}' for metadata export [OK]

Common Mistakes:

• Using default export instead of named export
• Missing 'const' keyword
• Incorrect export statement syntax

3. Given this metadata export in a Next.js page, what will be the page title shown in the browser tab?

export const metadata = {
  title: 'About Us - MySite',
  description: 'Learn more about us'
}

medium

A. MySite

B. Learn more about us

C. About Us - MySite

D. No title will show

Solution

1. Step 1: Identify the title property in metadata

   The title property is set to 'About Us - MySite'. This is what appears in the browser tab.

2. Step 2: Understand description does not affect title

   The description is for SEO and social previews, not the browser tab title.

3. Final Answer:

   About Us - MySite -> Option C

4. Quick Check:

   Title property sets browser tab title [OK]

Hint: Page title = metadata.title value [OK]

Common Mistakes:

• Confusing description with title
• Assuming default title if metadata is present
• Thinking title is empty if not set in layout

4. You wrote this metadata export but the page title does not update:

const metadata = {
  title: 'Contact'
}
export default metadata

What is the error?

medium

A. metadata object must be wrapped in a React component

B. title property must be inside a function

C. title property should be 'pageTitle' instead of 'title'

D. metadata must be exported as a named export, not default

Solution

1. Step 1: Check export type for metadata

   Next.js requires metadata to be a named export, not a default export.

2. Step 2: Verify other options

   Title property does not need a function, React component, or different key name.

3. Final Answer:

   metadata must be exported as a named export, not default -> Option D

4. Quick Check:

   Named export required for metadata [OK]

Hint: Use 'export const metadata', not 'export default' [OK]

Common Mistakes:

• Using default export instead of named export
• Thinking metadata needs to be inside a component
• Changing property names incorrectly

5. You want to add Open Graph metadata for social sharing in Next.js using the Metadata API. Which is the correct way to add the Open Graph title and image?

hard

A. export const metadata = { openGraph: { title: 'My Page', images: ['https://example.com/image.png'] } }

B. export const metadata = { ogTitle: 'My Page', ogImage: 'https://example.com/image.png' }

C. export const metadata = { social: { title: 'My Page', image: 'https://example.com/image.png' } }

D. export const metadata = { openGraphTitle: 'My Page', openGraphImage: 'https://example.com/image.png' }

Solution

1. Step 1: Recall Open Graph structure in Next.js metadata

   Open Graph data is nested under the openGraph key with properties like title and images (array of URLs).

2. Step 2: Compare options for correct property names and structure

   Only export const metadata = { openGraph: { title: 'My Page', images: ['https://example.com/image.png'] } } uses the correct nested openGraph object with title and images array.

3. Final Answer:

   export const metadata = { openGraph: { title: 'My Page', images: ['https://example.com/image.png'] } } -> Option A

4. Quick Check:

   Open Graph uses openGraph key with images array [OK]

Hint: Use openGraph object with images array for social metadata [OK]

Common Mistakes:

• Using flat keys like ogTitle instead of nested openGraph
• Passing image as string instead of array
• Using incorrect property names like social or openGraphTitle