Structured data is a standardized format for providing explicit clues about the meaning of a webpage to search engines. By implementing Schema.org structured data using JSON-LD (JavaScript Object Notation for Linked Data), website owners can help search crawlers understand their content better, resulting in eye-catching Rich Snippets (such as author bylines, publication dates, review stars, and breadcrumbs) directly in Google Search results.
While CMS platforms like WordPress often rely on third-party plugins to generate schema, Blogger requires adding dynamic JSON-LD scripts directly into the template XML. In this comprehensive guide, we explain how structured data works and provide ready-to-use dynamic code snippets for Articles, Breadcrumbs, and Site Search schemas.
1. Why JSON-LD is the Preferred Schema Format
Google officially recommends JSON-LD over legacy formats like Microdata or RDFa for several key technical reasons:
| Feature | JSON-LD (Recommended) | Microdata (Legacy) |
|---|---|---|
| Implementation | Self-contained <script> block in header/body |
Scattered inline HTML attributes (itemprop, itemscope) |
| Maintenance | Easy to update without breaking visual layout | Prone to syntax errors during template redesigns |
| Parsing Speed | Faster parsing by Googlebot and search crawlers | Requires full DOM tree traversal |
| Google Preference | Officially designated as the standard format | Supported, but considered legacy |
2. Essential Schema Types for Tech Blogs
A. WebSite & Sitelinks SearchBox Schema (Homepage)
This schema establishes your brand entity and enables Google to render an interactive search box directly within your search result listing. Place this inside your template's <head> tag wrapped in a homepage condition:
<b:if cond='data:view.isHomepage'>
<script type='application/ld+json'>
{
"@context": "https://schema.org",
"@type": "WebSite",
"name": "<data:blog.title.escaped/>",
"url": "<data:blog.canonicalHomepageUrl.jsonEscaped/>",
"potentialAction": {
"@type": "SearchAction",
"target": "<data:blog.canonicalHomepageUrl.jsonEscaped/>search?q={search_term_string}",
"query-input": "required name=search_term_string"
}
}
</script>
</b:if>B. Dynamic Article / BlogPosting Schema (Single Posts)
Article schema provides Google with key metadata including headline, publication date, last modified date, author profile, publisher logo, and featured image. In Blogger XML, place this inside the single post loop:
<b:if cond='data:view.isPost'>
<script type='application/ld+json'>
{
"@context": "https://schema.org",
"@type": "BlogPosting",
"mainEntityOfPage": {
"@type": "WebPage",
"@id": "<data:post.url.canonical.jsonEscaped/>"
},
"headline": "<data:post.title.jsonEscaped/>",
"description": "<data:post.snippets.short.jsonEscaped/>",
"image": [
"<data:post.featuredImage.jsonEscaped/>"
],
"datePublished": "<data:post.date.iso8601.jsonEscaped/>",
"dateModified": "<data:post.lastUpdated.iso8601.jsonEscaped/>",
"author": {
"@type": "Person",
"name": "<data:post.author.name.jsonEscaped/>",
"url": "<data:post.author.profileUrl.jsonEscaped/>"
},
"publisher": {
"@type": "Organization",
"name": "<data:blog.title.escaped/>",
"logo": {
"@type": "ImageObject",
"url": "https://www.digitalbhatti.com/favicon.ico"
}
}
}
</script>
</b:if>C. BreadcrumbList Schema (Navigation Hierarchy)
Breadcrumb markup displays your website’s category structure in search snippets (e.g., Home > Technology > Article Title) rather than a raw, unformatted URL string:
<b:if cond='data:view.isPost'>
<script type='application/ld+json'>
{
"@context": "https://schema.org",
"@type": "BreadcrumbList",
"itemListElement": [
{
"@type": "ListItem",
"position": 1,
"name": "Home",
"item": "<data:blog.canonicalHomepageUrl.jsonEscaped/>"
},
<b:if cond='data:post.labels'>
{
"@type": "ListItem",
"position": 2,
"name": "<data:post.labels.first.name.jsonEscaped/>",
"item": "<data:post.labels.first.url.jsonEscaped/>"
},
</b:if>
{
"@type": "ListItem",
"position": <b:eval expr='data:post.labels ? 3 : 2'/>,
"name": "<data:post.title.jsonEscaped/>",
"item": "<data:post.url.canonical.jsonEscaped/>"
}
]
}
</script>
</b:if>3. Testing and Validating Your Schema Markup
After inserting structured data into your Blogger theme, always validate your URLs using Google’s official testing suites:
- Google Rich Results Test (search.google.com/test/rich-results): Checks whether your structured data is eligible to generate rich snippets in search results and highlights any missing required fields.
- Schema.org Validator (validator.schema.org): Validates the general syntax, hierarchy, and property types against the official Schema.org standards.
- Google Search Console (Enhancements Tab): Monitors your site-wide schema implementation and flags errors or warnings across all indexed pages.
4. Common Structured Data Mistakes to Avoid
- Missing
jsonEscapedModifier: In Blogger XML, always append.jsonEscapedto text variables (likedata:post.title.jsonEscaped) to prevent quotes and special characters from breaking the JSON format. - Hidden or Misleading Content: Schema markup must accurately describe the content visible on the page. Never add ratings, reviews, or entities that are not present in the body text.
- Duplicate Schema Implementations: Ensure your template does not have conflicting legacy microdata attributes (e.g.,
itemscope itemtype="http://schema.org/BlogPosting") alongside JSON-LD scripts.
Summary: Schema Implementation Checklist
- Add WebSite schema with Sitelinks search box to the homepage.
- Inject dynamic BlogPosting / Article schema with author and publisher metadata on post pages.
- Implement BreadcrumbList schema to display structured site navigation in search results.
- Validate all URL types using the Google Rich Results Test tool.