WPCode Premium Migration & Snippet Management¶

Status: Complete migration; snippet management ongoing Project: Website

What this is¶

WPCode Premium is the firm's approved way to inject custom HTML, CSS, JS, and schema snippets into WordPress without touching theme files. In April 2026 the firm migrated off the free Code Snippets plugin to WPCode Premium, and WPCode has since become the delivery mechanism for a lot of sitewide fixes: H1 tag corrections, FAQ rendering fixes, schema injection, CallRail Dynamic Number Insertion scripts, and the BSG CTA banner.

Why WPCode Premium over Code Snippets¶

Conditional logic — snippets can target specific pages, post types, or URL patterns without PHP
Location targeting — header/footer/body placement is built in
Version history — each snippet edit is tracked
Auto-disable on error — a broken PHP snippet won't take the site down
Better UI — search, filter, tag snippets across a large library

Migration pain points¶

Migration from Code Snippets → WPCode Premium hit a few sharp edges: - Schema snippet 43605 had encoding issues picked up by Semrush — entities were double-encoded in WPCode's JSON field, producing broken JSON-LD. Fixed by re-entering the raw schema block. - Some snippets had page-level conditions that didn't port cleanly and needed manual reconfiguration - Post-migration QA sweep (April 12) caught several snippets that were disabled by default after import

Snippets actively managed in WPCode¶

BSG CTA Banner (snippet 43605 and related) — the Bigger Share Guarantee promotional banner, sitewide
CallRail DNI — Dynamic Number Insertion scripts for tracking campaign-specific phone numbers
Missing H1 Tag fix — a snippet that injected missing H1s on 45 pages without needing per-page edits
Sitewide FAQ Rendering Fix — CSS/JS to correct FAQ accordion rendering across pages
Custom Four-Column Footer — the footer layout lives in WPCode because Kadence couldn't produce the exact spec

Lessons learned¶

Test snippets in a conditional scope first, then broaden. The FAQ rendering fix would have looked like a sitewide breakage if the scope had been too wide on first deploy.
Keep schema snippets separate from styling snippets. Mixing them made the 43605 encoding bug harder to isolate.
Use meaningful snippet names with date + purpose. After the migration, several snippets had generic names like "New Snippet" and had to be identified by content.