<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Jahid Shah</title>
    <description>The latest articles on DEV Community by Jahid Shah (@jahidshah).</description>
    <link>https://dev.to/jahidshah</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3938757%2F5ffe6388-24ef-412a-aa39-a7a12013b8f8.png</url>
      <title>DEV Community: Jahid Shah</title>
      <link>https://dev.to/jahidshah</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/jahidshah"/>
    <language>en</language>
    <item>
      <title>Why I Built a Lightweight WordPress Plugin to Manually Control JSON-LD Schema?</title>
      <dc:creator>Jahid Shah</dc:creator>
      <pubDate>Mon, 18 May 2026 18:45:26 +0000</pubDate>
      <link>https://dev.to/jahidshah/why-i-built-a-lightweight-wordpress-plugin-to-manually-control-json-ld-schema-3hk8</link>
      <guid>https://dev.to/jahidshah/why-i-built-a-lightweight-wordpress-plugin-to-manually-control-json-ld-schema-3hk8</guid>
      <description>&lt;p&gt;Structured data (JSON-LD) is one of the most important parts of modern SEO. It helps search engines understand content context and enables rich results like FAQs, articles, and product snippets.&lt;/p&gt;

&lt;p&gt;However, working with WordPress at scale exposes a consistent problem:&lt;/p&gt;

&lt;h2&gt;
  
  
  The problem with automated schema generation
&lt;/h2&gt;

&lt;p&gt;Most &lt;strong&gt;SEO plugins&lt;/strong&gt; like &lt;strong&gt;Yoast&lt;/strong&gt; or &lt;strong&gt;Rank Math&lt;/strong&gt; automatically generate schema in the background. While this is useful for beginners, it introduces serious limitations in advanced setups:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Duplicate schema across plugins&lt;/li&gt;
&lt;li&gt;Conflicting JSON-LD structures&lt;/li&gt;
&lt;li&gt;Limited control over schema output&lt;/li&gt;
&lt;li&gt;Difficulty combining multiple schema types on a single page&lt;/li&gt;
&lt;li&gt;Lack of visibility into what is actually being injected&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;In complex WordPress environments, these issues often result in invalid or ignored structured data—even when everything appears “correct” in the UI.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I needed instead
&lt;/h2&gt;

&lt;p&gt;I wanted a workflow that gives full control over structured data without relying on hidden automation layers.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Specifically:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Manually define JSON-LD schema per post or page&lt;/li&gt;
&lt;li&gt;Combine multiple schema types cleanly&lt;/li&gt;
&lt;li&gt;Validate basic structural and duplicate issues instantly&lt;/li&gt;
&lt;li&gt;Avoid conflicts with existing SEO plugins&lt;/li&gt;
&lt;li&gt;Keep the system lightweight and predictable&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  The solution: BBH Custom Schema
&lt;/h2&gt;

&lt;p&gt;To solve this, I built a lightweight WordPress plugin called BBH Custom Schema.&lt;/p&gt;

&lt;p&gt;It is designed for developers and technical SEO workflows where control matters more than automation.&lt;/p&gt;

&lt;h3&gt;
  
  
  Key capabilities:
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;Manual JSON-LD schema injection on posts, pages, and custom post types&lt;/li&gt;
&lt;li&gt;Schema combining system for multiple structured data blocks&lt;/li&gt;
&lt;li&gt;Basic validation to detect formatting issues and duplicate entries&lt;/li&gt;
&lt;li&gt;Conflict-safe implementation alongside SEO plugins like Yoast SEO and Rank Math&lt;/li&gt;
&lt;li&gt;Lightweight architecture with no unnecessary frontend overhead&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Design philosophy
&lt;/h2&gt;

&lt;p&gt;This plugin is not trying to “automate SEO”.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Instead, the goal is:&lt;/strong&gt;&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Give developers full visibility and control over structured data output.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;&lt;strong&gt;That means:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;No hidden schema injection&lt;/li&gt;
&lt;li&gt;No silent overrides&lt;/li&gt;
&lt;li&gt;No opinionated automation logic&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Just explicit, controlled, structured data management.&lt;/p&gt;

&lt;h2&gt;
  
  
  When this approach makes sense
&lt;/h2&gt;

&lt;p&gt;This workflow is useful when:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;You are managing multiple schema types per page&lt;/li&gt;
&lt;li&gt;You need strict control over structured data output&lt;/li&gt;
&lt;li&gt;You are debugging rich result issues&lt;/li&gt;
&lt;li&gt;You are working in SEO-heavy or enterprise WordPress environments&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  What I learned building it
&lt;/h2&gt;

&lt;p&gt;The biggest insight was simple:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Schema problems in WordPress are rarely about missing data—they are about conflicting data.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Most “invalid schema” issues in Google tools are actually caused by:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;duplication&lt;/li&gt;
&lt;li&gt;overlapping plugins&lt;/li&gt;
&lt;li&gt;inconsistent injection order&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Not the schema itself.&lt;/p&gt;

&lt;h2&gt;
  
  
  Plugin link
&lt;/h2&gt;

&lt;p&gt;BBH Custom Schema&lt;br&gt;
&lt;a href="https://wordpress.org/plugins/bbh-custom-schema/" rel="noopener noreferrer"&gt;https://wordpress.org/plugins/bbh-custom-schema/&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Final note
&lt;/h2&gt;

&lt;p&gt;This project started as a small internal tool to solve schema conflicts in real projects. It evolved into a reusable plugin for anyone who needs precise control over structured data in WordPress.&lt;/p&gt;

</description>
      <category>wordpress</category>
      <category>seo</category>
      <category>structureddata</category>
      <category>webdev</category>
    </item>
  </channel>
</rss>
