[wp-meta] [Making WordPress.org] #4998: Improvements to plugin page schema

Making WordPress.org noreply at wordpress.org
Mon Feb 3 09:48:01 UTC 2020

#4998: Improvements to plugin page schema
 Reporter:  jonoaldersonwp    |       Owner:  (none)
     Type:  defect            |      Status:  new
 Priority:  low               |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:  seo               |

Comment (by jonoaldersonwp):

 Yeah, primarily because consistency of values is important.

 As we gradually extend the JSON into a full graph, we need to avoid the
 risk of conflicting or divergent values, otherwise, we're going to send
 conflicting signals. This is going to get particularly headachey as we
 start to use proper ID structures (based on URLs), when the URL values
 then differ from the ID structure.

 There are many cases where URL and ID values are used interchangably
 (e.g., in Google's interpretation of the `breadcrumb` spec), so we need a
 standardised approach. We also need to anticipate interoperability with
 other systems which use/reference nodes by ID or by URL, which means that
 those values have to be predictable and consistent.

 See the example markup
 [https://developer.yoast.com/features/schema/specification/#ids here], for

Ticket URL: <https://meta.trac.wordpress.org/ticket/4998#comment:7>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

More information about the wp-meta mailing list