How to Add JSON-LD Structured Data

Implement FAQ, LocalBusiness, and product markup correctly—the first time, without breaking your templates.

Generate JSON-LD Free
  • No signup required
  • Free schema generator
  • Valid JSON-LD output

How to Add JSON-LD (Quick Answer)

  1. Choose the schema type that matches your page
  2. Generate JSON-LD with the Schema Generator
  3. Paste the script tag into your page head or body
  4. Validate with Google's Rich Results Test
  5. Deploy and monitor for errors in Search Console

Generate copy-paste JSON-LD with our free Schema Generator.

Generate JSON-LD Free

Try It Yourself

Open the Schema Generator and create JSON-LD while following the steps in this guide.

Open Schema Generator

Example Report Preview

Preview valid JSON-LD output ready to copy into your site.

Generate JSON-LD Free

What JSON-LD Structured Data Covers

Adding JSON-LD tells search engines and AI systems what type of content is on a page and which facts are authoritative.

  • Organization and LocalBusiness entities

    On-page signal reviewed during analysis.

  • FAQPage question-and-answer pairs

    Buyer questions you can answer in content.

  • Article and blog post metadata

    Supporting copy that drives clicks from search results.

  • Product name, price, and availability

    On-page signal reviewed during analysis.

  • Required schema.org fields for validation

    Machine-readable context for rich results and AI.

  • Match between visible content and markup

    Whether the page fully answers the search intent.

Valid structured data reduces ambiguity and can unlock rich results in search and clearer AI interpretations.

Why JSON-LD Implementation Matters

  • Invalid JSON breaks parsing entirely one comma can void the snippet.
  • Mismatched schema types Confuse crawlers about page purpose.
  • Outdated prices or URLs Outdated prices or URLs in schema erode trust signals.

Step-by-Step: Add JSON-LD Markup

  1. Step 1: Choose a schema type

    Match the type to visible content: Article, FAQPage, LocalBusiness, Product, or Organization.

    • Does this type match what users see?
    • Are required fields available?

  2. Step 2: Generate a snippet

    Use the Schema Generator to produce valid JSON-LD with your real business data.

  3. Step 3: Paste into your template

    Add a script tag with type application/ld+json in the head or before </body>.

    Good

    <script type="application/ld+json">{ ... valid JSON ... }</script>

    Bad

    Inline microdata attributes mixed into unrelated HTML

  4. Step 4: Validate the page

    Run the live URL through Google's Rich Results Test or Schema Markup Validator.

    • Zero errors?
    • Warnings reviewed?
    • Fields match visible content?

  5. Step 5: Deploy and monitor

    Publish changes and watch Search Console for structured data issues.

Common JSON-LD Implementation Mistakes

  • Placeholder URLs and names

    Why it hurts Crawlers index wrong entities tied to your domain.

    How to fix it Replace every example.com value before deploy.

  • Schema type mismatch

    Why it hurts FAQ schema on a page with no FAQs triggers manual review risk.

    How to fix it Only use types that reflect on-page content.

  • Never updating after price or offer changes

    Why it hurts Stale product data misleads users and violates guidelines.

    How to fix it Regenerate schema when pricing, hours, or offers change.

Frequently Asked Questions

Can I add multiple schema types to one page?

Yes. Many pages use multiple JSON-LD blocks—for example, Organization plus WebSite on the homepage, or Product plus FAQPage on a product page with common questions. Each block should describe a distinct aspect of the page without contradicting the others. Avoid duplicating the same type with conflicting values. Validate the combined output on the live URL after deployment.

Where should I place the JSON-LD script?

Google accepts JSON-LD in either the head or body of the document. Most teams place it in the head for consistency with other meta tags, but either location works if the JSON is valid. In CMS platforms, use a dedicated SEO or schema field rather than embedding in article body content. Keep scripts out of user-editable areas where they might be accidentally removed.

Do I need JSON-LD on every page?

No. Focus on high-value URLs first: homepage, services, products, locations, and top articles or FAQs. Utility pages like login or cart rarely need schema. Quality beats quantity—one accurate LocalBusiness block beats schema spam on every footer link. Expand coverage as your process matures and validation stays clean.

Related Tools

Related Guides