What are the three formats for adding schema, and why is JSON-LD the right choice?
Schema.org markup can be implemented in three formats: Microdata (HTML attributes embedded directly in your content tags), RDFa (similar attribute-based approach), and JSON-LD (a separate JavaScript object embedded in a script tag). Google officially recommends JSON-LD, and it is the only format recommended for this project.[2]
The reason JSON-LD wins: it is completely independent of your HTML structure. You write it once in a clean block, it does not touch your visible content, and you can modify it without changing anything a visitor sees. Microdata and RDFa require weaving attributes through your content markup. Messy to write, harder to maintain, and more likely to introduce errors.
The critical implementation rule: your JSON-LD must be in the raw HTML source, not injected by JavaScript after page load. AI crawlers do not execute JavaScript. If your schema only appears after a script runs, it is invisible to GPTBot, Claude-Web, and PerplexityBot.
What does a complete working author schema JSON-LD example look like?
This is the exact pattern used on every content page of this site. Replace the values in brackets with your own information:
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@graph": [
{
"@type": "BlogPosting",
"headline": "[Your page H1. Exact, verbatim]",
"description": "[Your TL;DR text. 1-2 sentences]",
"url": "https://[yourdomain.com]/[page-path]",
"datePublished": "2026-03-18",
"dateModified": "2026-03-18",
"author": {
"@type": "Person",
"name": "Cindy Anne Molchany",
"url": "https://perfectlittlebusiness.com",
"jobTitle": "Founder, Perfect Little Business",
"sameAs": [
"https://www.linkedin.com/in/cindyannemolchany/",
"https://www.instagram.com/cindyannemolchany/"
]
},
"publisher": {
"@type": "Organization",
"name": "Perfect Little Business",
"url": "https://perfectlittlebusiness.com"
}
},
{
"@type": "BreadcrumbList",
"itemListElement": [
{
"@type": "ListItem",
"position": 1,
"name": "Home",
"item": "https://[yourdomain.com]"
},
{
"@type": "ListItem",
"position": 2,
"name": "[Pillar name]",
"item": "https://[yourdomain.com]/[pillar-path]/"
},
{
"@type": "ListItem",
"position": 3,
"name": "[Cluster name]",
"item": "https://[yourdomain.com]/[cluster-path]/"
},
{
"@type": "ListItem",
"position": 4,
"name": "[Page title]",
"item": "https://[yourdomain.com]/[page-path]"
}
]
}
]
}
</script>
This block goes inside the <head> element of your HTML page, before the closing </head> tag. It is pure text. No build step, no plugin, no framework required.
How do you add author schema to a custom HTML site step by step?
For a static HTML site (like the one built by the Authority Directory Method), the implementation is direct:[3]
- Open your page's HTML file in a code editor.
- Locate the
</head> tag. You will insert your schema block just before this closing tag.
- Copy the JSON-LD example above. Replace all bracketed placeholder values with your actual data: your headline, description, URL, name, jobTitle, website, LinkedIn URL, and Instagram URL.
- Save the file and view the page source in a browser (Ctrl+U or Cmd+U). Search for
schema.org to confirm the block appears in the raw HTML.
- Validate the schema using Google's Rich Results Test (search.google.com/test/rich-results) by pasting the page URL.
Repeat this process for every content page. The values that change per page: headline, description, url, datePublished, dateModified, and the breadcrumb trail. The author block stays identical across all pages. Because it is the same author on every page.
How do you add author schema in WordPress using existing tools?
For a WordPress site, the most straightforward path is using Yoast SEO or RankMath. Both have author schema configuration built in. The general process:
- Install and activate Yoast SEO or RankMath
- In the plugin settings, locate the Schema section
- Configure your Person entity with your name, URL, and sameAs links
- Set each post type (posts, pages) to output Article or BlogPosting schema with author attribution
The plugin will generate and inject the JSON-LD automatically on each page. However: verify that the schema is present in the static HTML source, not rendered client-side via JavaScript. Some plugin configurations inject schema via JS. Use View Source (not DevTools Elements panel) to confirm.
For full control, you can also add a custom JSON-LD block to your WordPress theme's header.php or use a header code plugin to insert the script tag. Manual insertion gives you more precision over exactly what appears in the schema, at the cost of more maintenance when pages change.
How do you validate your author schema and diagnose errors?
Schema validation is non-negotiable. An incorrectly formed JSON-LD block can be silently ignored by AI engines. The page looks fine, but the schema signal is lost. Two validation tools:
- Google Rich Results Test (search.google.com/test/rich-results). Paste your URL or raw code. Shows exactly how Google parses the schema and flags errors or missing recommended properties.
- Schema.org Validator (validator.schema.org). More granular validation against the Schema.org specification. Useful for catching property-level errors that the Google tool may not surface.[4]
Common errors to watch for:
- Invalid JSON. A missing comma, unclosed bracket, or extra quote breaks the entire block silently. Use a JSON linter (jsonlint.com) if the validator reports a parse error.
- Missing required properties. BlogPosting requires at minimum: headline, author. Both validators will flag missing required fields.
- sameAs links that redirect or 404. If your LinkedIn URL has changed, the sameAs link becomes a broken identity claim. Audit your profile URLs annually.
Run validation when you first add schema, and once per quarter thereafter. Schema is infrastructure. It needs the same maintenance attention as any other technical element of your site.
The VCYL Perspective
The implementation barrier here is lower than most experts expect. Author schema is not a developer task. It is a copy-paste-and-edit task. The JSON-LD format is human-readable. You can understand it without knowing how to code. The fields map directly to real things you already know about yourself: your name, your title, your URL, your LinkedIn.
What I find is that the barrier is psychological, not technical. Most entrepreneurs see <script type="application/ld+json"> and mentally file it under "things my developer handles." But when you are vibe coding your own site, this becomes your territory. And it should, because you are the person who knows your credentials best.
The FAQ cluster on this site (Cluster 3A) was the first place I added schema when I built this directory. Then author schema on every node in Cluster 1A. The combination. FAQPage + BlogPosting + Person as author. Is visible in the source of every page you are reading right now. That is not an abstraction. View Source on this page and you will see exactly the pattern described here, implemented exactly as described. The method teaches what the site does.
