Session Objective

Restore the standard site footer to the Bigger Share Guarantee page and make sure all pages have the standard footer available as site chrome.

What Was Accomplished

• Confirmed the public Bigger Share Guarantee page and sampled public pages were missing the visible SAIL standard footer because Kadence footer markup existed but was hidden, and the active WPCode custom footer snippet was not rendering publicly.
• Located the standard footer source in WPCode snippet 40125, Custom Site Footer - Four Column Layout.
• Added the standard footer markup to WPCode Global Header & Footer under the global footer field, preserving the existing CTA CSS already there.
• Added a small duplicate guard so if the old snippet begins rendering later, only one #sal-custom-footer remains in the DOM.
• Purged WP Rocket cache after saving.
• Did not insert a footer into any individual WordPress page body. The footer is now handled as global site chrome.

QA Evidence

• Public HTML checks confirmed exactly one sal-custom-footer marker on these pages: /, /about-us/bigger-share-guarantee/, /contact-us/, and /practice-areas/car-accidents/.
• Rendered browser QA on https://aguiarinjurylawyers.com/about-us/bigger-share-guarantee/ confirmed one visible footer on desktop and mobile.
• Desktop footer height: 471px. Mobile footer height: 1357px. Both were visible and contained Louisville, Lexington, Quick Links, Practice Areas, and Free Case Review footer content.
• Screenshots saved locally under /Users/samaguiar/Documents/Projects/wp-content-backups/bsg-footer-fix-2026-06-01/.

Rollback

Rollback path is the saved WPCode Global Footer backup at /Users/samaguiar/Documents/Projects/wp-content-backups/bsg-footer-fix-2026-06-01/admin/global-footer-before-2026-06-01.html. Restore that content into WPCode Global Footer and purge cache.

Suggested Next Steps

• Consider adding a lightweight footer watchdog to the website QA routine. It should flag any public page where #sal-custom-footer is missing or duplicated.
• Consider investigating why active WPCode snippet 40125 stopped rendering from its original sitewide-footer location. The global footer fix works, but the original snippet behavior is worth cleaning up later so future agents are not confused by an active but non-rendering footer snippet.

Handoff