Not seeing your schema on your website?

| Posted on |

If you added LocalBusiness schema in Schema Nerd but do not see it on your site, the cause is almost always one of these:

  • Your page is cached, so you are seeing an older version.
  • Another plugin is outputting schema too, creating duplicates or conflicts.
  • You are checking the wrong place (Schema Nerd outputs LocalBusiness JSON-LD in the universal header).
  • A performance tool is stripping or delaying scripts.

Use the steps below in order. Most issues are solved in under ten minutes.

Step 1: Confirm Schema Nerd is outputting schema on the page

Schema Nerd outputs LocalBusiness schema as JSON-LD in your site’s universal header. That means it should appear on most pages across your site.

How to check in your browser

  1. Open your website in Chrome (or your preferred browser).
  2. Right-click the page and select View Page Source.
  3. Press Ctrl + F (Windows) or Cmd + F (Mac).
  4. Search for: application/ld+json

If the schema is present, you should see a script block similar to:

  • A <script type="application/ld+json"> tag
  • A JSON object that includes @context and @type
  • For LocalBusiness, you should see @type as something like LocalBusiness or a more specific subtype (for example, Restaurant).

If you do not find any JSON-LD

Move to Step 2. This usually indicates caching, a theme output issue, or a script-stripping optimization plugin.

Step 2: Validate using Schema Nerd’s validator

Schema Nerd includes a validation tool that shows results from Google’s Schema Markup Validator.

  1. Open your WordPress dashboard.
  2. Go to Schema Nerd.
  3. Open the Schema Validation tool.
  4. Run validation for your site or the page you are testing.

What validation results mean

  • No errors: Your schema is valid. If you still do not see it in page source, your site is likely serving cached HTML or stripping scripts.
  • Warnings: Usually safe. Warnings often mean a recommended field is missing. Your schema can still be valid.
  • Errors: Fix these first. A single error can make the markup invalid or incomplete.

If you see errors, correct your schema entries and validate again.

Step 3: Clear caching, including server and plugin caches

Caching is the most common reason schema “does not show up,” especially right after changes.

Clear caches in this order:

  1. WordPress caching plugin cache
    Examples: WP Rocket, W3 Total Cache, LiteSpeed Cache, WP Super Cache.
  2. Hosting cache
    Many hosts provide a cache layer in their control panel. Clear it.
  3. CDN cache (if you use one)
    Examples: Cloudflare. Purge cache.
  4. Refresh the page and check again using View Page Source.

Quick test

Open the page in a private or incognito window after clearing cache. If schema appears there but not in your regular window, your browser cache may be involved too.

Step 4: Check for conflicts with other schema-producing plugins

Schema Nerd is designed to be your primary source of LocalBusiness schema output. If another plugin is also generating LocalBusiness schema, you can end up with:

  • Duplicate LocalBusiness nodes
  • Conflicting values (different phone numbers, hours, or addresses)
  • Validation warnings or errors

Common sources of duplicate schema:

  • SEO suites that output schema automatically (Yoast, Rank Math, AIOSEO, SEOPress, and similar)
  • Dedicated schema plugins
  • Themes that include built-in schema features
  • Manually added JSON-LD in header scripts

What to do

  1. Temporarily disable other schema-producing plugins, or disable their schema modules if they offer toggles.
  2. Clear cache again.
  3. Check page source for application/ld+json.
  4. Validate again using Schema Nerd.

If schema appears after disabling another plugin, you have confirmed a conflict. At that point, choose one tool to own LocalBusiness schema long term.

Step 5: Check optimization tools that strip or delay scripts

Some performance plugins and script optimizers can remove, delay, or alter JSON-LD.

Look for settings like:

  • “Delay JavaScript execution”
  • “Defer JavaScript”
  • “Remove unused CSS/JS”
  • “Minify inline scripts”
  • “Combine scripts”

What to do

Temporarily disable these features, clear cache, and re-check the page source. If schema reappears, re-enable features one at a time, and exclude Schema Nerd JSON-LD output if your tool supports exclusions.

Step 6: Confirm you are testing the right URL and page version

A few quick checks that catch a lot of edge cases:

  • Make sure you are viewing the correct domain version (www vs non-www).
  • Make sure you are not viewing a staging site.
  • Make sure you are not testing an AMP version or a cached “mobile” variant.
  • Make sure your theme or builder is not serving different templates to logged-in vs logged-out users.

Still not seeing it? Send this to Support

If you have worked through the steps and the schema still does not appear, contact support and include:

  1. The URL you tested
  2. A screenshot of your page source search for application/ld+json
  3. A screenshot of Schema Nerd validation results
  4. A list of active plugins, especially SEO, caching, and schema plugins
  5. Your theme name and hosting provider
  6. Whether you use a CDN (and which one)
  • With that information, we can usually pinpoint the cause quickly.