Skip to content

Web design, software and technical support

Log in +90 539 219 79 78 WhatsApp
SEO & GEO

Structured data guide: Schema.org for corporate websites

How corporate and service websites should use Organization, WebSite, Service, BreadcrumbList, BlogPosting and FAQPage, the rules to follow and the tools for testing.

Boran KaradenizKarınca Bilişim Last updated: 7 min

Summarise this article with an AI tool

The tool opens in a new tab with a summary prompt that includes this article’s address.

Structured data is information on a web page marked up with the Schema.org vocabulary, usually in JSON-LD, so that machines can read it. For corporate and service websites, Organization, WebSite, Service, BreadcrumbList and BlogPosting are usually enough. The ground rule is that everything you mark up must be visible on the page and accurate.

What is structured data?

Structured data is code that tells search engines, in a standard language, what a page is about, who published it and which entities it relates to. A person reading the page understands it is a service page; a search engine has to infer that from the text. Structured data makes the inference easier.

The shared vocabulary is Schema.org, started in 2011 by Google, Microsoft and Yahoo, with Yandex joining soon after. It defines hundreds of types, such as organisation, person, service, product, article and event, together with their properties. The vocabulary can be written in several formats, but the one Google recommends and the easiest to maintain is JSON-LD. JSON-LD is added as a script block independent of the page's HTML, so it does not affect the visual design.

On Karınca Bilişim's website, every page carries a single JSON-LD graph generated automatically from the page type. This guide explains the types and rules we use to build that graph.

Which schema types should a corporate site use?

A corporate site mainly needs to describe the business, the website and the type of each page consistently. The types below cover what most corporate and service sites need.

TypeWhere it is usedKey properties
OrganizationSite-wide, with one identifiername, url, logo, email, address, sameAs
WebSiteSite-widename, url, publisher, inLanguage
WebPageEvery pagename, description, url, breadcrumb
ServiceService pagesname, description, provider, serviceType, areaServed
BreadcrumbListPages with a breadcrumbitemListElement (position, name, URL)
BlogPosting / ArticleBlog postsheadline, datePublished, dateModified, author, publisher
FAQPagePages with a visible Q&A sectionmainEntity (Question, acceptedAnswer)
LocalBusinessBusinesses that receive customers in personaddress, openingHours, geo, telephone

Organization

Organization is your business's identity card and should repeat on every page with the same "@id". It holds the name, official URL, logo, contact email and social profiles (sameAs). These details must match your about and contact pages exactly; otherwise search engines and generative answer systems receive conflicting signals.

WebSite and WebPage

WebSite describes the site as a whole and WebPage describes individual pages. Inside WebPage, "isPartOf" links to the site, "breadcrumb" to the breadcrumb trail and "mainEntity" to the page's main subject. These links turn separate schema blocks into one meaningful graph.

Service

Service states the name, description and provider of a service you offer. The "provider" property should point to your Organization identifier. Add prices, ratings or durations only when the page states them clearly.

BreadcrumbList

BreadcrumbList shows the page's place in the site in order: Home, Services, Technical SEO, for example. The trail in the markup must match the breadcrumb visitors see.

BlogPosting or Article

For blog posts, provide the headline, publication date, modification date, author and publisher. Change the modification date only when the content genuinely changes; refreshing the date without touching the content is misleading.

FAQPage

FAQPage marks up question-and-answer sections that are visible on the page. Google has significantly limited how FAQ rich results are displayed in search, so FAQPage is best treated as the semantic counterpart of the page's Q&A structure rather than as a route to a visual rich result. Questions and answers must be identical in the markup and on the page.

When should you use LocalBusiness?

LocalBusiness suits businesses with an address customers can visit in person: a shop, a clinic, a workshop. For a software or consulting business that works remotely, Organization is more accurate. Using LocalBusiness for an address where you do not actually receive customers gives false information.

What rules apply to structured data?

The most important rule is that everything you mark up must be visible, accurate and current on the page. Google's structured data guidelines explicitly forbid marking up content hidden from users and giving misleading information.

  • Match the visible content: headlines, descriptions, questions and answers must be the same in the markup and on the page.
  • No invented reviews or ratings: a business marking up reviews about itself on its own site as AggregateRating falls outside Google's star display for local businesses and organisations. Adding reviews that are not real is a trust risk and can be a legal one.
  • One identity: Organization should use the same "@id" on every page, without different names on different pages.
  • The right type: avoid mismatches such as marking a service page as Product or a company page as LocalBusiness.
  • Honest dates: datePublished and dateModified should reflect real dates.
  • No padding: you do not need to fill every property; a little accurate information beats a lot of incomplete or wrong information.

How do you test structured data?

Structured data is tested with Google's Rich Results Test and Schema.org's Schema Markup Validator. The first shows the rich result types Google supports and their errors; the second shows general conformance with the Schema.org vocabulary.

  1. Enter the page URL in the Rich Results Test and review the detected types and warnings.
  2. Run the same URL through the Schema Markup Validator and confirm that every type and relationship is read correctly.
  3. Watch the enhancement reports in Search Console; new errors appear there.
  4. After template changes, retest at least one example of each page type.

Passing the test does not mean a rich result will be shown. Google decides that by its own assessment. The point of testing is to make sure the data is error-free and understandable.

Why does structured data matter for GEO?

Because it states the entity information about your business and content clearly, structured data can help generative answer systems describe your brand correctly. The platforms have not, however, confirmed a direct and measurable effect.

We therefore treat structured data not as a shortcut but as part of consistent brand information. When the name and description in your Organization data match your about page, social profiles and business listings, search engines and language models both get a more reliable picture. The wider context is in our guide to GEO.

How is structured data managed on WordPress?

On WordPress, structured data is usually produced by an SEO plugin, but the theme and other plugins can add their own markup. This can result in several conflicting Organization or Article blocks on the same page.

  • Identify which plugin or theme produces markup and settle on a single source.
  • Complete the organisation details in the plugin settings.
  • Add custom markup for service pages at template level if needed.
  • Retest the output after theme updates.

We handle this work as part of our WordPress SEO and technical SEO services. For a broader review, see our technical SEO checklist.

Frequently asked questions

Does structured data improve rankings directly?

Google has said structured data is not a general ranking factor. Its benefit is that search engines understand the page more accurately and, where appropriate, can show it in rich results.

Should I use JSON-LD or Microdata?

Google supports three formats but recommends JSON-LD. Because it sits apart from the page HTML, it is easier to maintain and unaffected by design changes.

Should every page have FAQPage markup?

No. Add FAQPage only when the page has a genuinely visible question-and-answer section. Marking up questions that are not visible breaks the guidelines.

Can structured data errors harm my site?

Incorrect markup usually just means the related rich result is not shown. Marking up misleading or hidden content, however, can lead to a manual action, so accuracy matters more than coverage.

All articles
Call nowWhatsApp