From localhost to the world.

# ROLE · WORLD-CLASS PANEL
  - Guillermo Rauch — modern DNS + custom domain UX
  - Julia Evans (Wizard Zines) — DNS + TLS explained clearly
  - Troy Hunt (HIBP) — HTTPS + HSTS · security posture

# CONTEXT
Use primed P00 (target domain from context). Stack: Lovable native domain
connection · no manual server config. If I haven't purchased a domain yet ·
guide me.

# GOAL
Get me from "lovable.app/xyz" to "https://[my-domain]" with valid TLS ·
www → apex redirect (or reverse) · verified.

# YOUR PROCESS · 5 stages

STAGE 1 · DOMAIN PURCHASE (5 min · skip if I have one)
Ask ONE question:
  "Do you have a domain already? If yes · which registrar? If no · I recommend:
    (a) Cloudflare Registrar (at-cost pricing · best DNS UX)
    (b) Namecheap (cheap · simple)
    (c) Porkbun (cheapest first year · quirky UX)
   Which do you want to use?"

If purchasing new · walk step-by-step:
  - Search for [my-product].com · .app · .io · .co in that order of preference
  - Avoid hyphens · numbers · foreign TLDs unless brand-specific
  - Turn ON WHOIS privacy (free at Cloudflare · $8 at Namecheap)
  - Enable auto-renewal
  - Confirm purchase

STAGE 2 · LOVABLE DOMAIN CONNECTION (3 min)
In Lovable:
  1 · Project Settings → Domains → Add custom domain
  2 · Enter [my-domain].com
  3 · Lovable shows you 2 required DNS records:
     · A record: @ → [Lovable IP shown in UI]
     · CNAME record: www → [Lovable subdomain shown]
  4 · Copy both

STAGE 3 · DNS RECORDS AT REGISTRAR (3 min)
Guide me to registrar's DNS panel:
  Cloudflare: Domain → DNS → Records → Add record
  Namecheap: Domain List → Manage → Advanced DNS → Add New Record
  Porkbun: Domain → DNS → Add

Add:
  Type: A     · Host: @    · Value: [Lovable IP]        · TTL: 300 (5 min)
  Type: CNAME · Host: www  · Value: [Lovable subdomain] · TTL: 300

If Cloudflare · set proxy status to \"DNS only\" (grey cloud) for first setup ·
switch to proxied (orange cloud) after TLS is confirmed working.

STAGE 4 · TLS + VERIFICATION (3 min)
Wait 2-5 minutes for DNS propagation. Then:
  1 · In Lovable Domains panel · click \"Verify\"
  2 · Lovable auto-provisions Let's Encrypt cert (no manual TLS config)
  3 · Test both variants:
     · https://[my-domain] — should load with green lock
     · https://www.[my-domain] — should redirect to apex (or reverse)
     · http://[my-domain] — should auto-upgrade to HTTPS
  4 · Add HSTS header via Lovable prompt:
     <meta http-equiv=\"Strict-Transport-Security\"
           content=\"max-age=31536000; includeSubDomains\">

STAGE 5 · UPDATE ALL OG + CANONICAL URLS (1 min)
Lovable chat prompt: \"Replace every hardcoded lovable.app URL in my code with
https://[my-domain]. Include og:url · twitter:url · canonical link tags ·
sitemap URLs · robots.txt sitemap reference.\"

# DELIVERABLE
- Domain purchased with WHOIS privacy + auto-renewal
- A + CNAME records added at registrar
- TLS certificate active · green lock
- www → apex redirect (or reverse) working
- HSTS header set
- All internal URLs updated to custom domain

# QUALITY BAR
- Rauch: does BOTH www AND apex work · no dead ends?
- Evans: did I explain what an A vs CNAME record does · or just tell them to paste?
- Hunt: HSTS active · no mixed content warnings?

# ROLE · WORLD-CLASS PANEL
  - John Mueller (Google) — what Search actually cares about
  - Aleyda Solis — indie sitemap patterns · under-the-radar wins

# CONTEXT
Use primed P00. Domain live from P04. Stack: Lovable + GitHub + Cowork.

# GOAL
Ship robots.txt + sitemap.xml + verify in Google Search Console + submit
sitemap for fast indexing.

# YOUR PROCESS · 4 stages

STAGE 1 · ROBOTS.TXT (2 min · via Lovable)
Ask ONE question: "Any routes that should NOT be indexed? (e.g. /admin · /debug ·
/dashboard · /pricing-experimental)"

Then Lovable prompt:
  \"Create public/robots.txt with:

  User-agent: *
  Allow: /
  Disallow: /admin
  Disallow: /api
  [Disallow: any private routes I named]

  Sitemap: https://[my-domain]/sitemap.xml\"

STAGE 2 · SITEMAP.XML (2 min · via Lovable)
Lovable prompt:
  \"Generate public/sitemap.xml listing every public route with:
   - <loc> = absolute URL (my-domain)
   - <lastmod> = today's ISO date
   - <changefreq> = weekly for marketing pages · monthly for legal
   - <priority> = 1.0 for landing · 0.8 for main routes · 0.5 for legal

   Include ONLY publicly accessible routes. Exclude anything in robots.txt Disallow."

STAGE 3 · GOOGLE SEARCH CONSOLE SETUP (4 min)
Walk me through:
  1 · Open search.google.com/search-console
  2 · Add property → Domain property (recommended · covers www + apex + subdomains)
  3 · Enter [my-domain] (no https · no path)
  4 · Google shows a TXT record to add
  5 · Add at registrar DNS:
     Type: TXT · Host: @ · Value: google-site-verification=[token]
  6 · Wait 2 min · click Verify

STAGE 4 · SUBMIT SITEMAP (2 min)
In Search Console:
  1 · Left sidebar → Sitemaps
  2 · Enter: sitemap.xml
  3 · Submit
  4 · Should say "Success" within 30 sec
  5 · First indexing usually within 24-48 hours (vs 2 weeks unassisted)

Bonus:
  - URL Inspection tool → paste homepage URL → click "Request Indexing"
     · pushes Google to crawl immediately
  - Repeat for your top 3 landing pages

# DELIVERABLE
- robots.txt live at /robots.txt
- sitemap.xml live at /sitemap.xml
- Google Search Console verified (TXT record method)
- Sitemap submitted · showing "Success"
- Top 3 URLs manually requested for indexing

# QUALITY BAR
- Mueller: is my sitemap actually accurate · or listing routes that 404?
- Solis: did I use Domain property (not URL prefix) · so future subdomains work?

# ROLE · WORLD-CLASS PANEL
  - Addy Osmani (Google Chrome) — Core Web Vitals authority
  - Harry Roberts (CSS Wizardry) — practical web performance
  - Ilya Grigorik — HTTP/2 · resource prioritization

# CONTEXT
Use primed P00. Deployed at custom domain from P04. Stack: Lovable + GitHub +
Cowork. Chrome DevTools open on my laptop.

# GOAL
Run Lighthouse on mobile + desktop · identify all Core Web Vitals issues ·
produce paste-ready Lovable fix prompts.

# YOUR PROCESS · 4 stages

STAGE 1 · RUN LIGHTHOUSE (3 min)
Walk me through:
  1 · Open https://[my-domain] in Chrome incognito (no extensions)
  2 · DevTools (⌘⌥I / F12) → Lighthouse tab
  3 · Categories: check Performance · Accessibility · Best Practices · SEO
  4 · Device: MOBILE first (that's what Google ranks on)
  5 · Click "Analyze page load"
  6 · Wait ~30 sec · screenshot the 4 scores
  7 · Also run for DESKTOP · compare

STAGE 2 · TARGET THRESHOLDS
Green zone (aim for all four):
  Performance:    ≥ 90 mobile · ≥ 95 desktop
  Accessibility:  ≥ 95
  Best Practices: ≥ 95
  SEO:            = 100 (should be trivial after P03)

Core Web Vitals (green):
  LCP (Largest Contentful Paint): < 2.5s
  CLS (Cumulative Layout Shift):  < 0.1
  INP (Interaction to Next Paint): < 200ms
  FCP (First Contentful Paint):   < 1.8s
  TBT (Total Blocking Time):      < 200ms

STAGE 3 · DIAGNOSE + FIX (8 min)
For EACH failing metric · Lighthouse shows "Opportunities" section. For the top
3 opportunities · produce a paste-ready Lovable prompt:

Common issues + fixes:
  · Images not optimized → "Convert all <img> tags to use loading='lazy' ·
                                     add width/height attributes to prevent CLS ·
                                     serve WebP with PNG fallback via <picture>"
  · Render-blocking CSS   → "Inline critical CSS · defer the rest with
                                     media='print' onload trick"
  · Unused JavaScript     → "Code-split routes with React.lazy + Suspense ·
                                     move analytics + non-critical JS to defer"
  · Font swap flash (FOUT) → "Add font-display: swap · preload primary font
                                     with <link rel='preload' as='font'>"
  · Missing alt text      → "Add descriptive alt to every <img> ·
                                     empty alt='' for decorative images"
  · Contrast fails        → "Bump all body text to 4.5:1 contrast minimum ·
                                     check via webaim.org contrast checker"

STAGE 4 · RE-RUN + VERIFY (2 min)
After Lovable applies fixes:
  1 · Re-deploy · wait for Lovable to build
  2 · Hard refresh in incognito (⌘⇧R)
  3 · Re-run Lighthouse
  4 · Compare · confirm scores climbed
  5 · If any category still red · loop back to STAGE 3

# DELIVERABLE
- Lighthouse scores ≥ target on mobile + desktop
- All Core Web Vitals in GREEN
- Screenshots saved for pre-launch checklist (P07)

# QUALITY BAR
- Osmani: did I test on mobile (Google's ranking target) · not just desktop?
- Roberts: are fixes surgical (biggest wins first) · not scattershot?
- Grigorik: is the largest image on the page > 200KB · and if so · why?