How: Use the "about" Schema.org property. Link to WikiData URL using "@id" property.
Best for: affiliates, eCommerce, niche websites, and programmatic sites.
Why: Anchor the 'what' behind any URL using this approach, especially to disambiguate similar topics.
How: Use "author", "editor", "contributor" and "reviewedBy" Schema.org properties, then link to the LinkedIn profile URL of the person as evidence.
Why: We live in the era of generative Al now where the 'who' behind the information is going to increasingly matter to searchers.
Best for: YMYL, affiliates, niche websites, and e-commerce.
How: Use the "significantLink" Schema.org property for WebPage schema types.
Why: Some internal links are more relevant than others. This is how you can communicate this.
Best for: Websites that rely on client-side rendering (JS front-end).
How: Use the "relatedLink" Schema.org property for WebPage schema types.
Why: Not all site-wide navigational links are relevant to the one the user or crawl bot is on.
Best for: Websites that cover a broad range of topics.
How: Use the "isPartOf" Schema.org property for the FAQPage schema type. Link it to the @id of the WebPage.
Why: FAQS is where good content goes to die. Doing this tells search engines the questions and answers are relevant to the context of the page they're on.
Best for: Any page that has FAQs marked up.
How: Use the "publisher" Schema.org property to define the relationship between the business entity, the website, and each URL.
Pro tip: Describe this relationship on the homepage or /about/ page. Give it an "id" and reference this everywhere else dynamically.
How: Grab the URL of the GBP and put it in the "@id" item property for localBusiness schema type.
Why: This easily proves who you are.
Best for: Local business websites and organizations with a physical location.
How: Use the "isPartOf" Schema.org property for the FAQPage schema type, then link it to the @id of the WebPage.
Why: This gives your unique content a little boost (via association).
Best for: Ecom sites that sell goods from a common manufacturer.
How: Use the "knowsAbout" and "jobTitle" Schema.org properties as part of Person schema.
Pro tip: Take the URL of a job description (e.g., from talentlyft.com) and paste it into the "sameAs" field for to validate the job title.
Best for: Informational content and YMYL sites.
How: Grab the "@id" from another website and put it into an item property on your webpage.
Why: Perhaps you're an affiliate and you want to use the "mention" Schema.org item property to describe a product that is in one of your links.
How: Use the "@id" of one item property to link to another to form a connected schema.
Why: Developers are busy. This allows you to piggyback off existing infrastructure and add more descriptive schema in a connected way, especially for Products.