La pagina richiesta al momento non è disponibile nella tua lingua. Puoi selezionare una lingua diversa nella parte inferiore della pagina oppure tradurre istantaneamente qualsiasi pagina web nella lingua che preferisci tramite la funzionalità di traduzione integrata di Google Chrome.

Debugging entity matching issues

Matching issues are experimental
We are still working on reporting results from our matching validation system. If a matching issue seems to have been correctly detected, please fix the issue and wait for the next ingestion to validate your fix. If the issue seems to be incorrectly attributed to an entity, please reach out to your Google Contact for support.

Before sending an entity from a feed to the Knowledge Graph, Google tries to determine whether the entity is already present in the Knowledge Graph, in order to avoid creating duplicate items. This process is called matching or reconciliation. If Google has a problem matching--for example, if an entity doesn't have enough information for Google to search for matches, or if the entity almost (but not quite) matches a known item--then Search Console might report a matching issue. If you see a mismatch error that affects a class of items and persists after repeated fix attempts, you might contact your Google representative to confirm whether it really is an error. A matching error doesn't necessarily mean that your suggested entity is incorrect, only that we can't match it to an entity in the Knowledge Graph.

Here is a list of matching issues exposed by the Feed report. Matching issues start with the string "Entity matching" in the Feed report. Note that the term "property" used below refers to a structured data field, not a Search Console property.

General tips:

  • Capitalization is ignored for matching, so you shouldn't see a matching error due to incorrect capitalization. However, if you are providing a new entity, Google may use your name as the official name, so you should try to capitalize the name as you would wish it to appear.
  • Do not include entities in the feed if most of the required properties are not available. For example, if you have neither the episode number nor the original release or air date for a TVEpisode, it's better to exclude such entities from the feed until the required info is secured.
  • For general debugging strategies, read the debugging section of the Feed report guide.

 

 

È stato utile?

Come possiamo migliorare l'articolo?

Hai bisogno di ulteriore assistenza?

Prova i passaggi successivi indicati di seguito:

true
15878616372558310520
true
Cerca nel Centro assistenza
true
true
true
true
true
83844
Search
Clear search
Close search
Main menu
false
false
false
false