More on the topic...
Generating detailed summary...
Failed to generate summary. Please try again.
JSON-LD embeds structured data in your site’s <head> so crawlers like Googlebot can parse it without running any JavaScript. You wrap a JSON object in a <script type="application/ld+json"> tag, set "@context" to "https://schema.org", then use "@graph" to list nodes. Each node gets an "@id" (usually your URL plus a hash) and an "@type" (WebSite, WebPage, Person, etc.), plus key/value properties like name, url, description or image.
Your site-level JSON-LD starts with a WebSite node: "@id": "https://hawksley.dev/#website", name "Ethan Hawksley", description of the blog, language "en-GB" and links to an ImageObject. On subpages you can slim that down to just type, id, url and name. A WebPage node covers page-specific details, including breadcrumb and isPartOf linking back to the WebSite node. For blog posts you’d swap WebPage for BlogPosting and add headline, author and datePublished.
Every page should also include a Person node for author identity. Hawksley’s example lists name fields, jobTitle, nationality, education, an image, and sameAs links to GitHub, LinkedIn, Lobsters and Hacker News. These details feed Google’s author metrics and help other crawlers build a knowledge graph. You can omit lesser properties, but url, name, image and sameAs are must-haves.
Questions about this article
No questions yet.