#schemaorg — Public Fediverse posts

https://t3forum.net/d/1100-strukturierte-daten-fuer-portfolioreferenzen

#t3academyforum #structureddata #schemaorg

Wolfgang Wagner @[email protected] · 2026-03-06 · 07:15 UTC

Neu im Forum:

Strukturierte Daten für Portfolio/Referenzen

https://t3forum.net/d/1100-strukturierte-daten-fuer-portfolioreferenzen

#t3academyforum #structureddata #schemaorg

Wolfgang Wagner @[email protected] · 2026-03-06 · 07:15 UTC

Neu im Forum:

Strukturierte Daten für Portfolio/Referenzen

https://t3forum.net/d/1100-strukturierte-daten-fuer-portfolioreferenzen

#t3academyforum #structureddata #schemaorg

Wolfgang Wagner @[email protected] · 2026-03-06 · 07:15 UTC

Neu im Forum:

Strukturierte Daten für Portfolio/Referenzen

https://t3forum.net/d/1100-strukturierte-daten-fuer-portfolioreferenzen

#schemaorg #structureddata #t3academyforum

Wolfgang Wagner @wowa_TYPO3 · 2026-03-06 · 07:15 UTC

Neu im Forum:

Strukturierte Daten für Portfolio/Referenzen

https://rmendes.net/articles/2026/03/03/adding-ai-usage-metadata-to

#t3academyforum #structureddata #schemaorg

Ricardo @[email protected] · 2026-03-03 · 18:48 UTC

Adding AI Usage Metadata to JSON-LD Structured Data

#indieweb #ai #structureddata #schemaorg #indiekit

Ricardo @[email protected] · 2026-03-03 · 18:48 UTC

Adding AI Usage Metadata to JSON-LD Structured Data

https://rmendes.net/articles/2026/03/03/adding-ai-usage-metadata-to

#indieweb #ai #structureddata #schemaorg #indiekit

Ricardo @[email protected] · 2026-03-03 · 18:48 UTC

Adding AI Usage Metadata to JSON-LD Structured Data

https://rmendes.net/articles/2026/03/03/adding-ai-usage-metadata-to

#indieweb #ai #structureddata #schemaorg #indiekit

Ricardo @[email protected] · 2026-03-03 · 18:48 UTC

Adding AI Usage Metadata to JSON-LD Structured Data

https://rmendes.net/articles/2026/03/03/adding-ai-usage-metadata-to

#indiekit #schemaorg #structureddata #ai #indieweb

Ricardo @[email protected] · 2026-03-03 · 18:48 UTC

Adding AI Usage Metadata to JSON-LD Structured Data

https://rmendes.net/articles/2026/03/03/adding-ai-usage-metadata-to

#indieweb #ai #structureddata #schemaorg #indiekit

PPC Land @[email protected] · 2026-03-03 · 11:52 UTC

Google's secret thumbnail formula: schema.org and og:image both count: Google today clarified it uses both schema.org markup and the og:image meta tag to select image thumbnails in Google Search and Discover, updating its official documentation. https://ppc.land/googles-secret-thumbnail-formula-schema-org-and-og-image-both-count/ #Google #SEO #SchemaOrg #WebMarketing #DigitalMarketing

#google #seo #schemaorg #webmarketing #digitalmarketing

Terence Eden’s Blog @[email protected] · 2026-01-12 · 12:34 UTC

Maximally Semantic Structure for a Blog Post

https://shkspr.mobi/blog/2026/01/maximally-semantic-structure-for-a-blog-post/

Yes, I know the cliché that bloggers are always blogging about blogging!

I like semantics. It tickles that part of my delicious meaty brain that longs for structure. Semantics are good for computers and humans. Computers can easily understand the structure of the data, humans can use tools like screen-readers to extract the data they're interested in.

In HTML, there are three main ways to impose semantics - elements, attributes, and hierarchical microdata.

Elements are easy to understand. Rather than using a generic element like <div> you can use something like <nav> to show an element's contents are for navigation. Or <address> to show that the contents are an address. Or <article><section> to show that the section is part of a parent article.

Attributes are also common. You can use relational attributes to show how a link relates to the page it is on. For example <a rel=author href=https://example.com> shows that the link is to the author of the current page. Or, to see that a link goes to the previous page in a series <a rel=prev href=/page5>.

Finally, we enter the complex and frightening world of microdata.

Using the Schema.org vocabulary it's possible to add semantic metadata within an HTML element. For example, <body itemtype=https://schema.org/Blog itemscope> says that the body of this page is a Blog. Or, to say how many words a piece has, <span itemprop=wordCount content=1100>1,100 words</span>.

There are many properties you can use. Here's the outline structure of a single blog post with a code sample, a footnote, and a comment. You can check its structured data and verify that it is conformant HTML.

Feel free to reuse.

<!doctype html>
<html lang=en-gb>
<head><title>My Blog</title></head>
<body itemtype=https://schema.org/Blog itemscope>

    <header itemprop=headline>
        <a rel=home href=https://example.com>My Blog</a>
    </header>

    <main itemtype=https://schema.org/BlogPosting itemprop=blogPost itemscope>
        <article>
            <header>
                <time itemprop=https://schema.org/datePublished datetime=2025-12-01T12:34:39+01:00>
                    1st January, 2025
                </time>
                <h1 itemprop=headline>
                    <a rel=bookmark href=https://example.com/page>Post Title</a>
                </h1>
                <span itemtype=https://schema.org/Person itemprop=author itemscope>
                    <a itemprop=url href=https://example.org/>
                        By <span itemprop=name>Author Name</span>
                    </a>
                    <img itemprop=image src=/photo.jpg alt>
                </span>
                <p>
                    <a itemprop=keywords content=HTML rel=tag href=/tag/html/>HTML</a> 
                    <a itemprop=keywords content=semantics rel=tag href=/tag/semantics/>semantics</a> 
                    <a itemprop=commentCount content=6 href=#comments>6 comments</a>
                    <span itemprop=wordCount content=1100>1,100 words</span>
                    <span itemtype=https://schema.org/InteractionCounter itemprop=interactionStatistic itemscope>
                        <meta content=https://schema.org/ReadAction itemprop=interactionType>
                        <span itemprop=userInteractionCount content=5150>
                            Viewed ~5,150 times
                        </span>
                    </span>
                </p>
            </header>

            <div itemprop=articleBody>
                <img itemprop=image src=/hero.png alt>
                <p>Text of the post.</p>
                <p>Text with a footnote<sup id=fnref><a role=doc-noteref href=#fn>0</a></sup>.</p>

                <pre itemtype=https://schema.org/SoftwareSourceCode itemscope translate=no>
                    <span itemprop=programmingLanguage>PHP</span>
                    <code itemprop=text>&amp;lt;?php echo $postID ?&amp;gt;</code>
                </pre>

                <section role=doc-endnotes>
                    <h2>Footnotes</h2>
                    <ol>
                        <li id=fn>
                            <p>Footnote text. <a role=doc-backlink href=#fnref>↩︎</a></p>
                        </li>
                    </ol>
                </section>
            </div>
        </article>

        <section id=comments>
            <h2>Comments</h2>
            <article itemtype=https://schema.org/Comment itemscope id="comment-123465">
                <time itemprop=dateCreated datetime=2025-09-11T13:24:54+01:00>
                    <a itemprop=url href=#comment-123465>2025-09-11 13:24</a>
                </time>
                <div itemtype=https://schema.org/Person itemprop=author itemscope>
                    <img itemprop=image src="/avatar.jpg" alt>
                    <h3>
                        <span itemprop=name>Alice</span> says:
                    </h3>
                </div>
                <div itemprop=text>
                    <p>Comment text</p>
                </div>
            </article>
        </section>
    </main>
</body>
</html>

This blog post is entitled "maximally" but, of course, there is lots more that you can add if you really want to.

Remember, none of this is necessary. Computers and humans are pretty good at extracting meaning from unstructured text. But making things easier for others is always time well spent.

#blogging #HTML #schemaOrg #semanticWeb

#blogging #html #schemaorg #semanticweb

Terence Eden’s Blog @[email protected] · 2025-12-24 · 12:34 UTC

Fixing "Date/time not in ISO 8601 format" in Google Search Console

https://shkspr.mobi/blog/2025/12/fixing-date-time-not-in-iso-8601-format-in-google-search-console/

I like using microdata within my HTML to provide semantic metadata. One of my pages had this scrap of code on it:

<time
   itemprop="datePublished"
   itemscope
   datetime="2025-06-09T11:27:06+01:00">9 June 2025 11:27</time>

The Google Search Console was throwing this error:

I was fairly sure that was a valid ISO 8601 string. It certainly matched the description in the Google documentation. Nevertheless, I fiddled with a few different formats, but all failed.

On the advice of Barry Hunter, I tried changing the datetime attribute to content. That also didn't work.

Then I looked closely at the code.

The issue is the itemscope. Removing that allowed the code to pass validation. But why?

Here's what the Schema.org documentation says:

By adding itemscope, you are specifying that the HTML contained in the block is about a particular item.

The HTML specification gives this example:

<div itemscope>
   <img itemprop="image" src="google-logo.png" alt="Google">
</div>

Here, the image property is the value of the element. In this case google-logo.png. So what's the problem with the time example?

Well, <image> is a void element. It doesn't have any HTML content - so the metadata is taken from the src attribute.

But <time> is not a void element. It does contain HTML. So something like this would be valid:

<time
   itemprop="datePublished"
   itemscope
>2025-06-09T11:27:06+01:00</time>

The text contained by the element is a valid ISO8601 string.

My choice was either to present the ISO8601 string to anyone viewing the page, or simply to remove the itemscope. So I chose the latter.

#HTML #metadata #schemaOrg

#html #metadata #schemaorg

Habr @[email protected] · 2025-10-09 · 15:52 UTC

AI-агенты для SEO: как автоматизировать 98% рутины и не потерять качество

Четыре месяца назад я сидел в офисе клиента в Минске. Владелец интернет-магазина спортивного питания смотрел на график Analytics. Линия трафика ползла вниз. Медленно. Но неумолимо. «Мы делаем всё правильно», — сказал он. И был прав. Контент. Техническая оптимизация. Ссылочная масса. Команда из трёх SEO-специалистов работала на пределе. Но конкурент из Москвы обгонял их каждую неделю. По всем фронтам. Я открыл сайт конкурента. Замер. За последние три месяца они опубликовали 90 новых статей. Детальные гайды по спортпиту. Сравнения. Обзоры. Внутренняя перелинковка выстроена хирургически точно. Schema.org разметка на каждой странице. Технические параметры — как у enterprise-проекта. Позвонил знакомому, который работает в той компании. Спросил прямо: «У вас что, команда из двадцати человек?» Пауза. Смех. «Один SEO-специалист. Плюс AI-агенты. Автоматизировали 98% процессов.» Вот тогда я понял. Правила изменились. И большинство об этом ещё не знает.

https://habr.com/ru/articles/955108/

#AIагенты_для_SEO #автоматизация_SEO #ai_overviews #schemaorg #eeat #кластеризация_запросов #внутренние_ссылки #линкбилдинг #keyword_research #техническое_SEO

#техническое_seo #keyword_research #линкбилдинг #внутренние_ссылки #кластеризация_запросов #eeat

Terence Eden’s Blog @[email protected] · 2025-09-19 · 11:34 UTC

Class Warfare! Can I eliminate CSS classes from my HTML?

https://shkspr.mobi/blog/2025/09/class-warfare-can-i-eliminate-css-classes-from-my-html/

I recently read a brilliantly provocative blog post called "This website has no class". In it, Adam Stoddard makes the case that you might not need CSS classes on a modern website:

I think constraints lead to interesting, creative solutions […]. Instead of relying on built in elements a bit more, I decided to banish classes from my website completely.

Long time readers will know that I'm a big fan of using semantic HTML where possible. If you peek beneath the curtain of this website you'll only see a handful of <div> elements (mostly because WordPress hardcodes them) - all the other blocks are fully semantic. Regrettably, there are rather too many <span> elements for my liking - normally for accessibility or for supplementing the metadata.

Overall, my CSS contained about 134 rules which selected based on class. Is that a lot? It feels like a lot.

On the one hand, classes are an easy way of splitting and grouping elements. Some <img>s should be displayed one way, the rest another. There's no semantic way to say "This is a hero image and should take up the full width, but this is an icon and should float discretely to the right."

But, on the other hand, why do we need classes? Keith Cirkel's excellent post "CSS Classes considered harmful" goes through their history and brings together some proposed solutions for replacing them. I think his idea of using data- attributes is a neat hack - but ultimately isn't much different from using classes. It's still a scrap of metadata to be tied into a style-sheet.

Classes are great for when you reuse something. I have multiple <section> elements but most don't share anything in common with the others. So they probably oughtn't have classes.

Removing classes has some advantages. It makes the HTML fractionally smaller, sure, but it also forces the author to think about the logical structure of their page and the semantics behind it.

Looking through my HTML, lots of classes exist because of laziness. If I want to position all the <time> elements which are within a comment, I don't need to write <time class="whatever"> and to pair it with .whatever { … }. Instead, I can use modern CSS selectors and say #comments time { … }.

But this leads me on to another existential question.

Are IDs necessary in modern HTML?

Mayyyyybe? I only have one <main> element, so an ID on there is unnecessary. <input> elements need IDs in order to be properly targetted by <label>s - but the label can wrap around the input. I have multiple <aside> elements because there's no semantic <widget> element, so they need unique IDs.

In theory, as suggested by Adam above, I could use an autonomous custom element like <my-widget> - but that has none of the semantics and, frankly, feels like a bit of a cheat.

Trimming the fat

Any day where I can delete some code is a good day. This was an excellent exercise in going through (years) of HTML and CSS to see what cruft had built up.

The first CSS rule I changed was, as mentioned above:

time.commentmetadata {    float: right;}

Which became:

#comments time {     float: right;}

Classless and slightly more brief. Is it more readable? Having the fact it was about the metadata in a class could have been slightly useful - but if I thought it would be confusing, I could stick a /* comment */ in there.

Next, I found <nav class="navigation posts-navigation"> - what a tautology! I have multiple <nav> elements, it is true. But none of them have the same style. So this swiftly became <nav id="posts-navigation"> with an accompanying CSS rewrite.

My theme switcher had a bunch of <label class=button>s. They were all within a container with a unique ID, so could they be changed? Yes. But seeing the class name in the HTML is a good reminder to the author of how they are meant to display. Does that co-mingle content and presentation too much?

Some of the WordPress default classes are ridiculous. The body_class() function injected this into every <body>

"wp-singular post-template-default single single-post postid-62959 single-format-standard wp-theme-edent-wordpress-theme"

Most of that is redundant - what's the difference between single and single-post? For my purposes, nothing! So they were all yeeted into the sun.

Rather than targetting IDs or classes, I targetted the presence or absence of Schema.org microdata.

For example:

main[itemprop="blogPost"] { … }main:not([itemprop="blogPost"]) { … }

This can go to the extreme. I have lots of comments, each one has an author, the author's details are wrapped in <div class="authordetails">…</div>

That can be replaced with:

/* Comment Author */li[itemtype="https://schema.org/Comment"] > article > div[itemprop="https://schema.org/author"] {    margin-bottom: 0;}

Is that sensible? It is more semantic, but feels a bit brittle.

Parent selector are also now a thing. If I want a paragraph to have centred text but only when there's a submit button inside it:

p:has(input#submit) {  text-align: center;}

Again, am I sure that my button will always be inside a paragraph?

Similarly, sibling selectors are sometimes superior - but they do suppose that your layout never changes.

What remains?

There are some bits of this site which are reusable and do need classes. The code-highlighting you see above requires text to be wrapped in spans with specific classes.

Image alignment was also heavily class based.

There are some accessibility things which are either hidden or exposed using classes.

A bunch of WordPress defaults use classes and, even if they are redundant, it's hard to exorcise them.

As much as I would have liked to get rid of all my IDs, many needed to stay for linking as well as CSS targetting.

All told, the changes I made were:

134 class selectors down to about 65.
35 ID selectors up to about 50.
5 attribute selectors up to to about 20.
Deleted or combined a lot of redundant CSS and tidied up my markup considerably.

I have around 250 CSS rules, so now the majority target semantics rather than classes or IDs.

Is this really necessary?

No, of course not. This is an exercise in minimalism, creativity, and constraint. Feel free to litter your HTML with whatever attributes you want!

As I went through, it increasingly became apparent that I was fitting my CSS to my HTML's logical structure rather than to its conceptual structure.

Previously, my comments were targetted with a class. Now they have the slightly more tangled targetting of "divs with this schema attribute whose parent is an article and whose grandparent has this ID".

It is a delightful meditative exercise to go through your code and deeply consider whether something is unique, reusable, or obsolete.

#blog #css #HTML #schemaOrg #semanticWeb

#blog #css #html #schemaorg #semanticweb

ljc @ljcastro · 2025-06-30 · 08:21 UTC

Last week we had tons of amazing discussions on #metadata for #TrainingMaterials #OER during our @NFDI #DiscoRSE #Quadriga #hackathon at @ZBMED

Thanks to all participants!

We worked on crosswalks and mappings including #SchemaOrg #LearningResource @dini @dalia #Bioschemas #AMB #Skills4EOSC

Results will be published in @zenodo_org Keep an eye to our updates on social media if you are interested in the topic.

#metadata #trainingmaterials #oer #discorse #quadriga #hackathon

ljc @[email protected] · 2025-06-30 · 08:21 UTC

Last week we had tons of amazing discussions on #metadata for #TrainingMaterials #OER during our @NFDI #DiscoRSE #Quadriga #hackathon at @ZBMED

Thanks to all participants!

We worked on crosswalks and mappings including #SchemaOrg #LearningResource @dini @dalia #Bioschemas #AMB #Skills4EOSC

Results will be published in @zenodo_org Keep an eye to our updates on social media if you are interested in the topic.

#metadata #trainingmaterials #oer #discorse #quadriga #hackathon

ljc @[email protected] · 2025-06-30 · 08:21 UTC

Last week we had tons of amazing discussions on #metadata for #TrainingMaterials #OER during our @NFDI #DiscoRSE #Quadriga #hackathon at @ZBMED

Thanks to all participants!

We worked on crosswalks and mappings including #SchemaOrg #LearningResource @dini @dalia #Bioschemas #AMB #Skills4EOSC

Results will be published in @zenodo_org Keep an eye to our updates on social media if you are interested in the topic.

#metadata #trainingmaterials #oer #discorse #quadriga #hackathon

ljc @[email protected] · 2025-06-30 · 08:21 UTC

Last week we had tons of amazing discussions on #metadata for #TrainingMaterials #OER during our @NFDI #DiscoRSE #Quadriga #hackathon at @ZBMED

Thanks to all participants!

We worked on crosswalks and mappings including #SchemaOrg #LearningResource @dini @dalia #Bioschemas #AMB #Skills4EOSC

Results will be published in @zenodo_org Keep an eye to our updates on social media if you are interested in the topic.

#skills4eosc #amb #bioschemas #learningresource #schemaorg #hackathon

ljc @[email protected] · 2025-06-30 · 08:21 UTC

Last week we had tons of amazing discussions on #metadata for #TrainingMaterials #OER during our @NFDI #DiscoRSE #Quadriga #hackathon at @ZBMED

Thanks to all participants!

We worked on crosswalks and mappings including #SchemaOrg #LearningResource @dini @dalia #Bioschemas #AMB #Skills4EOSC

Results will be published in @zenodo_org Keep an eye to our updates on social media if you are interested in the topic.

#metadata #trainingmaterials #oer #discorse #quadriga #hackathon

Cord Wiljes @[email protected] · 2025-06-27 · 20:09 UTC

“#Metadata is in the air, everywhere.”

61 metadata experts from the #NFDI consortia met on June 25-27 at @tibhannover Their goal was to prepare a NFDI recommendation on generic metadata schemas for research data. It was decided to adopt DataCite Metadata Schema (by @datacite), #DCAT (by @w3c) and #schemaorg. Crosswalks, provided by RDA (@resdatall), were investigated and fields classified as mandatory, recommended and optional. More info: https://www.nfdi.de/section-meta/task-force-metadata/?lang=en

@NFDI #rdm

#metadata #nfdi #dcat #schemaorg #rdm

Timo Tijhof @krinkle · 2025-06-20 · 07:18 UTC

You'd think Google, having launched schema.org, knows how to produce valid schema.org metadata and HTML5.

YouTube: How about a `<span>` inside the head, and `<link rel=alternative>` inside the body?

HTML5 parsers:
Thanks, I'll take that span as your implied end of `<head>`, and raise you an implied start of `<body>`. Everything that follows is now part of the body.

Context:
https://github.com/Ranchero-Software/NetNewsWire/issues/902#issuecomment-2990075755

#NetNewsWire #WebStandards #whatwg #HTML5 #schemaorg #google

#netnewswire #webstandards #whatwg #html5 #schemaorg #google

Thomas Tursics @[email protected] · 2025-06-02 · 21:15 UTC

@b2m @datenschatz der Musterdatenkatalog der Bertelsmann Stiftung hatte anfangs auch die #GND verlinkt. Beim letzten großen Update wurden einfach eine handvoll Links benutzt - für jeden sollte jetzt etwas dabei sein. #GND #Wikidata #SchemaORG #EuroVoc

https://github.com/bertelsmannstift/Musterdatenkatalog-V4/blob/main/assets/skos_sample.png

#gnd #wikidata #schemaorg #eurovoc

Habr @[email protected] · 2025-05-28 · 21:52 UTC

Schema.org на Tilda — раз и навсегда

Наверное у каждого разработчика на Тильде есть момент, когда он опубликовал сайт, порадовался, а потом открыл выдачу и увидел унылый двухстрочный сниппет без FAQ, без даты, без красивых крошек в URL. А ведь у конкурентов есть. И тогда само собой возникают вопросы: где вообще прятать JSON-LD в Тильде (и возможно ли это)? Как не сорвать вёрстку? И, главное, можно ли сделать всё так, чтобы через полгода не искать где запрятана эта микроразметка в админке сайта? Спойлер: можно. Ниже — то, чем мы сами пользуемся, и ничего лишнего.

https://habr.com/ru/articles/913758/

#Тильда #schemaorg #json #seo #микроразметка #jsonld

#jsonld #микроразметка #seo #json #schemaorg #тильда

Inautilo @[email protected] · 2025-05-24 · 10:15 UTC

#Development #Launches
Introducing NLWeb · Bringing conversational interfaces directly to the web https://ilo.im/1642dj

_____
#Business #AI #Website #Blog #RSS #SchemaOrg #SEO #WebDev #Frontend #Backend

#development #launches #business #ai #website #blog

Cord Wiljes @[email protected] · 2025-05-13 · 22:46 UTC

At #HMC_con2025, Emanuel Söding presented the results of the 1st NFDI Metadata Workshop: All 26 NFDI consortia participated and agreed to
1. promote the three cross-disciplinary standards: #DCAT, #DataCite Metadata Schema, #schemaorg
2. work towards an NFDI core metadata profile that identifies mandatory fields of these three
3. recommend registration and at least annual curation in #re3data
Report of the workshop: https://doi.org/10.5281/zenodo.15227236
Contact: https://www.nfdi.de/section-meta/task-force-metadata/?lang=en

#rdm #NFDI #metadata

#dcat #datacite #schemaorg #re3data #rdm #nfdi

Cord Wiljes @[email protected] · 2025-05-13 · 22:46 UTC

At #HMC_con2025, Emanuel Söding presented the results of the 1st NFDI Metadata Workshop: All 26 NFDI consortia participated and agreed to
1. promote the three cross-disciplinary standards: #DCAT, #DataCite Metadata Schema, #schemaorg
2. work towards an NFDI core metadata profile that identifies mandatory fields of these three
3. recommend registration and at least annual curation in #re3data
Report of the workshop: https://doi.org/10.5281/zenodo.15227236
Contact: https://www.nfdi.de/section-meta/task-force-metadata/?lang=en

#rdm #NFDI #metadata

#dcat #datacite #schemaorg #re3data #rdm #nfdi

Cord Wiljes @[email protected] · 2025-05-13 · 22:46 UTC

At #HMC_con2025, Emanuel Söding presented the results of the 1st NFDI Metadata Workshop: All 26 NFDI consortia participated and agreed to
1. promote the three cross-disciplinary standards: #DCAT, #DataCite Metadata Schema, #schemaorg
2. work towards an NFDI core metadata profile that identifies mandatory fields of these three
3. recommend registration and at least annual curation in #re3data
Report of the workshop: https://doi.org/10.5281/zenodo.15227236
Contact: https://www.nfdi.de/section-meta/task-force-metadata/?lang=en

#rdm #NFDI #metadata

#hmc_con2025 #metadata #nfdi #rdm #re3data #schemaorg

Habr @[email protected] · 2025-04-17 · 09:12 UTC

Как рассказать о сайте поисковой системе 2

Доброго времени суток. В этой статье я хочу дополнить первую часть рассказа о том как же донести поисковику информацию о своём сайте. Здесь будут рассмотрены такие темы как IndexNow, security.txt, schema.org.

Habr @[email protected] · 2025-04-17 · 09:12 UTC

Как рассказать о сайте поисковой системе 2

Доброго времени суток. В этой статье я хочу дополнить первую часть рассказа о том как же донести поисковику информацию о своём сайте. Здесь будут рассмотрены такие темы как IndexNow, security.txt, schema.org.

Habr @[email protected] · 2025-04-17 · 09:12 UTC

Как рассказать о сайте поисковой системе 2

Доброго времени суток. В этой статье я хочу дополнить первую часть рассказа о том как же донести поисковику информацию о своём сайте. Здесь будут рассмотрены такие темы как IndexNow, security.txt, schema.org.

Habr @[email protected] · 2025-04-17 · 09:12 UTC

Как рассказать о сайте поисковой системе 2

Доброго времени суток. В этой статье я хочу дополнить первую часть рассказа о том как же донести поисковику информацию о своём сайте. Здесь будут рассмотрены такие темы как IndexNow, security.txt, schema.org.

#securitytxt #indexnow #schemaorg #seoоптимизация

Habr @[email protected] · 2025-03-25 · 00:02 UTC

UUIDv7 — ключ к глобальному поиску с помощью LLM в произвольных внешних системах

Представим себе такой сценарий. Пользователь устно и/или в чате поручает ИИ-агенту найти и приобрести нужный товар с заданными параметрами. ИИ-агент в разговоре уточняет у пользователя задание, составляет описание товара и на его основе формирует запрос к поисковой системе... а затем ищет товар в базах данных поставщиков. Как это реализовать

#LLM #UUIDv7 #ииагент #RAG #MCP #бд #schemaorg #ключ #сниппет

#сниппет #ключ #schemaorg #бд #mcp #rag

Habr @[email protected] · 2025-03-25 · 00:02 UTC

UUIDv7 — ключ к глобальному поиску с помощью LLM в произвольных внешних системах

Представим себе такой сценарий. Пользователь устно и/или в чате поручает ИИ-агенту найти и приобрести нужный товар с заданными параметрами. ИИ-агент в разговоре уточняет у пользователя задание, составляет описание товара и на его основе формирует запрос к поисковой системе... а затем ищет товар в базах данных поставщиков. Как это реализовать

#LLM #UUIDv7 #ииагент #RAG #MCP #бд #schemaorg #ключ #сниппет

#сниппет #ключ #schemaorg #бд #mcp #rag

Habr @[email protected] · 2025-03-25 · 00:02 UTC

UUIDv7 — ключ к глобальному поиску с помощью LLM в произвольных внешних системах

Представим себе такой сценарий. Пользователь устно и/или в чате поручает ИИ-агенту найти и приобрести нужный товар с заданными параметрами. ИИ-агент в разговоре уточняет у пользователя задание, составляет описание товара и на его основе формирует запрос к поисковой системе... а затем ищет товар в базах данных поставщиков. Как это реализовать

#LLM #UUIDv7 #ииагент #RAG #MCP #бд #schemaorg #ключ #сниппет

#сниппет #ключ #schemaorg #бд #mcp #rag

Habr @[email protected] · 2025-03-25 · 00:02 UTC

UUIDv7 — ключ к глобальному поиску с помощью LLM в произвольных внешних системах

Представим себе такой сценарий. Пользователь устно и/или в чате поручает ИИ-агенту найти и приобрести нужный товар с заданными параметрами. ИИ-агент в разговоре уточняет у пользователя задание, составляет описание товара и на его основе формирует запрос к поисковой системе... а затем ищет товар в базах данных поставщиков. Как это реализовать

#LLM #UUIDv7 #ииагент #RAG #MCP #бд #schemaorg #ключ #сниппет

#llm #uuidv7 #ииагент #rag #mcp #бд

Chris Müller 🌱 @[email protected] · 2025-03-22 · 10:04 UTC

Folien meiner Session

Strukturierte Daten mit Schema.org

auf dem TYPO3camp Mitteldeutschland

https://brotkrueml.dev/presentations/t3cmd25/schema.html

https://brotkrueml.dev/presentations/t3cmd25/schema.html

Chris Müller 🌱 @[email protected] · 2025-03-22 · 10:04 UTC

Folien meiner Session

Strukturierte Daten mit Schema.org

auf dem TYPO3camp Mitteldeutschland

https://brotkrueml.dev/presentations/t3cmd25/schema.html

Chris Müller 🌱 @[email protected] · 2025-03-22 · 10:04 UTC

Folien meiner Session

Strukturierte Daten mit Schema.org

auf dem TYPO3camp Mitteldeutschland

https://brotkrueml.dev/presentations/t3cmd25/schema.html

Chris Müller 🌱 @[email protected] · 2025-03-22 · 10:04 UTC

Folien meiner Session

Strukturierte Daten mit Schema.org

auf dem TYPO3camp Mitteldeutschland

https://brotkrueml.dev/presentations/t3cmd25/schema.html

#t3cmd25 #t3cmd #typo3 #schemaorg

Chris Müller 🌱 @[email protected] · 2025-03-22 · 10:04 UTC

Folien meiner Session

Strukturierte Daten mit Schema.org

auf dem TYPO3camp Mitteldeutschland

ljc @ljcastro · 2025-02-26 · 10:10 UTC

And now #NelsonQuiñones presenting #MLentory, a registry for #MachineLearning models, aggregating information from multiple platforms and harmonizing it all using the @resdatall #FAIR4ML #schemaorg extension.

Using #STELLAFramework for live evaluation and @denbioffice for prototyping

Lost in a sea of #MachineLearning models? #MLentory to the rescue! Keep tune with our updates, official launch coming this year 2025!

#derse25 #nelsonquinones #mlentory #machinelearning #fair4ml #schemaorg

ljc @[email protected] · 2025-02-26 · 10:10 UTC

And now #NelsonQuiñones presenting #MLentory, a registry for #MachineLearning models, aggregating information from multiple platforms and harmonizing it all using the @resdatall #FAIR4ML #schemaorg extension.

Using #STELLAFramework for live evaluation and @denbioffice for prototyping

Lost in a sea of #MachineLearning models? #MLentory to the rescue! Keep tune with our updates, official launch coming this year 2025!

#derse25 #nelsonquinones #mlentory #machinelearning #fair4ml #schemaorg

ljc @[email protected] · 2025-02-26 · 10:10 UTC

And now #NelsonQuiñones presenting #MLentory, a registry for #MachineLearning models, aggregating information from multiple platforms and harmonizing it all using the @resdatall #FAIR4ML #schemaorg extension.

Using #STELLAFramework for live evaluation and @denbioffice for prototyping

Lost in a sea of #MachineLearning models? #MLentory to the rescue! Keep tune with our updates, official launch coming this year 2025!

#derse25 #nelsonquinones #mlentory #machinelearning #fair4ml #schemaorg

ljc @[email protected] · 2025-02-26 · 10:10 UTC

And now #NelsonQuiñones presenting #MLentory, a registry for #MachineLearning models, aggregating information from multiple platforms and harmonizing it all using the @resdatall #FAIR4ML #schemaorg extension.

Using #STELLAFramework for live evaluation and @denbioffice for prototyping

Lost in a sea of #MachineLearning models? #MLentory to the rescue! Keep tune with our updates, official launch coming this year 2025!

#stellaframework #schemaorg #fair4ml #machinelearning #mlentory #nelsonquinones

ljc @[email protected] · 2025-02-26 · 10:10 UTC

And now #NelsonQuiñones presenting #MLentory, a registry for #MachineLearning models, aggregating information from multiple platforms and harmonizing it all using the @resdatall #FAIR4ML #schemaorg extension.

Using #STELLAFramework for live evaluation and @denbioffice for prototyping

Lost in a sea of #MachineLearning models? #MLentory to the rescue! Keep tune with our updates, official launch coming this year 2025!