Use @id to connect schema pieces across pages, not copy them everywhere

Use @id to connect schema pieces across pages, not copy them everywhere

If your site mentions the same brand, person, or product on multiple URLs, give each entity a stable @id and reuse it. That lets search engines see one object with many references instead of separate, slightly different copies. Keep the @id short, unique, and consistent: one for the Organization, one for the Person, one for each Product or Service.

Use the same @id in every schema block where that entity appears: homepage, about page, product page, author page, and relevant articles. The page can change; the entity identifier should not. Pair that with matching name, logo, url, and sameAs fields where they belong. If two pages describe the same thing, they should point to the same entity node.

Avoid creating new @id values for every template or language version. That splits the graph and weakens confidence. Also avoid chaining irrelevant objects together just because they are on the same page. Connect only what is truly the same entity, and keep the relationship types clear. A clean graph beats a crowded one.

Practical rule: one entity, one @id, reused everywhere. Before publishing, check that your homepage and internal pages all reference the same identifiers for the same real-world things.