Google Ads Consolidation & Website Migration — 2026-04-05
Overview
Status check from a Mark / Sebastian sync on two parallel Cordwainer workstreams: consolidating duplicate Google Ads accounts and completing the website migration to the agency's WP Engine server. Both items surfaced in the same meeting that covered [1].
Google Ads Consolidation
Problem
Cordwainer has two active Google Ads accounts — one set up by a previous agency, one provided to the current team. The legacy account was still sending asset-disapproval and campaign-disapproval emails to the client, causing confusion.
Current State
- Sebastian obtained access to the legacy account during this meeting cycle.
- Conversion tracking had already been configured in the newer account; that work will need to be reconciled with the legacy account's historical data.
Plan
- Use historical performance data from the legacy account to inform a new "memory care" lead-generation campaign.
- Consolidate all active work into a single account; the legacy account will be retired.
- Sebastian is coordinating campaign structure with Gilbert (Cordwainer contact).
Open Items
- [ ] Confirm which account becomes the canonical account and migrate/archive the other (@Sebastian)
- [ ] Verify conversion tracking is correctly set up in the active account (@Mark)
Website Migration
Current State
| Dimension | Detail |
|---|---|
| Completion | ~80% |
| Environment | Staging (WP Engine) |
| Remaining work | ~4–5 pages (About, Contact, and similar non-SEO pages) |
| Estimated launch | 2–3 weeks from meeting date |
All content changes are being made on the staging site. The plan is to finalize copy, implement it on staging, then do a single push to production — avoiding piecemeal publishing and the artifact URL problems that come with it.
Blocker: Incorrect DNS A Record
The primary domain's A record in Cloudflare still points to the old server. The name servers were previously updated (Sebastian and Mark worked through GoDaddy together on an earlier call), but the A record was not corrected at that time.
Resolution plan:
1. 3–4 days before launch, Mark will update the Cloudflare DNS to add two A records and a CNAME pointing to the WP Engine server.
2. WP Engine's staging-to-production push automatically replaces all instances of the staging domain with the production domain, eliminating artifact URLs.
3. A working meeting between Mark and Sebastian is required at cutover to ensure no critical services are disrupted.
DNS Records Requiring Attention
During the meeting, Mark reviewed the Cloudflare account and flagged the following records for investigation before cutover:
| Record | Notes |
|---|---|
| A record (root) | Currently points to old server — must be updated |
| MX records | Routing through Barracuda firewall — must be preserved; Barracuda destination may need updating |
selector1 / selector2 |
Likely DKIM keys for an email provider — confirm which provider before touching |
paylinks.commerce.godad… |
Possibly a GoDaddy payment link; no payment functionality is expected on the new site — investigate before launch |
| Outlook / verification TXT records | Appear to be Microsoft 365 domain verification — leave in place |
Note: Sebastian should confirm whether Cordwainer uses a separate email platform (beyond MailChimp for campaigns) and whether the Barracuda MX record destination needs to change after migration.
Open Items
- [ ] Finalize remaining ~4–5 pages of copy this week (@Sebastian / Eshock)
- [ ] Implement final copy on staging next week (@Eshock)
- [ ] Identify Cordwainer email provider; confirm selector records and Barracuda MX destination (@Mark)
- [ ] Investigate
paylinks.commerce.godadrecord — determine if any active service depends on it (@Mark / @Sebastian) - [ ] Schedule cutover working meeting ~3–4 days before launch (@Sebastian + @Mark)
- [ ] Update Cloudflare A records and CNAME at cutover (@Mark)
Related
- [2]
- [3]