Technical Architecture
The Schema Tug-of-War
Why deleting AIOSEO’s default markup often destroys the foundational hooks of your Knowledge Graph.
The Overcrowded Engine Bay
In the specialised world of Creative SEO, I often look under the bonnet and notice a crowded engine bay. If you use AIOSEO on your WordPress site while injecting custom JSON-LD, you’ve likely seen both blocks appearing in your source code.
The instinct for many technical SEOs is to “clean house” and delete the default AIOSEO schema to avoid duplication. My advice? I suggest you leave it—but I will help you optimise it correctly.
AIOSEO Default (Skeleton)
I use this to provide global hooks for Organisation and Website. It sets the stage for the search engine to recognise your domain entity.
Custom JSON-LD (Muscle)
I provide hyper-specific, forensic data for BlogPosting or Services. When I link this via @id, it gives your skeleton its ranking power.
1. The Power of the @id Connector
I treat Schema as a web of connections, not just a flat list of data. AIOSEO generates a “graph” where every element—Organisation, Website, WebPage, and Author—is assigned a unique identifier called an @id.
When I craft your custom schema, I use those same references. This tells Google: “This custom piece of data is an extension of the ‘WebPage’ AIOSEO has already defined.”
“My Method: If AIOSEO defines your page as #webpage, I point your custom schema to that same ID. I merge the two blocks into one single entity for LLM recognition.”
Avoiding Fragmented Entity Errors
I know the risk isn’t “duplicate data,” but fragmented data. If AIOSEO identifies the author as “Nicholas Broderick” and your custom schema does the same but fails to link them via a shared ID, Google perceives two different individuals.
My “SEO Coach” Workflow:
- I keep AIOSEO Active: I let it handle the heavy lifting for Organisation and WebSite.
- I map Author IDs: I ensure custom JSON-LD uses the ID defined in your plugin settings.
- Nesting Strategy: I use @id tags like #blogposting to nest within the standard graph.
- Rich Results Testing: I always verify that Google sees one single, cohesive “Graph.”
Coaching Context
This technical analysis is a practical case study used in my Generative SEO Coaching. I teach these exact @id linking frameworks to ensure your brand remains a verifiable “Source of Truth” for AI Answer Engines.
