Deployment Operations
DonAshleyRealty.com Beverly Hills Platform Deployment Checklist
Use this page as the go-live operating checklist for launching donashleyrealty.com on Vercel, connecting DNS, activating webhook and Mailchimp lead capture, validating every form path, and preparing the site for SEO submission and local authority outreach.
Step 1
Pre-deployment code check
Start by confirming the project is production-ready before GitHub, Vercel, DNS, or automation changes are made. This prevents broken routes, incorrect branding, or missing lead-capture files from reaching the live domain.
Step 2
GitHub repository setup
Create a private GitHub repository and push the full project folder. Exclude node_modules, .next, and local runtime lead logs. Confirm the repository includes the operational handoff files and production API code.
| Required file | Purpose |
|---|---|
.env.example | Documents production environment variables. |
IMPLEMENTATION_README.md | Developer and deployment handoff. |
src/app/api/leads/route.ts | Lead capture API endpoint. |
src/lib/lead-integrations.ts | Webhook and Mailchimp integration logic. |
src/app/sitemap.ts | Canonical sitemap generation. |
src/app/robots.ts | Robots file with sitemap reference. |
Step 3
Vercel project setup
Import the GitHub repository into Vercel as a Next.js project. Deploy once with non-blocking integration settings before turning on strict webhook or Mailchimp failure handling.
| Setting | Value |
|---|---|
| Framework | Next.js |
| Install command | pnpm install |
| Build command | pnpm build |
| Output directory | Default Next.js output |
| Production branch | main |
Step 4
Production environment variables
Add these variables in Vercel under Project Settings → Environment Variables. Use .env.example as the source of truth, and keep private keys server-side only.
| Variable | Recommended launch value | Purpose |
|---|---|---|
NEXT_PUBLIC_SITE_URL | https://donashleyrealty.com | Public canonical site URL. |
LEAD_OWNER_NAME | Don Ashley | Internal lead owner. |
INTERNAL_LEAD_EMAIL | Your lead alert email | Internal routing email. |
LEAD_WEBHOOK_URL | Zapier or Make webhook URL | Sends every validated lead to automation. |
LEAD_WEBHOOK_REQUIRED | false | Keep false during launch QA. |
LEAD_WEBHOOK_TIMEOUT_MS | 7000 | Webhook timeout. |
DISABLE_LOCAL_LEAD_LOG | true after QA | Disables runtime JSONL logging in production. |
MAILCHIMP_API_KEY | Mailchimp API key | Server-side Mailchimp connection. |
MAILCHIMP_SERVER_PREFIX | Example: us21 | Mailchimp data center prefix. |
MAILCHIMP_AUDIENCE_ID | Audience/list ID | Target Mailchimp list. |
MAILCHIMP_REQUIRED | false | Keep false during launch QA. |
MAILCHIMP_DOUBLE_OPT_IN | false or true | Use based on email compliance preference. |
MAILCHIMP_ADD_ALL_LEADS | false | Adds only newsletter/report leads by default. |
MAILCHIMP_PHONE_FIELD | Optional | Maps phone to Mailchimp if field exists. |
MAILCHIMP_FORM_TYPE_FIELD | Optional | Maps form type to Mailchimp if field exists. |
MAILCHIMP_SOURCE_FIELD | Optional | Maps source page to Mailchimp if field exists. |
Step 5
Domain and DNS setup
Add the domain inside Vercel first, then update DNS at the domain registrar. Do not remove active email records such as MX, SPF, DKIM, or DMARC if email is already running on the domain.
| Record | Host | Type | Value | Notes |
|---|---|---|---|---|
| Apex domain | donashleyrealty.com | A | 76.76.21.21 | Use Vercel’s exact value if different in the dashboard. |
| WWW | www.donashleyrealty.com | CNAME | cname.vercel-dns.com | Redirect www to apex, or make www primary if preferred. |
Step 6
Lead automation setup
Create a Zapier or Make scenario using LEAD_WEBHOOK_URL. Every validated lead should keep form type, source, offer title, consent, and routing metadata so follow-up can be fast and properly segmented.
| Lead type | Routing action |
|---|---|
| Home valuation | Create hot seller lead, alert Don Ashley, create same-day follow-up task. |
| Consultation | Send booking/confirmation workflow, create CRM task, alert Don Ashley. |
| Report download | Send report link, tag by report, add to nurture. |
| Newsletter signup | Add to Mailchimp audience and Beverly Hills newsletter segment. |
| Press inquiry | Notify media contact and send press kit response. |
| Advertiser or directory inquiry | Send media kit and create partner follow-up task. |
Speed-to-lead rule
Home valuation and consultation submissions are hot leads. The workflow should alert Don Ashley immediately, create a CRM task, and start a short confirmation sequence without waiting for manual review.
Step 7
Mailchimp QA
Submit newsletter and market-report test leads before launch. Confirm contacts, tags, source data, and duplicate-email behavior are correct before adding traffic or promoting the newsletter.
| Test | Expected result |
|---|---|
| Newsletter form | Contact added to Mailchimp with newsletter tag. |
| Market report form | Contact added with report/source tags. |
| Consultation form | Does not enter newsletter nurture unless MAILCHIMP_ADD_ALL_LEADS=true. |
| Duplicate email | Updates existing record without losing original attribution. |
Step 8
Live site QA
After Vercel deployment and DNS propagation, check every public operational route on the live domain. The sitemap and robots files must resolve before submitting the site to search tools.
| URL | Verification |
|---|---|
https://donashleyrealty.com/ | Homepage loads correctly. |
https://donashleyrealty.com/press | Press page loads. |
https://donashleyrealty.com/real-estate | Real estate lead funnels load. |
https://donashleyrealty.com/crm-email-setup | CRM setup documentation loads. |
https://donashleyrealty.com/deployment-checklist | Deployment checklist loads. |
https://donashleyrealty.com/sitemap.xml | Sitemap resolves. |
https://donashleyrealty.com/robots.txt | Robots file references sitemap. |
Step 9
Form testing
Submit one test from every major form path. Do not start paid traffic, backlink outreach, or sponsor sales until webhook, CRM, and Mailchimp routing are confirmed end-to-end.
| Form | Required QA |
|---|---|
| Newsletter | Confirms Mailchimp add/tagging. |
| Home valuation | Confirms webhook, hot-lead routing, alert, and CRM task. |
| Consultation | Confirms booking/consultation workflow. |
| Report download | Confirms content-offer attribution. |
| Submit event | Confirms non-real-estate inquiry routing. |
| Submit business | Confirms directory/advertiser routing. |
| Advertise | Confirms partner inquiry workflow. |
Step 10
SEO launch steps
Once the live site and forms are verified, submit the sitemap, check crawlability, and begin controlled publishing and relationship-based local outreach. Replace any placeholder data with verified Beverly Hills source data before broad promotion.
| Task | Purpose |
|---|---|
Verify donashleyrealty.com in Google Search Console. | Gives access to indexing and performance data. |
Submit /sitemap.xml. | Helps Google discover launch pages. |
Check index coverage after launch. | Confirms crawlability. |
Replace placeholder metrics with verified Beverly Hills data. | Improves trust and compliance. |
Begin backlink outreach using the workbook. | Builds legitimate local authority. |
Go-live sequence
Deploy, connect, test, then promote
Deploy the site first, connect donashleyrealty.com, test lead forms, activate automation, submit the sitemap, then begin promotion. This keeps the revenue engine ready before audience-building campaigns start.