←→ navigate
WordPress Hartford CT · March 2026

Launching Your
WordPress Website

Everything that needs to go right — before, during, and after.

Before Launch Launch Steps Post-Launch

Covering SEO considerations · new vs. replacement · DNS & hosting · content migration · error monitoring · forms, email deliverability, accessibility, and more.

Hosted by Ray & Peter I. · wordpresshartford.com
02
Step Zero

Decide Your Launch Type First

Every decision downstream — redirects, DNS, email, SEO, rollback — depends on which scenario you’re in. Set this before you do anything else.

🆕
Brand-New Site
New domain
Focus: indexing, analytics, SMTP, social promotion, DNS setup. Less SEO risk since there’s nothing to preserve.
🔄
Redesign
Same domain
Focus: SEO preservation, redirect map, content freeze, rollback plan. Existing rankings are at risk.
🚚
Migration
New domain or host
Focus: everything — DNS, email DNS (MX/SPF/DKIM), redirects, credentials, staging cleanup.
Rollback plan: Write it down before you start. Know whether you’ll re-point DNS, restore a backup, or both — and who can authorize it.
03
Before Launch

Content & Cleanup

  • Remove placeholder & demo contentNo “Lorem ipsum,” Hello World post, sample pages, test CTAs, or dummy images.
  • Finalize menus, footer links & internal navigationNo dead ends. Breadcrumbs, related links, and footer all intentional.
  • Review & remove unused plugins/themesUnused = security risk + performance drag. Update everything you keep.
  • Clean up post revisions, trash & unused mediaReduces DB bloat. Do carefully if you rely on revision history.
  • Clean up admin users & enforce least privilegeRemove old accounts. Only true admins should have admin access.
  • Media sanity checkFix missing images. Compress large files. Confirm alt text on key images.
  • Confirm key integrations listForms, CRM, email marketing, payments, maps, calendars, embeds, memberships.
04
Before Launch

Migration & URL Correctness

  • Migration fully verifiedNot just “import ran” — confirm pages, posts, media, forms, users & settings all made it.
  • Database search & replace completed Better Search Replace WP-CLIReplace staging/dev URLs with production URLs. Beware serialized data — use a plugin, not a raw SQL REPLACE.
  • Hardcoded links auditedButtons, image src, PDFs, CSS @import, embeds — all pointing to production.
  • Dev/staging dependency testTemporarily block or disable the dev domain and confirm nothing on the live site breaks.
  • Block editor / FSE template parts confirmedHeader, footer, sidebar template parts work on all page types. Synced patterns intact.
  • Local fonts installed (not Google Fonts)Improves privacy, eliminates external DNS lookup, speeds page load.
WP-CLI tip: wp search-replace 'staging.example.com' 'example.com' --all-tables — add --dry-run first.
05
Before Launch

DNS, Hosting & Email

DNS & Hosting

  • DNS change plan documentedNameservers vs A/CNAME — know exactly what you’re changing and where it’s managed.
  • Lower DNS TTL (24–48 hrs ahead)Helps propagation happen faster when you flip records. Set to 300–600 seconds.
  • SSL certificate readyHTTPS must be live from minute one. Avoid mixed content issues from launch.
  • Server health checkPHP version, memory limits, disk space, TLS support — confirm nothing needs upgrading.
  • Caching strategy confirmedKnow what cache layers exist (plugin, host, CDN) and exactly how to purge each.

Email (Don’t Skip)

  • MX records confirmedDNS changes can silently break domain email for 24–48 hours if MX isn’t preserved.
  • SPF / DKIM / DMARC presentPrevents form emails and transactional mail from going to spam.
  • SMTP configured for WordPress WP Mail SMTP FluentSMTPContact forms and password resets must actually deliver. Default WP mail often doesn’t.
  • New email addresses created + forwarding setConfirm contact@, info@, etc. route correctly.
  • Test emails land in inboxSend to at least 2 destinations (e.g., Gmail + Outlook) and confirm not spam.
06
Before Launch · SEO

SEO Essentials (Critical for Redesigns)

  • On-page SEO complete for key pages Yoast Rank MathTitles, meta descriptions, H1/H2, alt text, internal links — all key pages done.
  • Redirect map finalized (old → new)Every removed or renamed URL gets a 301 to its best replacement. Import via plugin CSV.
  • Staging site confirmed as blocked from indexing“Discourage search engines” ON for staging. Staging should never be indexed.
  • Canonical strategy confirmedPages point to themselves. Especially http vs https, www vs non-www — pick one and stick to it.
  • XML sitemap confirmed reachableSitemap exists, is correct, and will be live at /sitemap.xml (or equivalent) immediately post-launch.
  • robots.txt plan reviewedNo pages you want indexed are accidentally blocked. Staging block won’t carry over.
  • Structured data / schema where relevantOrganization, breadcrumbs, articles, FAQs, products — only where genuinely appropriate.
07
Before Launch

Security & Compliance

Security Hardening

  • Strong passwords + 2FA where possibleAdmin accounts especially. Use a password manager.
  • Login attempt limiting active Limit Login Attempts Wordfence
  • File editing disabled in wp-adminAdd DISALLOW_FILE_EDIT to wp-config.php
  • SSL enforced in wp-config.phpFORCE_SSL_ADMIN true
  • Review forms + data handlingWhere does form data go? How is it stored? Who can access it?

Privacy & Accessibility

  • Cookie/consent notice configuredMust match reality — analytics, embeds, ads all trigger consent requirements.
  • Privacy Policy updatedReflects what you actually collect and which third parties are involved.
  • Accessibility Statement publishedEspecially for organizations, educational institutions, or public-sector clients.
  • Accessibility quick passKeyboard nav, focus states, color contrast, heading hierarchy, form labels, skip link.
  • reCAPTCHA / anti-spam on forms Turnstile Akismet
08
Before Launch · Final Testing

Performance & Final Preflight Testing

Performance Baseline

  • Speed test key pages PageSpeed Insights GTmetrixMeasure before launch. Fix big regressions — don’t let launch be the baseline.
  • Images compressed + WebP/AVIF servedSingle biggest quick win on most sites. Use a plugin or build-time optimization.
  • Caching confirmed and tested WP Rocket LiteSpeed CacheVerify cache is serving and you know how to purge it completely.
  • Broken link scan on staging Screaming FrogCatch 404s before users do.

Preflight Test Checklist

  • Test in incognito modeAvoid cached / admin-only views hiding real problems.
  • Test in Chrome, Firefox, Safari & Edge + mobileCheck responsive breakpoints on real devices, not just dev tools.
  • Test on a mobile hotspotDifferent network surfaces DNS issues and caching edge cases.
  • Forms tested end-to-endSubmit → confirm notification → confirm CRM/inbox delivery. On staging.
  • Rollback plan written downWritten. Not in your head. Includes who can authorize it.
09
Launch Steps

Go-Live Sequence

A · Safety First

  • Full backup of current live site UpdraftPlus DuplicatorFiles + database. Confirm you know exactly where it’s stored.
  • Snapshot of the new build pre-launchSo you can revert within the new environment too, not just back to the old site.
  • Content freeze beginsStop edits on the old site right now. No two sources of truth.

B · Deploy / Switch

  • Deploy using your planned methodStaging push, migration plugin, or manual — avoid improvisation at go-live.
  • Confirm WP_HOME / SITEURL are correctNo staging URLs remaining in WP settings or database.
  • SSL active + force HTTPSAll pages load without mixed content warnings. Redirect http→https.

C · WordPress “Make It Work”

  • Save permalinks onceFlushes rewrite rules. Fixes many mysterious 404s that appear right after launch.
  • Purge ALL cachesPlugin cache + host/server cache + CDN cache. Visitors must see the new site immediately.
  • Confirm file permissions/ownershipPrevents upload failures and reduces security exposure.

D · SEO “Turn On”

  • Uncheck “Discourage search engines…” on productionLive site must be indexable. Easy to forget, hard to undo the SEO damage.
  • Enable 301 redirects from your redirect mapEspecially top traffic pages and any renamed or removed sections.
  • Confirm robots.txt + sitemap reachableNo accidental global disallow. Sitemap accessible at expected URL.
10
Launch Steps · DNS

DNS Cutover

DNS is where most surprises live. Prepare carefully and monitor actively.

01
Choose your DNS change method
Nameservers: Transfer full DNS control to new host — simpler but slower (24–48hr TTL).
A/CNAME records: Point specific records to new IP while keeping DNS at registrar — more surgical, faster propagation if TTL was pre-lowered.
02
Update DNS records at your registrar
Implement your planned A/AAAA/CNAME changes. Also add or preserve any TXT records (domain verification, SPF) and MX records (email routing). Do not delete MX records.
03
Monitor propagation actively
Use whatsmydns.net or dnschecker.org to watch propagation across regions. Expect split traffic — some visitors will hit the old site for a while. normal
04
Raise TTL back to normal once stable
After DNS is fully propagated and stable (24–48hrs), raise TTL back to 3600+ seconds to reduce DNS query load.
Common DNS disasters: Deleting MX records (kills all domain email) · Forgetting SPF/DKIM (forms go to spam) · Not waiting for propagation before declaring “it’s broken”
11
Post-Launch · First Hour

Smoke Test — Run Immediately

Do this on the live domain, in incognito, right after DNS/deploy. These are must-pass items — don’t move on until they’re green.

  • Home + top 10 pages load correctlyNo broken layout, no missing CSS, no missing hero images.
  • Navigation & footer links workDesktop and mobile menu. All links resolve. No dead ends.
  • Forms: submit + notification + delivery confirmedOn the live domain. CRM and inbox delivery verified, not just form submission.
  • Browser console cleanNo mixed content warnings, no blocked scripts, no major JS errors. (F12 → Console)
  • Custom 404 page works — begin logging missesVisit a random URL. Confirm your custom 404 page displays. Enable 404 log monitoring.
  • Ecommerce / booking / login testFull transaction path in test mode (checkout, booking, password reset, restricted content).
  • Check server error logs (first 30–60 min)PHP fatals, permission issues, timeouts. Catch these before users report them.
12
Post-Launch · Day 1 & Week 1

Monitoring, Analytics & Stabilization

Analytics & Search

  • GA4 / Tag Manager pageviews firingVisible within minutes of launch. Key events tracked (forms, purchases, signups).
  • Google Search Console verified + sitemap submittedSpeeds discovery of new/changed pages. Helps catch indexing errors quickly.
  • Confirm no accidental noindexImportant pages indexable. Canonicals look correct. Check Search Console coverage report.
  • Google Maps API billing confirmedIf using Maps embed with API key — confirm billing account and quota so maps don’t break.
  • Validate redirects on real trafficWatch 404 logs. Real-world traffic will find missed legacy URLs your redirect map didn’t cover.

Stabilize & Secure

  • Fix high-impact issues quicklySmall UX bugs kill trust right after launch. Prioritize forms, speed, broken layouts.
  • Automated backups confirmed runningScheduled, off-site, tested. Not “I’ll set that up later.”
  • Remove temporary admin accountsIf any were created for the launch process, remove them now.
  • Update external profilesSocial bios, Linktree, directories, Google Business Profile, email signatures.
  • Decommission old site safelyKeep an archive/snapshot. Cancel old hosting only after DNS is stable and redirects work.
13
Reference

Essential Tools by Task

Backups
  • UpdraftPlus
  • Duplicator Pro
  • All-in-One WP Migration
  • ManageWP
  • Host-native snapshots
SEO
  • Yoast SEO
  • Rank Math
  • AIOSEO
  • Redirection plugin
  • Google Search Console
Performance
  • WP Rocket
  • LiteSpeed Cache
  • PageSpeed Insights
  • GTmetrix
  • WebPageTest
Migration & DB
  • Better Search Replace
  • WP Migrate DB Pro
  • WP-CLI
  • Local by Flywheel
  • Duplicator
Email / SMTP
  • WP Mail SMTP
  • FluentSMTP
  • Postmark
  • SendGrid
  • Mailgun
Security
  • Wordfence
  • iThemes Security
  • Sucuri
  • Limit Login Attempts
  • Cloudflare (WAF/CDN)
DNS / Monitoring
  • whatsmydns.net
  • dnschecker.org
  • UptimeRobot
  • Better Uptime
  • Pingdom
Testing & Audit
  • Screaming Frog
  • WAVE (accessibility)
  • axe DevTools
  • Dead Link Checker
  • BrowserStack
14
Real-World Failures

What Actually Goes Wrong

These happen to experienced developers. Every one of these is preventable with the checklist.

💀
Mixed content breaks the entire site
Moved to HTTPS but forgot to run DB search/replace. Images load over HTTP. Browsers block them silently. Everything looks broken. Fix: search-replace + purge cache
📧
Contact forms deliver to no one
Default WordPress mail uses PHP mail — rejected by most modern servers. No error shown. Client doesn’t notice for weeks. Fix: SMTP plugin before launch
📮
DNS change kills domain email for 48 hours
Switched nameservers without preserving MX records. All email to the domain bounces until DNS propagates with corrected records. Fix: confirm MX before any DNS change
🔍
Site launches with “Discourage search engines” still checked
Staging setting carried over to production. Site is invisible to Google for days or weeks before someone notices. Fix: checklist item + Search Console immediate verify
🔧
DISALLOW_FILE_EDIT causes mysterious admin errors
Added the constant to wp-config.php but a plugin also tries to write files through the editor API. Confusing fatal errors on first login. Fix: test in staging, not production
💾
DB search/replace breaks serialized data
Raw SQL REPLACE on URLs inside serialized PHP arrays corrupts the data. Widget settings, theme options, plugin configs silently fail. Fix: always use Better Search Replace or WP-CLI
15
The Handoff

The Website Owner Guide

One of the most professionally differentiating things you can hand a client. Creates trust, reduces support calls, and makes ongoing ownership sane.

✏️
Content Editing
How to update pages, posts, images, and menus. Block editor basics. What not to delete.
👤
Users & Access
How to add/remove users. What each role can do. Who to contact for admin-level changes.
💾
Backups & Updates
Where backups live, how often they run, and what to do before updating plugins or core.
📬
Forms & Email
Where form submissions go. How to test. What to do if notifications stop arriving.
🗺️
Where Things Live
Hosting dashboard, DNS registrar, analytics, Search Console, domain renewal dates.
🆘
Support Contacts
Who to call for hosting, developer, domain, email — with URLs and account IDs.
16
Quick Reference

Your Launch Day Kit

Have these open before you touch a single DNS record or hit deploy.

Tabs / Logins Open

  • DNS registrar dashboard
  • Hosting control panel
  • WordPress admin (production)
  • DNS propagation checker (whatsmydns.net)
  • Error / server log view
  • Your redirect map / CSV
  • Test email inboxes (Gmail + Outlook)

Written Down & Ready

  • Rollback steps (exact, step by step)
  • Who can authorize a rollback
  • Where the backup is stored
  • Smoke test script (20–30 URLs to check)
  • Issues log template (time / issue / severity / owner)
  • Client / stakeholder contact list
  • Launch window + communication plan
WordPress Hartford CT · March 2026

Happy
Launching.

Every site launch that goes smoothly is the result of a hundred small decisions made before go-live. You now have the list.

Previous recordings: youtube.com/@hartfordwordpress
Slides & resources: hartfordwp.com
Questions to spark discussion
  • → What’s the most painful launch mistake you’ve made?
  • → Staging push vs. manual migration — what’s your workflow?
  • → How do you handle the Website Owner Guide?
  • → What’s your go-to SMTP setup?
Hosted by Ray & Peter I. · WordPress Hartford, CT