#4469 – Two "Organization" entries generated

Hi

We output json-ld in a modular fashion, based on which data user actually input. The data is used the same by search engines and Google specifically, so we don't have plans on unifying this to be honest.

Rgds

Hi

Google appears to identify two separate organizations (see attached),

Sorry, how do you come to that conclusion? This is the normal representation of structured data from the Google tool, it does not mean it sees 2 organizations.

Rgds

Hi

Normally, Schema provides objects. An article can contain references to different organizations, many of them actually. How would Google know that the data refers to the same one?

The structure data is on the same website, and have the same URL. They will be consolidated.

Rgds

Hi

"Organization" schemas do not refer to the website; they refer to content. For example, a site could have a whole directory of organizations, each a separate entry.

You must be thinking of microdata then. That's not how json-ld works. A page that has a list of organizations would be not have that sort of markup. The root Organization markup that you have on your screenshots and sh404SEF produces would be the same, and refer to the organization producing the list. The list itself, or rather any page of the site that has that list or a part of tha tlist, would be additionally marked up as an "ItemList", each item in the list being itself an organization snippet.

Rgds

Hi

would you consider expanding the schema information available

We have not pushed very much in that direction because it's basically the role of the component creating the content to do that, otherwise it's pretty hard to know which type to use for each page exactly. Or we need to have per-component "plugins" to handle that.

As structured data importance grows, we will certainly implement something like this for Joomla default content types in the coming month. Likewise, the content type will be overridable on a per URL basis.

One important thing to consider is that most templates, and even Joomla itself already provide this markup to some extent - usually as microdata. So adding our own (as json-ld, we won't do anything else) also means be able to detect this, and maybe cleanup the data provided by the template or Joomla (microdata should not contradict our user generated input).

As for image entries, it's unlikely we will get into that for detection is too complex and time consuming (which images do you include, which not?) considering the expected benefit.

Rgds