Structured data is one of those topics where the advice online swings between "add every schema type you can find" and "it does nothing". Both are wrong. On a typical marketing site, a small amount of accurate markup is worth having. A large amount of decorative markup is a liability.

Here is how I decide what goes in, based on the sites we build and host at CoderCorn.

What structured data actually is

It is a block of JSON-LD in your page that says, in a machine-readable way, what the page is about. Search engines and AI answer tools can read it without guessing. It does not make a page rank higher on its own. It removes ambiguity, and it can make you eligible for some rich results.

The rule I never break: the markup must describe what a visitor can see on the page. If the JSON says something the page does not, delete the JSON.

The short list worth adding

Organization. Name, URL, logo, and links to your real profiles. Put it on the homepage or in the site layout. This is the cheapest way to tell machines who you are, and the wording should match your LinkedIn and directory listings.

WebSite. Name and URL. Only add a search action if your site has working search.

Article or BlogPosting. Headline, author, publish date, modified date. The author should be a real, named person with a page of their own. This is where many sites cut corners, and it is the one that helps with trust.

BreadcrumbList. Cheap to add, and it matches the breadcrumb trail already on the page.

FAQPage. Only when the questions and answers are visible on the page, word for word. Google has limited FAQ rich results in recent years, but the markup still describes the content accurately, so I keep it when the FAQ is real.

Service. For a service page, a short description and the provider. Keep it plain.

What I skip

Review and rating markup without real reviews. Self-written ratings are the fastest way to a manual action. If you do not have verifiable reviews on the page, do not add it.

Markup for content that is not there. Hidden FAQs, products you do not sell, events that never happen.

Duplicate blocks from three plugins. I see this a lot on WordPress. An SEO plugin, a theme and a page builder each output their own Organization block, with slightly different names. Pick one source and turn the others off.

Every type in the vocabulary. More types do not mean more visibility. They mean more things to keep correct.

A minimal example

This is roughly what a small Organization block looks like. Swap in your own details.

{ "@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-studio" ] } 

Put it in a script tag with type="application/ld+json". On a static framework such as Astro, generate it from the same data that renders the visible page, so the two cannot drift apart.

How to keep it honest

First, generate markup from your content data, not by hand-editing JSON on each page. Hand edits go stale.

Second, update dateModified only when the content really changed. Bumping it on every deploy teaches search engines to ignore it.

Third, test in the Rich Results Test and the Schema.org validator after each template change, not once at launch.

Fourth, check that your canonical URLs, titles and structured data all agree. A page whose JSON says one thing and whose title says another is sending mixed signals.

Where it fits in the bigger picture

Structured data is a layer on top of a site that is already fast, crawlable and clear. It will not fix thin pages or a confusing offer. If you want a quick read on the technical basics first, the free PageScore check looks at titles, canonicals, performance and markup in about a minute. For the wider picture of how we handle structure and search readiness, see our technical SEO work, and if the markup question is part of a larger rebuild, here is how we approach web development.

If you would like a second pair of eyes on your site's structure before you spend money, get in touch through codercorn.com and we will tell you plainly what is worth doing and what is not.

Abdul Haseeb Sadiq - Founder