JSON-LD Schema for Business Websites: What Actually Helps SEO

Schema markup will not magically rank a thin brochure site. Used correctly, it helps search engines understand what the business is—and can unlock richer results for articles, FAQs, and local entities.

Here is the structured-data baseline I add on client websites.

Prefer JSON-LD in the page head

Google recommends JSON-LD. Keep one (or a few) <script type="application/ld+json"> blocks instead of scattering Microdata attributes through templates.

On Astro/static sites, generate it from a single data source (company name, URL, logo, social profiles). On WordPress, use a lean SEO plugin—or a small custom snippet—rather than three plugins fighting over the same graph.

Types that matter for most business sites

1. Organization / LocalBusiness

Use when the site represents a real company:

• name, url, logo;
• telephone, email, address when public;
• sameAs for official social profiles;
• LocalBusiness (or a more specific subtype) for local service businesses.

Do not invent NAP data. Inconsistent address/phone across the web hurts trust more than missing schema.

2. WebSite + SearchAction (optional)

Useful for sites with on-site search. Skip if there is no real search endpoint.

3. Article / BlogPosting

For blog posts: headline, datePublished, dateModified, author, image, mainEntityOfPage.

This supports content hubs—not every landing page needs Article markup.

4. FAQPage (only with visible FAQs)

Add FAQ schema only when the same Q&A is visible on the page. Hidden FAQ markup is a classic spam pattern.

5. BreadcrumbList

Helps clarify hierarchy on nested URLs (/portfolio/project/). Keep breadcrumbs consistent with visible UI.

Minimal Organization example

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Example Studio",
  "url": "https://example.com/",
  "logo": "https://example.com/logo.png",
  "sameAs": [
    "https://www.linkedin.com/company/example"
  ]
}

Extend to LocalBusiness when physical location or service area is a ranking factor.

Validation workflow

1. Deploy the page.
2. Test with Google Rich Results Test.
3. Check Search Console → Enhancements / Experience reports over the next weeks.
4. Fix errors; ignore vanity warnings that do not match the page type.

What not to do

• stuffing every Schema.org type “just in case”;
• marking product prices that are not shown;
• duplicating Organization five times via theme + plugin + GTM;
• using Review schema with fake ratings.

Keyword intent

Queries like schema markup website bisnis, json-ld localbusiness, and cara pasang structured data wordpress usually want a short, safe implementation list. Start with Organization/LocalBusiness + Article for the blog, validate, then expand only when the content supports it.