Skip to content

Identify your business with Organization structured data

Describe your business (name, logo, contact details, official profiles) in JSON-LD so search and AI systems can connect your site to the right entity.

Intermediate 30 minutes By WebGrowthEngine team · Updated Oct 14, 2026

The problem

The site has no structured data identifying the organization, no links to official profiles, or JSON-LD blocks that are not valid JSON.

How to spot it

The audit reports no Organization or LocalBusiness markup, or invalid JSON-LD blocks.

Why it matters

Structured data states facts about your business in a machine-readable form, which helps systems tell you apart from similarly named businesses. Invalid JSON-LD is ignored entirely.

What happens if you leave it

Machines must guess who you are from page text, and broken markup gives no benefit at all.

How to fix it

  1. Add JSON-LD to your homepage (and optionally every page) using the most specific type that fits: Organization, LocalBusiness or a subtype such as Plumber or Dentist:

    <script type="application/ld+json">
    {
      "@context": "https://schema.org",
      "@type": "Plumber",
      "name": "Acme Plumbing",
      "url": "https://www.example.com/",
      "logo": "https://www.example.com/logo.png",
      "telephone": "+880-1700-000000",
      "address": { "@type": "PostalAddress", "addressLocality": "Dhaka", "addressCountry": "BD" },
      "sameAs": ["https://www.facebook.com/acmeplumbing", "https://www.linkedin.com/company/acme-plumbing"]
    }
    </script>
    
  2. Only include facts that are true and visible elsewhere on your site.

  3. Add markup for other page types too (Article, Product, Service, BreadcrumbList).

  4. Validate every block. A single missing comma invalidates it.

Common mistakes

  • Adding review ratings you did not collect, or details that are not on the site. This is against search guidelines.
  • Several conflicting Organization blocks from different plugins.

How to check the fix worked

Paste the page URL into the Schema.org validator; it should parse with no errors. Re-run the audit.

References and further reading

Was this guide helpful?

Are you sure?