Json Ld Puns

My organization has recently kicked off market based pricing and we need to clarify some details. Does anyone know if there are any guidelines around schema pricing and UI pricing not matching up? We do not want our PLA or LIA campaigns to become suspended because of pricing discrepancies in the structured data and the UI.

Current scenarios we're considering:

1. User opens product page (non-PLA link) - JSON-LD data will show default store sent in LIA feeds to Google. However, the user will initially see a loading indicator where the price is. Once it loads, the user will see in the UI the market-based price based on their closest store, which may not be the deafult store price. The JSON-LD data will not change.
2. User opens product page through a PLA ad (the non-local ads, which are always based ondefault store price). JSON-LD data will show deafult store price. The price the user sees in the UIwill also be the default store price. It will not be overriden by the closest store since the usercoming through an ad

Any thoughts or input is greatly appreciated.

We're using Yoast to generate default schema on our site (it adds types like 'WebPage' everywhere).

This is fine for us but for the pages that we optimize for SEO, we're considering adding custom schema, but only for only pages, by integrating our custom schema with Yoast's via their schema graph API.

While it's true that Yoast publishes its API documentation, it's hard to find any other resources (outside of Yoast) on how to do this (e.g., other sites providing examples of integrating different schema types with Yoast's, or even freelancers with experience in this).

Given this impression (which may be mine alone), are there many other sites actually attempting to integrate their schema code with Yoast's? Or maybe better put, is this actually feasible to do? Thanks in advance

<script type="application/ld+json">

{

"@context": "https://schema.org",

"@type": "BreadcrumbList",

"itemListElement":

[

{

"@type": "ListItem",

"position": 1,

"item":

{

"@id": "https://example.com/first-page”,

"name": “Page Title”

}

},

{

"@type": "ListItem",

"position": 2,

"item":

{

"@id": "https://example.com/second-page”,

"name": “Page Title”

}

}

]

}

</script>

We have product pages with many reviews. They are located at the bottom of the page, loading 10 at a time with the option of loading more through next/prev page buttons.

Each product page does have an aggregate rating schema but we want to also include the Reviews schema (which includes Author type Person, Name, ReviewBody) but how many reviews do we include in the json markup on intial page load?

The latest 10? A sample set of the reviews? or all of them?

There are warnings in GSC for Missing 'Field' review on my product pages. The helpful doc that GSC is pointing me to is at https://developers.google.com/search/docs/data-types/product#examples but the example shows a product with one review. This page https://developers.google.com/search/docs/data-types/review-snippet#embedded-review-example shows 2 reviews for the one product - but what if you have hundreds/thousands? Surely you dont add all of them on the page load.

I feel this is related to post under TechSEO even though I know there is no seo ranking benefit for rich snippets. I feel this community will have the best answer.

Google send me email about my local business snippet. The problem they point is the value missing. This page is about a service whit variable prices, I can not fix just one. How I solve it?

Would generating a JSON-ld document from a page’s Microdata/RDFa attributes be useful?

Hi everyone,

I wondered if anyone had any tips on adding JSON-LD while using the Yoast plugin.

To give an example, I have just posted a blog post and Yoast autogenerates some markup as Open Graph tags, such as title, description, etc.

It also adds autogenerated JSON-LD such as Website, Web Page, and BreadCrumb.

I have added a separate script of Article JSON-LD. Is it ok to have overlaps between the OG tags and the JSON-LD script? Or am I best to disable Yoast and do all structured data manually?

Happy to share web page URL if anyone wants to take a look at the source code to get a better idea.

Are there any published algorithms for doing this, or applications?

Hi ! Beginner here :) I'd like to know if there is any structured data that would be useful for definitions. I have a bunch of highschool definitions on my website (dedicated pages for those definitions such as "What is an NGO ?" for example).

I've been browsing schema.org and found the DefinedTerm property, which is not working with Google's structured data tool simulation. Maybe I'm missing something ? Nothing about definitions in the Google's documentation about JSON LD.

Thanks a lot ! :) Hope my question is not out to lunch... Cheers

SEO experts,

Newbie here, trying to optimize my website's SEO (which is on wix). What is JSON-LD code, and do you feel the difference is remarkable?
(Any other tip to improve is also appreciated!)

I have an API which returns descriptions of items (datasets) in JSON. I am considering using JSON-LD, as a lot of the vocabulary I need already exists in schema.org (in fact I am already using their types to describe my data) and other actors are already building on this (e.g. Google search).

My question is how to deal with terms that don't already have an established IRI in a well-known vocabulary (like schema.org). It is easy enough to roll out my own (e.g. http://remram.fr/my-property), however if I ever want to change that (for example, I change my vocabulary and this is now http://remram.fr/other-property, or schema.org adopts that and I want to use http://schema.org/my-property), I have no way of keeping my API compatible for old consumers: their code is written to read http://remram.fr/other-property from the expanded JSON-LD, and not http://schema.org/my-property.

My choices become:

• don't update, keep using my own property name forever; then I lose the "linked" part of "linked data" by using my own version of properties that no one can link to their own concepts
• update my @context, and consumers of my API suddenly break as the property IRIs change from under them

I noticed an issue in the JSON-LD spec repo that would allow the context to map a key to multiple terms. This seems to me like a great way to fix this (so I can link to both the old and new property, and have everyone happy) and I don't understand how JSON-LD could be rolled out without it, or how anyone uses JSON-LD contexts for an API without this.

I have been in the research field for IoT for more than a couple of years now and able to deploy stacks to collect sensor data for a fixed site e.g. a company. I wish to go further with making this data collected interoperable by using JSON-LD.

I am actually on the lookout for blogs, or repositories that can actually show where the JSON-LD occurs. From the looks of it, Linked Data generally is bulky and I dont think programming the sensor nodes to send @context and @id every time is optimum and assuming that the Linked Data layer comes somewhere higher.

Help me understand where does Web Semantics comes into play within the Realm of IoT?

We just migrated our ecommerce site from M1 to M2 and have added schema markup for price (although not for reviews/stock/etc). It's not showing up, though it does show up on some listings if I do a search:site search. I checked it in the structured data tester and the rich results test tool -- looks like the markup was implemented correctly, but it's microdata.

I'm wondering if switching to JSON-LD might help us out, as well as implementing Google's recommended addition properties (in addition to price). Thoughts? Does that sound real out there?

Metadata Fetch

I wrote a simple library to parse Metadata from websites. Things like Open Graph and Twitter Card metadata is used by readers, link previewers, search visibility and social sharing.

You can easily use this for any app that needs to create link previews, or to work with metadata.

Inspiration

This library was inspired by open_graph_parser. Their project is unmaintained so I rewrote it. The architecture makes it easy to add new Parsers for different metadatas (like json+ld schema).

I also wrote it to improve my dart.

Get it

Metadata Fetch

Note: Code Reviews are welcome! Hit me up on github!

I'm really interested in JSON-LD's @context feature and would like to build a database using it. However, most documentation out there only explains its connections to SEO (which is cool, but I'm not trying to rank sites on Google). It seems like a really great format for linked data. I have some experience with RDF and XML already, so I'm trying to expand on what those formats can do.

I guess I have two questions. (1) what kind of databases can be organized using JSON-LD, and (2) is there documentation that can guide me through it? I'd like to use a traditional relational database like MySQL and hook it up to a website with PHP -- Is this possible?

Essentially I already have a lot of content on my current site, and would like to mark it up. I have content like Recipes, with a consistent format of the information. Is there a way to add Schema that allows me to avoid doing it for the hundreds of posts I have?

Any help would be appreciated, thanks

Hey ya'll, I noticed a large company with review stars on their site. I looked into it and they're not using JSON-LD. It's working on every page of their website with the code.

Does anybody know of a plugin that can help me with this? I can only find plugins that work with JSON

My Organization is about a MedicalCondition. Do I include two (at)types:

<script type="application/ld+json">

{

"@context": "https://schema.org",

"@type": "MedicalCondition",

"name": "stuttering",

},

{

"@context": "https://schema.org",

"@type": "Organization",

"name": "National Stuttering Clinic",

}

</script>