The Author Entity Hack: Using JSON-LD to Strengthen E-E-A-T Without a CMS Plugin

Most technical SEOs treat structured data as a vehicle for rich results. You slap a Product schema on a product page, an FAQPage schema on a support article, and call it a day. But the real leverage isn’t in the blue links or the star ratings. It’s in the entity graph that you quietly assemble for Google’s Knowledge Graph. Specifically, the overlooked markup of author and person entities is a low-cost, high-signal hack that can separate your brand from the noise, particularly if you publish content across a fragmented domain structure or lean heavily on guest contributors. The good news is you don’t need a heavyweight CMS plugin. A hand-rolled JSON-LD block in your `` or injected via a server-side include is all it takes.

The core of this hack is understanding that Google’s search quality systems, particularly the E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) framework, increasingly rely on entity association. When you publish a piece of content, Google wants to know who wrote it, what that person’s credentials are, and how they relate to the broader web of knowledge. Without explicit structured data, Google has to infer this from context. That inference is often wrong. Authors with common names get conflated. Contributors who write for multiple sites lose their attribution trail. The fix is to implement Schema.org’s `Person` type combined with `sameAs` properties and then link that person to the `author` property of your `Article` or `BlogPosting` markup. This isn’t speculative. Google’s documentation on `author` for articles explicitly supports the `Person` type, and the `sameAs` property is a well-documented signal for entity reconciliation.

Here’s the practical, plugin-free implementation. Start by creating a single, canonical JSON-LD block for each author on your site. That block should contain a stable `@id` — a permanent URL that identifies the author, ideally an `about` page or a profile page on your domain. Use `@type: “Person”` and populate the fields that matter: `name`, `url`, `jobTitle`, `worksFor` (pointing to your Organization), and `sameAs` with URLs to their verified external profiles like LinkedIn, GitHub, Twitter, or a personal site. The `sameAs` array is the critical part because it disambiguates your author from other people with the same name. Once you have that author block, reference it from your article markup using the `author` property with `@id` pointing back to that same permanent URL. Do not inline a fresh `Person` object on every article. Use a reference. This creates a node in the entity graph instead of a scattered set of unlinked claims. For WordPress or static sites, you can achieve this with a simple custom field, a partial template, or even a short snippet in your theme’s `single.php` that outputs a `