Culture Talkz replace the blog.
Same words, instrumented better, hosted on GHL.

2026-06-01

• Landed Push greenlight flipped and the first live auto-push proven. Day 14 (AUTHORITY, Competence, 4E Executive Framework) created 3 GHL drafts, LinkedIn, Facebook, Instagram, all gates passed, Rule 12 drafts only. Day 15 auto-fires daily.
• Landed Section 02 instrumentation audited live: GA4 plus GTM verified firing; JSON-LD schema, Microsoft Clarity, Search Console, and the meta description confirmed missing. Section 02 updated to the verified state.
• Landed Culture Insight 01, "I Wore a Heart Monitor to Work," drafted from her own Day 9 post, all 12 voice gates passed, layered with Quick Captures 18, 19, 23. Lives in Section 03.6.
• Landed Culture Talkz blog restructure locked: a native GHL Blog owns /culture-talkz, the current funnel page is cloned and parked at /culture-talkz-legacy, branded via the CSS in Section 03.7. API finding: GHL has 0 blogs, posts are API-creatable, the blog site is UI-only. The create-post script is staged.
• Landed GHL mapped: /culture-talkz is the page "Culture Talkz" (id CxBX4w78CLVlcPo2pxBE) inside the "2025 Updated IEXDG" website. Verified no API clones or repaths a GHL page (read + redirects only), so Phase 0 is a UI step. Full design backup of the live page saved to disk.
• Landed Culture Insight 01 built as a full branded 12-section HTML and registered in the library: brain.iexdg.com/strategy/IEXDG_Field_Note_01_Heart_Monitor.html. All 12 anatomy sections present, Article and FAQPage schema embedded, voice gates passed, DRAFT.
• Landed Culture Insight 01 enriched with rich media to break the wall of text: an infographic (stated vs experienced culture gap), an interactive 90-second culture-check widget, an in-body licensed photo, and a HeyGen video slot. Today's Day 14 social drop also got the licensed hero attached in GHL (all 3 drafts, media verified).
• Landed Culture Insight rich media completed: a cited Gallup data graph (23/62/15 engagement, real sources) and a real HeyGen video of Dr. DNicole (her talking photo, 55 second read) are now embedded and playing in the Culture Insight. Live, md5-verified.
• Rule The ELCC pillars are INTERNAL, not client-facing. Public categories and tags use sector or plain topic language; the pillar is internal metadata only.
• Held · Robert UI, about 7 min: clone and park the legacy page, create the Blog, add author Dr. DNicole Fields Ed.D., add client-facing categories. Then I wire the posts via API.
• Held · Robert Send the pushback email to Dr. DNicole.

📋 First-comment artifact: latest is source/_audit/ghl_first_comment_artifacts/6a1984a5bc18acafed16b603.txt (Day 13). Future iteration: live fetch from /api/latest_first_comment.

Old framing vs new framing

The seven concurrent jobs

If a Culture Insight does not serve all seven, it is not yet a Culture Insight.

📊 Where each artifact lands

📡 Detection greps live in regression_registry.md. Gate 3 (repeat-scan) auto-elevates any R-NNN with count ≥ 2. Hygiene H3 (stochastic-consensus) and H4 (delivery hygiene) sweep on every deploy.

The stack

Registrar / DNS

Squarespace (record points at GHL)

Website hosting

GoHighLevel (GHL)

Culture Talkz / blog

GHL native blog feature

Email list

GHL native email marketing

Forms

GHL native (no iframes, native embed)

Workflows

GHL workflows (110 live as of Apr 24, 2026)

CRM contacts

1,956 in GHL as of Apr 24, 2026

Tracking codes

GHL Sites > Settings > Tracking codes (custom JS injection)

301 redirects

GHL Sites > Settings > URL Redirects (per-path)

URL structure on GHL

GHL Blog uses a flat URL pattern, NOT hierarchical. Hierarchical paths like /culture-talkz/2026/04/[slug]/ are not supported by GHL Blog out of the box. We use:

FINAL URL PATTERN
https://iexdg.com/culture-talkz/[slug]/

# Examples
https://iexdg.com/culture-talkz/captaincy-pattern-public-sector/
https://iexdg.com/culture-talkz/why-training-fails-without-architecture/
https://iexdg.com/culture-talkz/seven-signals-of-culture-quitting/

# Date is preserved as metadata in GHL Blog post field, NOT in URL

Master structure overview

12 sections · Fixed order · All present in every Culture Insight · No exceptions
+ Section 13: What to Say When It Lands (post-publish outreach framework)
+ Section 14: Gap Analysis + Blind Spot Audit (recurring cycle)

Twelve sections in a fixed order, built into the GHL Culture Insight page template. Every Culture Insight carries all twelve. No exceptions.

For years, I wore a heart monitor to work.

Not because of a heart condition. Because the stress of working under a leadership culture that talked about courageous conversations but punished anyone who actually had one was literally measurable in my body.

Read that again. The conversations the organization said it wanted were the same conversations it quietly made you pay for. And my body kept the receipt.

That is the part most leaders miss. A culture is not what is written in the values deck. A culture is the set of things that get rewarded, the things that get ignored, and the things that get punished when no one is watching. You can announce psychological safety in a town hall on Monday. If the person who raised the hard truth gets frozen out by Thursday, the staff learned the real rule, and it was not the one on the slide.

People are very good at reading that gap. They learn it fast, and they adjust. They stop bringing the concern. They stop naming the risk early. They route around the leader instead of through the leader. From the top it can look like things finally calmed down. What actually happened is that the organization went quiet, and quiet is not the same as healthy.

I know that gap from the inside, because I lived in it.

I have six degrees. A doctorate in leadership. I had every credential to climb the traditional path, principal, superintendent, university chancellor. I chose not to.

Because I realized I wasn't going to fix from the inside what was designed to stay broken.

That sentence took me years to be able to say plainly. The structures I worked under were not failing by accident. They were producing exactly what they were built to produce. Compliance read as alignment. Silence read as agreement. Turnover read as a people problem instead of a design problem. Nobody in those rooms was a villain. The system was simply doing its job, and its job was to protect itself.

So I stopped trying to argue with the system from inside it. I built a different one.

I built the Effective Leadership Culture Code. Six pillars. Real systems. Because the leaders I worked under needed it and didn't have it. Because the staff under those leaders needed it and didn't have it.

The six pillars are not a personality model and they are not a training curriculum. They are the load-bearing structure of a culture: Communication, Connection, Collaboration, Captaincy, Culture, and Competence. When one of them is missing, the organization does not announce it. It just starts to ache in ways that show up as attrition, as missed strategy, as the quiet departure of the exact people you most needed to keep. The same way stress showed up in me before I was willing to name it.

Here is what I want you to take from this, because this is not really a story about me.

If your best people have gone quiet, do not read it as peace. Read it as data. Ask what your culture rewards when no one is watching, and whether that matches what your leaders say from the stage. Ask whether a person on your team could raise the uncomfortable truth this week and still be safe next week. If the honest answer is no, more training will not close that gap, because the gap is structural, and you cannot develop your way out of a structure that punishes the behavior the development teaches.

That is the work I do now, alongside leaders and their teams, not in place of the HR and learning partners already carrying it. We do not hand an organization another program to sit on top of a broken foundation. We rebuild the foundation, one pillar at a time, so the culture the leadership intends and the culture the team experiences finally become the same culture.

I do not wear the monitor anymore.

And now I partner with organizations to build the kind of culture I needed and never found.

This is the work.

Dr. DNicole | Strategic B.E.L.O.N.G Solution | IEXDG

🔧 Publish metadata (paste into the GHL blog post)

SEO title

I Wore a Heart Monitor to Work | IEXDG Culture Talkz

Slug

https://iexdg.com/culture-talkz/heart-monitor-to-work/

Meta description

For years I wore a heart monitor to work. Not for a heart condition. For the cost of a leadership culture that punished the conversations it claimed to want.

CTA

iexdg.com/clarity (Leadership Culture Strategy Call)

<!-- Article schema · paste in the post HEAD -->
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "I Wore a Heart Monitor to Work",
  "author": { "@type": "Person", "name": "Dr. DNicole Fields", "honorificSuffix": "Ed.D." },
  "publisher": { "@type": "Organization", "name": "Integral Exploration Development Group, LLC" },
  "datePublished": "FILL-ON-PUBLISH",
  "mainEntityOfPage": "https://iexdg.com/culture-talkz/heart-monitor-to-work/",
  "articleSection": "Culture"
}
</script>

Can the API do it? The honest split (verified 2026-06-01)

Probed the GHL API directly. It exposes funnel and page READ plus redirect management only. No endpoint clones a page, edits page content, or changes a page path, and the blog site, authors, and categories are UI-only. So Phases 0 and 1 are Robert's clicks, about 7 minutes; everything after is mine via API.

Exact location: /culture-talkz is the page "Culture Talkz" (id CxBX4w78CLVlcPo2pxBE) inside the "2025 Updated IEXDG" website. A full HTML design backup of the live page is saved at source/content/culture_talkz/_backups/culture_talkz_page_BACKUP_2026-06-01.html.

🪜 Micro-steps · all five phases

Phases 0 and 1 are yours in the GHL UI, about 7 minutes. Phase 2 is a paste. Phases 3 and 4 are mine via API, plus two account logins that are yours.

Step C · the schema block (paste-ready)

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "Organization",
      "@id": "https://iexdg.com/#organization",
      "name": "Integral Exploration Development Group, LLC",
      "alternateName": "IEXDG",
      "url": "https://iexdg.com",
      "logo": "https://iexdg.com/FILL-IN-LOGO.png",
      "description": "A leadership and organizational culture development ecosystem built on owned intellectual property, system-driven delivery, and measurable leadership experience.",
      "areaServed": "US",
      "founder": { "@id": "https://iexdg.com/#drdnicolefields" },
      "address": { "@type": "PostalAddress", "addressLocality": "Silver Spring", "addressRegion": "MD", "addressCountry": "US" }
    },
    {
      "@type": "Person",
      "@id": "https://iexdg.com/#drdnicolefields",
      "name": "Dr. DNicole Fields",
      "honorificSuffix": "Ed.D.",
      "jobTitle": "Founder and Leadership and Organizational Culture Strategist",
      "worksFor": { "@id": "https://iexdg.com/#organization" },
      "sameAs": ["FILL-IN-HER-LINKEDIN-URL"]
    },
    {
      "@type": "WebSite",
      "@id": "https://iexdg.com/#website",
      "url": "https://iexdg.com",
      "name": "IEXDG",
      "publisher": { "@id": "https://iexdg.com/#organization" }
    }
  ]
}
</script>

Step B · the brand CSS (paste in the blog template custom code)

/* IEXDG Culture Talkz blog theme · navy / cream / Playfair / rust. No em-dashes. */
/* Selectors target GHL's default blog markup; adjust to your template's classes if needed. */
@import url('https://fonts.googleapis.com/css2?family=Inter:wght@400;600;700;800&family=Playfair+Display:wght@700;800;900&display=swap');
:root{ --navy:#1B2A4A; --cream:#EBECE3; --paper:#ffffff; --rust:#B85C2A; --gold:#C9A84C; --ink:#15243E; }
body, .blog-list, .blog-single{ background:var(--cream); color:var(--ink); font-family:'Inter',system-ui,sans-serif; line-height:1.6; }
h1, h2, h3, .post-title, .blog-title{ font-family:'Playfair Display',serif; color:var(--navy); }
a, .read-more{ color:var(--rust); }
a:hover{ color:var(--gold); }
.blog-post-card, .post-card, article.post{ background:var(--paper); border:1px solid rgba(27,42,74,.10); border-left:4px solid var(--rust); border-radius:14px; padding:18px; box-shadow:0 6px 18px rgba(27,42,74,.06); }
.post-category, .category-tag{ background:var(--navy); color:var(--cream); border-radius:999px; padding:3px 10px; font-size:11px; letter-spacing:1px; text-transform:uppercase; }
.blog-single .post-content{ max-width:720px; margin:0 auto; font-size:17px; }
.blog-single .post-content p{ margin:0 0 18px; }

📡 Source-of-truth: source/assets/dnicole_references/30day_plan_from_doc/dayN_verbatim.json per day. CANONICAL.raw.md mirrors the full plan from her Doc. Future iteration: live fetch from /api/post_index.

1 · The website is not the front door, LinkedIn is

Her live GA4 (property 535502749), last 90 days: 73 sessions, 71 visitors, only 3 from organic search and 1 from social. Almost all traffic was direct, links she sent herself. Her buyers, the HR directors, CHROs, city managers, and operations leaders, are not searching iexdg.com. CultureTalkz puts her authority in front of them on LinkedIn, every weekday, in her voice.

2 · Reach is built by posts, the close happens in conversation

Her First Customer Playbook is explicit: "two hours every single day goes to one thing only: talking to people who have the problem you solve. Not content. Not your website. Conversations." CultureTalkz and that discipline are partners. The daily post warms the name, the direct conversation closes it. Recommendation: protect the 2-hour outreach block, and make every pain-point post drive to culture-pulse and invite a reply.

4 · The decisions still sitting with her

Layer 3 (daily LinkedIn distribution) is live and auto-drafts for review. Still waiting on her word: Layer 1, the video pipeline that carries trust velocity at the research gate, and Layer 2, the deep written cadence. In 90 days, that "3 from organic search" line should not look like that anymore.

🔁 The architecture, corrected 2026-06-11

GHL has three publishing surfaces, and Funnel pages and Website pages use the same drag-and-drop builder with full <style> control. The decision (Robert, Jun 11): each Culture Insight is its own rich, fully-designed page (a Website or Funnel page, built like the live Heart Monitor insight), and /culture-talkz is a rich hub page that indexes them. The GHL Blog is not used. It strips the global styles, media queries, and design these pieces are built on, so it cannot render a Heart Monitor. The native-SEO convenience of the blog does not outweigh the richness, the SEO is rebuilt by hand instead (per-page schema, sitemap, a hand-maintained index).

Her own GA4 still frames the urgency: 73 sessions in 90 days, 3 from search, 1 from social, near-zero discovery. The fix is not the page type, it is feeding the top plus the manual SEO floor below. We accept that rich pages need hand-built SEO, because the alternative (a stripped blog post) loses the richness that makes a Culture Insight worth reading. This corrects an earlier draft of this section that proposed hosting the posts as Blog posts.

🧱 What each Culture Talkz piece becomes

Each Culture Insight is its own rich, fully-designed page (a GHL Website or Funnel page, full <style> control), built like the live Heart Monitor insight. It is NOT a Blog post. Each page carries its content and the route into conversion:

• The content: the full Culture Insight, in her brand, fully styled (hero, quote cards, FAQ, the 12-section anatomy from Section 03), the same richness as the Heart Monitor page.
• The qualify step, inline: the Culture Pulse 3-question scan as a form embed, or a one-click link to it, on the page itself.
• The route step, inline: a soft book-a-call into the existing Discovery / Clarity funnel for the call-path tiers.

LinkedIn post  ──▶  Culture Insight page (rich)  ──▶  Culture Pulse scan  ──▶  Clarity / Discovery funnel  ──▶  Close
   (reach)        (full-design page, like Heart Monitor)  (qualify)        (existing funnel, scope + price)   (ladder)

⚖️ The trade-off we accept, and how we cover it

Rich pages cost us the blog's free SEO conveniences. We take that trade on purpose: the richness is the point, and the SEO is rebuildable by hand. Here is what the blog gave free and how we replace it on rich pages.

🧭 The five stages the funnel pages serve

🔀 The offer-router · buy vs call

One rule governs every lead. Under $5,000, ask them to buy. At $5,000 and up, ask for a call. The threshold is set by procurement: a school or agency purchase of $5,000 or more usually needs district-office approval, under that it stays in-house.

A router only works if the buy lane has something to buy. The consulting ladder is anchored at $7,500 and is all call-path, so the buy lane is the sub-$5,000 products: the free Culture Pulse scan to qualify, then the Leadership Gap Audit ($97 a seat, $1,500 a team) and the Culture Pulse Diagnostic ($2,500) as direct-checkout entries. Everything at $5,000 and up books a call, where scope and price are set. Keep at least one real sub-$5K product live. If every self-serve tier is removed, the router has no buy branch and collapses into a single all-call funnel, which deletes the only path a cold, unconvinced buyer can take without a sales conversation.

⚠️ Open decision: keep the self-serve buy lane (recommended) or collapse to all-call. The scan-to-buy router page cannot ship until this and the pricing reconciliation below are settled.

🪜 The offer ladder · scope-based, price held for the call

Sales Plan v2, the coached high anchor. Price tracks scope, not org size, and is set on the Discovery Call. No price in the cold email.

DISC (Maxwell) rides inside a Stabilization engagement as a roughly $1,500 add-on, never branded as IEXDG IP. Target: a six-figure month by September 2026.

🎓 The masterclass math

The masterclass is the qualifier that converts. The revenue equation: Calls needed = Revenue goal divided by (Price times Close rate). Track conversations, not dials.

100 registrants
  └▶ 25 attend          show-up 20 to 30 percent
       └▶ 3 buy or book  convert 5 to 15 percent (10 percent is good)
            └▶ 1 to 2 close on the call

Title formula: How to [outcome] without [the thing they hate] even if [their struggle]. Structure: scripted hook, a high price anchor in the first ten minutes, the three buyer beliefs (personal, business, community worth), core offer, bonus stack, three-tier fast-action bonuses (live, by midnight, before cart close). Launch every four to six weeks.

📈 The ads and ROAS plan

Objectives ladder: start with Awareness, use Traffic to warm a large list, then Leads and Sales. One pixel, events on view, lead, and purchase across the funnel pages, verified with Meta Pixel Helper. Strict targeting over Advantage Plus until the data earns the expansion. Run ads in-house 30 to 90 days before hiring out.

🛠️ Build status, grounded in the GHL API 📡 API reference

Important: GHL Funnel and page content is built in the UI. The API only lists funnels, pages, and redirects (three read-only GET endpoints). It cannot clone a page, edit page content, change a path, or create a redirect. So the funnel pages are a UI build, the automation is in the data layer around them.

🛠️ Build the rich-pages hub · the runbook

I produce the styled HTML for each rich page, Robert pastes it into a GHL page (the pages API is read-only). The funnel layer already exists, so there is no funnel to build here, only the content pages that feed it.

Phase 1 · the funnel + the hub step · you, UI, ~5 min

1. Sites, Funnels, New Funnel, name it Culture Talkz, set the funnel path to culture-talkz. The current Blog at that slug is retired or moved aside, it is not the host.
2. The funnel URL loads its first step, so the first step is the hub at /culture-talkz. On the blank page click Insert Element (or Blank Section, then the +) and add ONE Custom Code / Custom JS-HTML element, the </> icon.
3. Paste the ENTIRE page into that one element, the whole file from <!DOCTYPE html> through </html>, style block and all. Do NOT split the CSS into the page head. This is exactly how /culture-pulse is built: verified against its live DOM, its custom-code element holds the full document.
4. The Culture Pulse scan and book-a-call links are already inside the HTML, so no separate Form or Button element is needed. Save, preview, publish, then curl the path for a 200.

Phase 2 · each Culture Insight step · you, UI, ~3 min each

1. In the culture-talkz funnel, add a Step (or clone the hub step), set the step path to a clean slug like heart-monitor so the URL is /culture-talkz/heart-monitor. Set it by hand, distinct from the funnel and page slug, or GHL appends a numeric suffix. 50 steps max per funnel.
2. Add ONE Custom Code element and paste the ENTIRE Culture Insight HTML into it, same as the hub. The per-page JSON-LD (Article, FAQPage) lives inside that same element, it needs no separate head paste, Google reads it in the body.
3. Save, Publish, verify in Google's Rich Results Test, then add the URL to the hub index.

Phase 3 · content I produce

• The Heart Monitor insight is already built (live HTML, the master template). I develop each new Culture Insight into a rich page in that same design from the DRAFT markdown (Culture Insight 02 "Strong team, wrong results" is next).
• Each page ships with literal-value JSON-LD (no merge tokens), the 12-section anatomy from Section 03, an inline scan, and the book-a-call into the existing funnel.
• I keep every page's HTML in version control as the source of truth, since GHL pages are not API-readable back.

Scan-to-buy router · spec (dev queue, gated)

• Trigger: Culture Pulse scan submit. Branch: under $5,000 to a buy-now page (the legacy Gap Audit or $2,500 Diagnostic), $5,000 and up to book-a-call.
• Mechanism: a GHL workflow on form-submit with an if/else to redirect or email.
• Acceptance: a test submit routes to the correct destination for each branch.
• Blocked on the pricing reconciliation gate, the buy lane cannot go live while the ladders disagree.

Attribution wiring · per funnel page

• Fire the GA4 events that apply (rename field_note_view to culture_talkz_view, plus inline_cta_click, schedule_consult_clarity, scroll_75), triggered in GTM against the funnel builder classes, not the old blog classes.
• Set a GHL hidden field on the scan form, source_culture_talkz = [slug], so attribution survives the move off the blog.

🔎 SEO Floor Kit · generated 2026-06-09

A live audit found the organic floor is currently zero: sitemap.xml is empty (0 URLs), robots.txt is blank, and /culture-talkz has no meta description, no canonical, and no schema. A paste-ready kit closes it. iexdg.com is GHL UI-managed, so these are pasted in the builder, not pushed by API.

Kit files: source/strategy/internal/seo_floor/ (head_culture_talkz.html, head_field_note_TEMPLATE.html, robots.txt, sitemap.xml, PASTE_GUIDE.md). Verify after paste: the sitemap populates, /culture-talkz returns four or more JSON-LD blocks, every page passes Google's Rich Results Test, then submit the sitemap in Search Console.

⚠️ Risks, blindspots, and gates · audit 2026-06-09

• Organic discovery, the founding risk. The premise is starving at the top, and rich custom pages do not get the blog's free SEO, so we must build the floor by hand or discovery stays zero. This is the cost we accept for the richness. Mitigation: ship the hub and every Culture Insight page with the full SEO floor above (per-page JSON-LD, OG, canonical, indexing ON, a sitemap entry each), keep LinkedIn organic strong, and read Search Console at 90 days. Verified 2026-06-11: the live sitemap is an empty stub and /culture-talkz carries no schema, so the SEO floor is currently zero. This risk is live, not theoretical, and the manual floor is non-optional.
• Two live ladders, trust. See the pricing reconciliation gate above. Until she signs off one ladder and the GHL products match it, the $7,500 numbers stay internal.
• Cold-email contact-back gap. The live executive sequence carries a booking link only on Day 12, emails one and two are reply-only at the highest-intent moment. Fix: add the free Culture Pulse scan link to A1 and A2 (deferred for now per Robert).
• Manual scale vs cadence. Funnel pages are UI-only and hand-duplicated, but the cadence promises four pieces a month plus daily derivatives. Mitigation: funnel pages for the two DEEP pieces a month that justify a landing page, route the two LIGHT pieces and derivatives through the API-automatable Social Planner so the engine stays hands-free. Budget the minutes per page.
• Concentration and capacity. One reach channel (Culture Talkz and LinkedIn), one platform (GHL holds content, pages, payments, CRM, attribution), one closer (her, on calls). An all-call $7,500 ladder caps revenue at calls she can personally take times close rate times price, the real ceiling on the September six-figure-month target and not modeled in the masterclass math. Hedges: keep an owned organic channel, export GHL contacts and orders monthly, keep page source in version control, and model her weekly call capacity against the target. If the target needs more calls than her two-hour block holds, the constraint is her calendar, not the funnel, and a self-serve tier or a second closer is required.

Per-week production cycle

Depth alternation per month

• Week 1: solo deep-dive episode → DEEP Culture Insight (3,000+ words, book-grade)
• Week 2: interview / conversation → LIGHT Culture Insight (1,200 words, show-notes plus)
• Week 3: solo deep-dive episode → DEEP Culture Insight
• Week 4: interview / conversation → LIGHT Culture Insight

Output per month: 4 podcast episodes, 4 Culture Talkz (2 deep + 2 light), 12-16 video clips, 8-12 LinkedIn posts, 4 emails, 16-20 quote cards.

Required tools

Custom GA4 dimensions

// To create in GA4 Admin > Custom dimensions
// Scope: Event-scoped unless noted

content_pillar         // Communication / Connection / Collaboration / Captaincy / Culture / Competence
hero_persona           // CPO / VP_HR / SUPT / COS / NEW_CEO / RED
sector                 // Corporate / Government / Education
episode_id             // links Culture Insight to companion podcast
field_note_depth       // deep / light
publish_date           // ISO 8601
internal_link_count    // count of in-page links to other IEXDG content
authority_count        // count of cited authorities (HBR, McKinsey, OECD, etc.)
word_count             // 1200 / 1500 / 2000 / 3000 / 4000+
cta_location           // inline_mid / closing / sidebar / lead_magnet

Custom GA4 events

field_note_view              // page view + custom dims
inline_cta_click             // mid-content CTA clicked
faq_expand                   // which FAQ question opened
related_link_click           // adjacent content clicked
diagnostic_download_start    // form opened
diagnostic_download_submit   // form submitted, lead captured
schedule_consult_clarity     // closing CTA clicked
podcast_companion_click      // link to companion episode
share_action                 // LinkedIn / Email / Copy URL
scroll_75                    // scrolled past 75%, deep reader signal
audio_play                   // embedded podcast player started
audio_75                     // audio listened past 75%

Microsoft Clarity install snippet

Drop into GHL Sites > Settings > Tracking codes > Custom JS (head). Replace YOUR_PROJECT_ID after creating Clarity project at clarity.microsoft.com.

<script type="text/javascript">
    (function(c,l,a,r,i,t,y){
        c[a]=c[a]||function(){(c[a].q=c[a].q||[]).push(arguments)};
        t=l.createElement(r);t.async=1;t.src="https://www.clarity.ms/tag/"+i;
        y=l.getElementsByTagName(r)[0];y.parentNode.insertBefore(t,y);
    })(window, document, "clarity", "script", "YOUR_PROJECT_ID");
</script>

Multi-touch attribution model (GHL-native)

Culture Insight view (Touch 1)
    │
    ▼
Diagnostic download (Touch 2, identity captured via GHL form)
    │  GHL contact created with custom field source_field_note = [slug]
    ▼
Email nurture engagement (Touch 3-N, tracked in GHL workflow)
    │
    ▼
Clarity Call booking (Touch N+1, conversion event)
    │  GHL custom fields:
    │    first_field_note_touched
    │    last_field_note_before_call
    ▼
Engagement contract signed
    │
    ▼
Revenue attribution: 50% weight to first touch, 50% to last touch
                     OR linear attribution across all Notes touched

Article schema (per Culture Insight)

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "{{post.title}}",
  "description": "{{post.excerpt}}",
  "image": "{{post.featured_image}}",
  "datePublished": "{{post.publish_date}}",
  "dateModified": "{{post.updated_date}}",
  "author": {
    "@type": "Person",
    "name": "Dr. DNicole Fields",
    "url": "https://iexdg.com/about/dr-dnicole-fields/"
  },
  "publisher": {
    "@type": "Organization",
    "name": "Integral Exploration Development Group",
    "logo": {
      "@type": "ImageObject",
      "url": "https://iexdg.com/logo.png"
    }
  },
  "mainEntityOfPage": {
    "@type": "WebPage",
    "@id": "{{post.url}}"
  },
  "articleSection": "{{post.pillar}}",
  "keywords": "{{post.tags}}",
  "wordCount": {{post.word_count}}
}
</script>

Person schema (Dr. DNicole · global, in site head)

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Person",
  "name": "Dr. DNicole Fields",
  "honorificPrefix": "Dr.",
  "honorificSuffix": "Ed.D.",
  "jobTitle": "Founder + Principal",
  "worksFor": {
    "@type": "Organization",
    "name": "Integral Exploration Development Group, LLC"
  },
  "url": "https://iexdg.com/about/dr-dnicole-fields/",
  "image": "https://iexdg.com/headshot.jpg",
  "sameAs": [
    "https://www.linkedin.com/in/drdnicolefields/",
    "https://iexdg.com/"
  ],
  "knowsAbout": [
    "Leadership development",
    "Organizational culture",
    "Tri-sector consulting",
    "ELCC framework",
    "Public sector leadership",
    "Educational leadership",
    "Corporate culture intervention"
  ]
}
</script>

Organization schema (IEXDG · global, in site head)

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "ProfessionalService",
  "name": "Integral Exploration Development Group",
  "alternateName": "IEXDG",
  "url": "https://iexdg.com",
  "logo": "https://iexdg.com/logo.png",
  "founder": {
    "@type": "Person",
    "name": "Dr. DNicole Fields"
  },
  "address": {
    "@type": "PostalAddress",
    "addressRegion": "MD",
    "addressCountry": "US"
  },
  "areaServed": ["US-MD", "US-DC", "US-VA", "US"],
  "serviceType": [
    "Leadership development",
    "Organizational culture consulting",
    "Executive coaching",
    "Culture diagnostic"
  ]
}
</script>

FAQPage schema (per Culture Insight FAQ section)

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "{{question_1}}",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "{{answer_1}}"
      }
    },
    {
      "@type": "Question",
      "name": "{{question_2}}",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "{{answer_2}}"
      }
    }
  ]
}
</script>

<!-- OpenGraph -->
<meta property="og:type" content="article">
<meta property="og:title" content="{{post.title}}">
<meta property="og:description" content="{{post.excerpt}}">
<meta property="og:url" content="{{post.url}}">
<meta property="og:image" content="{{post.featured_image}}">
<meta property="og:image:width" content="1200">
<meta property="og:image:height" content="630">
<meta property="og:site_name" content="IEXDG · Integral Exploration Development Group">
<meta property="article:author" content="Dr. DNicole Fields">
<meta property="article:published_time" content="{{post.publish_date}}">
<meta property="article:section" content="{{post.pillar}}">
<meta property="article:tag" content="{{post.tags}}">

<!-- Twitter Card -->
<meta name="twitter:card" content="summary_large_image">
<meta name="twitter:title" content="{{post.title}}">
<meta name="twitter:description" content="{{post.excerpt}}">
<meta name="twitter:image" content="{{post.featured_image}}">

<!-- LinkedIn-specific (uses OG, but explicit) -->
<meta property="og:image:type" content="image/webp">
<meta property="og:image:alt" content="{{post.featured_image_alt}}">

Concrete rules baked into the GHL template

• Color contrast: all body text on cream uses navy or ink (ratio > 7:1, AAA). Rust accent only on text 18pt+ and bold (ratio 3.9:1, hits AA Large).
• Alt text: every image requires descriptive alt text in GHL post editor. Decorative images use alt="" explicitly.
• Heading hierarchy: H1 once, H2 for sections, H3 for sub-sections, no level skipping.
• Keyboard nav: all interactive elements (links, form fields, share buttons) reachable via Tab. Focus rings visible (do not outline:none).
• ARIA labels: share buttons, audio embed, FAQ disclosures all have explicit aria-label or aria-expanded.
• Form labels: every GHL form field has a visible label (no placeholder-only fields).
• Skip-to-content link: first focusable element jumps to main content.
• Audio embed alternatives: every audio embed has a transcript link (the Culture Insight itself counts as transcript).
• Reduced motion: prefers-reduced-motion media query disables animations.
• Screen reader test: NVDA on Windows + VoiceOver on macOS verified before any new template ships.

Reduced motion CSS (drop into global stylesheet)

@media (prefers-reduced-motion: reduce) {
  *, *::before, *::after {
    animation-duration: 0.01ms !important;
    animation-iteration-count: 1 !important;
    transition-duration: 0.01ms !important;
    scroll-behavior: auto !important;
  }
}

Skip-to-content link

<!-- First focusable element on every page -->
<a href="#main-content" class="skip-link">Skip to main content</a>

<!-- CSS -->
.skip-link {
  position: absolute; top: -40px; left: 8px;
  background: var(--navy); color: var(--cream-warm);
  padding: 8px 14px; border-radius: 6px;
  text-decoration: none; font-weight: 700;
  z-index: 1000;
}
.skip-link:focus {
  top: 8px;
}

Hard rules

• Hero images load WebP under 250KB at 1200px width (use srcset for retina)
• Body font: 17px on mobile (16px feels too small at arm's length on iOS)
• Line height: 1.65 minimum
• Tap targets: minimum 44×44 px (Apple HIG)
• Form fields: minimum 48px tall on mobile to avoid iOS zoom
• Sticky TOC collapses to a "📑 Table of contents" button on width < 760px
• Sidebar reflows below content on mobile
• No horizontal scroll anywhere except deliberate code blocks
• Lazy-load all images below the fold
• Audio embed renders at 100% width on mobile

Breakpoints

Component spec

<aside class="author-bio" aria-labelledby="author-name">
  <img src="/headshot.jpg" alt="Dr. DNicole Fields, Ed.D., Founder of IEXDG"
       width="120" height="120" loading="lazy">
  <div>
    <h3 id="author-name">Dr. DNicole Fields, Ed.D.</h3>
    <p class="role">Founder + Principal · Integral Exploration Development Group</p>
    <p>
      Dr. DNicole Fields, Ed.D., is a leadership culture consultant working
      across corporate, government, and education sectors. She founded IEXDG
      to deliver structural interventions, not training. Active engagements
      include the City of Tucson, Garfield Heights, and CareFirst BCBS.
      The ELCC 6-Pillar Framework is her proprietary diagnostic system.
    </p>
    <ul class="author-links">
      <li><a href="/about/dr-dnicole-fields/">Full bio</a></li>
      <li><a href="https://www.linkedin.com/in/drdnicolefields/" rel="me">LinkedIn</a></li>
      <li><a href="/clarity">Schedule a Clarity Call</a></li>
    </ul>
  </div>
</aside>

Required structural tags (every Culture Insight)

Granular topic tags (curated, controlled vocabulary)

Choose 3-6 per Culture Insight. Drives AI citation and SERP long-tail.

Print CSS (drop in GHL global CSS)

@media print {
  /* Strip nav, footer, share buttons, ads, sidebar */
  .topbar, .toc-bar, .sidebar, .share-row, .author-bio,
  .lead-magnet, .closing-cta, .related-links, .footer,
  button, .btn-link, .btn-primary {
    display: none !important;
  }

  body {
    background: white !important;
    color: black !important;
    font-size: 11pt;
    line-height: 1.5;
  }

  .field-note-content {
    max-width: 100% !important;
    margin: 0 !important;
    padding: 0 !important;
  }

  h1 { font-size: 22pt; page-break-after: avoid; }
  h2 { font-size: 16pt; page-break-after: avoid; margin-top: 18pt; }
  h3 { font-size: 13pt; page-break-after: avoid; }

  p, li { orphans: 3; widows: 3; }

  .anatomy, .wireframe, table {
    page-break-inside: avoid;
  }

  pre {
    white-space: pre-wrap;
    word-wrap: break-word;
    font-size: 9pt;
  }

  a {
    color: black;
    text-decoration: none;
  }
  a[href^="http"]:after {
    content: " (" attr(href) ")";
    font-size: 8pt;
    color: #555;
  }

  /* Show URL after each link in print */
  .header-url {
    display: block;
    font-size: 9pt;
    color: #555;
    margin-bottom: 12pt;
  }
}

Y1 light approach

• Default language: English (US)
• Add <html lang="en"> on every page for screen readers and translation engines
• Open Graph locale: en_US
• No hreflang tags Y1 (single-language site)
• Allow Google Translate widget integration via ?translate=1 URL param (off by default)
• Avoid US-only idioms in headlines (no "fourth quarter", "off the dome", "shoo-in")
• Use ISO date format YYYY-MM-DD in metadata, friendly format ("April 25, 2026") in body
• Include named clients with country/region context (City of Tucson, Arizona; Ghana; etc.)

Y2+ if international scales

• Subdomain or path strategy: iexdg.com/uk/ or uk.iexdg.com
• hreflang tags between language versions
• Manual translation, never machine-only for thought leadership
• Local case studies per region

Spotify episode embed

<iframe
  src="https://open.spotify.com/embed/episode/{{episode_id}}"
  width="100%" height="232" frameborder="0"
  allow="autoplay; clipboard-write; encrypted-media; fullscreen; picture-in-picture"
  loading="lazy"
  title="Companion podcast episode for this Culture Insight">
</iframe>

Apple Podcasts embed

<iframe
  allow="autoplay *; encrypted-media *; fullscreen *; clipboard-write"
  frameborder="0" height="175" width="100%"
  src="https://embed.podcasts.apple.com/us/podcast/{{slug}}/id{{show_id}}?i={{episode_id}}"
  loading="lazy"
  title="Companion podcast episode for this Culture Insight">
</iframe>

HTML5 fallback (always renders)

<audio controls preload="none" style="width:100%;">
  <source src="{{episode.mp3_url}}" type="audio/mpeg">
  Your browser does not support audio playback.
  <a href="{{episode.mp3_url}}">Download episode</a>.
</audio>

Y1 (under 60 Culture Talkz)

• Use GHL's native blog search component (built into the GHL Blog feature)
• Cost: $0 (included in GHL)
• Limitations: keyword match only, no fuzzy / synonym handling, no instant search
• Acceptable for < 60 posts where readers can also browse pillar pills

Y2 (60+ Culture Talkz, if needed)

• Algolia Search starter plan: $0 up to 10K records, $89/mo for InstantSearch
• Custom JS install via GHL Tracking codes
• Better UX: as-you-type, typo-tolerant, multi-attribute (pillar + sector + tags)
• Or: Pagefind (open-source, $0, static index)

Recommended tool: Klaro (open-source, free)

• Drop-in JavaScript banner
• Granular per-tool consent (GA4 yes / Clarity no acceptable to user)
• Auto-blocks scripts until consent
• GitHub: klaro/klaro

Klaro install (drop in GHL Tracking codes)

<link rel="stylesheet" href="https://cdn.kiprotect.com/klaro/v0.7/klaro.min.css">
<script defer src="https://cdn.kiprotect.com/klaro/v0.7/klaro.js"></script>
<script>
var klaroConfig = {
  version: 1,
  elementID: 'klaro',
  styling: { theme: ['light', 'top', 'wide'] },
  default: false,
  mustConsent: false,
  acceptAll: true,
  hideDeclineAll: false,
  privacyPolicy: '/privacy/',
  services: [
    {
      name: 'google-analytics',
      title: 'Google Analytics 4',
      purposes: ['analytics'],
      cookies: [/^_ga.*/, /^_gid$/],
      onAccept: 'gtag("consent", "update", { analytics_storage: "granted" });',
      onDecline: 'gtag("consent", "update", { analytics_storage: "denied" });'
    },
    {
      name: 'microsoft-clarity',
      title: 'Microsoft Clarity (behavior recordings)',
      purposes: ['analytics'],
      cookies: [/^_clck$/, /^_clsk$/],
    }
  ]
};
</script>

Privacy policy update

The /privacy/ page on iexdg.com must add (Phase 1):

• What GA4 collects (page URL, referrer, device type, location at city level, behavior events)
• What Microsoft Clarity collects (mouse movement, clicks, scroll, page interactions)
• What GHL stores (form submissions, email, name, role, sector, all explicit submissions)
• Retention periods (GA4: 14 months default, Clarity: 1 year, GHL: per consent)
• Right to access, delete, export (GDPR Article 15-20)
• California Civil Code 1798.100 disclosure (CCPA)
• Cookie management link to Klaro banner

Defense actions (Phase 1)

1. USPTO trademark check on "Culture Pulse" word mark and "ELCC" acronym. Free at uspto.gov/trademarks/search. Document filing status of competitors.
2. Defensive trademark filing if not already filed. ~$250-350 USPTO filing fee per class. File "Culture Pulse" in Class 41 (educational services) and Class 42 (consulting). Covers IEXDG.
3. Domain defensive registrations: culturepulse.com (if available), culture-pulse.com, common typos. ~$10-15/yr each.
4. Search position monitoring: weekly check on "Culture Pulse" SERP via the Brain. Cultiv8tiv climbs = signal to push more Culture Talkz targeting the term.
5. Cease-and-desist template ready in source/docs/operations/legal/ with attorney review on file. Activated if Cultiv8tiv US enters with confusingly similar mark.
6. Anchor terms in Culture Talkz: every reference to her Culture Pulse uses the trademark superscript pattern Culture Pulse™ on first mention per Note. Establishes use in commerce.

Robert's job: monthly USPTO search + SERP check (15 min). Dr. DNicole's job: file the trademark. Lawyer's job: review C&D template once.

Decision matrix per legacy post

Implementation in GHL

# In GHL Sites → Settings → URL Redirects, add lines like:
/blog/why-training-fails              →  /culture-talkz/why-training-fails-without-architecture/   301
/blog/old-take-on-leadership          →  /culture-talkz/                                            301
/blog/dated-2019-post                 →  410 Gone
/blog/q4-tactics-2018                 →  410 Gone

Pre-migration checklist

• ☐ Pull GA4 (after install) or alternative report on top 50 blog posts by traffic
• ☐ Crawl iexdg.com/blog/* with Screaming Frog free tier (500-URL limit) for inbound links
• ☐ Decide each URL via the matrix above
• ☐ Build redirect map in spreadsheet
• ☐ Apply via GHL UI in single batch
• ☐ Update sitemap.xml (GHL auto-regenerates)
• ☐ Submit new sitemap to Search Console
• ☐ Spot-check 10 redirects with curl: curl -I https://iexdg.com/blog/[old-slug]/
• ☐ Monitor Search Console for crawl errors over 14 days post-migration

Email send to existing list (1 week before public Culture Talkz launch)

Subject: A few changes to how I publish

Pre-header: Same voice, deeper format, more for you to take into your boardroom.

Body:

Quick note before the next podcast episode lands.

Starting [date], the IEXDG blog is becoming Culture Talkz. Same voice.
Deeper format. Hosted on iexdg.com/culture-talkz.

Why the change:

  Culture Talkz are research-grade companions to the new IEXDG Podcast.
  Each podcast episode produces one Culture Insight. The Note carries the
  research anchors, the case data, and the structural fix in writing
  so you can take it into your next boardroom.

What changes for you:

  → New episodes hit your inbox each Tuesday with the companion
    Culture Insight attached.
  → A new Self-Diagnostic PDF (the ELCC 6-Pillar Quick Audit) is
    available at iexdg.com/diagnostic for your team.
  → All my old posts are still searchable. Some have been refreshed
    and renamed. Old links forward automatically.

What stays the same:

  → My voice, my framework, my client commitments.
  → Direct email reply when something lands for you.
  → No newsletter spam.

If you want to get ahead of the launch, listen to the first episode
here: [link]

Or skip straight to the new diagnostic: iexdg.com/diagnostic.

Talk soon,
Dr. DNicole Fields, Ed.D.
Founder, IEXDG

LinkedIn post (day of launch)

The IEXDG blog is now Culture Talkz.

Same voice. Deeper format. Companion to the new IEXDG Podcast.

Each episode lands with a written research brief you can share with
your leadership team. Authority anchors, sector data, structural fixes.

First episode: [title]
First Culture Insight: [link]

Diagnostic for your team: iexdg.com/diagnostic

All 10 green = auto-publish via Brain. Any fail = Brain Review Queue, Robert reviews within 24 hrs, Dr. DNicole approves within 48 hrs. Items not reviewed in 48 hrs auto-publish IF voice drift < 30 AND brand_rules pass. Items with voice drift 70+ never auto-publish.

2 deep Culture Talkz/mo × 12 months = 24 deep pieces × 3,000 words avg
                                  = 72,000 words of vetted, audience-tested
                                    content for the Y2 book editor

EDITORIAL FLOW (Y2):
   Month 1-2: Editor reviews 24 Culture Talkz, selects 12-15 chapter
              candidates, identifies gaps
   Month 3-5: Dr. DNicole expands 5-7 chapters, adds connective tissue,
              voice consistency pass
   Month 6-8: Manuscript complete, agent submits
   Month 9-12: Edit cycle, marketing prep
   Y3 launch: Book ships

• ❌ Generic listicle ("7 tips for better leadership")
• ❌ Transcript dump with no editorial pass
• ❌ Posts shorter than 1,200 words
• ❌ Authority-free opinion pieces
• ❌ Brand violations (any one of the 10 gates)
• ❌ Culture Talkz hosted off iexdg.com
• ❌ Culture Talkz without companion podcast episode
• ❌ Culture Talkz without instrumentation events
• ❌ Culture Talkz without lead magnet attached
• ❌ Culture Talkz referencing Dr. DNicole as the hero of any anecdote

1. Items added to queue automatically when voice drift score is 30+
2. Items also added if brand_rules.json check fails on any gate
3. Robert reviews within 24 hours
4. Dr. DNicole approves within 48 hours
5. Items not reviewed within 48 hours auto-publish IF voice drift is under 30 AND brand_rules pass
6. Items with voice drift 70+ NEVER auto-publish, hold indefinitely
7. Robert's role: edit drafts, fix automation that produced the issue, escalate edge cases
8. Dr. DNicole's role: approve voice/tone/positioning calls, comment on strategic angles
9. Brain auto-monitor role: monitor queue depth, alert if backlog exceeds 8 items (legacy line named a teammate who departed in early 2026; the function persists, the named role does not)