Can Google read a robots meta tag outside the HTML head?

Definition: Yes. Google Search documents that it respects robots meta tags in the body section of an HTML document, even though its example places the tag in the <head>. The page still has to be accessible to crawlers for the setting to be read and followed.

Key facts

• Google says it does not enforce placement of meta robots in the HTML head and respects robots meta tags in the body section of an HTML document. Google's robots metadata reference is the source for this behavior.
• Google describes a robots meta tag as a page-specific control for how an individual HTML page is indexed and served in Google Search results.
• Google says that robots meta tags and X-Robots-Tag HTTP headers are discovered when a URL is crawled.
• Google documents that JavaScript can add a robots meta tag to a page or change its content, but says that a noindex tag can cause Google to skip rendering and JavaScript execution.
• The HTML Standard's meta element definition classifies meta as metadata content and gives a name attribute a context where metadata content is expected.

What exactly does Google document?

Google's robots metadata reference gives the normal implementation pattern: put a robots meta tag in the <head> and use attributes such as name="robots" and content="noindex". The same reference then states that Google Search does not enforce that placement and respects the tag in the body section of an HTML document.

The documented answer is therefore yes for Google Search. It is a statement about Google's processing of an HTML page, rather than a general rule for every crawler. Google also says that these settings can be read and followed only when crawlers are allowed to access the pages that contain them. A robots.txt rule that prevents crawling can therefore prevent Google from finding the body tag.

What does the HTML standard add?

The HTML Standard defines the meta element as metadata that cannot be expressed with elements such as title, base, link, style, or script. It says that a name attribute represents document-level metadata and that content supplies the value when name is used.

The standard describes where a meta element with a name attribute is allowed as “where metadata content is expected.” Google's documentation recommends the head as the usual location, then explicitly documents body processing for robots metadata. This separates HTML placement guidance from Google's crawler behavior.

<!DOCTYPE html>
<html>
  <head>
    <title>Example page</title>
  </head>
  <body>
    <meta name="robots" content="noindex">
    <p>Page content.</p>
  </body>
</html>

Does JavaScript change the answer?

Google's JavaScript SEO guidance says that JavaScript can add a robots meta tag or change its content. Its example creates a meta element, sets name to robots, sets content to noindex, and appends the element to document.head.

That guidance also records a processing limit: when Google encounters noindex, it may skip rendering and JavaScript execution. Google says changing or removing that tag with JavaScript may therefore fail as expected, and recommends that a page intended for indexing not contain noindex in its original page code. A body tag in the delivered HTML is covered by Google's explicit body-processing note; a tag added later by JavaScript depends on the rendering behavior described in the JavaScript guidance.

What should you check on a website?

For a static directive, inspect the HTML response and locate the meta element, its name value, and its content value. Confirm that the URL is crawlable, because Google says the indexing and serving rules are ignored when the URL is disallowed by robots.txt.

If a script changes the directive, inspect the rendered HTML as well as the original response. Google's JavaScript guidance says that Google can only see content visible in the rendered HTML and that noindex may cause rendering and JavaScript execution to be skipped. The page's body placement can be processed by Google Search, but the source and rendering path still determine when the directive is available.

Related terms

• noindex
• X-Robots-Tag
• Which directive wins when robots meta tags conflict?
• How can a robots meta tag target Googlebot separately?

FAQ

Should you put the tag in the body?

Google documents that it respects the tag in the body, but its reference presents the head as the standard implementation location. Use the head when you control the HTML structure, and treat body processing as Google's documented tolerance for an existing page.

Does a body tag override robots.txt?

No. Google says that it must crawl a URL to find indexing or serving rules. If robots.txt disallows the page, the rules in the page are not found and are ignored.

Can JavaScript add a body robots tag?

Google documents JavaScript changes to robots metadata and separately warns that noindex can cause rendering and JavaScript execution to be skipped. The documentation does not specify a separate rule for a script that inserts the tag into the body.

Sources

1. Google Search Central, "Robots meta tag, data-nosnippet, and X-Robots-Tag specifications", 24 March 2026
2. Google Search Central, "Understand JavaScript SEO Basics", 4 March 2026
3. WHATWG, "HTML Standard", 19 October 2026

---

Check how a page reads to answer engines. Open the GEO score analyzer