Shared Reference — Creative × Growth × Engineering

Website Backend Infrastructure

The systems that power every page a patient ever sees.

Prepared for: Mike — VP of Creative From: Dakota Milner, Growth Date: April 20, 2026 Scope: 260 SGA practices

The Point in 3 Bullets

  • A website is a system, not a file. Design is one layer. Hosting, DNS, SEO, analytics, and embeds are the layers underneath that make the design actually work for patients and search engines.
  • Scaling to 260 practices needs one builder, not 260 sites. Every decision here gets made once and applied everywhere — that's the multiplier.
  • Creative designs the template. The backend does the rest 259 times. When we pick the right infrastructure, one design ships to every practice automatically.

The 7 Layers of a Website Builder

One sentence each · what it means for SGA
1

Hosting

The servers that store the site files and send them to visitors.

For SGA: one platform serving all 260 practices, not 260 separate accounts.

2

Domain & DNS

The address (valdostafamilydental.com) and the switchboard that routes it to the server.

For SGA: centralize 260 domains under one registrar to kill renewal risk.

3

Site Structure

Sitemap.xml, robots.txt, URL patterns — how search engines find and rank pages.

For SGA: one URL convention across the portfolio = compounding SEO authority.

4

Programmatic SEO

One template × a data table = hundreds of ranked pages per practice.

For SGA: Creative designs once; the builder generates for every service × every city.

5

Analytics & Tags

GA4 + Google Tag Manager to measure what patients do and which channels work.

For SGA: one tag container standard so we compare practices apples-to-apples.

6

Embeds & Integrations

iframes, booking widgets, maps, chat — the vendor tools that make a site convert.

For SGA: approved widget list; one booking integration, one chat, one review display.

7

Publishing Workflow

How a design change gets previewed, approved, published, and rolled back.

For SGA: Creative edits copy/imagery directly; structural changes gated by Growth.

How a Website Actually Works — Two Flows, One System

Left: how a patient's visit reaches our page in milliseconds. Right: how a Creative change gets from Figma to live across 260 practices.

Flow A · Patient Visit (≈2 seconds) 1 Patient searches or types URL e.g. "dentist valdosta ga" or valdostafamilydental.com 2 DNS lookup Domain translates to server IP via Cloudflare DNS 3 CDN + hosting respond Nearest edge server sends cached HTML, images, fonts 4 Page renders in browser Design loads · embeds (map, booking) fire · widgets attach 5 Analytics & tracking fire GA4 + GTM record visit · source · events · conversions 6 Patient converts Books appointment · calls · gets directions · submits form Flow B · Publishing a Design Change 1 Creative designs template Figma · hero, CTAs, FAQ blocks, imagery, copy 2 Template becomes a component Engineering wires variables: {service}, {city}, {practice} 3 Data table fills the variables Services × cities × 260 practices = thousands of pages 4 Builder generates & previews Staging URL · Creative & Growth review · sign off 5 Publish to production One click · sitemap regenerates · CDN cache purges globally 6 Live across 260 practices Rollback available in < 60 seconds if anything breaks

Read this chart like this

  • Flow A tells Creative why small backend details matter — every layer adds milliseconds, and every millisecond changes conversion.
  • Flow B tells Creative why the builder matters — without it, every change is 260 manual updates instead of one.
  • The same builder is on both sides. Getting it right is what makes SGA's portfolio scale without exploding the creative team's workload.

Ten Decisions the Builder Must Answer

One-pager version · use this to shortlist vendors or scope in-house
  1. Hosting platform. One platform across all 260 practices, or per-site? What's the uptime SLA?
  2. Domain & DNS ownership. Consolidated under SGA, or inherited per acquisition?
  3. URL convention. What's the pattern for services, locations, and programmatic pages? Locked once, forever.
  4. Sitemap automation. Is sitemap.xml auto-generated on every publish and submitted to Google Search Console?
  5. Robots.txt standard. Does every site keep staging, admin, and thank-you pages out of Google's index?
  6. Programmatic SEO engine. How does it consume the service × city data table? Who maintains it?
  7. Analytics container. Is there one GTM container per site with standard event names across the portfolio?
  8. HIPAA-compliant forms. Where does patient-submitted data land? Do we have BAAs with every vendor?
  9. Preview · Publish · Rollback. What's the Creative edit flow? How fast can a bad publish be reverted?
  10. Access control. Who can change what — Creative, Growth, Engineering, practice managers?

Any builder we pick — custom or off-the-shelf — should have a clean answer to these ten. The clearer the answers, the more the design system scales without extra creative lift per practice.

Deep Dive

Open any section for detail · skip what you already know
1Infrastructure · Hosting, DNS, SSL, CDNWhere the site physically livesOpen

Hosting

Every page, image, and font sits on a server. Hosting decides speed, uptime, and cost.

  • Static (Vercel, Netlify, Cloudflare Pages) — fast, cheap, ideal for marketing sites.
  • Managed WordPress (WP Engine, Kinsta) — if we need a CMS editor.
  • Self-hosted (AWS, Railway) — full control, more engineering lift.
SGA fit: static hosting, one build pipeline for 260 sites.

Domain & DNS

The domain is the address. DNS is the switchboard routing that name to our server's IP.

  • Registrar — where the domain is bought (GoDaddy, Cloudflare).
  • Nameservers — who controls the records.
  • Records — A / CNAME (website), MX (email), TXT (verification, SPF/DKIM).
SGA fit: centralize 260 domains under one registrar + Cloudflare DNS.

SSL / HTTPS

The lock icon. Encrypts connections, protects trust, and is a Google ranking signal.

  • Auto-renewed via Let's Encrypt through the host.
  • Must cover root + www subdomain.
  • Mixed content (HTTP on HTTPS) breaks the lock.

CDN

Cached copies of the site on servers around the country so every patient loads from nearby.

  • Bundled with modern hosts (Vercel, Cloudflare).
  • Matters most for images and video.
2Site Structure · Sitemap, robots.txt, URLs, homepageHow search engines see the siteOpen

Sitemap.xml

A machine-readable list of every indexable page. Google crawls this first. Missing or broken sitemaps are the #1 reason pages don't rank.

  • Auto-generated on every publish.
  • Includes last-modified date and priority.
  • Submitted once per domain to Google Search Console.

Robots.txt

Tells crawlers where they can't go. Keeps staging, admin, and thank-you pages out of Google.

# valdostafamilydental.com/robots.txt
User-agent: *
Disallow: /admin/
Disallow: /thank-you/
Sitemap: https://valdostafamilydental.com/sitemap.xml

URL Strategy

URLs are read by humans and search engines. Good ones match the page's topic.

  • ✅ /services/dental-implants-valdosta
  • ❌ /page?id=4821&ref=nav
  • Lowercase, hyphens not underscores, no trailing junk.
  • Never change a published URL without a 301 redirect.

Homepage Role

The homepage is the #1 entry point for branded search and the page Google trusts most. Three jobs, fast:

  • Answer "am I in the right place?" in 2 seconds.
  • Push to the next step (book, call, map).
  • Link to every important service page — SEO authority flows downhill.
3Programmatic SEO · One template × data = hundreds of pagesHow we ship at 260-practice scaleOpen

Instead of writing each page by hand, Creative designs one template per page type ("Service in City"). The builder merges that template with a data table to generate thousands of unique, indexable pages — each one targeting a real search like "dental implants in Thomasville GA."

1 · Template (Creative)

Hero · benefits · FAQs · CTA · NAP block · map embed. Designed once, styled per brand kit.

2 · Data (Growth)

Services: implants, Invisalign, whitening, crowns… Cities: Valdosta, Tifton, Thomasville, Moultrie…

3 · Pages (Builder)

implants-in-valdosta, implants-in-tifton, invisalign-in-thomasville… hundreds per practice.

Creative owns the template, photography, copy blocks, CTAs. Growth owns the data table and keyword targeting. The builder owns page generation, internal linking, and sitemap inclusion.
4Analytics & Tracking · GA4, GTM, conversionsKnowing what patients actually doOpen
ToolWhat it doesWhere it livesOwner
Google Analytics 4Traffic, sources, on-site behavior by page.Single tag in <head>Growth
Google Tag ManagerOne container that loads every other tag (GA4, Meta Pixel, call tracking) without touching code.Single script in <head>Growth
Meta PixelTracks patients from Facebook/Instagram ads through to booking.Fired via GTMPaid Media
Google Search ConsoleSearch queries per page, indexing issues, rankings.Verified per domainGrowth
CallRailDynamic phone number swapping by traffic source.JS via GTMGrowth
Conversion eventsbooking_submit · phone_click · directions_click · form_submit — same names across all 260 sites.GTM triggersGrowth
What this means for Creative: every button, form, and phone link on every template needs a predictable hook (e.g. data-cta="book-now") so tracking works the same way on every site. The markup convention lives inside the design system.
5Embeds & Third-Party Tools · iframes, widgets, formsEverything that's not "ours"Open

iframe

A window into another site — Google Maps, YouTube, a vendor's booking calendar.

  • ✅ Maps, video, third-party schedulers.
  • ❌ Don't put core content in an iframe — Google can't index it.
  • Must be responsive (percentage width).

Widgets

Chat bubbles, review carousels, booking buttons — usually a single script tag.

  • Loaded via GTM so we can toggle per practice.
  • Audit quarterly — every widget adds weight.

Forms & HIPAA

Any form collecting name + health info is potentially PHI. The backend decides where it goes.

  • No PHI in GA4 or Meta Pixel.
  • Forms route to a HIPAA-compliant inbox or PMS integration.
  • Every vendor needs a signed BAA.
6Publishing Workflow · Staging, publish, rollbackHow a change goes live safelyOpen
Draft / StagingEvery change lives on a preview URL (staging.valdostafamilydental.com). Blocked from Google via robots.txt, password-protected. Creative reviews here.
PublishOne-click promotion from staging to production. Sitemap regenerates. CDN cache purges globally.
RollbackEvery publish is versioned. Revert to last known-good build in < 60 seconds — no backup restore needed.
RedirectsWhen a URL changes or page retires, the builder writes a 301 redirect. Old Google results and patient bookmarks still work.
Access controlCreative: copy & imagery. Growth: tags, redirects, structural changes. Engineering: hosting & DNS.