ShippedChange check — first crawl stores a baseline

Became CONFLICTING

This page isolates the “Became CONFLICTING” alert from the Indexability state check (indexability.state_conflicting).

What this page tests

Check Indexability state (indexability.state), alert indexability.state_conflicting.

Index signals conflict (for example mixed robots and canonical guidance). Conflicting instructions make it harder for Google to choose the right URL to index.

Why it matters

Index signals conflict (for example mixed robots and canonical guidance). Conflicting instructions make it harder for Google to choose the right URL to index.

How the fail is produced

Serves conflicting robots tokens (index and noindex) so derived state becomes CONFLICTING.

Also trips conflicting robots directives when that check has a baseline.

This page is part of the TechDash Test Site used to exercise the TechDash desktop app. Each fixture isolates a single check so you can add one path at a time and see a clear pass or fail. Search engines and users rely on stable HTTP responses, index signals, metadata, and site files. When those signals drift, organic visibility, crawl efficiency, and measurement can all suffer. Keep the homepage as the healthy control origin, then monitor the specific path you want to fail. Substantial body copy is included so thin-content and soft-404 heuristics do not fire unless that is the intended test.