Focused Dental WordPress Build on a Live Site
Focused dental WordPress build on a live WP Engine site — 11 templates, 18 redirects, 40-item checklist, 39 hours over 38 days, no overrun.
Screenshots captured by automated tooling — some elements may not have loaded fully or may layer on top of each other. For the most accurate view, visit the live site →
Build the URLs across the agency's templates, wire the conversion primitive, then work the QA backlogs to closure.
Client (end user): Northern Westchester Dental Care — Yorktown Heights, NY
Engagement: White-label development for a US marketing agency
Delivered: September – November 2025 · 38 days · 39 hours across build, redirect reconciliation, and fix-and-feedback phases
The Craft of a Build
Eleven templates, 18 URL restructures, and a live WP Engine site that could not go down — a focused dental build delivered in 38 days and 39 hours to a US marketing agency. The new Service Lander, Doctor Pages, and About Us were constructed on password-protected, noindex test URLs while the existing site continued serving patients, and every legacy service path was reconciled against a 40-item launch checklist before any page was set to index.
This case study is a record of such a surgical build — delivered for a US marketing agency in the general-dental segment.
Snapshot
| Field | Value |
|---|---|
| End-client industry | Healthcare — General Dental |
| End-client | Northern Westchester Dental Care (Yorktown Heights, NY) |
| Engagement | White-label WordPress build for a US marketing agency specialising in local-business websites |
| Project Type | WordPress build with Elementor on WP Engine, executed on an existing live site with password-protected test URLs |
| Scope | Focused build — new Service Lander, Doctor Pages, and About Us built on noindex test URLs; 18 existing service URLs restructured and redirected; full site tracked across 126 URLs in the sitemap |
| Timeline | 38 days (30 Sep – 7 Nov 2025), with a 2-page refresh follow-on; delivered on schedule |
| Effort | 39 hours against a 39-hour estimate — no overrun |
| Team | 5 specialists (dev-heavy distribution appropriate for a focused build on a live surface with redirect discipline) |
| Templates | 11 reusable templates — the agency’s standard dental template library |
| Tech Stack | WordPress · Elementor · WP Engine · Rank Math · Site Checker (xaverPRO QA plugin) |
| Delivered | New Service Lander, Doctor Pages, and About Us built on test URLs; 18 URL redirect pairs reconciled; 40-item launch checklist closed; 34/46 SEO Issues Backlog + 1/3 CX Issues Backlog worked to Completed |
| Engagement cadence | 46 agency-raised issues · all closed by handoff |
| Review rounds | ≈7 review rounds across the 38-day calendar window |
| Per-ticket effort | 48 internal Redmine tickets · median 23m / P75 28m per ticket |
| Launch checklist | 39 items, signed off before cutover |
The Brief
A US marketing agency retained by Northern Westchester Dental Care — a general-dental practice in Yorktown Heights, New York — handed us a Google Sheets workbook with a full site inventory, a templates catalogue, a launch checklist, and pre-populated SEO and CX issues backlogs. The practice’s homepage was already live on their WP Engine environment; the page builder was Elementor. The source content for the doctor pages was sparse — limited biographical copy per provider — so practice-area descriptions were shared across all doctor profiles as a placeholder, to be replaced when the agency sourced expanded narratives. The ask was to build the remaining core pages (Service Lander, Doctor Pages, and About Us) on password-protected, noindex test URLs within the existing WordPress installation, reconcile 18 URL changes from the old service-path structure to the new location-based structure, and work through both QA backlogs until the agency accepted the site.
Risk Context. When a build touches a live production site, the agency’s exposure is not whether new pages can be built — it is whether the dev partner will treat the live surface as fragile. A redirect misconfiguration on an existing dental site does not announce itself with an error log; it announces itself when a patient clicks an old bookmark and lands on a 404. The risk is not in coding pages; it is in coding pages on a live host without breaking the URLs that patients and search engines already know. The brief for this engagement was structured around exactly that concern: password-protected test URLs, a 18-row redirect map, and two QA backlogs reviewed before any new page was set to index.
How We Did It
1. Eleven templates, focused build scope, one pipeline on a live site. The agency’s standard dental template library covered Homepage, About Us, Services Lander, Service Page, Doctor Page, Blog Lander, Blog, Smile Gallery, Contact Us, and Default Template. The build scope was deliberately narrow: construct the new Service Lander, Doctor Pages, and About Us on noindex test URLs within the existing WordPress installation, assigned to their templates from the sitemap row. No page was hand-rolled outside the template system. Building on password-protected test URLs within the live installation — rather than provisioning a separate staging environment — avoided the overhead of a staging-to-production migration for a focused three-page build, at the cost of requiring rigorous redirect discipline on the existing URL surface.
2. URL restructuring with redirect discipline across 18 unique pairs. The workbook’s sitemap carried 18 “URL Change” rows — existing service pages moving from /services/ paths to /yorktown-heights/ paths. We reconciled each old-to-new pair in the redirect table and verified the mappings against the live site. All 18 pairs were closed before the new pages were set to index.
3. Fix-and-feedback loop on a live surface. After the initial build, the agency opened rounds of reviewer feedback through their shared backlog. Issue #1230 (Review & Prioritize Backlog) and #1240 (Review Google Sheet Issues) covered pre-launch QA across meta data, button styles, FAQ blocks, and content gaps. Issue #1246 (Refresh 2 pages) addressed a follow-on refresh of two location-specific pages. The 46-row SEO Issues Backlog closed at 34 Completed (10 flagged After Release, 1 To Do, 1 in QA); the 3-row CX Issues Backlog closed at 1 Completed.
4. Pre-handoff verification on a site that could not go down. Before handing off, we ran our Site Checker pre-handoff QA pass — core settings, content and SEO surface, URL structure, content-language sanitization across pages and menus, and multi-resolution screenshots. For a build on an existing live site, the categories that matter most are exactly those: redirect correctness, slug consistency, and meta accuracy on both old and new URL surfaces. The pass confirmed the build was clean before the agency’s own post-handoff QA layer ran.
Building on password-protected test URLs within the live WP Engine installation — rather than a separate staging environment — meant the 18 redirect pairs had to be verified before any new page was set to index, not after. That ordering was the constraint. The fix-and-feedback loop ran on top of an already-clean redirect surface, which is why the backlog closed without a post-handoff URL regression.
Results
| Metric | Outcome |
|---|---|
| New pages built | Service Lander (1) · Doctor Pages (multiple) · About Us (1) on noindex test URLs within the existing live site |
| Templates applied | 11 / 11 from the agency’s standard dental library |
| URL redirect pairs reconciled | 18 unique pairs mapped from old /services/ paths to new /yorktown-heights/ paths |
| SEO Issues Backlog | 34 / 46 closed as Completed; 10 After Release, 1 To Do, 1 in QA |
| CX Issues Backlog | 1 / 3 closed as Completed; 1 In progress, 1 Info-Needed |
| Launch checklist | 40 items signed off across Design / Functionality / Content / Pre-Migration / Post-Migration |
| Timeline | 38 days primary engagement (30 Sep – 7 Nov 2025), with a 2-page refresh follow-on |
| Effort | 39h / 39h estimate — no overrun, no scope creep |
| Handoff | Site live on WP Engine, https://www.nwdentist.com/ returning HTTP 200 |
| Site status, verified 2026-04 | Production live and serving 200 from a fresh curl check |
The outcome, restated plainly: the agency’s focused build shipped new pages on the existing WP Engine environment, inside the 39-hour quoted budget. Eighteen legacy URLs were mapped to new permalinks, both QA backlogs were worked to agency-acceptance levels, and the launch checklist closed before the new pages were indexed.
Operational Integrity at handoff
Internal QA caught two issues before handoff: a Cyrillic-language block in the Elementor template library on this English dental site (chat #1084, 2025-10-13 — content-language sanitization), and a phone-number mismatch in CTA buttons where the footer number and button href pointed to different locations (chat #1246, 2025-10-28 — content accuracy) — both resolved before the agency saw the build. Pre-handoff QA ran through Site Checker — see our QA discipline for the categories and the fail-zero gate. The agency’s own QA layer — their tools, their process — ran post-handoff and surfaced issues into the shared backlog for our fix loop until they signed off.
Process
| Phase | Duration | Outcome |
|---|---|---|
| Brief & estimation | ~3 days | Workbook reviewed, staging credentials confirmed, 39h quoted and agreed |
| Build phase (new pages on test URLs) | ~2 weeks | Service Lander, Doctor Pages, and About Us built on noindex test URLs; 18 URL redirect pairs mapped |
| Fix-and-feedback tail | ~2 weeks | SEO and CX backlogs worked in parallel; button styles, FAQ blocks, and content gaps resolved |
| 2-page refresh follow-on | ~1 week | Two location-specific pages refreshed per agency feedback |
| Launch checklist + delivery | final days | 40-item checklist signed off; new pages set to index |
Phases overlap — the fix-and-feedback tail began before the last build-phase items had closed, which is why the calendar timeline is 38 days rather than the sum of sequential phases.
Team
Delivery team
- Pavel Sazhin — QA iterations and fixes
- Anna Polunina — implementation support and QA
- Timur Arbaev — QA on backlog review and refresh verification
- Lyudmila Travkina — lead developer across build, redirect reconciliation, and refresh phases
- Anton Hersun, xaverPRO — project lead (estimation, agency-side communication, sign-off)
Agency-side project management and client-facing communication remained with the partner agency throughout. Our team was invisible to the end client.
For agencies commissioning a white-label WordPress build
Dev partners who have built only on staging tend to underestimate what changes on a live surface — redirects touching patient-facing URLs, phone numbers branching by location, QA running against password-protected drafts. If your agency is commissioning a focused build on an existing WP Engine or Kinsta installation, send us the workbook or sitemap. We will return a fixed-hours quote within 24 hours, with a note on any redirect rows that carry more risk than they look.
No cost for the review and no obligation to proceed.
Don't have a spec yet? Send a one-paragraph description — we'll come back with the questions worth asking. Send a description →