45-Page Pediatric Dental Website Rebuild

Client (end user): Little Bytes Pediatric Dentistry — pediatric dental and orthodontic practice, Palo Alto, CA
Engagement: White-label development for a US marketing agency
Delivered: August 2025 · ~20 days · 58 hours · on schedule, no overrun

The Craft of a Rebuild

45 URLs, two patient ladders under one brand — Little Bytes Pediatric Dentistry serves children’s dental patients and orthodontic patients under a single domain. The rebuild had to honour the visual and functional distinction between the two ladders at every page, a constraint the agency’s workbook could not fully pre-identify at spec time, producing 21 hours of review across three rounds.

This case study is a record of one such rebuild — a pediatric dental and orthodontic practice in Palo Alto, CA — in which the agency owned the strategy and we owned the execution.

Snapshot

The Brief

A US marketing agency retained by Little Bytes Pediatric Dentistry — a dual-specialty pediatric dental and orthodontic practice in Palo Alto, CA — brought us in to rebuild the existing site from scratch on Elementor Pro. The spec called for every URL to be preserved with a matching redirect, every meta title and description to be carried over, and the full two-specialty service structure (pediatric dentistry and orthodontics) to be rebuilt as a cohesive site. The two-ladder service architecture — where pediatric dental care and orthodontic care share a brand but follow different patient journeys — was load-bearing: the agency’s design distinguished the two ladders visually, and our build had to honour that distinction at every page level.

The ask was precise. Work from the agency’s Google Sheets workbook; implement each row as written; stay outside the client-facing loop throughout. The staging environment ran on Kinsta. The risk the agency was hedging against was specific to a dual-specialty pediatric rebuild: a child patient’s parent navigating to a service page expects to find pediatric dental content, not orthodontic content, and vice versa. A rebuild that produces the right visual output but routes the wrong CTA or form to the wrong ladder fails silently — the site looks fine, but the appointment request flows to the wrong specialty. The workbook did not pre-identify every cross-ladder edge case at spec time — SEO discrepancies, form-integration gaps, and content-parity drift surfaced only after the initial handoff and required 21 hours of additional review across three Redmine rounds before each ladder’s integrity was confirmed.

How We Did It

1. Template-first build across two service ladders. Rather than rebuilding every page independently, we mapped the existing site’s structure into reusable Elementor Pro templates covering both the pediatric dentistry and orthodontic service ladders. The pediatric ladder (cleanings, sealants, fluoride treatments, pulpotomies, restorative work) and the orthodontic ladder (early Phase 1 treatment, traditional braces, ceramic braces, clear aligners, retainers) each required distinct template treatment — not because the design diverged structurally, but because the CTA routing, form integrations, and parent-facing copy on each ladder needed to remain ladder-specific in the rebuild. One Service Page template served both ladders; the content layer and the per-ladder CTA blocks handled the distinction.

2. Spec followed line-for-line, from the agency’s sheet. The agency handed us a Google Sheets workbook covering the full URL inventory (45 staging URLs, all returning HTTP 200), meta titles and descriptions for each, and a pre-launch checklist. We implemented each row as written. The “Hours Estimated” column in the workbook carried the agency’s own hour allocations per page — a signal that the spec was a committed budget, not a rough guide. Where the sheet had a value, that value landed on the new site. Where it didn’t, we flagged it back to the agency. No “creative interpretations” shipped.

The principle behind this is simple: on a rebuild, the spec is the contract between the agency and its client. A dev team’s job is to protect that contract, not to edit it.

3. Crawl-based verification, not “looks fine to me”. Before DNS cutover, we ran a parallel crawl of the original production site and the staging rebuild. Status codes, broken links, redirect chains, meta-tag integrity — every delta was reconciled against the agency’s spec. The two-ladder service structure received additional scrutiny: each pediatric service page and each orthodontic service page was checked individually to confirm the correct form integration and CTA routing. A second crawl confirmed every internal link resolved on the live domain after cutover.

4. Launch checklist, closed before handoff. The checklist covered design fidelity, functionality, content accuracy, SEO settings, responsive behaviour, and client-specific integrations across both ladders. Nothing shipped until each line was reviewed and signed off. Cross-device QA ran on multiple viewports, including mobile portrait and landscape — a critical check for a pediatric practice, where parents frequently research and book appointments on mobile devices.

The tension in a dual-specialty rebuild is that both ladders share a domain but cannot share a CTA or a form. The crawl-based verification resolved it: each pediatric service page and each orthodontic page was checked individually for correct form integration and routing before cutover — the pre-cutover pass also caught the phone-number swapping script on the original domain, so the rebuild carried the real hardcoded number throughout.

Results

The outcome, restated plainly: the agency’s spec was implemented as written across both pediatric and orthodontic service ladders, inside the quoted hours, on the scheduled cutover window. The site remains live and indexed.

Operational Integrity at handoff

The parity diff against the original site caught a phone-number swapping script on the live domain — the rebuild required the real hardcoded number (tel:+16503229837) rather than inheriting the original’s dynamic substitution — and a post-release pass through the SEO backlog found the canonical URL still pointing to the staging domain. 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

Phases overlap (QA ran alongside late development), which is why the calendar timeline is ~20 days rather than the sum of individual phases.

Team

Delivery team

• Nikita Tumasevic — lead developer (full site build and two-ladder template system)
• Pavel Sazhin — QA (rounds across build stages, responsive verification)
• Anna Polunina — implementation support and QA across the rebuilt pages
• Lyudmila Travkina — development support (backlog fixes and content implementation)
• Anton Hersun, xaverPRO — project lead (estimation, agency-side communication, sign-off)

The agency stayed the visible vendor; we stayed invisible to the end client throughout cutover and migration. All decisions on URL preservation, redirect strategy, and two-ladder service architecture belonged to the agency; our role was implementation fidelity to the spec they delivered.

For agencies considering a white-label WordPress build