Field Notes replace the blog.
Same words, instrumented better, hosted on GHL.

Old framing vs new framing

The seven concurrent jobs

If a Field Note does not serve all seven, it is not yet a Field Note.

The stack

Registrar / DNS

Squarespace (record points at GHL)

Website hosting

GoHighLevel (GHL)

Field Notes / 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 /field-notes/2026/04/[slug]/ are not supported by GHL Blog out of the box. We use:

FINAL URL PATTERN
https://iexdg.com/field-notes/[slug]/

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

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

Per-week production cycle

Depth alternation per month

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

Output per month: 4 podcast episodes, 4 Field Notes (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 Field Note 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)

Field Note 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 Field Note)

<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 Field Note 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 Field Note 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 Field Note)

Granular topic tags (curated, controlled vocabulary)

Choose 3-6 per Field Note. 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 Field Note">
</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 Field Note">
</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 Field Notes)

• 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+ Field Notes, 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 Field Notes targeting the term.
5. Cease-and-desist template ready in OPERATIONS/legal/ with attorney review on file. Activated if Cultiv8tiv US enters with confusingly similar mark.
6. Anchor terms in Field Notes: 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              →  /field-notes/why-training-fails-without-architecture/   301
/blog/old-take-on-leadership          →  /field-notes/                                            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 Field Notes 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 Field Notes. Same voice.
Deeper format. Hosted on iexdg.com/field-notes.

Why the change:

  Field Notes are research-grade companions to the new IEXDG Podcast.
  Each podcast episode produces one Field Note. 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
    Field Note 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 Field Notes.

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 Field Note: [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 Field Notes/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 Field Notes, 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)
• ❌ Field Notes hosted off iexdg.com
• ❌ Field Notes without companion podcast episode
• ❌ Field Notes without instrumentation events
• ❌ Field Notes without lead magnet attached
• ❌ Field Notes 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. Hannah Baldwin's role: monitor queue depth, alert if backlog exceeds 8 items