Metadata API for SEO in NextJS - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of the Metadata API in Next.js?

The Metadata API in Next.js helps you add SEO-friendly tags like title, description, and social media info to your pages easily and consistently.

beginner

How do you define metadata for a page using the Next.js Metadata API?

You export a constant named metadata from your page or layout file with properties like title, description, and openGraph to set SEO tags.

beginner

Which metadata property controls the page title in Next.js Metadata API?

The title property sets the page title shown in the browser tab and search results.

intermediate

What is the benefit of using the Metadata API over manually adding <head> tags?

The Metadata API ensures consistent, automatic SEO tags across pages, reduces errors, and integrates well with Next.js routing and server rendering.

intermediate

Name two social media metadata types supported by Next.js Metadata API.

Next.js Metadata API supports openGraph for Facebook and LinkedIn, and twitter for Twitter card metadata.

How do you export metadata in a Next.js page for SEO?

A Export a constant named metadata with SEO info

B Add meta tags inside the page's JSX return

C Use a special hook called useMetadata()

D Create a separate JSON file with SEO data

You export a constant named metadata from the page or layout file to define SEO tags.

Which property sets the page description in Next.js Metadata API?

A description

B title

C keywords

D summary

The description property sets the page's meta description tag.

What does the openGraph property in metadata configure?

A Browser tab color

B Font styles

C Page loading speed

D Social media preview info

openGraph configures social media preview details like title, description, and images.

Where should you place the metadata export in a Next.js app?

A In the public folder

B In the global CSS file

C Inside the page or layout file

D In the next.config.js file

Metadata is exported from the page or layout file to apply SEO tags for that route.

Which Next.js version introduced the Metadata API for SEO?

A Next.js 12

B Next.js 13

C Next.js 14

D Next.js 11

Next.js 13 introduced the Metadata API to simplify SEO management.

Explain how to use the Metadata API in Next.js to improve SEO on a page.

Think about what SEO tags you want and where to put them in your Next.js app.

Describe the advantages of using Next.js Metadata API instead of manual meta tags.

Consider how automation helps avoid mistakes and saves time.

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