Why Metadata in layouts in NextJS? - Purpose & Use Cases

The Big Idea

Discover how a small change in layouts can boost your site's SEO and save hours of repetitive work!

The Scenario

Imagine you have a website with many pages, and you want to add titles and descriptions to each page manually by editing every single HTML file.

The Problem

Manually adding metadata to each page is slow, easy to forget, and causes inconsistent titles or missing descriptions, which hurts user experience and search engine ranking.

The Solution

Using metadata in layouts lets you set default titles and descriptions once, then customize them per page easily, ensuring consistency and saving time.

Before vs After

✗ Before

<title>Home</title>
<meta name="description" content="Welcome to our homepage">

✓ After

export const metadata = { title: 'Home', description: 'Welcome to our homepage' }

What It Enables

This makes your website SEO-friendly and user-friendly with less effort and fewer mistakes.

Real Life Example

A blog site where each article page automatically shows the article title in the browser tab and a summary in search results without repeating code.

Key Takeaways

Manually adding metadata is repetitive and error-prone.

Layouts let you define metadata once and reuse it.

This improves consistency, SEO, and developer productivity.

Practice

1. What is the main purpose of the metadata object in a Next.js layout?

easy

A. To manage client-side state in the layout

B. To style the layout components with CSS

C. To define page information like title and description for browsers and search engines

D. To handle user authentication in the layout

Solution

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

   The metadata object is used to provide page details such as title and description that browsers and search engines use.

2. Step 2: Differentiate metadata from other layout tasks

   Styling, authentication, and state management are handled separately, not by metadata.

3. Final Answer:

   To define page information like title and description for browsers and search engines -> Option C

4. Quick Check:

   Metadata = page info for browsers and SEO [OK]

Hint: Metadata sets page info, not styles or logic [OK]

Common Mistakes:

• Confusing metadata with CSS styling
• Thinking metadata manages user data
• Assuming metadata controls client state

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

easy

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

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

C. export function metadata() { return { title: 'Home' }; }

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

Solution

1. Step 1: Recall Next.js metadata export syntax

   Next.js expects a named export called metadata as a constant object.

2. Step 2: Check each option's syntax

   export const metadata = { title: 'Home' }; correctly exports a constant object. const metadata = { title: 'Home' }; export default metadata; exports default, which is incorrect. export function metadata() { return { title: 'Home' }; } exports a function, not an object. export metadata = { title: 'Home' }; has invalid export syntax.

3. Final Answer:

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

4. Quick Check:

   Named const export = correct syntax [OK]

Hint: Use named const export for metadata object [OK]

Common Mistakes:

• Using default export instead of named export
• Exporting a function instead of an object
• Incorrect export syntax without const

3. Given this layout file snippet, what will be the page title shown in the browser tab?

export const metadata = { title: 'Dashboard' };

export default function Layout({ children }) {
  return <main>{children}</main>;
}

medium

A. Dashboard

B. Home

C. Layout

D. No title will be shown

Solution

1. Step 1: Identify the metadata title value

   The metadata object sets title to 'Dashboard'.

2. Step 2: Understand Next.js behavior with metadata

   Next.js uses this metadata to set the HTML <title> tag, which appears in the browser tab.

3. Final Answer:

   Dashboard -> Option A

4. Quick Check:

   metadata.title = browser tab title [OK]

Hint: metadata.title sets browser tab title [OK]

Common Mistakes:

• Assuming default title if metadata is present
• Confusing layout function name with title
• Thinking children content affects title

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

const metadata = { title: 'Profile' };

export default function Layout({ children }) {
  return <main>{children}</main>;
}

What is the error?

medium

A. The title property must be inside a function

B. metadata must be exported with export const metadata

C. Layout must be a class component to use metadata

D. Children must be wrapped in a <section> tag

Solution

1. Step 1: Check metadata export

   The metadata object is declared but not exported, so Next.js cannot read it.

2. Step 2: Confirm correct export syntax

   Next.js requires export const metadata = { ... } to recognize metadata.

3. Final Answer:

   metadata must be exported with export const metadata -> Option B

4. Quick Check:

   Export metadata for Next.js to use it [OK]

Hint: Always export metadata as named const [OK]

Common Mistakes:

• Forgetting to export metadata
• Using function or class for metadata
• Changing children wrapper tags unnecessarily

5. You want to set a default description for all pages using a root layout metadata, but override it on a specific page. How should you structure your Next.js metadata exports?

hard

A. Export metadata with description in root layout, then export metadata with a different description in the page layout

B. Only export metadata in the root layout; page metadata is ignored

C. Merge metadata objects manually inside the root layout component

D. Use a global CSS file to set description meta tag

Solution

1. Step 1: Understand metadata inheritance in Next.js

   Metadata in layouts is merged, so root layout metadata applies by default.

2. Step 2: Override metadata in nested layouts or pages

   Exporting metadata in a page or nested layout overrides root metadata for that page.

3. Step 3: Confirm correct approach

   Export metadata with description in root layout, then export metadata with a different description in the page layout correctly describes exporting metadata in root and overriding in page layout.

4. Final Answer:

   Export metadata with description in root layout, then export metadata with a different description in the page layout -> Option A

5. Quick Check:

   Root metadata sets default, page metadata overrides [OK]

Hint: Root metadata sets default; page metadata overrides [OK]

Common Mistakes:

• Assuming page metadata is ignored if root exists
• Trying to merge metadata manually in code
• Using CSS to set metadata tags