imbahub
Menu +
EN
Talk to us
IMBAHUB / Knowledge & guides

Check which real object each @id describes.

Several components can describe an organisation, page and service in one delivery. Valid JSON does not prevent two different objects sharing an identifier or a relationship pointing incorrectly. This guide focuses on identity and references; the existing schema guide covers broader field review.

Keep three identity outcomes separate
  1. Same object

    Reuse has an explained real identity.

  2. Different objects

    Distinct entities need their intended identifiers.

  3. Unclear relation

    Source decision or reference model needs investigation.

Counting identifier strings is different from correct object identity.

Two distinct services receive the organisation's @id from a copied template. Just duplicate text?

No. The model merges different objects. Correct identities and relationships and retest services and publisher.

Write identity decisions before comparing strings

List described objects and why they are the same or different. A real organisation can remain the same publisher across languages while each page version needs its own context. Language difference does not automatically create another company.

A fictional example has organisation, page and service nodes. Two distinct services should not accidentally receive the same @id from a shared template. Repeating the same publisher identity is not automatically a collision, either.

Collect identifiers and relationships using them

Read relevant scripts from the rendered sample. Collect @id, described type and referring relationships. A reference can target an object described elsewhere; do not blindly require every object to be defined in the same script block.

Inspect relative identifiers against the document base and actual URL model. The same text can resolve differently when the base changes. A canonical address and object identifier have different roles and need a documented relationship where used.

Test collisions and legitimate reuse together

Introduce a deliberate collision in safe test data and check it is detectable. Then try legitimate reuse of the same organisation. A test banning every repeated string would reject valid relationships.

Also compare facts different components give the same object. Two names can be valid language variants, but a page and business must not silently merge because a template copied the wrong identifier. Interpret the finding against identity decisions rather than occurrence counts alone.

CaseRiskExpected decision
Same publisher in two languagesUnnecessary identity splittingApproved organisation identity reused
Two distinct servicesTemplate assigns one identifierDifferent objects have intended identities
Separate script blocksConflicting descriptions of one objectShared identity has compatible facts
Relative referenceChanged base points elsewhereResolved identifier follows the model
Moved pageOld relationship remainsAffected relation follows migration decision

Keep reference tests for future template changes

Document object, identity source, components and why reuse is legitimate or wrong. Repeat cases after base, language model, generator or URL changes. Use fictional fixtures without private facts.

State verified relationships and external descriptions outside the sample. A consistent identifier register demonstrates a traceable model; it does not prove how a search engine built its knowledge graph or whether the page will be cited.

Sources and further reading

Questions, answered

Is every repeated @id an error?

No. The same identifier can describe the same object in several places. Incorrect merging or incompatible facts are the concern.

Must a reference be defined in the same script?

Not generally. JSON-LD can reference objects elsewhere. Test against your documented model.

IMBAHUB

What would you like to make possible?

Choose one reused @id and follow its object and references across two components and two languages.

Talk to us
Product interface set to English in an isolated environment with fictional English demo content.

Product interface set to English in an isolated environment with fictional English demo content.