Schema Markup & Structured Data: How to Use JSON-LD Correctly

Schema Markup helps search engines understand content not just as text, but as structured information. Instead of only reading that a page contains a company, a product, an article or an FAQ, machines can assign this information clearly and consistently.

This is why RankScan combines the insights “Missing Schema Markup”, “Missing Organization MarkupOrganization schema describes a company or organisation as an entity, with details such as name, URL, logo, address, contact and official profiles.Open glossary entry →” and “Missing Q&A Structure” in the Website Health category.

The correct classification is important:

Structured dataSchema markup is code that describes a page's content in a structured way, so search engines understand it not just as text but as clearly classified information.Open glossary entry → is not a ranking trick and not a guarantee for rich snippetsRich results are enhanced displays in Google, for example with ratings, prices or breadcrumbs, which can be enabled by suitable structured data.Open glossary entry →. It is a technical clarity signal.

For Google, structured markup can be a requirement for certain rich results. For website operators, it is primarily a way to mark up content in a more machine-readable, unambiguous and consistent way.

This article explains what Schema Markup is, when you should use JSON-LDJSON-LD (JavaScript Object Notation for Linked Data) is a data format for embedding structured data in a page, separate from the visible HTML. Google recommends it where technically possible.Open glossary entry → (JavaScript Object NotationJavaScript Object Notation (JSON) is a lightweight, text-based data format for storing and exchanging data. It is human-readable and easy for machines to process.Open glossary entry → for Linked Data, a data format for structured data), which schema types are especially relevant for RankScan and how to prioritize missing structured data sensibly.

What Is Schema Markup? #

Schema Markup is code that describes the content of a web page in a structured way.

Example: On a product page, a human immediately sees:

• product name,
• price,
• availability,
• brand,
• rating.

Search engines can infer this information from the text, but structured data marks it up explicitly.

Google describes structured data as a standardized format for providing information about a page and classifying its content. Structured data can help Google understand content better and qualify it for rich results.
Source: Google Search Central – Introduction to structured data

Schema.org, Structured Data and Rich Results: The Difference #

These terms are often mixed together, but they do not mean the same thing.

Schema.org is the dictionary.
JSON-LD is the format.
Structured data is the marked-up information.
Rich results are a possible effect.

Schema.org describes itself as a shared vocabulary for structured data on the internet.
Source: Schema.org – Getting started

Why Structured Data Matters for Website Health #

Structured data is not equally important on every page. However, missing or incorrect structured data can make it harder for search engines to assign important information clearly.

Typical benefits:

• clearer entity information,
• more machine-readable content structure,
• rich-result eligibility for suitable page types,
• better connection between organization, website, author, article and products,
• more consistent signals between website, Google Business Profile, social profiles and external sources,
• easier validation of technical SEOSearch Engine Optimization (SEO) covers all measures that help a website become more visible in unpaid (organic) search results.Open glossary entry → quality.

Important: Google explicitly states that structured data can be used to understand content and qualify it for rich results. But Google does not guarantee that rich results will be displayed.
Source: Google Search Central – Structured Data Gallery

Why JSON-LD Is Recommended #

There are several ways to implement structured data:

• JSON-LD,
• Microdata,
• RDFa.

Google recommends JSON-LD when the website setup allows it because it is easier to implement and maintain.
Source: Google Search Central – Introduction to structured data

Example:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "WebPage",
  "name": "Schema Markup & Structured Data: Guide with JSON-LD",
  "description": "A guide to implementing structured data with JSON-LD."
}
</script>

Advantages of JSON-LD:

• separate from visible HTML (Hypertext Markup Language, the markup language for web pages),
• easier to output in templates,
• easier to maintain,
• less vulnerable to design changes,
• well suited for CMSA content management system (CMS) is software for creating, managing and publishing web content, usually without programming knowledge. Well-known examples are WordPress or Shopify.Open glossary entry → (Content Management System) and shop templates.

What Does “Missing Schema Markup” Mean? #

The RankScan insight “Missing Schema Markup” means that no, or no meaningfully recognizable, structured data markup was found on a relevant page.

This is not equally critical for every URL.

It is usually less critical on:

• simple privacy policy pages,
• login pages,
• unimportant technical pages,
• noindexnoindex is a robots directive telling search engines that a page should not appear in search results. The page must remain crawlable for it to work.Open glossary entry → pages,
• thank-you pages.

It is more relevant on:

• homepages,
• about pages,
• service pages,
• product pages,
• local location pages,
• guide articles,
• FAQ or help pages,
• events,
• job postings,
• recipes,
• reviews,
• software or SaaS pages.

For RankScan, the decisive factor is therefore which page type is affected and which schema would make sense there.

What Does “Missing Organization Markup” Mean? #

The insight “Missing Organization Markup” means that RankScan did not find clear Organization markup.

The Organization Schema describes your company as an entity.

Typical information:

• name,
• URL,
• logo,
• legal name,
• address,
• contact,
• social media profiles,
• identifiers,
• founding information,
• brand relationships.

Schema.org defines Organization as an organization such as a company, school, NGO, club or similar institution.
Source: Schema.org – Organization

Organization Schema is especially important on:

• homepage,
• about page,
• contact page,
• global website layout,
• company profile pages.

It does not need to be repeated in full on every page. What matters is that the organization is marked up clearly and consistently.

Example: Organization Schema with JSON-LD #

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "@id": "https://example.ch/#organization",
  "name": "Example AG",
  "legalName": "Example AG",
  "url": "https://example.ch/",
  "logo": "https://example.ch/assets/logo.png",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "Bahnhofstrasse 10",
    "postalCode": "8001",
    "addressLocality": "Zurich",
    "addressCountry": "CH"
  },
  "contactPoint": {
    "@type": "ContactPoint",
    "telephone": "+41 44 123 45 67",
    "contactType": "customer service",
    "email": "contact@example.ch"
  },
  "sameAs": [
    "https://www.linkedin.com/company/example",
    "https://www.youtube.com/@example"
  ]
}
</script>

Important:

• keep @id stable,
• make the logo URL accessible,
• only include social profiles if they are official,
• keep address and contact details up to date,
• details must match the visible company information.

What Does “Missing Q&A Structure” Mean? #

The insight “Missing Q&A Structure” means that a page contains questions and answers, or could benefit from them, but no clear Q&A or FAQ structure was detected.

This is not only about code. A good check also evaluates whether questions and answers are editorially structured in a clean way.

Examples of suitable pages:

• FAQ pages,
• help sections,
• support articles,
• product questions,
• guides with frequently asked questions,
• service pages with recurring customer questions.

Important: FAQ markup should only be used for visible FAQ content. Content in the markup must match the visible content on the page. In its general structured data guidelines, Google notes that structured data must represent the visible page content.
Source: Google Search Central – General Structured Data Guidelines

FAQ Markup: A Realistic Classification #

FAQ markup was long a popular way to gain prominent FAQ rich results in Google. Today, this visibility is heavily restricted.

Google already announced in 2023 that FAQ rich results would be shown more frequently only for well-known, authoritative government and health websites. Current Google documentation still describes FAQPage markup and also notes that structured data is not a guarantee for rich results.
Source: Google Search Central – FAQPage Structured Data

For RankScan, this means:

• FAQ markup is no longer primarily a CTRThe click-through rate (CTR) indicates how many users click a search result relative to the number of times it is shown (impressions). It reflects how appealing a listing appears in search.Open glossary entry → (click-through rate) lever.
• FAQ markup should not be added artificially to every page.
• FAQ structures are still useful when real questions and answers are present.
• The focus is on clarity, machine-readable structure and content qualityHigh-quality content comes from better information value, not from more words. It fully answers the search intent, provides concrete facts, shows expertise and supports key statements with sources.Open glossary entry →.

Example: FAQPage with JSON-LD #

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "What is Schema Markup?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Schema Markup is structured code that helps search engines understand the content of a web page clearly."
      }
    },
    {
      "@type": "Question",
      "name": "Does FAQ markup guarantee a rich result?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "No. Structured data can qualify content for rich results, but it does not guarantee a display in Google."
      }
    }
  ]
}
</script>

Important:

• The questions and answers must be visible on the page.
• FAQPage is not suitable for forums with multiple user answers.
• For genuine question-and-answer communities, QAPage is more suitable.
• FAQ markup should not be abused as spam or as a keywordA keyword is the search term users enter into a search engine to find information, products or providers. Keywords are the basis against which rankings and visibility are measured.Open glossary entry → collection.

Schema.org defines FAQPage as a web page with one or more frequently asked questions and answers.
Source: Schema.org – FAQPage

The Most Important Schema Types by Page Type #

Not every page needs the same markup. The page type is what matters.

Google offers a gallery of supported structured-data types for Google Search. Not every Schema.org type creates a Google rich result.
Source: Google Search Central – Structured Data Gallery

Prioritization: Which Missing Schema Really Matters? #

Not every missing schema should be treated the same way.

The most important rule:

Prioritize Schema Markup where structured data represents real content: products, organization, locations, articles, FAQs, events and jobs.

Common Structured Data Mistakes #

Mistake 1: Markup Without Visible Content #

Structured data must not contain information that users cannot see or verify on the page.

Bad:

"aggregateRating": {
  "ratingValue": "5.0",
  "reviewCount": "128"
}

if no reviews are visible on the page.

Mistake 2: Wrong Schema Type #

Not every page is an Article, not every service page is an FAQPage, and not every company is automatically a LocalBusiness.

Choose the schema type based on the actual content.

Mistake 3: Outdated or Incorrect Data #

Prices, opening hours, phone numbers, availability and reviews must be up to date.

Mistake 4: Syntax Errors in JSON-LD #

A missing comma can invalidate the entire markup.

Mistake 5: Markup Contradicts Canonical or Visible Content #

If JSON-LD contains a different URL, name or product data than the visible page, contradictory signals arise.

Mistake 6: Too Much Generic Markup #

“More schema” is not automatically better. Markup should describe real content, not be artificially inflated.

Content Error or Template Error? #

For RankScan, it is important to know whether missing schema affects only individual pages or an entire page type.

Content Error #

Examples:

• FAQ section exists editorially but is not marked up.
• Author data is missing from one article.
• Product data is incomplete.
• Opening hours were not maintained.

Solution: Add the missing content or data field.

Template or CMS Error #

Examples:

• Product template does not output Product schema.
• Article schema is missing on all blog articles.
• Organization schema is not output anywhere.
• JSON-LD is only generated client-side.
• Wrong canonical URLThe canonical tag is an HTML link element that tells search engines the preferred (canonical) URL of a page. It helps consolidate duplicate or similar URLs onto a main version.Open glossary entry → is used in the schema.
• Multilingual setup creates inconsistent information.
• Reviews are output in JSON-LD although they are not visible in the template.

Solution: Fix the template, data model or plugin configuration.

What to Do After a RankScan Finding #

When RankScan reports “Missing Schema Markup”, “Missing Organization Markup” or “Missing Q&A Structure”, proceed systematically.

Step 1: Determine the Page Type #

First check whether the affected page is a:

• homepage,
• company page,
• product page,
• category,
• blog article,
• FAQ page,
• location page,
• event,
• job page.

The page type determines which schema makes sense.

Step 2: Evaluate Relevance #

Ask:

• Is the page indexableIndexing is the step in which a search engine processes crawled content and decides whether a URL is added to the search index. Only indexed pages can appear in search results.Open glossary entry →?
• Does it have organic impressions?
• Is it commercially important?
• Does it contain structured information?
• Is there rich-result potential?
• Can the markup be implemented via template across multiple pages?

Step 3: Choose the Right Schema Type #

Examples:

Homepage → Organization + WebSite
Product page → Product + Offer
Blog article → Article or BlogPosting
FAQ page → FAQPage
Location page → LocalBusiness
Category → BreadcrumbList + CollectionPage

Step 4: Check the Data Source #

Structured data should not be invented manually. It should come from real data fields.

Check:

• title,
• description,
• URL,
• canonical,
• image,
• price,
• availability,
• author,
• date,
• address,
• phone,
• opening hours,
• FAQ questions and answers.

Step 5: Implement JSON-LD #

Implement JSON-LD as template-based markup wherever possible.

Important:

• output it in the HTML,
• align it with visible content,
• use absolute URLs,
• keep the canonical URL consistent,
• use suitable data fields for each page type.

Step 6: Validate #

Use:

• Google Rich Results Test,
• Schema Markup Validator,
• Google Search Console,
• RankScan Re-CrawlCrawling is the process by which a search engine bot fetches a URL and downloads its content. It is the first step before a page can be indexed.Open glossary entry →.

The Google Rich Results Test checks whether a page is eligible for Google rich-result types. The Schema Markup Validator checks Schema.org markup more generally.
Sources: Google Rich Results Test, Schema Markup Validator

What a Good Schema Check Looks For #

A good structured-data check evaluates more than just “schema exists or does not exist”.

A good check detects:

• is structured data completely missing?
• is Organization Schema missing?
• is FAQ/Q&A structure missing on suitable pages?
• is JSON-LD syntactically valid?
• does the schema type match the page type?
• do schema URL and canonical match?
• are required fields for Google rich results present?
• are recommended fields present?
• are visible content and markup consistent?
• are prices, availability and reviews up to date?
• is there markup on noindex pages?
• are there duplicate or contradictory markups?
• does the issue affect individual pages or a template?
• are there differences between desktop, mobile and rendered HTML?

This turns the insights “Missing Schema Markup”, “Missing Organization Markup” and “Missing Q&A Structure” into concrete technical and editorial tasks.

Example: SaaS Website Without Organization and Article Schema #

Initial Situation #

A B2B SaaS company regularly publishes guide articles and has several product pages. RankScan reports:

“Missing Schema Markup”
“Missing Organization Markup”
“Missing Q&A Structure”

Analysis #

• The homepage has no Organization schema.
• Blog articles have no Article markupArticle and BlogPosting schema label editorial content such as blog posts or news in a structured way, providing context like title, author, date and image.Open glossary entry →.
• FAQ sections are visible but not structured.
• Breadcrumbs are visible but not marked up as BreadcrumbList.

Solution #

1. Define Organization schema on the homepage and globally via @id.
2. Add Article schema to the blog article template.
3. Output FAQPage only where visible questions and answers exist.
4. Add BreadcrumbList to subpages.
5. Validate JSON-LD with the Rich Results Test and Schema Validator.
6. Re-crawl with RankScan after deployment.

Result #

The website provides clearer machine-readable information about the company, articles, navigation and FAQ content. This does not guarantee better rankings, but it strengthens technical clarity and rich-result eligibility.

Checklist: Using Schema Markup Correctly #

Use this checklist:

• Is JSON-LD present on relevant page types?
• Does the schema type match the content?
• Do markup and visible content match?
• Do markup URL and canonical match?
• Is Organization Schema present and up to date?
• Are logo, name, URL and sameAssameAs is a Schema.org property that links an entity to reference pages confirming its identity, such as official profiles, Wikipedia or Wikidata. It serves disambiguation.Open glossary entry → correct?
• Do articles have author, date, title and image?
• Do products have price, availability, image and brand?
• Are FAQ contents visible and correctly marked up?
• Is BreadcrumbList present on subpages?
• Are there no fake reviews in the markup?
• Are there no outdated prices or opening hours?
• Is JSON-LD valid?
• Was it tested with Google Rich Results Test?
• Was it tested with Schema Markup Validator?
• Was the site re-crawled after the fix?

In addition, E-E-A-T, semantic HTML, Generative Engine Optimization and AI Readiness Score help narrow down the cause and prioritize the next SEO measures cleanly.

For further optimization, thin content and high-quality content are especially relevant because these topics are directly linked to how the page is evaluated and found.

Conclusion: Structured Data Makes Content Clearer #

Schema Markup is not a magic SEO lever. But it is an important technical signal for making content clearer, more consistent and more machine-readable.

The RankScan insights “Missing Schema Markup”, “Missing Organization Markup” and “Missing Q&A Structure” show where a website does not mark up structural information sufficiently.

The best approach is:

1. determine the page type,
2. prioritize relevance,
3. choose the right schema type,
4. use real data sources,
5. implement JSON-LD via templates,
6. align visible content and markup,
7. validate with Google Rich Results Test and Schema Validator,
8. re-crawl after the fix.

This turns structured data into a clean website-health process – and makes your most important content easier for search engines, rich results and modern AI systems to understand.

Sources and Further Reading #

• Google Search Central – Introduction to structured data
• Google Search Central – Structured Data Gallery
• Google Search Central – General Structured Data Guidelines
• Google Search Central – FAQPage Structured Data
• Schema.org – Getting started
• Schema.org – Organization
• Schema.org – FAQPage
• Google Rich Results Test
• Schema Markup Validator