Organization describes an organization in a page’s structured data. The source code contains two such blocks: one has the company’s old name, the other its new name. Most often, the theme and SEO plugin are both outputting the data. But multiple organizations on a page are not always an error: the seller, product manufacturer, and article publisher may be different companies.
First, find out which entity each object describes and where the rest of the markup refers to it. Deleting every Organization except the first one is risky: you could leave an outdated object and lose the connection to the actual publisher or seller.
Find the organizations and the objects linked to them
Review all application/ld+json blocks in the source HTML and after the page has loaded. An Organization may be inside @graph or nested in publisher, seller, manufacturer. Searching for the word in just one script does not show the full picture.
For each object, record its name, @id, URL, phone number, logo, and where it is used. For example, the theme outputs the company “Old Brand,” while the plugin outputs “New Brand.” The Article refers to the old identifier. In that case, the problem affects not only the two names, but also the article’s link to its publisher.
Identify the source: a plugin setting, theme template, or separate module. This will help you fix the output across all pages, rather than deleting a piece of HTML from just one page.
Check the details against the actual company
Check the name, primary website, and logo. The phone number should belong to this organization, and the links in sameAs should point to its actual profiles. Don’t add similarly named companies or the director’s personal profile just to fill out the list.
If the site still has old contact details in the theme settings after a rebrand, update those settings first. The markup should describe the company visitors see on the page. For fields and requirements, use Google’s Organization documentation.
Check the manufacturer in the product listing separately. If the store sells someone else’s products, the manufacturer does not become the same entity just because you remove duplicate blocks for the store.
Link repeated mentions of the same organization
For one company, it’s useful to use a persistent @id, such as https://example.com/#organization. Other objects can refer to it. This avoids recreating the company with slightly different details in every nested field.
The fragment below shows this relationship. It is not a complete, ready-to-use Article markup:
{
"@context": "https://schema.org",
"@graph": [
{
"@type": "Organization",
"@id": "https://example.com/#organization",
"name": "Компания Пример",
"url": "https://example.com/"
},
{
"@type": "Article",
"headline": "Пример статьи",
"publisher": { "@id": "https://example.com/#organization" }
}
]
}Before replacing an identifier, check every reference to the old one. Otherwise, the company object may disappear while Article continues to refer to the old @id. An identical identifier does not make conflicting phone numbers or names in different places acceptable.
Disable duplicate output without losing other markup
If two modules describe the same company, choose where the current record will be maintained and disable only the duplicate Organization output. Don’t disable an entire SEO plugin without checking first: it may generate canonical tags, breadcrumbs, and product markup.
You can brief the developer like this:
The theme outputs the old name in Organization. Keep the current data from the SEO plugin; update publisher references to use its @id. Product, BreadcrumbList, and canonical must continue to work. Check the homepage, an article, and a product page.
Check three different page templates
After making the change, inspect the markup on the homepage, an article, and a product page. The company should be described consistently, while different real organizations should remain in their respective roles. To check the structure, enter a public URL in Google’s Rich Results Test and run the test. Review the detected objects and error messages. Check that the phone number, name, and publisher relationship are correct against your own information.
Keep a record of which generator you disabled. After updating the theme, check that the old block has not returned. For more about how the objects work, see the Schema.org guide; for common errors, see the broken markup troubleshooting guide. You can check other template changes with a site audit.