Summary

Completed a live intake form parity audit for https://aguiarinjurylawyers.com after concerns that web forms were not consistently feeding Litify, email notifications, and tracking.

What Was Accomplished

Key Finding

The initial static crawl showed many failures, but the static crawl does not execute JavaScript. The browser-executed crawl is the better source of truth for rendered behavior. The site is largely wired correctly at runtime. The remaining issue is normalization: four forms should be brought into the same explicit class and selector contract as the homepage form so future audits and future scripts do not treat them as special cases.

Forms Needing Follow-up

URL Form Current class Runtime endpoint Issue
https://aguiarinjurylawyers.com/lexington-personal-injury-lawyer/ sa-lex-inline-form sa-inline-form https://aguiarinjurylawyers.com/wp-json/sal/v1/contact-intake Missing approved homepage/custom intake class
https://aguiarinjurylawyers.com/locations/ cta-banner-form sa-cta-banner-form https://aguiarinjurylawyers.com/wp-json/sal/v1/contact-intake Missing approved homepage/custom intake class
https://aguiarinjurylawyers.com/locations/lexington/ sa-lex-inline-form sa-inline-form https://aguiarinjurylawyers.com/wp-json/sal/v1/contact-intake Missing approved homepage/custom intake class
https://aguiarinjurylawyers.com/lesiones-personales/ no id sa-lp-form https://aguiarinjurylawyers.com/wp-json/sal/v1/contact-intake Missing approved homepage/custom intake class

Suggested Next Steps

A good next pass would back up Kadence Element 62671, Attribution Capture - Google Ads GCLID and UTMs, then update its FORM_SELECTOR to explicitly include the homepage form class and the known variant form classes: sa-homepage-custom-form, sa-custom-contact-intake-form, sa-inline-form, sa-cta-banner-form, sa-lp-form, form[data-rest-endpoint*="/sal/v1/contact-intake"], and form#contact-form.

A second cleanup can add sa-custom-contact-intake-form or sa-homepage-custom-form to the four source forms through the normal publishing path, then rerun the Chrome audit and no-send probe.

Reason For Ending

Audit completed. The remaining action is a public WordPress form-contract cleanup, so it is being held as a clear follow-up rather than mixed into the diagnostic session.