memory/seo-geo/tune/technical-seo-checker/

• Reads: target URLs or domain, PageSpeed/CrUX reports, robots.txt, sitemap, and reported symptoms.
• Writes: a user-facing audit or optimization plan plus a reusable summary that can be stored under

  memory/seo-geo/tune/technical-seo-checker/

  .
• Promotes: blocking defects, repeated weaknesses, fix priorities, and pending decisions to

  memory/open-loops.md

  .
• Done when: each audited area carries evidence, issues, fixes, and a score; blocking indexation/revenue risks are flagged P0; a scorecard, priority queue, and handoff summary are produced.
• Primary next skill: use the

  Next Best Skill

  below when the repair path is clear.

Emit the standard shape from skill-contract.md §Handoff Summary Format.

1. Audit Crawlability — review robots.txt, sitemap discovery, crawl waste, redirect chains, and orphan patterns.
2. Audit Indexability — verify coverage, blockers (

   noindex

   , X-Robots, robots.txt, canonicals), duplicate signals, and 4xx/5xx failures.
3. Audit Site Speed & Core Web Vitals — evaluate LCP/INP/CLS plus supporting metrics, resource weight, and highest-impact fixes.
4. Audit Mobile-Friendliness — check viewport setup, layout fit, tap targets, and mobile-first parity.
5. Audit Security & HTTPS — confirm SSL health, HTTPS enforcement, mixed content, HSTS, and security headers.
6. Audit URL Structure — inspect URL patterns, parameters, case consistency, and redirect hygiene.
7. Audit Structured Data — validate schema, map missing opportunities, and note CORE-EEAT

   O05

   implications. ⚠ Raw fetches miss client-side-injected JSON-LD (Yoast/RankMath/AIOSEO render via JS); verify with the rendered DOM (

   document.querySelectorAll('script[type="application/ld+json"]')

   ) or Rich Results Test before reporting "no schema".
8. Audit International SEO (if applicable) — verify hreflang, return tags, locale targeting, and

   x-default

   .
9. Generate Technical Audit Summary — roll findings into a scorecard, priority queue, quick wins, roadmap, and monitoring plan.

• Rendering (step 1 & 7) — AI crawlers don't execute JS; critical content and JSON-LD must be in the initial HTML. SSR/SSG ships it server-side; pure CSR hides it until hydration, so client-injected content and schema can go unseen. Compare raw fetch vs rendered DOM.
• Core Web Vitals thresholds (step 3) — pass: LCP <2.5s, INP <200ms, CLS <0.1.
• Crawl-budget checklist (step 1) — flag faceted-nav explosion (filter/sort combinations), parameterized URLs (tracking/session params creating duplicates), and session-ID URLs. Each multiplies crawlable URLs and wastes budget on near-duplicates.

• Auditing AI-crawler handling and the desired stance is unstated — ask: (1) default-open (allow all), (2) default-closed (block all), or (3) split (allow retrieval, block training). The robots.txt template depends on the answer; see LLM Crawler Handling.
• A migration is requested without both the old and new domain/stack — ask for the missing endpoint before producing a redirect map.

• Scope is a single issue (e.g., "just check Core Web Vitals") — run only that area; do not force a full 9-step audit.
• 5+ URLs share a pattern — switch to bulk mode (sample per pattern, report pattern-level findings); do not ask per URL.
• Missing optional tool data (CrUX field data, log files) — mark the affected checks N/A and proceed on available evidence.

• robots.txt Reference — Syntax guide, templates, common configurations
• HTTP Status Codes — SEO impact of each status code, redirect best practices
• Technical Audit Templates — Compact starter blocks for all 9 audit steps and the final scorecard
• Technical Audit Example & Checklist — Compact worked example shape and technical SEO checklist
• Bulk Audit Playbook — Multi-URL technical audit workflow
• Ecommerce Platform Patterns — Shopify, WooCommerce, headless, BigCommerce, Magento checks
• LLM Crawler Handling — GPTBot, ClaudeBot, Gemini, Perplexity robots patterns
• Pre-Migration Playbook — Migration audit stages and launch checks