ubricHelp

Where should the Google Tag Manager noscript code go?

Rubric check: noscript block in the head with body elements (check id html_head_noscript)

Put it just after the opening <body> tag, not in the head. A <noscript> in the head may only hold link, meta and style. When it holds an img or iframe, as Tag Manager and Facebook pixel fallbacks do, readers that don't run JavaScript end the head there.

Free, no card. Your report opens with this check first.

Why it matters for SEO

Google renders pages with JavaScript on, so for Google this rarely changes anything. Other crawlers read the raw HTML. For them, every tag after that img or iframe lands in the body, which can include your canonical, robots tag or structured data.

Does this matter for ChatGPT and AI Overviews?

Many AI crawlers don't run JavaScript, so they read the page the way this problem hurts. If your canonical or description comes after the noscript block, they may miss it. Moving one block of code fixes it for all of them.

How Rubric scores it

MinorMinor checks cost a quarter to a half of a standard check when they fail.

Why this tier: For readers that don't run JavaScript, an img or iframe here ends the head early.

It is judged on every page Rubric scores.

Every Rubric score starts at 100. When this check fails, it takes up to 6 points off. Even one failing page costs at least 3 points (half of the most), and the rest comes off as the share of affected pages grows. A warning costs less than a failure.

All the minor checks share one limit: together they can take off at most 25 points, however many of them fail.

This check doesn't cap your score. It only takes off its own points.

From the engine's scoring files, scoring 2026-v2.1 (engine d5c591d).

How common it is

Found on 15 of 299 sites where Rubric could judge it (5.0%). That is 15 of 286 judged sites in Rubric's 313-site test set and 0 of 13 sites audited on Rubric between 11 Nov 2026 and 17 Nov 2026 under the current check rules (scoring 2026-11k or later). Measured 17 Nov 2026 with scoring 2026-v2.1.

5.0% of the sites Rubric could judge have this problem. Check yours.

Free, no card. Your report opens with this check first.

How accurate the check is

Lab test: passed. On test pages built with this problem, it caught 3 of 3. On clean test pages, it stayed quiet 2 of 2 times. (Engine build bbcec7c.)

Real sites: people checked 3 of its findings by hand and 0 were wrong (0%). Last checked 14 Nov 2026. That's a small sample, so treat the rate as rough.

Holdout test 5 (sites the check had never seen): 0 of 14 findings judged wrong.

Lab as of 16 Nov 2026; judged findings as of 15 Nov 2026.

How to fix it

WordPress

  1. View the page source and find the <noscript> inside <head>.
  2. If a Tag Manager or pixel plugin adds it, look in its settings for a placement option and choose the body (this needs a theme that supports wp_body_open, as most current themes do).
  3. If you pasted the code yourself with a header-and-footer plugin, move the noscript part to the Body box.

Shopify

  1. Shopify's own pixels and customer events don't add a noscript block, so this usually comes from code pasted into the theme.
  2. Go to Online Store > Themes > Edit code, open theme.liquid and move the <noscript> block to just after <body>.
  3. Keep the <script> part in the head.

Webflow

  1. Go to Site settings > Custom code.
  2. Keep the Tag Manager <script> in Head code and move the <noscript> part to Footer code, which sits inside the body.
  3. Save and publish.

Custom code

Google Tag Manager's own instructions put the fallback right after the body opens:

html
<body>
<noscript><iframe src="https://www.googletagmanager.com/ns.html?id=GTM-XXXX"
height="0" width="0" style="display:none;visibility:hidden"></iframe></noscript>

More html validity checks · The full AI SEO glossary

Free, no card. Your report opens with this check first.