{
  "acceptance": "The test record should show both the chosen group and the decisive path rule for every URL. Reordering groups alone should not be accepted as evidence that the intended policy changed.",
  "automated_checks": true,
  "batch_id": "analytics-editorial-20261104-v1",
  "built_at": "2026-11-04T11:50:28.566595+00:00",
  "claims": [
    {
      "id": "c1",
      "section": "Explanation and verification steps",
      "source_numbers": [
        1
      ],
      "statement": "Google uses the most specific matching user-agent group; group order is irrelevant."
    },
    {
      "id": "c2",
      "section": "Explanation and verification steps",
      "source_numbers": [
        1
      ],
      "statement": "Google merges multiple groups relevant to the same specific user agent."
    },
    {
      "id": "c3",
      "section": "Explanation and verification steps",
      "source_numbers": [
        1
      ],
      "statement": "Google resolves path rules by specificity and uses the less restrictive rule in conflicts."
    },
    {
      "id": "c4",
      "section": "Explanation and verification steps",
      "source_numbers": [
        1
      ],
      "statement": "Google does not merge global and user-agent-specific robots groups."
    }
  ],
  "description": "Test user-agent group selection separately from URL-path matching when robots behavior seems inconsistent.",
  "diagram": [
    "Select user-agent group",
    "List matching URL rules",
    "Resolve path specificity",
    "Verify deployed bytes"
  ],
  "draft_hash": "0c1f16a59533c936e3e01fe2acfd9d87a6755d9c2db4754c59ae078119e84be4",
  "evidence": {
    "observed_at": "2026-11-02T11:46:07.171405+00:00",
    "period": {
      "end": "2026-11-02T11:46:07.171405+00:00",
      "start": "2026-11-02T11:46:07.171405+00:00",
      "timezone": "UTC"
    },
    "rows": [],
    "scope": "Official documentation; no customer or own-site traffic measurement"
  },
  "evidence_kind": "documentation",
  "figure_caption": "Original explanatory diagram based on the dated sources below. Any example values are hypothetical; this is not a screenshot, customer measurement or AI platform result.",
  "figure_kind": "sequence",
  "figure_notes": [
    "Google selects the most specific matching group.",
    "Within that group, inspect the applicable path patterns.",
    "Use specificity and the documented conflict rule.",
    "A local edit is not evidence of the public file contents."
  ],
  "figure_title": "Google robots rules: diagnose group and path precedence",
  "group": "Crawl access and indexing",
  "human_review_claim": false,
  "intent": "robots-specific-rule-precedence",
  "interpretation": "There are two decisions to inspect: the applicable user-agent group and the applicable path rule. Google selects the most specific matching user-agent group; moving a global group above another group is not a reliable repair. Within path matching, the most specific path length matters, and Google uses the less restrictive rule when matching rules conflict. Keep these stages separate in a test table.",
  "keyword_volume": "Not obtained",
  "limits": "These are Google’s documented interpretation rules. They do not establish how an unidentified crawler behaves, and robots.txt is not a substitute for authorization.",
  "paid_api_calls": 0,
  "path": "/ai-analytics/guides/robots-specific-rule-precedence/",
  "policy": "session-evidence-editorial-v1",
  "preparation_mode": "session_editorial_batch",
  "problem": "A global robots rule seems to conflict with a crawler-specific group.",
  "product": "/ai-analytics",
  "published_at": "2026-11-05T09:30:10.674534+00:00",
  "reader": "Site owners and analysts investigating a global robots rule seems to conflict with a crawler-specific group.",
  "related": [
    "robots-directives-vs-access-enforcement"
  ],
  "related_links": [
    {
      "path": "/ai-analytics/guides/robots-directives-vs-access-enforcement/",
      "title": "Separate robots directives from observed access enforcement"
    }
  ],
  "research_document_ids": [
    "4af1244f4e1ec7865296dc21f4817812"
  ],
  "slug": "robots-specific-rule-precedence",
  "source_signature": "46ec1db054e5a8b18deb4c2b31fcdb8545c2c4a5c37dadec40c1c6c4ef8d0818",
  "sources": [
    {
      "hash": "3db2f2c94597a0afbfde20b320a65102dac3c30f5fa3b4562a373a8e6e00fe18",
      "locator": "Examples / b100; Order of precedence for rules / b132; Order of precedence for user agents / b89; Order of precedence for user agents / b90",
      "observed_at": "2026-11-02T11:46:07.171405+00:00",
      "title": "How Google interprets the robots.txt specification",
      "url": "https://developers.google.com/crawling/docs/robots-txt/robots-txt-spec"
    }
  ],
  "sources_required": [],
  "steps": [
    "Save the exact public robots.txt bytes, retrieval time and host. Do not analyze a local editor copy as if it were the deployed response.",
    "For each crawler token being tested, identify the matching group and record why it is more specific. Check relevant repeated groups rather than relying on their visual order.",
    "For each representative URL, list the matching path rules and their lengths. Include an allowed path, a blocked path and a conflict case.",
    "After editing, fetch the deployed file again and repeat the same table. Keep private endpoints behind authentication independently of robots behavior."
  ],
  "title": "Google robots rules: diagnose group and path precedence",
  "worked_example": "Hypothetical file: a global group blocks /private/, while a Googlebot-specific group contains only a rule for /draft/. Do not assume the global block is inherited into the selected specific group. This is a configuration example, not a recommendation to expose /private/; genuinely private pages still need access control."
}