Index-rule conflict

Seen in a real crawl

From a crawl of Fernhollow Outdoor, a test site built for this site’s demo.

Where you’ll see it

The id is stable, and every surface uses it, so it’s the thing to search for or hand to an agent.

Terminal

When it is one of the five findings under Fix first, raptor crawl prints the id under it.

Check: directives.conflicting_directives

crawl.json and the CSV

The crawl JSON names the finding by this id, and so do the CSV and raptor_query.

"check_id": "directives.conflicting_directives"

The HTML report

This link opens the finding in the report, and each finding shows its id.

crawl.html#finding=directives.conflicting_directives

MCP

raptor_findings with this check_id returns the finding in full, with a fix brief ready to paste into a task. If it didn’t fire, it says why.

raptor_findings {
  "job_id": "...",
  "check_id": "directives.conflicting_directives"
}

›The brief it returned on Fernhollow Outdoor

## 1 page both allows and blocks listing in search results

`directives.conflicting_directives` · Fix now · 1 page

**What we found:** These pages give robots rules (instructions for search engines) in both a meta tag and an X-Robots-Tag header, and together the two say both index (list this page) and noindex (do not list it).

**Why it matters:** Search engines obey the stricter rule, so these pages are likely to be left out of search results.

**How to fix:** Make the robots meta tag in the page template and the X-Robots-Tag header in the server settings agree. Remove noindex from both on any page you want in search results.

**Example:** "Waterproof Jackets and Trousers | Fernhollow" http://127.0.0.1:8006/waterproofs/
> Meta robots: [index, follow], X-Robots-Tag: noindex

**Affected pages (1):**
- http://127.0.0.1:8006/waterproofs/ — Meta robots: [index, follow], X-Robots-Tag: noindex