Confirmed the May 8, 2026 Ahrefs Site Audit alert from Gmail: project 9708957, issue 3XX page receives organic traffic: 3 URLs, crawl timestamp 2026-05-08T18:35:58Z. Ahrefs detail API could not return the exact issue rows because the account had 0 API units left for the 50-unit Site Audit detail endpoint, so the session used the alert metadata, Screaming Frog 5.8.26 response_codes_all.csv, live GSC page clicks/impressions for 2026-02-08 through 2026-05-08, and live HTTP checks on 2026-05-10.
Created the working folder traffic_3xx_cleanup_2026-05-10 inside /Users/samaguiar/Documents/Projects/Screaming Frog 5.8.26 with three deliverables:
traffic_3xx_cleanup_plan.md: short recommended change set and evidence summary.traffic_facing_3xx_ranked.csv: 135 GSC-matched redirect candidates from the crawl, with live status and impact ranking.concrete_source_replacements.csv: 64 prepared WordPress source-record replacements, marked Priority A or B.The shortest recommended fix set is three old URLs that are still live 301s, have real GSC impact, and are non-canonical slug/content redirects rather than harmless trailing-slash redirects:
https://aguiarinjurylawyers.com/first-ups-wrongful-death-suits-filed -> https://aguiarinjurylawyers.com/ups-wrongful-death-suits-filed/: 31 GSC clicks, 7,544 impressions, 2 source records located.https://aguiarinjurylawyers.com/concussion-symptoms-from-car-accidents-understanding-long-term-medical-risks-and-legal-implications/ -> https://aguiarinjurylawyers.com/concussion-symptoms-car-accidents/: 17 GSC clicks, 7,090 impressions, 3 source records located.https://aguiarinjurylawyers.com/about-us/bigger-share-guarantee/ -> https://aguiarinjurylawyers.com/about-us/bigger-share-guarantee-kentucky/: 1 GSC click, 2,432 impressions, 89 crawl inlinks, 37 source records located.High-click no-trailing-slash URLs like /insurance-bad-faith-mistreatment-in-kentucky, /car-accident-injuries/injury-mechanisms, and /mcs90-coverage are one-hop WordPress canonical trailing-slash redirects. They should not be changed to 200 no-slash URLs because that would conflict with the site's canonical URL policy. Best handling is to ensure internal links use the final trailing-slash URLs and request recrawl/indexing of the final URLs.
Two high-impact crawl rows were already cleared live by the time of this session: /about-us/meet-our-team/sam-aguiar/ and /diminished-value-claim-kentucky/ now return 200.
Sam flagged that https://aguiarinjurylawyers.com/about-us/bigger-share-guarantee-kentucky/ is not a desired URL. Live verification confirmed that URL returns 200, while /about-us/bigger-share-guarantee/ returns 301 to the -kentucky slug. Do not publish any prepared replacements pointing internal links to /about-us/bigger-share-guarantee-kentucky/. Treat the likely next fix as restoring the canonical Bigger Share Guarantee slug to /about-us/bigger-share-guarantee/, after revision capture, redirect export, live HTTP verification, and cache purge.
No live WordPress content was published. The prepared replacements should go through the WordPress content deployment/autosave QA path with revision capture before publishing. No redirect rules were changed because the existing 301s resolve to 200 destinations and should remain as fallbacks.
Use concrete_source_replacements.csv as the batch input for a staged WordPress link-replacement pass. Start with Priority A only. Capture current revisions/autosaves, replace the old URLs with the final URLs, verify affected pages, purge Cloudways cache if needed, then request recrawl/indexing for the three final destination URLs. Priority B can be handled later if Sam wants to clear low-volume remnants too.