Structured data (JSON-LD) in NextJS - Performance & Optimization

Performance: Structured data (JSON-LD)

LOW IMPACT

Structured data affects page load speed slightly by adding script tags but mainly impacts SEO and rich results, not visual rendering.

Adding structured data to a Next.js page for SEO

NextJS

import Head from 'next/head'

export default function Page() {
  const jsonLd = {
    "@context": "https://schema.org",
    "@type": "Organization",
    "name": "Example"
  };

  return (
    <>
      <Head>
        <script
          type="application/ld+json"
          dangerouslySetInnerHTML={{ __html: JSON.stringify(jsonLd) }}
          key="jsonld"
        />
      </Head>
      <h1>Welcome</h1>
    </>
  )
}

Using Next.js Head with dangerouslySetInnerHTML injects JSON-LD as a single script tag without extra DOM nodes.

📈 Performance GainSingle script tag reduces DOM complexity and parsing time, improving load speed slightly.

Adding structured data to a Next.js page for SEO

NextJS

export default function Page() {
  return (
    <>
      <script type="application/ld+json">
        {`{
          "@context": "https://schema.org",
          "@type": "Organization",
          "name": "Example"
        }`}
      </script>
      <h1>Welcome</h1>
    </>
  )
}

Embedding JSON-LD as a React child causes React to treat it as text nodes, increasing DOM nodes and slowing parsing.

📉 Performance CostTriggers extra DOM nodes and parsing overhead, slightly delaying first content paint.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Embedding JSON-LD as React children	Multiple text nodes created	0	Minimal but increased parsing time	[X] Bad
Injecting JSON-LD via Next.js Head with dangerouslySetInnerHTML	Single script node	0	Minimal parsing cost	[OK] Good

Rendering Pipeline

JSON-LD script tags are parsed during HTML parsing but do not affect style calculation or layout. They add minimal script parsing cost but do not block rendering.

→HTML Parsing

→Script Parsing

⚠️ BottleneckScript Parsing

Optimization Tips

1Always inject JSON-LD as a single script tag to minimize DOM nodes.

2Avoid embedding JSON-LD as React children to prevent extra parsing overhead.

3Use Next.js Head with dangerouslySetInnerHTML for best structured data performance.

Performance Quiz - 3 Questions

What is the main performance impact of adding JSON-LD structured data to a Next.js page?

A Minimal script parsing cost without blocking rendering

B Triggers multiple reflows and layout shifts

C Blocks rendering until JSON-LD is fully parsed

D Adds large bundle size increasing load time

DevTools: Elements

How to check: Open DevTools, go to Elements panel, search for <script type="application/ld+json"> tag, and verify it is a single script node with JSON content.

What to look for: Confirm only one script tag exists for JSON-LD and no extra text nodes or nested elements increase DOM size.

Practice

1. What is the main purpose of adding JSON-LD structured data in a Next.js page?

easy

A. To improve server response time

B. To help search engines understand the page content better

C. To add interactive animations to the page

D. To style the page with custom CSS

Solution

1. Step 1: Understand JSON-LD role

   JSON-LD is a format for structured data that helps search engines understand the content of a webpage.

2. Step 2: Identify its use in Next.js

   In Next.js, JSON-LD is used to improve SEO by providing clear data to search engines, not for styling or animations.

3. Final Answer:

   To help search engines understand the page content better -> Option B

4. Quick Check:

   JSON-LD purpose = SEO improvement [OK]

Hint: JSON-LD is for SEO, not styling or animations [OK]

Common Mistakes:

• Confusing JSON-LD with CSS or JavaScript animations
• Thinking JSON-LD speeds up server response
• Assuming JSON-LD changes page appearance

2. Which is the correct way to include JSON-LD structured data in a Next.js component?

easy

A.

B.

C.

D.

Solution

1. Step 1: Use Next.js Script component

   Next.js provides the Script component from next/script to safely add scripts including JSON-LD.

2. Step 2: Use dangerouslySetInnerHTML correctly

   JSON-LD must be added as a string inside dangerouslySetInnerHTML to avoid React escaping it.

3. Final Answer:

   <Script type="application/ld+json" dangerouslySetInnerHTML={{ __html: JSON.stringify(data) }} /> -> Option C

4. Quick Check:

   Use Next.js Script + dangerouslySetInnerHTML [OK]

Hint: Use Next.js Script with dangerouslySetInnerHTML for JSON-LD [OK]

Common Mistakes:

• Using lowercase <script> tag directly in JSX
• Not using dangerouslySetInnerHTML for JSON-LD
• Forgetting to import Script from next/script

3. Given this Next.js code snippet, what will be the rendered output in the HTML?

import Script from 'next/script';

const data = {"@context": "https://schema.org", "@type": "Person", "name": "Alice"};

export default function Page() {
  return (
    <>
      <h1>Profile</h1>
      <Script type="application/ld+json" dangerouslySetInnerHTML={{ __html: JSON.stringify(data) }} />
    </>
  );
}

medium

A. Profile

B. Profile

C. Profile

D. Profile

Solution

1. Step 1: Understand Script output

   The Next.js Script component renders a <script> tag with the specified type and inner HTML.

2. Step 2: Check JSON-LD content

   The JSON-LD data is stringified and inserted as raw JSON inside the script tag with type application/ld+json.

3. Final Answer:

   <h1>Profile</h1><script type="application/ld+json">{"@context":"https://schema.org","@type":"Person","name":"Alice"}</script> -> Option D

4. Quick Check:

   JSON-LD script tag with stringified data [OK]

Hint: JSON-LD renders as script with type and stringified JSON [OK]

Common Mistakes:

• Using wrong script type attribute
• Rendering JSON object instead of string
• Placing JSON inside curly braces in HTML output

4. What is wrong with this Next.js code for adding JSON-LD?

import Script from 'next/script';

const data = {"@context": "https://schema.org", "@type": "Organization", "name": "My Company"};

export default function Home() {
  return (
    <Script type="application/ld+json">{JSON.stringify(data)}</Script>
  );
}

medium

A. Using <Script> without dangerouslySetInnerHTML causes JSON to render as text, not script content

B. Missing import of React causes error

C. JSON.stringify should not be used inside Script

D. Script component must be self-closing

Solution

1. Step 1: Check Script usage

   The Script component requires dangerouslySetInnerHTML to insert raw JSON-LD content inside the script tag.

2. Step 2: Identify the error

   Passing JSON string as children renders it as text inside the script tag, which is invalid for JSON-LD.

3. Final Answer:

   Using <Script> without dangerouslySetInnerHTML causes JSON to render as text, not script content -> Option A

4. Quick Check:

   Use dangerouslySetInnerHTML for JSON-LD scripts [OK]

Hint: Always use dangerouslySetInnerHTML for JSON-LD in Script [OK]

Common Mistakes:

• Passing JSON as children instead of dangerouslySetInnerHTML
• Forgetting to stringify JSON data
• Assuming Script auto-inserts raw JSON

5. You want to add multiple JSON-LD scripts for different entities on a Next.js page. Which approach correctly adds two JSON-LD scripts safely?

hard

A. Use two <Script> components each with type="application/ld+json" and dangerouslySetInnerHTML containing separate JSON objects

B. Combine both JSON objects into one and add a single <Script> with dangerouslySetInnerHTML

C. Add one <Script> with an array of JSON objects inside dangerouslySetInnerHTML

D. Add JSON-LD as inline JavaScript variables inside a single <Script> tag

Solution

1. Step 1: Understand JSON-LD script requirements

   Each JSON-LD script tag should contain a single JSON object describing one entity for clarity and correctness.

2. Step 2: Use multiple Script components

   In Next.js, you can safely add multiple Script components each with their own JSON-LD data using dangerouslySetInnerHTML.

3. Final Answer:

   Use two <Script> components each with type="application/ld+json" and dangerouslySetInnerHTML containing separate JSON objects -> Option A

4. Quick Check:

   Multiple Script tags with separate JSON-LD objects [OK]

Hint: Use separate Script tags for each JSON-LD object [OK]

Common Mistakes:

• Putting multiple JSON objects in one script tag without array
• Using arrays inside JSON-LD script which is invalid
• Embedding JSON-LD as JS variables instead of script content