JSON-LD explained for personal websites

Post by jack_pp » Sun, Jun 21, 2026, 9:45 PM UTC

calessian wrote: post #30

jack_pp wrote: post #26

Earlier quoted context omitted.

I remember reading somewhere that you can influence Gemini search for example, say you're selling vacuum cleaners, you want to make a landing page for it basically saying it is the best vacuum in existence and Gemini will recommend it above others or something like that. LE: so if you're consulting for Elixir or whatever, maybe it can help to make a "hidden" page only for LLM search where you basically lie about your…

It's somewhat unfortunate that, at least in my experience, its rather that non-technical people try to implement with a LLM of their choice these days. They don't look for experts or consulting, because that costs more than $20, or $200. Whether you show up in an LLM's search for "expert in near " has any measurable impact is uncertain, but I wouldn't want that to be my source of traffic.

Post by senfiaj » Sun, Jun 21, 2026, 10:15 PM UTC

abstractbeliefs wrote: post #32

JdeBP wrote: post #19

> It can aid web crawlers in understanding the semantic structure of your site, qualifying you for richer link previews, and even potentially improving your search ranking. This is fighting the last war, to stretch a metaphor. As far as I and my WWW site are concerned, Google has nowadays switched to giving people lengthy LLM-generated versions of my stuff, with errors, above pointing people to my actual stuff. 'Brea…

If you want a world where the data you present like this matters, seed it. Even if google doesn't use it, the collective internet applying this kind of metadata makes the web fertile for non-LLM-scraping competitors to provide an alternative option. Rolling over to google only ensures that they remain dominant, with a high bar for competitors, and driving them to use the same technologies.

Post by _heimdall » Sun, Jun 21, 2026, 10:49 PM UTC

angrybards wrote: post #34

_heimdall wrote: post #18

Earlier quoted context omitted.

Microdata is also a thing, and if I'm not mistaken supports the same vocabulary as JSON-LD (schema.org is a good resource). That said, JSON-LD has the default for a while now, much like how we largely abandoned REST for RPC. I'm not actually sure if microdata is still supported by all the important parsers today, I've defaulted to using LD for any site I've built for clients, especially ecommerce sites where I want G…

HTML markup designed for presentation doesn't always map well to the relationships JSON-LD is used to describe which I imagine is probably why Microdata didn't work out. I have an idea which might use it, but it is a simple use case that doesn't try do too much. Microdata requires the agent supports a more complex HTML parser, Finding a script tag in the document head is probably simpler. I wouldn't dismiss REST beca…

Post by angrybards » Sun, Jun 21, 2026, 11:23 PM UTC

_heimdall wrote: post #35

angrybards wrote: post #34

Earlier quoted context omitted.

HTML markup designed for presentation doesn't always map well to the relationships JSON-LD is used to describe which I imagine is probably why Microdata didn't work out. I have an idea which might use it, but it is a simple use case that doesn't try do too much. Microdata requires the agent supports a more complex HTML parser, Finding a script tag in the document head is probably simpler. I wouldn't dismiss REST beca…

Personally I'm of the camp that HTNL schema data should only represent what's visually displayed, much like how accessibility is usually done. In that way I like Microdata because it reinforces that if there isn't a DOM node showing price, for example, I shouldn't be showing that data in a visually hidden way. For REST, I think the only reason HTML has been useful this long is because of the REST ideas that Fielding…

Post by deftio » Sun, Jun 21, 2026, 11:41 PM UTC