Architecture scenarioMedium~10 min

Interview question

How would you generate correct metadata for a dynamic Next.js page?

Builds titles, descriptions, canonicals, Open Graph data, and not-found behavior from the same canonical page record.

1Say itAnswer out loud first

2CompareCompare with Core answer

3RefineRefine with Stronger and Advanced

TL;DR

I set a canonical metadataBase at the root and use static metadata when values do not depend on the route. For a dynamic page, generateMetadata awaits the params, loads the canonical record, and returns a specific title, description, canonical path, and Open Graph values. The page and metadata share the same data function so they cannot describe different resources.

Full answer below

Practice focus

Metadata API, generateMetadata, metadataBase, canonical URLs, Open Graph, data reuse, and SEO correctness.

Answer first

Answer path

Core answer first, then checkpoints toward a stronger answer.

Start
Core answer
Start here. This is the direct spoken answer to practice first.
Overview
Metadata is part of the page contract and should agree with the rendered resource, canonical host, and indexability decision.
I set a canonical metadataBase at the root and use static metadata when values do not depend on the route. For a dynamic page, generateMetadata awaits the params, loads the canonical record, and returns a specific title, description, canonical path, and Open Graph values. The page and metadata share the same data function so they cannot describe different resources.
Checkpoint
Stronger answer
Optional upgrade with examples, trade-offs, and sharper phrasing.
Missing content calls notFound rather than producing indexable metadata for an empty page. I use stable canonical URLs that exclude tracking parameters and point to the one preferred host, while localized or alternate pages get deliberate alternate links. Next.js memoizes matching fetch work across metadata and rendering, or I use React cache for non-fetch access. I remember that nested metadata objects are shallowly replaced, so setting one Open Graph field can discard inherited fields unless I merge the intended values.
Finish
Advanced answer
Optional deeper angle for production judgment and nuance.
I decide whether dynamic metadata can stream for the target crawler and whether cache behavior matches the content's publishing lifecycle. User-specific, preview, filtered, or private pages do not accidentally become canonical public records. Validation compares the final page URL, canonical tag, Open Graph URL, sitemap entry, status code, and robots directive for representative routes. I also monitor duplicate titles and descriptions because technically valid tags can still flatten thousands of pages into indistinguishable search results.

Review signals

Use these to catch weak phrasing, shallow reasoning, and risky claims.

Common mistakesCandidateCommon mistakesMistakes that weaken the answer or signal shallow understanding.Open details

Details

Building canonical URLs from an untrusted incoming host header.
Fetching separate inconsistent records for metadata and page content.
Overwriting inherited Open Graph fields unintentionally.

Red flagsCandidateRed flagsSignals that an interviewer may treat as risky.Open details

Details

Tracking parameters appear in canonical URLs.
Missing content returns 200 with generic metadata.
Every dynamic page has the same description.

Follow-up prompts

Quick interviewer prompts inside this drill.

Follow-up questionsCandidateFollow-up questionsLikely next questions after the main answer.Open details

Details

Treat these as the next interviewer turn. Answer one out loud, then save the gap in your practice notes.

What does metadataBase solve?
How are nested metadata fields merged?
Should filtered pages be canonical?

Continue practice

Move to the linked follow-up, next path step, prerequisite, or deeper variant.

1 linked

Prerequisite

Review this first if the current drill feels shaky.

Async route APIsUses asynchronous route params to resolve canonical page data.

Practice route

Read core answer Review checklist Follow-up prompts Track progress

Finished this drill?

Practice freely. Sign in only when you want to save completion, confidence, notes, or bookmarks.

New to Aporeon? Create account

Drill details

Human editorial direction

Aporeon is shaped by Aleksandar Tomovski, a software developer with experience on both sides of technical interviews. Content is reviewed for accuracy, natural spoken delivery, useful depth, and honest trade-offs.

About the creator Editorial standards

Was this drill useful?

Help improve the interview library.

Found this answer useful?

Say thanks with a standalone, one-time $5 contribution. No account required.

No subscription or perks.Choose another amount

Opening drill

Architecture scenarioMedium~10 min

Interview question

How would you generate correct metadata for a dynamic Next.js page?

Builds titles, descriptions, canonicals, Open Graph data, and not-found behavior from the same canonical page record.

1Say itAnswer out loud first

2CompareCompare with Core answer

3RefineRefine with Stronger and Advanced

TL;DR

Full answer below

Practice focus

Metadata API, generateMetadata, metadataBase, canonical URLs, Open Graph, data reuse, and SEO correctness.

Answer first

Answer path

Core answer first, then checkpoints toward a stronger answer.

Start
Core answer
Start here. This is the direct spoken answer to practice first.
Overview
Metadata is part of the page contract and should agree with the rendered resource, canonical host, and indexability decision.
I set a canonical metadataBase at the root and use static metadata when values do not depend on the route. For a dynamic page, generateMetadata awaits the params, loads the canonical record, and returns a specific title, description, canonical path, and Open Graph values. The page and metadata share the same data function so they cannot describe different resources.
Checkpoint
Stronger answer
Optional upgrade with examples, trade-offs, and sharper phrasing.
Missing content calls notFound rather than producing indexable metadata for an empty page. I use stable canonical URLs that exclude tracking parameters and point to the one preferred host, while localized or alternate pages get deliberate alternate links. Next.js memoizes matching fetch work across metadata and rendering, or I use React cache for non-fetch access. I remember that nested metadata objects are shallowly replaced, so setting one Open Graph field can discard inherited fields unless I merge the intended values.
Finish
Advanced answer
Optional deeper angle for production judgment and nuance.
I decide whether dynamic metadata can stream for the target crawler and whether cache behavior matches the content's publishing lifecycle. User-specific, preview, filtered, or private pages do not accidentally become canonical public records. Validation compares the final page URL, canonical tag, Open Graph URL, sitemap entry, status code, and robots directive for representative routes. I also monitor duplicate titles and descriptions because technically valid tags can still flatten thousands of pages into indistinguishable search results.

Review signals

Use these to catch weak phrasing, shallow reasoning, and risky claims.

Common mistakesCandidateCommon mistakesMistakes that weaken the answer or signal shallow understanding.Open details

Details

Building canonical URLs from an untrusted incoming host header.
Fetching separate inconsistent records for metadata and page content.
Overwriting inherited Open Graph fields unintentionally.

Red flagsCandidateRed flagsSignals that an interviewer may treat as risky.Open details

Details

Tracking parameters appear in canonical URLs.
Missing content returns 200 with generic metadata.
Every dynamic page has the same description.

Follow-up prompts

Quick interviewer prompts inside this drill.

Follow-up questionsCandidateFollow-up questionsLikely next questions after the main answer.Open details

Details

Treat these as the next interviewer turn. Answer one out loud, then save the gap in your practice notes.

What does metadataBase solve?
How are nested metadata fields merged?
Should filtered pages be canonical?

Continue practice

Move to the linked follow-up, next path step, prerequisite, or deeper variant.

1 linked

Prerequisite

Review this first if the current drill feels shaky.

Async route APIsUses asynchronous route params to resolve canonical page data.

How would you generate correct metadata for a dynamic Next.js page?

Practice focus

Answer path

Overview

Review signals

Follow-up prompts

Continue practice

Prerequisite

How would you generate correct metadata for a dynamic Next.js page?

Practice focus

Answer path

Overview

Review signals

Follow-up prompts

Continue practice

Prerequisite