GenerateMetadata for dynamic metadata in NextJS - Step-by-Step Execution

Concept Flow - GenerateMetadata for dynamic metadata

Request for page

↓

Call generateMetadata()

↓

Fetch or compute data

↓

Return metadata object

↓

Next.js uses metadata to set <head>

↓

Render page with dynamic metadata

When a page is requested, Next.js calls generateMetadata to get dynamic metadata, then uses it to set the page's head before rendering.

Execution Sample

NextJS

export async function generateMetadata({ params }) {
  const data = await fetchData(params.id);
  return {
    title: data.title,
    description: data.description
  };
}

This code fetches data based on params and returns dynamic metadata for the page.

Execution Table

Step	Action	Input/State	Output/Result
1	Page requested	params.id = '123'	Trigger generateMetadata call
2	Call generateMetadata	params.id = '123'	Start fetching data
3	Fetch data	params.id = '123'	{ title: 'Hello', description: 'Welcome' }
4	Return metadata	Fetched data	{ title: 'Hello', description: 'Welcome' }
5	Next.js sets <head>	Metadata object	Page head updated with title and description
6	Render page	Metadata set	Page rendered with dynamic metadata

💡 generateMetadata returns metadata object, Next.js uses it to render page head dynamically

Variable Tracker

Variable	Start	After Step 3	Final
params.id	undefined	'123'	'123'
data	undefined	{ title: 'Hello', description: 'Welcome' }	{ title: 'Hello', description: 'Welcome' }
metadata	undefined	undefined	{ title: 'Hello', description: 'Welcome' }

Key Moments - 2 Insights

Why does generateMetadata receive params as input?

Because generateMetadata uses params to fetch or compute the right metadata for the requested page, as shown in step 2 and 3 of the execution_table.

What happens if generateMetadata returns incomplete metadata?

Next.js will use whatever metadata is returned to set the page head, but missing fields may cause default or empty values, as seen in step 4 and 5.

Visual Quiz - 3 Questions

Look at the execution_table, what is the output of step 3?

A Trigger generateMetadata call

B { title: 'Hello', description: 'Welcome' }

C Page rendered with dynamic metadata

D Start fetching data

💡 Hint

Check the 'Output/Result' column in step 3 of the execution_table.

At which step does Next.js update the page head with metadata?

A Step 5

B Step 2

C Step 4

D Step 6

💡 Hint

Look for the action describing setting in the execution_table.

If params.id was '456' instead of '123', which variable changes in variable_tracker?

A data

B metadata

C params.id

D All of the above

💡 Hint

Check the 'params.id' row in variable_tracker for changes.

Concept Snapshot

generateMetadata is an async function in Next.js that runs on each page request.
It receives params and returns an object with metadata like title and description.
Next.js uses this metadata to update the page <head> dynamically before rendering.
This enables pages to have unique metadata based on data or route parameters.

Full Transcript

When a user requests a page, Next.js calls the generateMetadata function with route parameters. This function fetches or computes data needed for metadata, such as the page title and description. After fetching, it returns an object containing this metadata. Next.js then uses this object to update the HTML head tags dynamically, ensuring the page has the correct metadata before rendering. This process allows each page to have unique metadata based on its content or URL parameters.

Practice

1. What is the main purpose of the generateMetadata function in Next.js?

easy

A. To fetch data on the client after page load

B. To handle client-side routing between pages

C. To create dynamic page titles and descriptions before rendering

D. To style components dynamically using CSS

Solution

1. Step 1: Understand the role of generateMetadata

   This function runs on the server before the page renders to set metadata dynamically.

2. Step 2: Identify its main use

   It is used to create dynamic page titles and descriptions for SEO and relevant info.

3. Final Answer:

   To create dynamic page titles and descriptions before rendering -> Option C

4. Quick Check:

   Dynamic metadata = To create dynamic page titles and descriptions before rendering [OK]

Hint: Remember: generateMetadata sets SEO info before page loads [OK]

Common Mistakes:

• Confusing generateMetadata with client-side data fetching
• Thinking it handles routing or styling
• Assuming it runs on the client

2. Which of the following is the correct syntax to export a generateMetadata function in a Next.js page?

easy

A. export const generateMetadata = () => { document.title = 'Page' }

B. export async function generateMetadata() { return { title: 'Page' } }

C. function generateMetadata() { console.log('metadata') } export generateMetadata

D. export default function generateMetadata() { return Page }

Solution

1. Step 1: Recall correct export syntax

   Next.js expects generateMetadata as an exported async function returning an object with metadata.

2. Step 2: Check each option

   export async function generateMetadata() { return { title: 'Page' } } correctly exports an async function returning an object with a title property.

3. Final Answer:

   export async function generateMetadata() { return { title: 'Page' } } -> Option B

4. Quick Check:

   Correct export syntax = export async function generateMetadata() { return { title: 'Page' } } [OK]

Hint: Use async function returning object for generateMetadata [OK]

Common Mistakes:

• Using default export instead of named export
• Returning JSX instead of an object
• Trying to set document.title inside generateMetadata

3. Given this generateMetadata function, what will be the page title?

export async function generateMetadata({ params }) {
  return { title: `User: ${params.username}` };
}

And the URL is /user/jane.

medium

A. User: jane

B. User: params.username

C. User: undefined

D. User: /user/jane

Solution

1. Step 1: Understand parameter usage

   The function receives params with username from the URL segment.

2. Step 2: Substitute params.username with actual value

   Since URL is /user/jane, params.username is 'jane', so title becomes 'User: jane'.

3. Final Answer:

   User: jane -> Option A

4. Quick Check:

   Dynamic title uses params.username = User: jane [OK]

Hint: URL params fill template strings in generateMetadata [OK]

Common Mistakes:

• Using literal string 'params.username' instead of value
• Assuming params is undefined without route setup
• Confusing URL path with metadata title

4. What is wrong with this generateMetadata function?

export function generateMetadata() {
  return { title: 'Home' }
  console.log('Metadata generated')
}

medium

A. generateMetadata cannot be a named export

B. The function must be async to work

C. The return value must be a string, not an object

D. The console.log runs after return and is unreachable

Solution

1. Step 1: Analyze function flow

   The return statement ends the function immediately, so code after it won't run.

2. Step 2: Identify unreachable code

   The console.log after return is unreachable and will never execute.

3. Final Answer:

   The console.log runs after return and is unreachable -> Option D

4. Quick Check:

   Code after return is unreachable = The console.log runs after return and is unreachable [OK]

Hint: Code after return is ignored, place logs before return [OK]

Common Mistakes:

• Thinking function must be async always
• Expecting return to accept strings only
• Confusing export types

5. You want to create dynamic metadata for a blog post page that shows the post title and author. Which generateMetadata implementation correctly handles this using params and fetch to get post data asynchronously?

hard

A. export async function generateMetadata({ params }) {
const post = await fetch(`/api/posts/${params.id}`).then(res => res.json());
return { title: post.title, description: `By ${post.author}` };
}

B. export function generateMetadata({ params }) {
const post = fetch(`/api/posts/${params.id}`).then(res => res.json());
return { title: post.title, description: `By ${post.author}` };
}

C. export async function generateMetadata() {
const post = await fetch('/api/posts').then(res => res.json());
return { title: post.title, description: post.author };
}

D. export async function generateMetadata({ params }) {
return { title: params.title, description: params.author };
}

Solution

1. Step 1: Identify async data fetching

   To get post data dynamically, generateMetadata must be async and await the fetch call.

2. Step 2: Check usage of params and fetch

   export async function generateMetadata({ params }) { const post = await fetch(`/api/posts/${params.id}`).then(res => res.json()); return { title: post.title, description: `By ${post.author}` }; } correctly awaits fetch with params.id and returns metadata using fetched data.

3. Final Answer:

   export async function generateMetadata({ params }) { const post = await fetch(`/api/posts/${params.id}`).then(res => res.json()); return { title: post.title, description: `By ${post.author}` }; } -> Option A

4. Quick Check:

   Async fetch with params used correctly = export async function generateMetadata({ params }) { const post = await fetch(`/api/posts/${params.id}`).then(res => res.json()); return { title: post.title, description: `By ${post.author}` }; } [OK]

Hint: Use async/await with params to fetch dynamic metadata [OK]

Common Mistakes:

• Not awaiting fetch causing unresolved promises
• Ignoring params and fetching all posts
• Returning params directly without fetching data