Metadata in layouts in NextJS - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of metadata in Next.js layouts?

Metadata in Next.js layouts defines information like page titles, descriptions, and icons that help browsers and search engines understand the page content.

beginner

How do you define metadata in a Next.js layout file?

You export a constant named metadata from the layout file, which is an object containing properties like title, description, and icons.

intermediate

Can metadata in Next.js layouts be dynamic or must it be static?

Metadata in Next.js layouts is typically static and exported as a constant. For dynamic metadata, you use special functions or server components to generate it per page.

intermediate

What happens if you define metadata in both a layout and a page in Next.js?

Metadata defined in a page overrides or merges with the metadata from the layout, allowing specific pages to customize titles or descriptions while keeping shared layout metadata.

beginner

Why is it important to include metadata like description and icons in layouts?

Including metadata like description helps search engines show meaningful summaries, and icons improve user experience by showing the right favicon in browser tabs.

How do you add a page title in a Next.js layout's metadata?

A Use a <code>&lt;title&gt;</code> tag inside the layout's JSX

B Set a global variable named <code>pageTitle</code>

C Export a <code>metadata</code> object with a <code>title</code> property

D Add a <code>title</code> attribute to the layout's root element

In Next.js layouts, you export a metadata object with a title property to set the page title.

What type of data structure is used for metadata in Next.js layouts?

A A plain JavaScript object

B A function returning JSX

C An array of strings

D A JSON string

Metadata is defined as a plain JavaScript object exported from the layout file.

If a page defines metadata and its parent layout also defines metadata, what happens?

A Page metadata merges or overrides layout metadata where specified

B Layout metadata is ignored

C Both metadata objects cause an error

D Page metadata completely replaces layout metadata

Page metadata merges with or overrides layout metadata, allowing customization per page.

Which metadata property is used to specify the favicon in Next.js layouts?

A image

B favicon

C icon

D icons

The icons property is used to specify favicons and related icons.

Why should metadata be included in layouts rather than only in pages?

A To make metadata dynamic

B To avoid repeating common metadata on every page

C Because pages cannot have metadata

D To disable SEO

Including metadata in layouts avoids repetition and ensures consistent metadata across pages.

Explain how metadata is defined and used in Next.js layouts.

Think about how you tell the browser about page info in a shared layout.

Describe the benefits of placing metadata in layouts instead of only in individual pages.

Consider how shared info helps when many pages use the same layout.

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