SEO and Schema.org: Article and Organization as JSON-LD

Schema.org is a shared vocabulary for structured data on web pages: types such as Article and Organization, usually as JSON-LD in the HTML. SEO gets machine-readable facts beside the prose. Google may build rich results from that. It does not have to.

Two checkpoints before you ship:

• Schema.org Validator: checks whether types and properties match the standard. Also useful for reading how other sites mark things up.
• Google Rich Results Test: checks what Google accepts for enhanced results.

What Schema.org gives you

You name entities explicitly: this is an article, this is the organization behind it, this is the publish date. Search engines and other parsers guess less. Visible upside often shows up around Q&A-style results, bylines, logos, and knowledge-panel building blocks. The prose still has to work. Markup without content is decoration.

Article: JSON-LD example

For magazine and blog pages, Article is usually enough (or a subtype such as NewsArticle / BlogPosting when it truly fits). A minimal useful block:

{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "SEO and Schema.org",
  "datePublished": "2023-01-05T11:57:54+01:00",
  "dateModified": "2026-09-09T12:00:00+02:00",
  "author": {
    "@type": "Person",
    "name": "John McGrinsey"
  },
  "publisher": {
    "@type": "Organization",
    "name": "McGrinsey",
    "logo": {
      "@type": "ImageObject",
      "url": "https://mcgrinsey.com/logo.png"
    }
  },
  "image": "https://mcgrinsey.com/media/auto-seo-und-schema-org.png",
  "mainEntityOfPage": "https://mcgrinsey.com/magazin/seo-und-schema-org/"
}

Replace URLs and dates with your real values. Keep the headline short. Use dates with a timezone. Give the publisher logo a stable absolute URL.

Organization: JSON-LD example

For about pages, legal pages, or sitewide identity:

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Example Corporation",
  "url": "https://www.example.com",
  "logo": "https://www.example.com/images/logo.png",
  "sameAs": [
    "https://www.linkedin.com/company/example",
    "https://x.com/example"
  ],
  "contactPoint": {
    "@type": "ContactPoint",
    "contactType": "customer service",
    "email": "contact@example.com"
  }
}

sameAs ties official profiles together. One Organization per brand is usually enough. Several conflicting blocks on the same domain create noise.

Do tables need schema so Google can read them?

No. The Googlebot can extract table contents without semantic markup. Schema.org does not replace a clear HTML table or a clear sentence about it. It adds types and relationships that would otherwise stay implicit.

Short workflow

1. Pick the type (Article, Organization, …).
2. Put JSON-LD in a <script type="application/ld+json"> in the document.
3. Run validator.schema.org on the URL or the snippet.
4. Run the Rich Results Test if you aim at Google enhancements.

Fact table

Claim	Basket	From where
Schema.org is a shared vocabulary for structured data on the web	Fact	schema.org docs
JSON-LD is a common embedding format for Schema.org in HTML	Fact	schema.org / Google Search Central on structured data
Article and Organization are Schema.org types with documented properties	Fact	schema.org/Article, schema.org/Organization
Tables do not need schema markup for the Googlebot to read cells	Fact	Original stub 5 Jan 2023; common crawl practice, not a promise of any specific rich result
Valid markup raises the chance of rich results, it does not force them	Hypothesis	Google stresses eligibility and guidelines; serving stays on their side