Schema.org - Search Engines
<head>
<meta charset="utf-8" />
<title>The Seattle Viaduct Before & After - Gregle.dev</title>
<meta name="description" content="Seattle's waterfront before and after the removal of the Alaskan Way Viaduct.
Two timelapses from the same perspective to highlight the change in the area with the completetion of 30 seperate waterfront projects." />
<!-- ... -->
<script type="application/ld+json">
{
"@context": "https://schema.org/",
"@type": "Article",
"headline": "The Seattle Viaduct Before & After - Gregle.dev",
"abstract": "Seattle's waterfront before and after the removal of the Alaskan Way Viaduct.",
"description": "Seattle's waterfront before and after the removal of the Alaskan Way Viaduct. Two timelapses from the same perspective to highlight the change in the area with the completetion of 30 seperate waterfront projects.",
"image": "https://assets.gregle.dev/timelapses/viaduct/preview.jpg",
"thumbnailUrl": "https://assets.gregle.dev/timelapses/viaduct/preview.jpg"
}
</script>
</head>Schema is another standard for describing content on the web created by Google, Microsoft, Yahoo, and Yandex to make the job of their search web scrapers easier. Its documentation is long and complicated, and honestly, after years of them making Google Search worse, I don't think it's my job to make it better, and likely defining these schemas just makes it easier for their AI to hoover up your content right before they charge you for the privilege of using it again. So it's better to let Google and friends worry about their own bots and save your time for building cool things. But this is how you make those fancy Google results your marketing department keeps going on about.