seo-technicallisted

# Technical SEO Audit and fix the layer beneath the content: how search engines crawl, render, index, and trust a site. Stack-agnostic. --- ## When to use - Site-wide audit before or after a migration - Investigating indexing or ranking drops - Setting up SEO foundations on a new site - Auditing Core Web Vitals or page experience signals - Fixing crawl waste, redirect chains, or canonical issues - Setting up multilingual or multi-regional sites ## When NOT to use - Single-page on-page optimization (use `seo-onpage`) - Keyword strategy or content planning (use `seo-keyword`) - Competitor backlink or SERP analysis (use `seo-competitor`) - Pure performance optimization without SEO context (use `performance-optimization`) --- ## Required inputs - The site URL or staging URL - Access to (at minimum) view the rendered HTML, robots.txt, and sitemap - Ideally: search console access, server logs, and a crawler If the site is large (10K+ URLs), confirm whether the audit is a full crawl or a sample. --- ## The framework: 6 layers Technical SEO has six layers, stacked. A failure in a lower layer breaks everything above it. ### 1. Crawlability Can search engines access the URLs? - robots.txt does not block important paths - No accidental `noindex` on indexable pages - No accidental `disallow` patterns blocking CSS or JS (rendering breaks) - Sitemap is present, returns 200, and lists canonical URLs only - Sitemap is referenced in robots.txt - No infinite spaces (faceted nav