Batch 5 hygiene note, 2026-05-17: Active source of truth for the Amazon legacy page audit. This remains Needs Follow-up because the malformed nested 404 and any legacy consolidation decisions require GSC/backlink evidence or a confirmed redirect write path. Indexed in the SAIL Knowledge Base Hygiene Hub - 2026-05-12.
Approved follow-up 4A was executed as a separate Amazon duplicate/legacy audit.
https://aguiarinjurylawyers.com/practice-areas/delivery-vehicle-accidents/amazon-delivery-accidents/.13026: seven stale internal links were updated from old /amazon-delivery-vehicle-accidents/{spoke}/ paths to current /practice-areas/delivery-vehicle-accidents/{spoke}/ paths.The malformed nested URL still returns 404: https://aguiarinjurylawyers.com/practice-areas/delivery-vehicle-accidents/practice-areas/amazon-delivery-vehicle-accident-lawyers/.
It was not found as a live internal link, but a narrow 301 to the current Amazon spoke is reasonable after confirming the correct RankMath/WP-CLI arbitrary source-path write path. The available RankMath REST route exposed in this run is object-level only.
C:\Users\SAguiar\Documents\Codex\seo-amazon-legacy-audit-2026-05-15_084548\AMAZON_LEGACY_AUDIT.mdC:\Users\SAguiar\Documents\Codex\seo-amazon-legacy-audit-2026-05-15_084548\ROLLBACK_AND_RESTORE.mdC:\Users\SAguiar\Documents\Codex\seo-amazon-legacy-audit-2026-05-15_084548\amazon_legacy_audit.jsonC:\Users\SAguiar\Documents\Codex\seo-amazon-legacy-audit-2026-05-15_084548\legacy_internal_link_status.json