Crawl / sitemap / robots remediation — high-level pointers

ariados’s audit tells you what is wrong with a site’s crawl setup — which sitemaps are missing or oversized, which URLs robots.txt blocks, which point off-host or over http://. The detailed, current fix procedures — exact CMS/plugin steps, robots.txt syntax, sitemap regeneration — live in the team wiki (set OUTLINE + OUTLINE_API_URL and the report links them directly). This file is the minimal high-level fallback for when the wiki isn’t configured: direction only, deliberately not step-by-step, so there’s no detailed content to drift out of sync with the wiki.

• robots.txt blocking listed URLs — a Disallow rule is hiding URLs the sitemap declares. Narrow or remove the rule so crawlers can reach what you’re advertising (Disallow: / blocks the whole site).
• Missing / oversized sitemaps — no sitemap found, or a file over the 50,000-URL / 50 MB spec limit. Generate one (or split it) and declare it in robots.txt via a Sitemap: line.
• Cross-host / insecure URLs — the sitemap lists URLs on another host or over http://. Point every entry at the canonical host over https://.
• Orphan / declared-but-broken sitemaps — a sitemap declared in robots.txt that 404s, or children an index points to that fail. Fix the reference or regenerate the index.

Full playbook → the team wiki’s crawl & indexing reference (per-signal procedures, CMS specifics, agent-safety notes). Configure the wiki to have ariados surface the live versions in its report.