A structured lesson workspace with readable content, hands-on examples, and a clean path to completion.
When this goes wrong, the browser usually keeps rendering. That is what makes the bug easy to miss: recovery can hide a broken source document. In this lesson, the focus is robots, canonical URLs, Open Graph, and social preview metadata. That matters because HTML is interpreted by a parser and then exposed to browser features such as navigation, accessibility tooling, form controls, media handling, and script APIs. A correct-looking screenshot can still hide a poor document model.
Start with the smallest meaningful example. The working snippet demonstrates the core syntax, but the important part is what each piece contributes: the element supplies semantics or behavior, attributes refine that meaning, and surrounding structure gives the browser context. Don't add markup just because a framework or copied example happens to include it.
<link rel="canonical" href="https://example.org/docs"><meta property="og:title" content="Docs">
Checkpoint: you can now connect the markup for metadata for search engines and social sharing to a browser behavior and a concrete debugging step.
Now put the same idea under pressure. A realistic failure is: Separate crawler directives from social metadata and make canonicalization consistent. The browser may recover, ignore an invalid combination, or leave the user with a control that appears visually fine but behaves differently than expected. That is why source inspection and keyboard testing belong in the workflow.
<meta charset="utf-8"><meta name="viewport" content="width=device-width, initial-scale=1">
Don't confuse browser-side convenience with a security boundary. The markup in metadata for search engines and social sharing should improve behavior, but authoritative validation and policy belong at the trust boundary that processes the request.
You can now explain the browser behavior behind robots, canonical URLs, Open Graph, and social preview metadata, build the markup deliberately, and diagnose the most common failure mode instead of guessing.
Implementation note: Separate crawler directives from social metadata and make canonicalization consistent. Keep the browser behavior observable while you work.
Warning: invalid or overly permissive markup may still render. Rendering is not proof that the document model is correct.
Finish the lesson once you have worked through the material. This awards ★ 20 XP.