Week 02 · Crawl controls
robots-outage · dirty-sitemaps · facet-explosion
Use the protected switches below to activate one issue family, load a repeatable weekly scenario, crawl the live site, diagnose the problem, and restore the clean baseline.
Presets activate a known issue bundle. Use one for a focused exercise, then restore the clean baseline.
robots-outage · dirty-sitemaps · facet-explosion
canonical-conflict · soft-404 · thin-programmatic
csr-invisibility · schema-mismatch · cwv-regression
migration-defects · data-join-mismatch · bot-errors
Each switch changes the server-side state used by the crawlable site, APIs, redirects, metadata, and sitemaps.
The marketplace is accidentally disallowed after a release.
Redirects, noindex URLs, and parameter variants leak into the sitemap.
Product canonicals point back to the marketplace category.
Empty generated pages return 200 with thin boilerplate.
Every filter combination becomes crawlable and self-canonical.
Core product copy appears only after client JavaScript runs.
Price, availability, and reviews disagree with the visible page.
Hero discovery, filtering tasks, and image sizing create measurable failures.
Mobile removes critical product discovery links.
Localized pages canonicalize to English and reciprocity breaks.
Synthetic bot traffic encounters 429 and 503 bursts.
Incomplete records publish without a quality gate.
Robots, canonicals, and sitemaps can regress without alerts.
Legacy routes contain gaps, chains, and irrelevant destinations.
URL keys differ by host, slash, encoding, and parameters.
SEO-critical fields have no accountable owner or release gate.
Company and product facts vary across site and profile surfaces.
This disables every seeded issue and changes the mode back to clean. No rebuild or Vercel redeploy is required.