Skip to main content

SC WordPress Stack Standard

Purpose​

This document defines the canonical WordPress plugin and theme stack for all Symphony Core client sites hosted on GHL WordPress infrastructure. It replaces all prior plugin recommendation lists and establishes the approval process for exceptions.

Key Principle: GHL WordPress hosting provides CDN, daily backups, SSL, and security at the infrastructure level. The plugin stack is intentionally minimal -- every component must justify its presence against what the hosting platform and GHL ecosystem already provide.


Standard Stack​

#ComponentTypeLicenseDetails
1AstraTheme (Free or Pro)Free / $79/yr ProLightweight (~50 KB), 280+ starter templates, full Elementor compatibility, WordPress Customizer integration
2ElementorPlugin (Free)FreePage builder framework base. Required foundation for Elementor Pro.
3Elementor ProPlugin (Paid)Agency licenseGlobal design systems, theme builder, advanced widgets, unlimited client sites
4Rank Math SEO + Rank Math PROPlugins (Free + Paid)SC Business licenseTitles, meta, schema, sitemap (/sitemap_index.xml), robots.txt, redirects and IndexNow. Both plugins are required; PRO depends on the free plugin. Baseline settings and license rules: Rank Math Configuration Standard. New site: Rank Math Client Site Configuration SOP. An inherited site still running SearchAtlas (MetaSync): migration SOP
5LeadConnectorPlugin (Free)FreeOfficial GHL integration: forms, chat widget, funnel embedding, CRM sync, calendar widgets. When serving a full GHL funnel at a WordPress URL, set Page Display Method = Native HTML Embed (see policy below).
6GTM4WPPlugin (Free)FreeSitewide Google Tag Manager container deployment without manual theme edits. Required for GA4 + GTM tagging per GTM WordPress Plugin SOP and GA4 Property Creation SOP

Total: 6 plugins + 1 theme. This is the complete standard stack. No additional plugins should be installed without following the approval process below.

Retired from the stack​

ComponentRetiredWhyReplacement
SearchAtlas SEO (MetaSync plugin, OTTO pixel)2026-08-21 (subscription lapsed)Full vendor exit; see the SEO tooling migration decision log D1-D3. A lapsed MetaSync generates no titles, silently drops meta written over REST, and is an unpatched attack surfaceRank Math (row 4). Every client site was swapped by 2026-10-31. A newly inherited site still carrying MetaSync is swapped by the migration SOP
XML Sitemap Generator for Google (Auctollo)2026-09-30Adopted only to guard against the SearchAtlas sitemap regression (incident); with SearchAtlas gone, two sitemap systems is cost without benefit. Decision D6Rank Math's Sitemap module. Known cost: Auctollo's Additional Pages could list non-WordPress URLs (GHL funnel routes); Rank Math cannot. If a funnel page must be indexed, use GHL's own sitemap or GSC URL Inspection, per Make a GHL Funnel Page Indexable on WordPress

Never reinstall either on any site.

LeadConnector Page Display Method (SEO policy)​

When a full GHL funnel is served at a WordPress URL via LeadConnector > Funnels > Edit Page, the Page Display Method controls how the funnel is delivered. "Embed Full Page Iframe" is reserved for pages deliberately kept out of search — it produces a noindex iframe wrapper that is not crawlable and is excluded from Rank Math's sitemap, so the page silently disappears from /sitemap_index.xml.

Native HTML Embed is no longer an unconditional default for pages that must rank. Measured on symphonycore.com on 2026-09-17: it re-serialises the funnel HTML and prepends an escaped > to the data of every HTML comment, so Vue's server-rendered anchors <!----> are emitted as <!--&gt;-->. Most close harmlessly. Where the escaping breaks comment pairing, the opener swallows real markup until the next -->:

PageEscaped anchorsSwallowingMarkup buried inside comments
/platform5765137.5 KB, 1,143 elements — including the page's only <h1>
/pricing13,1151,05163.9 KB, 1,157 elements

Client-side hydration appears to repair the DOM for human visitors, which is why this is invisible in a browser. A crawler parsing the server response sees a comment. Native HTML Embed also hoists <script> elements out of their containers to the end of <body>, which breaks any embed script that mounts relative to its own tag — the failure mode that removed the prospecting audit widget from /audit on 2026-09-17.

Before relying on Native HTML Embed for a page that must rank, check the served HTML:

curl -sL https://<domain>/<path> | grep -c '<!--&gt;'

Zero is required. Non-zero means the markup is corrupted and the funnel embed cannot be trusted to rank — rebuild the page natively in WordPress/Elementor instead, per Make a GHL Funnel Page Indexable on WordPress § When to rebuild natively instead.

Scope of this finding. Measured on symphonycore.com only. It is not established whether the escaping originates in the LeadConnector plugin or in a WordPress-side output filter on this site — a filter escaping comments in the plugin's output would produce the same signature. The WPCode snippet that strips the funnel noindex was ruled out: /audit was corrupted with that snippet's guard absent. The check above is valid either way.

Procedure, decision table, and verification: GHL Asset Handoff SOP — Funnel Pages Served at a WordPress URL. If the LeadConnector plugin admin is stuck on the onboarding splash and the Funnels tab is unreachable, see the LeadConnector Connection Troubleshooting SOP.


Runtime Requirements​

Minimum PHP version: 8.2 — all SC-managed WordPress sites must run PHP 8.2 or higher.

Why: In April 2026, PHP 7.4 caused WSOD outages on symphonycore.com and ctbuildingbroker.com. 9 of 18 active plugins — including core stack components (LeadConnector, SearchAtlas/metasync) — are incompatible with PHP 7.4. The error is silent (no debug.log, no error display) because PHP cannot parse the plugin files. Full incident detail in WordPress WSOD Recovery Runbook.

How to apply:

  • When creating or auditing any WP site, verify PHP version in GHL > WordPress > Advanced Settings > Server Settings before any other configuration
  • If PHP is below 8.2: upgrade. For working sites, use staging first. For sites already down, upgrade live directly (backup first per the runbook)
  • 8.2 is the floor, not the ceiling — newer versions (8.3, 8.4) are acceptable when supported by all stack plugins. Avoid bleeding-edge 8.4 until stack-wide compatibility is verified

Prohibited Plugin Categories​

Plugins in these categories are prohibited on SC-managed WordPress sites. Each category has an SC alternative that makes the plugin unnecessary.

CategoryExamplesSC Alternative
Other SEO suites and sitemap pluginsYoast, All in One SEO, SEOPress, SearchAtlas (MetaSync), XML Sitemap Generator for Google (Auctollo)Rank Math (row 4) is the only SEO suite and the only sitemap. One SEO plugin per site
Form pluginsContact Form 7, WPForms, Gravity Forms, Ninja FormsLeadConnector embeds GHL forms with direct CRM routing
Chat/popup pluginsChaty, Popup Maker, OptinMonster, LiveChatLeadConnector provides GHL chat widget and popups
Caching/performanceWP Rocket, W3 Total Cache, LiteSpeed Cache, AutoptimizeGHL hosting includes global CDN and server-level optimization
SecuritySucuri, Wordfence, iThemes Security, All In One SecurityGHL hosting provides infrastructure-level security
BackupAll-in-One WP Migration, UpdraftPlus, BackupBuddyGHL hosting provides automatic daily backups at 05:00 AM CST + manual backup capability
Alternative page buildersDivi, Beaver Builder, Brizy, Bold BuilderElementor Pro is the standard; alternative builders create conflicts
Code snippet pluginsCode Snippets, WPCodeUse Elementor custom code or child theme functions.php. Approved exception: WPCode Lite, solely to host the funnel noindex-strip snippet in Make a GHL Funnel Page Indexable on WordPress, on sites that serve GHL funnels at WordPress URLs (live on symphonycore.com). No other snippet goes in it; record the exception in the client folder per the approval process below

Why This Stack​

Minimal Maintenance​

Six plugins plus one theme means fewer updates, fewer compatibility issues, and faster update cycles. Each plugin update is a potential breaking change -- fewer plugins means less risk.

Maximum Integration​

LeadConnector connects WordPress directly to the GHL CRM ecosystem. Forms, chat, calendars, and funnels all route to a single CRM without webhooks or middleware. Rank Math manages titles, meta and schema from one plugin, configured from the client profile.

Reduced Attack Surface​

Every WordPress plugin is a potential security vulnerability. The standard stack limits the attack surface to a small set of well-maintained, widely-used plugins from established vendors. GHL hosting handles the infrastructure security layer that plugins like Sucuri and Wordfence traditionally address.

Consistent Client Experience​

A standardized stack means every SC client site works the same way. Troubleshooting is predictable, onboarding new team members is faster, and knowledge transfers between projects are seamless.


Optional Plugin Approval Process​

Plugins beyond the standard stack require explicit approval. The requesting team member must answer all five questions:

  1. What problem does this plugin solve? -- Describe the specific functionality needed.
  2. Why can't Elementor Pro, Rank Math, LeadConnector, GTM4WP, or GHL hosting solve it? -- Demonstrate that the standard stack cannot address the need.
  3. What is the maintenance cost? -- How often does the plugin update? What happens during WordPress core upgrades?
  4. What happens if this plugin is abandoned? -- Is there a fallback plan if the vendor stops maintaining it?
  5. Is this a per-client exception or a stack-wide addition? -- Per-client exceptions are documented in the client folder. Stack-wide additions require updating this standard.

Approval authority: CEO approval required for all plugin additions.

Documentation: Approved exceptions are recorded in the client's folder (e.g., 09-clients/[client-slug]/) with the justification and approval date. Stack-wide additions are added to this document with a version bump.


Theme Configuration: Astra​

Initial Setup​

  1. Install Astra from Appearance > Themes > Add New
  2. Activate Astra as the site theme
  3. Open Appearance > Customize to configure:
    • Site Identity: Upload client logo and favicon
    • Colors: Set primary brand colors (link color, heading color, body text)
    • Typography: Configure primary and secondary font families
    • Layout: Select full-width or boxed layout, set container width
    • Header: Configure header layout, logo position, menu style
    • Footer: Set footer layout, copyright text, widget areas

Starter Templates​

Astra provides 280+ starter templates organized by industry. Import via Appearance > Starter Templates, select Elementor as the page builder, then customize for the client brand.


Plugin Configuration Reference​

For detailed step-by-step configuration of each stack component (Elementor global design system, Rank Math, LeadConnector authorization), see:


Document Maintenance​

Review Schedule: Quarterly or when a stack component releases a major version

Update Triggers:

  • New plugin added to or removed from the standard stack
  • GHL WordPress hosting capabilities change
  • Rank Math or LeadConnector major feature updates
  • New prohibited category identified

Changelog​

DateVersionChange
2026-10-311.5Rank Math becomes row 4 (6 plugins + 1 theme). SearchAtlas and Auctollo moved to a Retired from the stack table; the mid-migration warning removed: every client site is on Rank Math and the SearchAtlas docs are archived. Prohibited table names both retired plugins; Auctollo no longer listed as approved. Funnel iframe note retargeted to /sitemap_index.xml. WPCode Lite recorded as an approved exception for the funnel noindex snippet
2026-09-301.4Auctollo row 7 retired (D6). It had been added 2026-05-24 as a sitemap-only plugin with SearchAtlas's sitemap module disabled, publishing /sitemap.xml
2026-09-111.3SearchAtlas row marked superseded; Rank Math un-prohibited after the Business license purchase