Schema Graph Combiner

This schema graph combiner takes every JSON-LD block on a page, whether it comes from your theme, your SEO plugin, or a store app, and merges them into one clean @graph. It removes duplicate entities, gives each one a stable @id, links related entities together, and shows you exactly what changed and where two sources disagree.

What is @graph in JSON-LD?

A JSON-LD @graph is a single block that holds several entities side by side, such as your Organization, WebSite, the WebPage, a BreadcrumbList, and the Article on it. Each entity gets an @id, a unique identifier, usually your URL plus a fragment like #organization. Entities then point to each other with those IDs instead of repeating their details:

"publisher": { "@id": "https://www.example.com/#organization" }

Search engines read structured data split across several script tags as well as one combined graph; both are valid JSON-LD. The difference is clarity. A connected graph states the relationships outright: this article is on this page, the page belongs to this website, the website is published by this organization, and this person wrote the article.

Why combine separate JSON-LD blocks?

Most sites don’t plan their schema; it accumulates. A theme adds Organization markup, an SEO plugin adds its own Organization and WebSite, a review app adds Product markup with the seller described again. The result is a page that describes the same organization three times, sometimes with three different phone numbers, and entities that aren’t connected to each other at all.

Combining them into one schema graph fixes three problems at once:

• Duplicates. One organization, one website, one page, each described once.
• Conflicts. When two sources disagree, you see it and choose the right value instead of letting search engines guess.
• Missing connections. Publisher, author, and page relationships are stated explicitly, which helps search engines and AI systems understand who is behind the content.

How the schema graph combiner works

Paste every JSON-LD block from a page, or the page’s whole HTML source, and the tool works through these steps:

• Reads every block. Several script tags, several objects one after another, existing @graph arrays, and even minor syntax errors are handled. Broken blocks are reported and skipped.
• Merges duplicates. Items with the same @id are merged, and so are organizations, people, websites, pages, articles, and products that describe the same thing, matched by URL, or by name when one copy has no URL.
• Assigns stable @id values. Site-wide entities get IDs on your homepage URL, such as /#organization and /#website; page-level entities get IDs on the page URL, such as #webpage, #breadcrumb, and #article. Relative IDs are made absolute.
• Replaces nested copies. An organization repeated inside an article’s publisher or a product’s seller becomes a reference to the main Organization entity.
• Links related entities. WebSite gets its publisher, WebPage gets isPartOf and breadcrumb, articles get publisher and mainEntityOfPage, a single product or event becomes the page’s mainEntity, and an author written as a name is linked to the matching Person.

Each step can be turned off. The report lists every change, every conflict, and an entity map showing how everything connects.

Duplicates and conflicts

When the same entity appears twice with different values, the combiner keeps the first value and lists the conflict, showing both values side by side. Order matters, so paste the most trustworthy source first, usually your SEO plugin’s output. Lists such as sameAs are merged rather than treated as conflicts, and the same image written as text in one place and as an ImageObject in another counts as the same value.

Conflicts are worth fixing at the source, not just in the combined code. If your theme says one phone number and your plugin says another, update the one that’s wrong, or turn off one of the two outputs.

A good graph for common pages

Most pages need only a handful of entities. A typical schema graph looks like this:

• Every page: Organization (or LocalBusiness), WebSite with publisher pointing to the organization, and a WebPage with isPartOf pointing to the website.
• Pages below the homepage: a BreadcrumbList, referenced from the WebPage.
• Blog posts: an Article or BlogPosting with publisher, mainEntityOfPage, and an author that points to a Person entity.
• Product pages: a Product with offers, set as the WebPage’s mainEntity, with the seller pointing to your organization.

Keep the organization’s @id identical on every page. That consistency is what lets search engines recognize it as one entity across your whole site. The Organization Schema Generator creates that entity with the #organization ID this tool uses.

Adding the combined code to your site

Replace the separate blocks with the combined schema graph in a single script tag, ideally in the page’s <head>. On WordPress, that usually means turning off the duplicate sources first: disable your theme’s built-in schema if it has one, and either configure your SEO plugin to output everything or turn off the parts you’re replacing. Adding the combined graph on top of the old blocks would bring the duplicates back.

Before publishing, click Check in the JSON-LD Validator to open the result in the JSON-LD Validator, which checks it against schema.org and Google’s rich result requirements, then test the live page with Google’s Rich Results Test.

What the combiner can’t do

The tool works only with the code you give it. It can’t check that your markup matches what’s visible on the page, which Google requires, and it doesn’t know which of two conflicting values is true. Matching by name is a sensible default but not infallible, so review the merge list if two different organizations share a name. Everything runs in your browser, and your code isn’t uploaded.