JSON-LD

And the second feature was more about discoverability of your content on your site.

So it's a JSON-LD feature for schema.org or schema.org kind of JSON.

So I think if you've used maybe like e-commerce plugins in the past, they will create a schema to describe your product whilst you're viewing that product page and it will create json that's in a certain format it's json ld that will be output sort of hidden from the front end the viewer but it will be inside the page source and it will be readable by google and it will sort of define what the product is with certain attributes so google will know okay well the the name of the product is this it's a type of product it's the price is this whatever and and that then gives google in the past uh the information to be able to actually index it properly maybe put it into the shopping tab of Google.

And that's using something called schema.org. It's a way to describe data in a classification.

We've tried to look at use cases and tried to look at how to make experiences better.

And it will be the same with AI.

So the JSON-LD feature, there's a lot of mapping going on there.

There was a lot of thought that goes into that to make that work.

Yeah, I'll add a couple of things there on the, you know, using AI to add things or, you know, actually analyze your website.

I was on the phone with a customer last week and we were talking about LLMS text files, JSON-LD format, those formats, those sorts of things to add into the back end of the website.

And one of the things that I've seen very consistently, Zach, and I think you've seen this too, is AI is really good if you just point AI at your website and say, I need an LLMS text file, I need JSON-LD formats, I need your help deploying this, it can go off and create all of that content for you.

That way you don't have to manually create it on your own.

And It's a virtuous cycle now where you're going to end up showing up better from an AI search perspective because you have all of this content formatted in the right way.

Uh, the next thing that I was thinking about in what you were talking about there, um, is the schema.

So have you taken inspiration from other schemas and other documentation stuff out there? Like one of the ones that I was thinking about from some of my earlier work, uh, in, in this is like JSON LD.

I don't know if you're familiar with that.

But I'm just curious if you've had any other, uh, you know, influences there.

No, it's, it's 100% right.

I mean, you know, it, there, there is, there is absolutely something to be said going, again, going back to the documentation thing, is there's absolutely something to be said about existing patterns out there.

Like I mentioned the, uh, the JSON LD thing in particular, uh, as a direction to potentially help me out in like asset management.

Uh, so like, you know, just, you know, putting up fonts somewhere in a CDN, putting up SVGs, putting up, uh, you know, images and stuff like that on the CDNs for them to get, to, to, to be able to be grabbed.

Add images or video when they help.

Do not hide the steps only in JSON-LD.

Do not expect how-to rich results in Google search.

Data catalogs, best combination.

Keep catalog metadata synchronized with the actual files.

Document update frequency and last update date.

JSON-LD example.

Fax page.

And it could be a product, it could be like its sale price, it could be lots of different things.

And for many years, the schema markup was kind of a reproduction of your web content as JSON-LD or as even Microdata or RDFA.

But it was just a reproduction of that.

And I think as we were going here more recently, there's a real opportunity to use this in new ways.

So Google uses scripts, To understand entity details, they write the script here in the article, like product prices, review stars, et cetera, et cetera.

Practically speaking, this means doubles escaped entities like it does AMP with the code for AMP will no longer be unrolled if you're using JSON-LD for structured data.

Be sure to update your code to standard escapes or unit code hexadecimal or it will not read it.

So I don't know if all the WordPress tools automatically Do it the right way? So I would check with your plugin provider if you are using WordPress to do your structured

I've been through several of these semantic cycles.

2012 and 2013, there was a big JSON-LD link data push.

And it coincided with a previous AI wave.

If you remember IBM Watson, Wolfram Alpha, there was quite a few.