Skip to content
regensbot
DEV-SRV-06Avoid6 of 11 in SRV

Do not put Content-Signal or other non-standard lines between user-agent lines

Level
Avoid

Must not: the site is not ready to launch while it does this.

Documentation

Documented

At least one cited Google document states or supports it.

Covered

Automatic

Decided from one URL.

Why it matters

Googlebot ignores an unknown line placed between two user-agent lines and merges both user agents into one group, so the rules that follow apply to both. A Google slide at Search Central Live showed Bing closing the group at that line instead, so the same file blocks one crawler and not the other. Google's robots.txt talk called this the real trouble spot of the format: while RFC 9309 was being written, opinions on whether the first crawler should inherit the rules that follow split roughly 50-50. Managed robots.txt files from some CDNs add such lines, and said at Search Central Live, CDNs sometimes update a site's robots.txt without the owner's knowledge.

How to meet it

Keep each group as an uninterrupted run of user-agent lines followed by its allow and disallow rules. If a CDN or plug-in adds Content-Signal or other non-standard lines, make sure they sit after a group's rules, never between user-agent lines, and review the generated file after every CDN setting change. Check the version history in Search Console's robots.txt report for changes nobody on the team made.

How to test it

Fetch the live file (curl https://www.example.com/robots.txt) and check that every run of user-agent lines is uninterrupted; test it in Bing Webmaster Tools' robots.txt tester and with Google's open-source robots.txt parser (github.com/google/robotstxt). The robots.txt report's latest fetched version matches the file the team deployed.

How Regensbot covers it

AutomaticNeedsOne URL

Decided from one URL.

An audit reads the response, the headers, the HTML, robots.txt, the sitemaps and the structured data, and the finding shows the evidence it saw.

How verdicts workWhat you connect

Sources

Google documents02

  1. 01How Google interprets the robots.txt specificationGoogle (opens in a new tab)
  2. 02robots.txt reportGoogle Search Console Help (opens in a new tab)

Claims in the knowledge base06

  1. D1-C087ConfirmedHow Google interprets robots.txtShown on screen
  2. D1-C123UndocumentedHow Google interprets robots.txtShown on screen
  3. D1-C088n/aHow Google interprets robots.txtThe author's interpretation
  4. D1-C526UndocumentedHow Google interprets robots.txtSaid on stage
  5. D1-C529UndocumentedHow Google interprets robots.txtSaid on stage
  6. D1-C528ConfirmedHow Google interprets robots.txtSaid on stage

Claim IDs refer to the Search Central Live 2026 knowledge base. The knowledge base (opens in a new tab)

Confirmed
Google's documentation states the same thing.
Undocumented
Said or shown at the event, not in the documentation.
n/a
Nothing to verify: a quotation, framing, opinion or analysis.

Audit

Check it on your site.

One audit checks a URL against all 138 requirements and returns one finding for each, with its source. One URL decides 66; for each of the others, the finding says which source to connect.