A disallowed element inside the head (an image, an iframe, a div) makes browsers and Google treat the head as finished at that point: everything after it, such as the canonical or hreflang, may be ignored. It is an invisible mistake that silently disables important tags.

AD2SPIDER checks the structure of every document: a single head and a single body, no invalid elements in the head and the head at the top, HTML and resources that are not too heavy, and the estimated carbon footprint of each page.

HTML validation warnings

Real problems worth fixing.

Invalid HTML elements in <head>

Why it matters
An element that cannot go in <head> (img, div, iframe…) closes it early: Google stops reading what follows, such as canonical, hreflang or robots metas.
How to fix it
Move those elements into <body> or place them after the important metas and links.

Priority: highDocumented by GoogleDocumentation ↗

<head> not first in <html> element

Why it matters
There are elements before <head>: the browser may open <body> early and what is in <head> may stop counting as such.
How to fix it
Make <head> the first element inside <html>.

Priority: lowDocumented by GoogleDocumentation ↗

Missing <head> tag

Why it matters
The document has no explicit <head>: the browser creates one, but any unexpected element may leave the metas outside it.
How to fix it
Add a <head> with the title, metas and links.

Priority: lowTechnical standardDocumentation ↗

Multiple <head> tags

Why it matters
Only the first <head> counts: what is in the others is treated as <body> content and Google may ignore it.
How to fix it
Keep a single <head> (extra ones usually come from templates or plugins inserting their own).

Priority: mediumTechnical standardDocumentation ↗

Missing <body> tag

Why it matters
The document has no explicit <body>: the browser creates one, but the structure depends on how it gets repaired.
How to fix it
Add a <body> wrapping the content.

Priority: lowTechnical standardDocumentation ↗

Multiple <body> tags

Why it matters
There is more than one <body>: the browser merges them and the result may not be what was intended.
How to fix it
Keep a single <body>.

Priority: mediumTechnical standardDocumentation ↗

HTML document over 2MB

Why it matters
Google only processes the first 2MB of HTML: content and links after that may not be indexed.
How to fix it
Shrink the HTML: move inline CSS/JS to files, paginate long listings and drop unnecessary embedded data.

Priority: mediumDocumented by GoogleDocumentation ↗

Resource over 2MB

Why it matters
An internal resource (CSS, JS, PDF…) weighs over 2MB: Google only processes the first 2MB of each resource and it also slows the page down.
How to fix it
Shrink the resource: minify, split the code or compress the document.

Priority: lowDocumented by GoogleDocumentation ↗

HTML validation opportunities

Improvements with impact, usually based on configurable thresholds.

High carbon rating

Why it matters
The page HTML alone exceeds 0.359 g of CO2 per visit (rating F in the Sustainable Web Design v4 model).
How to fix it
Reduce the HTML weight: less inline code, less embedded data and paginated listings.

Priority: lowBest practiceDocumentation ↗