Structured data 7 min read

Schema.org for indie products: the JSON-LD to actually paste in

You do not need ten schema types. You need two: Organization with sameAs to tell machines who you are, and SoftwareApplication to tell them what you offer. Here is the exact JSON-LD to paste, where it goes, and an honest account of what it buys you.

Last updated June 17, 2026

Key takeaway

For an indie product, two structured-data blocks are worth adding: Organization (with sameAs linking your official profiles) and SoftwareApplication. Put them in your page <head> as JSON-LD, the format Google prefers. Organization plus sameAs is the highest-leverage piece in 2026, because it tells Google and AI systems exactly which entity you are, which feeds the Knowledge Panel and AI citations. Schema does not improve your ranking and will not invent rich results you have not earned, so do not fake ratings to chase a star snippet.

Two blocks cover most indie products: Organization with sameAs, and SoftwareApplication. Skip the rest until you have a reason.
Organization + sameAs (links to your X, GitHub, LinkedIn, Crunchbase, Wikidata) is the entity signal that feeds Knowledge Panels and AI recognition. It is the cheapest, highest-leverage schema you can add.
Use JSON-LD in the <head>. It is the format Google recommends, and it keeps your markup separate from your HTML.
Schema is not a ranking lever and does not create rich results out of nothing. Never add a fake aggregateRating to fish for stars; it risks a manual action.

For an indie product you need two structured-data blocks, not ten: Organization with sameAs to tell machines which entity you are, and SoftwareApplication to tell them what you offer. Paste both as JSON-LD in your page <head>, validate them, and you have done the part that matters. This is the copy-paste how-to; for the strategy of which schema is worth your time after Google’s deprecations, see the companion piece on schema markup for indie products. The running example is Pagewatch, a webpage-change monitor.

01 · The entity signalOrganization with sameAs: tell machines who you are

This is the single highest-leverage block you can add in 2026. Organization schema states your name, URL, and logo, and the sameAs array links you to your official presence elsewhere, which tells Google and AI systems that all of those profiles are the same entity as you. That entity disambiguation is what feeds the Knowledge Panel and what lets an AI cite you with confidence instead of guessing.

Organization JSON-LD (in your <head>)

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Pagewatch",
  "url": "https://pagewatch.dev",
  "logo": "https://pagewatch.dev/logo.png",
  "description": "Monitors any webpage and alerts you the moment it changes.",
  "sameAs": [
    "https://x.com/pagewatch",
    "https://github.com/pagewatch",
    "https://www.linkedin.com/company/pagewatch",
    "https://www.crunchbase.com/organization/pagewatch"
  ]
}

Fill sameAs with the profiles you actually control, and only those. The more authoritative the link (a Wikidata or Crunchbase entry alongside your social profiles), the stronger the entity signal. This is the cheapest way to remove ambiguity about who you are, and for a product nobody knows yet, that ambiguity is exactly what is costing you recognition. Google documents the full set of supported properties in its Organization structured data reference.

02 · The product signalSoftwareApplication: tell machines what you offer

The second block describes the product itself: what kind of application it is, what it runs on, and what it costs. Google still supports SoftwareApplication as a rich-result type, and even when no rich result shows, the markup helps machines categorise what you are.

SoftwareApplication JSON-LD (in your <head>)

{
  "@context": "https://schema.org",
  "@type": "SoftwareApplication",
  "name": "Pagewatch",
  "applicationCategory": "BusinessApplication",
  "operatingSystem": "Web",
  "url": "https://pagewatch.dev",
  "description": "Monitors any webpage for changes and alerts you instantly.",
  "offers": {
    "@type": "Offer",
    "price": "0",
    "priceCurrency": "USD"
  }
}

applicationCategory takes a value like BusinessApplication or DeveloperApplication; operatingSystem is Web for a web app, or the platforms you ship on. The offers block states price, which is legitimate and useful if you have a free tier or a clear price.

Do not fake an aggregateRating

The star-rating rich result for SoftwareApplication needs a real aggregateRating or review data, and a brand-new product does not have one yet. Adding a fabricated rating to trigger the stars is against Google’s guidelines and risks a manual action that strips your rich-result eligibility entirely. Ship the markup without ratings now, and let real reviews populate it later. A missing star snippet is fine; a faked one is a liability.

03 · Placement and testingWhere it goes and how to validate

Put both blocks in your page <head> as separate <script type="application/ld+json"> tags. JSON-LD is the format Google recommends, because it keeps the structured data in one clean block rather than tangled through your HTML, which makes it far easier to maintain and debug.

in your HTML <head>

<script type="application/ld+json">
{ "@context": "https://schema.org", "@type": "Organization", "name": "Pagewatch", "...": "..." }
</script>

One mechanical catch worth checking: if your site is a client-side JavaScript app, make sure the JSON-LD is in the HTML the crawler receives, not injected only after hydration, or a machine may never see it. Then validate. Google’s Rich Results Test and the schema.org validator both tell you whether your markup is well-formed and which rich results, if any, it qualifies for. Validate once after you add it, and again any time you change it.

04 · The honest scopeWhat schema does, and does not, do

It is worth being precise, because schema is routinely oversold. Structured data does not improve your ranking; Google’s own guidelines are explicit that it does not change where you appear, only whether your listing can show a rich result. It also does not conjure rich results you have not earned: no real ratings, no star snippet.

What it does do is make you legible. Organization plus sameAs tells machines which entity you are, SoftwareApplication tells them what you offer, and both help Google and AI systems describe you accurately instead of guessing. That is real value, especially for a no-name product, but it is comprehension value, not a ranking hack. In the two halves of launch readiness, schema sits in the Readiness work you control: it makes your page parseable and your entity clear, which is necessary groundwork, not a substitute for the footprint that actually gets you found.

FAQ

Common questions

What schema should an indie product use?

Two types cover almost everything: Organization with a sameAs array pointing to your official profiles, and SoftwareApplication describing the product. Organization tells machines which entity you are; SoftwareApplication tells them what you offer and on what platform. Add others (Article for blog posts, BreadcrumbList for navigation) only where they genuinely match the page. Do not paste every schema type you can find; unused markup just adds noise.

Does schema markup help my Google ranking?

What is sameAs and why does it matter?

Do I need FAQ or HowTo schema?

Will SoftwareApplication get me star ratings in search?

The nudge off zero

Get your free launch-readiness score

See what else is between your product and its first real users — Nilkick scores your readiness and hands you the map. Free, no login.

https:// optional · no account · we don't email you

Keep going · Indexing cluster All guides →

Guide

Schema markup for indie products: what's actually worth it in 2026

Google retired most niche rich results, FAQ included as of May 2026. Structured data still helps machines parse you. What schema an indie product should actually ship.

8 min read

Guide

How to get a new site indexed by Google fast

To get a new site indexed: verify in Search Console, submit a sitemap, request indexing, and stay crawlable. But there is no instant-index button for Google, and a new domain often waits. The honest levers.

8 min read

Guide

Why your AI-built SPA is invisible to AI crawlers (and risky for Google)

AI crawlers like GPTBot and ClaudeBot don't run JavaScript, so a client-rendered single-page app serves them a blank shell. Why it happens, how to check, how to fix it.

7 min read