Skip to content

feat: add JSON-LD structured data for SEO and rich snippets#536

Open
Vaishnav88sk wants to merge 1 commit into
microcks:masterfrom
Vaishnav88sk:feat/json-ld-structured-data-clean
Open

feat: add JSON-LD structured data for SEO and rich snippets#536
Vaishnav88sk wants to merge 1 commit into
microcks:masterfrom
Vaishnav88sk:feat/json-ld-structured-data-clean

Conversation

@Vaishnav88sk

Copy link
Copy Markdown
Contributor

Description

Enhance SEO efforts mentioned in issue #209. Structured data is a fundamental SEO best practice that the site currently lacks.

This PR adds JSON-LD structured data templates that output Schema.org markup:

  • TechArticle for documentation pages
  • BlogPosting for blog posts
  • Article for general pages

Includes: headline, description, author, datePublished, dateModified, image, and publisher information.

How will this change help?

  • Enable rich snippets in Google search results
  • Improve click-through rates with better SERP appearance
  • Help search engines understand content types (blog posts vs documentation)
  • Support Google's Knowledge Graph with proper entity data

Related issue(s)

#209

@yada

yada commented Jun 1, 2026

Copy link
Copy Markdown
Member

Same comment on this one: #537 (comment)

Signed-off-by: Vaishnav88sk <vaishnavsk8804@gmail.com>
@Vaishnav88sk Vaishnav88sk force-pushed the feat/json-ld-structured-data-clean branch from 99f387f to bed556c Compare June 5, 2026 22:26
@Vaishnav88sk

Copy link
Copy Markdown
Contributor Author

@yada I tested this locally.

The JSON-LD <script type="application/ld+json"> is now correctly injected into on individual blog posts and documentation pages. Screenshot from browser source confirms it works:
Screenshot from 2026-06-06 03-51-49

browsers ignore <script type="application/ld+json"> entirely. Only search engine crawlers read it to generate rich snippets.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants