Schema you can copy, and how to test it

How to add it

Chapters 6, 7 and 10

• WordPress: an SEO plugin such as Yoast or Rank Math adds Organization and Person schema from its settings. Fill in every field it offers, including social profiles.
• Shopify, Webflow and others: most themes or apps add Product and Organization schema; check what yours outputs before adding more, or you will publish two conflicting versions.
• Anything custom: a developer pastes a JSON-LD block like the ones below into the page's HTML.

Rather fill in a form than write JSON-LD? Hawk Academy's free Schema Generator builds the block for you. Skip its FAQ type: Google no longer shows FAQ rich results.

Direct link: thesourceframework.com/how/sameas

Organization, with sameAs

Chapter 7

Put this on your homepage (and About page). The sameAs list tells machines these profiles are all you. Only list live profiles you control or that describe you.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "@id": "https://www.example.com.au/#organization",
  "name": "Example Pty Ltd",
  "alternateName": "Example",
  "url": "https://www.example.com.au/",
  "logo": "https://www.example.com.au/logo.png",
  "description": "One plain sentence on what you do, for whom, and where.",
  "foundingDate": "2012",
  "telephone": "+61 3 9000 0000",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "1 Example St",
    "addressLocality": "Melbourne",
    "addressRegion": "VIC",
    "postalCode": "3000",
    "addressCountry": "AU"
  },
  "sameAs": [
    "https://www.linkedin.com/company/example",
    "https://www.wikidata.org/wiki/Q00000000",
    "https://www.crunchbase.com/organization/example",
    "https://www.facebook.com/example",
    "https://www.instagram.com/example"
  ]
}
</script>

A shop or office people visit: use LocalBusiness (or a more specific type such as Plumber) instead of Organization, and add opening hours that match your Google Business Profile exactly.

Direct link: thesourceframework.com/how/sameas

Person, for every author

Chapter 10

Put this on each author's profile page. The @id is what article pages point to.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Person",
  "@id": "https://www.example.com.au/team/jane-smith#person",
  "name": "Jane Smith",
  "jobTitle": "Senior Consultant",
  "url": "https://www.example.com.au/team/jane-smith",
  "image": "https://www.example.com.au/team/jane-smith.jpg",
  "worksFor": { "@id": "https://www.example.com.au/#organization" },
  "knowsAbout": ["ecommerce logistics", "supply chain"],
  "sameAs": ["https://www.linkedin.com/in/janesmith"]
}
</script>

Direct link: thesourceframework.com/how/person-schema

Article, pointing at its author

Chapter 10

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "The article's title, as it appears on the page",
  "datePublished": "2026-09-01",
  "dateModified": "2026-09-20",
  "author": { "@id": "https://www.example.com.au/team/jane-smith#person" },
  "publisher": { "@id": "https://www.example.com.au/#organization" }
}
</script>

Direct link: thesourceframework.com/how/person-schema

Test it before you publish

Chapter 6

1. Rich Results Test: paste a URL or code to see which Google features it qualifies for and any errors.
2. Schema Markup Validator: checks any schema.org markup, including types Google does not show as rich results. Hawk Academy's free Schema Validator does both jobs in one place and lists missing required and recommended properties.
3. Then read the page: every value in the schema (price, hours, name, address) must match what a visitor sees. Schema that disagrees with the page is worse than none.

FAQ markup: Google stopped showing FAQ rich results in May 2026. Keep useful questions and answers visible on the page; the markup no longer earns a result.

Direct link: thesourceframework.com/how/canonicals