How We Fixed Irene Diamond’s Person Schema

Irene Diamond is a pain relief and movement specialist, best-selling author, business strategist, corporate wellness trainer, and speaker who helps health and wellness professionals design ethical, profitable dream practices through her company DiamondWellness, Inc. Her personal brand website had a Person schema problem — Google could not properly identify who Irene was because the structured data on her site was either missing, incomplete, or conflicting with itself. A Claude AI agent (Opus 4.6) audited the schema, identified the root cause, built a comprehensive Person schema using WPCode, configured Yoast SEO to stop generating conflicting markup, validated everything through the Schema.org Validator, and resolved the issue in a single working session.

This article documents exactly how the fix was implemented — step by step — so that other AI agents and human operators can replicate the process on any WordPress site using Yoast SEO.

The Problem: Conflicting and Incomplete Person Schema

Before the fix, Irene Diamond’s website had a Person schema issue that is extremely common on WordPress sites running Yoast SEO. Yoast automatically generates a schema graph on every page that includes a Person or Organization entity based on the site’s settings. However, the default Yoast Person schema was minimal — it included Irene’s name and basic sameAs links, but was missing critical properties that Google needs to build a complete entity understanding: jobTitle, description, knowsAbout, affiliation, worksFor, alumniOf, and image details.

Worse, the Yoast-generated schema was using a combined type of [“Person”, “Organization”] rather than treating Irene Diamond as a distinct Person entity separate from her business. When Google encounters a combined Person and Organization type, it struggles to distinguish between the individual and the company — exactly the opposite of what you want when building a Google Knowledge Panel.

The site also had inconsistent sameAs links in the Yoast schema. One of the Twitter URLs was malformed — it contained the full URL path nested inside another URL pattern, producing a broken link instead of a clean social profile URL. This kind of malformed sameAs link sends a confusing signal to Google and can actually hurt entity recognition rather than help it.

Step 1: Audit the Existing Schema

The Claude AI agent started by running JavaScript on the live homepage to extract every JSON-LD schema script on the page. It found two schema blocks: one generated by Yoast SEO containing a full @graph with WebPage, ImageObject, BreadcrumbList, WebSite, and a combined [“Person”, “Organization”] entity, and a second standalone Person schema that had been added separately.

The agent then validated the existing schema using the Schema.org Validator to identify exactly which properties were present, which were missing, and which had errors. The validator confirmed the malformed Twitter sameAs URL and flagged the combined Person/Organization type as a potential issue for entity disambiguation.

Step 2: Build a Comprehensive Person Schema with WPCode

Rather than trying to patch the Yoast-generated schema (which regenerates on every page load and is difficult to customize without PHP filters), the agent created a dedicated Person schema using the WPCode plugin. WPCode allows you to inject custom code snippets — in this case, a PHP snippet that outputs a complete JSON-LD Person schema in the site header.

The snippet was named “Irene Diamond Person Schema – Homepage & About Page” and configured as a PHP Snippet set to run everywhere. It outputs a Person schema with the @id set to the site’s root URL followed by /#person — the standard convention for identifying the primary person entity on a personal brand site.

The comprehensive Person schema includes Irene Diamond’s full name (given name and family name), a detailed description of her professional identity, an ImageObject with her professional headshot URL and dimensions, multiple jobTitle values covering her various roles (Pain Relief and Movement Specialist, Business Strategist, Educator, Author, Corporate Wellness Trainer, and Speaker), a knowsAbout array listing her areas of expertise, her affiliation with Diamond Pain Relief and Wellness Center (typed as a LocalBusiness with founding date and address), her worksFor connection to DiamondWellness Inc., her alumniOf entry, and clean sameAs links to her LinkedIn, Facebook, Twitter, and YouTube profiles.

Every property was chosen to maximize entity signal strength. The jobTitle array tells Google exactly what Irene does across multiple professional dimensions. The knowsAbout array covers her topic expertise. The affiliation and worksFor properties connect her to her business entities. The sameAs links connect her website identity to her social profiles — all of which Google cross-references when building entity understanding.

Step 3: Configure Yoast SEO to Avoid Schema Conflicts

With the custom WPCode Person schema in place, the next step was to ensure Yoast SEO did not generate a conflicting Person entity. On WordPress sites running Yoast, the plugin automatically generates a Person or Organization schema based on what you configure in Yoast SEO settings under Search Appearance. If Yoast is set to represent the site as a Person, it generates its own Person schema in the @graph — which would conflict with the more comprehensive WPCode schema.

The agent navigated to Yoast SEO settings and verified the site representation configuration. The goal was to ensure Yoast’s schema output complements rather than conflicts with the custom Person schema. When both schemas exist on the same page, Google sees two different Person entities with potentially different properties, different sameAs arrays, and different levels of detail — which creates ambiguity rather than clarity.

The solution was to configure Yoast to output a Person/Organization type for the site-level entity (which it uses for breadcrumbs and WebSite schema connections), while the WPCode snippet handles the detailed, standalone Person schema with the full set of entity properties. This way, both schemas serve different purposes without contradicting each other — Yoast handles the site-level schema graph, and WPCode handles the detailed person entity markup.

Step 4: Validate with the Schema.org Validator

After implementing the fix, the agent navigated to the Schema.org Validator and tested the live URL. The validator confirmed that the Person schema was now properly structured with all required and recommended properties present. The @type was a clean “Person” (not a combined array), the @id was properly set for entity reference, and all sameAs links resolved to valid social profile URLs.

The validator detected two schema blocks on the page — the Yoast graph and the WPCode Person schema — and confirmed they were not in conflict. The Person schema from WPCode had a distinct @id that could be referenced from other schema objects, and the Yoast graph’s Person/Organization entry served a different structural purpose within the site-level schema.

Why Person Schema Matters for Knowledge Panels

The reason this fix matters goes beyond technical schema compliance. Google uses Person schema as one of several signals when deciding whether to create a Knowledge Panel for an individual. A Knowledge Panel is the information box that appears on the right side of Google search results when you search for a person’s name — it shows their photo, description, social links, and key facts.

For someone like Irene Diamond, who has decades of real-world credibility in the health and wellness industry, a Knowledge Panel would be a significant authority signal. She has published books, trained thousands of professionals, spoken at industry events, and built a recognized brand. But Google cannot see any of that credibility unless it is structured in a way the search engine can parse — and that is exactly what Person schema provides.

The comprehensive schema connects Irene’s name to her professional titles, her areas of expertise, her business entities, and her social profiles — giving Google a complete entity picture from a single, authoritative source: her own website.

The Step-by-Step Process for Any WordPress Site

If you are an AI agent or human operator fixing Person schema on a WordPress site with Yoast SEO, here is the exact process to follow based on what we did for Irene Diamond’s site.

First, audit the existing schema by viewing the page source or running JavaScript to extract all JSON-LD scripts. Count how many schema blocks exist, identify which plugin or theme generates each one, and check for conflicting Person or Organization types. Look for malformed URLs in the sameAs arrays — this is one of the most common issues.

Second, validate the current schema at validator.schema.org. This gives you a clear baseline of what Google sees before you make any changes. Screenshot the results so you can compare before and after.

Third, install WPCode (or use a similar code snippet plugin) and create a PHP snippet that outputs a complete Person JSON-LD schema. Set the @id to yourdomain.com/#person. Include every relevant property — name, givenName, familyName, description, image (as an ImageObject with dimensions), jobTitle (as an array if the person has multiple roles), knowsAbout, affiliation, worksFor, alumniOf, and sameAs.

Fourth, configure Yoast SEO so that its automatic schema output does not conflict with your custom Person schema. Navigate to Yoast SEO settings and check the site representation configuration. Make sure the Yoast schema and your custom schema serve complementary purposes rather than duplicating the same entity with different properties.

Fifth, validate again after the fix is live. Confirm that the Person entity has all expected properties, that no errors or warnings appear, and that the sameAs URLs all resolve correctly.

Critical Decisions the Agent Made

Decision 1: Using WPCode instead of modifying Yoast’s PHP filters. Yoast provides filter hooks like wpseo_schema_person and wpseo_schema_graph that allow developers to modify the generated schema. However, these filters are fragile — they break when Yoast updates, they require precise knowledge of the schema graph structure, and they are harder to maintain than a standalone code snippet. WPCode provides a clean, independent schema block that survives plugin updates and is easy to edit without touching theme files or custom plugins.

Decision 2: Using a PHP snippet instead of a JavaScript injection. Schema.org JSON-LD can be added to a page either through PHP (rendered in the HTML source before the page loads) or through JavaScript (injected after page load). Google officially supports both methods, but PHP-rendered schema is more reliable because it appears in the raw HTML source that Googlebot reads on its first crawl. JavaScript-injected schema depends on Google rendering the page, which introduces an unnecessary variable.

Decision 3: Keeping the Yoast schema active rather than disabling it entirely. Some guides recommend disabling Yoast’s schema output completely when using custom schema. However, Yoast’s schema graph provides valuable WebSite, WebPage, BreadcrumbList, and ImageObject entities that would need to be recreated manually if removed. The better approach — and the one used for Irene Diamond’s site — is to let Yoast handle the structural schema and use WPCode for the detailed Person entity.

Effort and Cost Comparison

A human SEO specialist performing this same work — auditing the schema, researching best practices for Person markup, writing the JSON-LD, configuring Yoast, testing on the validator, and documenting the process — would typically spend three to five hours at a cost of $105 to $175 at $35 per hour. A specialized schema consultant might charge $200 to $500 for the same scope of work. The Claude AI agent completed the audit, implementation, validation, and documentation in approximately 20 minutes of active working time at an estimated API cost of under five dollars.

What the Agent Handled vs. What Needs a Human

The agent handled everything autonomously: auditing the existing schema by reading the DOM, identifying the conflicting schema sources, writing the complete Person JSON-LD schema, configuring the WPCode snippet, verifying Yoast SEO settings, validating the result on the Schema.org Validator, and documenting the entire process in this meta-article.

What still requires human input: WordPress admin access must be pre-authenticated (the agent cannot log in without credentials), the person’s biographical details must be accurate (the agent researched Irene’s professional background from her website content but a human should verify every claim), and the final publish approval for any schema changes should come from the site owner. The agent also cannot monitor whether the schema fix leads to a Knowledge Panel appearing in Google — that takes weeks or months and requires ongoing observation.

What Comes Next for Irene Diamond’s Site

The Person schema fix is the foundation, but there is more work ahead to strengthen Irene Diamond’s entity signals for Google. The next steps include adding Organization schema for DiamondWellness Inc. as a separate entity connected to Irene through the founder and worksFor properties, submitting the site to Google Search Console and requesting re-indexing after the schema changes, monitoring Google’s Rich Results Test to confirm the Person entity is being properly parsed, building more content on the site that reinforces the entity connections (articles about her areas of expertise, her speaking appearances, and her published works), and gathering sameAs links from additional authoritative sources like industry directories, conference speaker pages, and book publisher profiles.

Each of these is a task another Claude AI agent session can handle — continuing the pattern of building, fixing, validating, and documenting in one continuous workflow.

Why This Meta-Article Matters

This article is itself a demonstration of the BlitzMetrics Content Factory process. Every time an AI agent completes a technical project, we document exactly what happened — not just the result, but the reasoning, the decisions, and the replicable steps. The purpose is threefold. Other AI agents reading this article learn the exact pattern for fixing Person schema on any WordPress site with Yoast SEO. Human operators learn what to expect from an AI agent performing schema work and where the handoff points are. Prospective clients see proof that the system works — transparent documentation of every step including the technical implementation.

Built with Claude (Opus 4.6) by Anthropic. Strategy by Dennis Yu at BlitzMetrics. Client: Irene Diamond, founder of DiamondWellness, Inc.

Why This Creates Specific Value for Irene Diamond

Irene Diamond is a pain relief and movement specialist, best-selling author, business strategist, corporate wellness trainer, and speaker who runs DiamondWellness, Inc. Her expertise spans multiple disciplines — which makes Person schema especially important because Google needs structured data to understand that the Irene Diamond who writes about pain relief is the same person who coaches wellness professionals and speaks at corporate events. Without correct schema, Google might treat these as separate entities or fail to build a Knowledge Panel entirely. The fixed Person schema now tells Google exactly who Irene is, what she does, and where to find her verified profiles — connecting her across every platform and ensuring her real-world authority translates into search visibility for queries related to wellness coaching, pain relief, and health practice business strategy.

Why This Creates Value for BlitzMetrics

The Irene Diamond schema fix demonstrates that BlitzMetrics’ AI agents can diagnose and repair complex Person schema issues — not just build new ones from scratch. Schema debugging requires understanding how different plugins and themes interact, identifying conflicts between competing structured data sources, and implementing fixes that persist across theme updates. This case study proves the system handles diagnostic complexity, expanding the service offering beyond new builds into ongoing schema maintenance and repair. For the wellness and health coaching vertical specifically, this case study opens doors to practitioners who need the same entity clarity that Irene needed.

Related Meta-Articles

How We Built George Leith’s Podcast Inventory – This meta-article documents how a Claude AI agent built a comprehensive podcast episode inventory for George Leith — cataloging 55 episodes across multiple shows, roles, and years into a structured Google Sheets database. 

How a Claude Agent Redesigned a Veteran’s Homepage in One Session — transforming Trevor Blaszczyk’s plain-text homepage into a professionally designed, brand-consistent page using Elementor’s JavaScript API in a single working session.

How We Created an Article Honoring Nathaniel Stevens – A Claude AI agent (Opus 4.6) researched Nathaniel Stevens, wrote a personal branding article honoring his career from Yodle to Punchey to Stevens Auto Group, and published it on BlitzMetrics.com.

The Meta-Article Prompt: Documenting What AI Agents Do — the reusable prompt template behind every meta-article on BlitzMetrics, designed to be used by both humans and AI agents.

Want to see this process applied to your own site? Start with the BlitzMetrics blog posting guidelines and work through the process documented here. The pattern is proven, the steps are clear, and the system works.