# A “link” element must not appear as a descendant of a “body” element unless the “link” element has an “itemprop” attribute or has a “rel” attribute whose value contains “dns-prefetch”, “modulepreload”, “pingback”, “preconnect”, “prefetch”, “preload”, “prerender”, or “stylesheet”. > Canonical HTML version: https://rocketvalidator.com/html-validation/a-link-element-must-not-appear-as-a-descendant-of-a-body-element-unless-the-link-element-has-an-itemprop-attribute-or-has-a-rel-attribute-whose-value-contains-dns-prefetch-modulepreload-pingback-preconnect-prefetch-preload-prerender-or-style > Attribution: Rocket Validator (https://rocketvalidator.com) > License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) The HTML specification restricts where `` elements can appear based on their purpose. Links that load resources needed for rendering (like stylesheets and preloaded assets) or carry microdata (`itemprop`) are allowed in `` because they have a direct relationship to the content around them. Other types of `` elements—canonical URLs, icons, alternate versions—are document-level metadata and belong exclusively in ``. This matters for several reasons. Browsers may ignore or inconsistently handle `` elements placed in unexpected locations, leading to issues like missing canonical signals for search engines or broken favicon references. Standards compliance also ensures your HTML is forward-compatible and behaves predictably across all browsers. ## Common causes ### Direct placement in `` The most straightforward cause is placing a metadata `` directly inside ``, often due to a CMS, template system, or plugin injecting it in the wrong location. ### Implicit `` creation by the parser A subtler cause occurs when an element that's only valid in `` appears inside ``. When the HTML parser encounters such an element (like ``, `

`, or `

`), it implicitly closes the `` and opens the ``. Any `` elements that follow are then treated as descendants of ``, even though they appear to be inside `` in your source code. For example, an `` tag in the `` causes the parser to switch to body context, so the subsequent `` is interpreted as being inside `` and triggers this error. ## How to fix it 1. **Move disallowed `` elements to ``**: If a `` with `rel="canonical"`, `rel="icon"`, `rel="alternate"`, or similar values is in ``, move it into ``. 2. **Check for body-only elements in ``**: Look for elements like ``, `

`, `