Session: AI Visibility + AI-SEO Audit (2026-05-31)

Importance: High. Status: audit COMPLETE; recommended fixes PENDING Sam approval.

What was done

• Ran ai-visibility-auditor + ai-seo end to end. 18 queries (12 core + 6 extended) across Perplexity Sonar (live + citations), Gemini 2.5 Flash with Google Search grounding (live + grounded sources), and GPT-4o (memory baseline). 54 of 54 calls succeeded.
• On-site AI-SEO audit of aguiarinjurylawyers.com: robots.txt AI-bot access, llms.txt, sitemap inventory (581 URLs), schema and structure on 5 key pages.
• Delivered a combined report plus raw JSON to the session outputs folder: ai-visibility-audit-2026-05-31.md and data/ai-audit-2026-05-31.json. The auditor skill's intended save path Marketing_project/ai-visibility/ did not exist in this container, so outputs were used instead.

Key findings

• The firm is the #2 player in the market by AI presence: named in 13 of 36 live answers and the #2 most-cited domain (17 source appearances), behind Hughes & Coleman (15 named, 19 cited).
• Scores: Gemini grounded 1.28/3, Perplexity 0.89/3, GPT-4o 0.11/3 (training memory barely knows the firm, which is normal and confirms live citation is the battleground).
• By query type (live engines): Reputation 3.00, Transactional 1.50, Extended 1.00, Informational 0.00 (a complete shutout).
• Accuracy is clean. Engines describe the firm correctly: 4.9 from 1,000+ reviews, A+ BBB, award-winning trial lawyers. Nothing to correct.
• Technical foundation is already strong: all AI crawlers explicitly allowed, llms.txt present, rich schema (Attorney, LegalService, LocalBusiness, AggregateRating, FAQPage). Not the bottleneck.
• Root cause: informational content is thin, mis-structured, or missing. The statute-of-limitations resource exists yet scores 0/3 (an extractability problem, not absence). "How much is my case worth" and "should I hire a lawyer" pages do not exist. Only 18 informational URLs versus 91 practice-area and 76 location URLs. Truck practice page has an editorial H1 and is thin; Lexington page is thin at ~1,100 words.

Why the session is at this point

The audit and report are complete. The fixes themselves (new informational pages, restructures, live deploy) are content-pipeline work that should run through brand-voice-enforcer, pre-publish-qa, and wp-content-deployer, so they were teed up for a go decision rather than shipped inside the audit run.

Recommended next actions (leverage order)

1. Restructure /resources/kentucky-statute-of-limitations/ with a 40 to 60 word direct-answer lead block and FAQPage schema. The content already exists, so this can flip a 0 to a 3 quickly.
2. Build "How much is my car accident case worth in Kentucky" and "Do I need a lawyer after a Kentucky car accident" pages in extractable Q&A format.
3. Rework the truck practice page: transactional H1, lead answer block, expand toward the ~2,600 word depth of the car-accident page.
4. Deepen the Lexington location page toward Louisville parity.