Pediatric Dental Rebuild — Canonical, Portland

Client (end user): Pine Tree Pediatric Dentistry — solo-pediatric dental practice, Portland, OR
Engagement: White-label development for a US marketing agency
Delivered: January–February 2025 · core build ~8 days · 26 hours · on schedule, no overrun

The Craft of a Rebuild

A solo-pediatric dental site in Portland rebuilt from a single Issues-Backlog spreadsheet — no separate sitemap — where the gating requirement was URL canonicalization, not page structure. Every page had to enforce a trailing-slash redirect, and the practice blog, housed under /portland-pediatric-dental-blog/, had to preserve its three-segment path. Without both disciplines, search engines would index duplicate versions of every URL and returning parents would land on broken paths.

This case study is a record of one such rebuild — a solo-pediatric dental practice in Portland, OR — in which the agency owned the strategy and we owned the execution.

Snapshot

The Brief

A US marketing agency retained by Pine Tree Pediatric Dentistry — a solo-pediatric dental practice in Portland, OR — brought us in to rebuild the existing site on Elementor Pro. The practice serves children exclusively, with a single-track service structure covering preventive care, restorative work, sedation dentistry, special-needs pediatric dentistry, post-operative instructions, and first-visit guidance. Unlike pediatric practices that run parallel orthodontics and pediatric dentistry ladders, this practice operates a single patient journey — the parent books an appointment for their child, navigates to one service track, and follows one set of contact forms. That simplicity in service architecture made the technical requirements sharper, not looser: every URL had to behave identically, every internal link had to resolve cleanly, and the tracking infrastructure had to be in place from the first page load after cutover.

The ask was precise. Work from the agency’s spec and Issues Backlog; implement each row as written; stay outside the client-facing loop throughout. The agency’s specification was delivered as a single-spreadsheet Issues Backlog — no separate sitemap, template map, or page inventory accompanied it. The full page structure had to be reconstructed from the backlog issues and chat threads rather than verified against a formal workbook, which was a constraint of how the project was briefed rather than a process choice. The staging environment ran on WP Engine. The risk the agency was hedging against was a set of URL canonicalization failures specific to this rebuild: the practice’s blog posts sat under a three-segment path (/portland-pediatric-dental-blog/), and every URL on the site needed to enforce a trailing-slash redirect — without both disciplines in place, crawlers would index two versions of the same page, and parents navigating older bookmarked links would land on unresolved paths.

How We Did It

1. Template-first build across the pediatric service structure. The site’s service architecture followed the solo-pediatric pattern: a Services Lander feeding individual Service Pages for each clinical offering (preventive dental care, restorative dentistry, sedation dentistry, special-needs pediatric dentistry, post-operative care), alongside the practice’s first-visit and patient-forms pages. Each Service Page carried consistent structure — procedure description, parent-facing guidance, and a contact form routed to the practice. The blog, housed under the practice-specific /portland-pediatric-dental-blog/ subdirectory, was rebuilt with matching path structure to preserve any links in place from prior publications.

2. Trailing-slash canonicalization, applied site-wide. The agency’s spec required that all pages — static and dynamic — be accessible only with a trailing slash, and that all non-slash variants redirect to the canonical slash form. This was enforced through WordPress permalink settings and redirect rules, applied consistently across service pages, blog posts, and the blog archive. The treatment removed the dual-resolution problem before go-live and prevented downstream crawl artifacts.

3. Spec followed line-for-line, from the agency’s sheet. The agency’s Issues Backlog documented every content and functional gap against the original site. Incomplete content blocks — including a sedation-dentistry page missing sections from the original — were rebuilt to match. The post-operative instructions page, which carried a button for a PDF download that was not yet available in the original, was noted and escalated to the agency rather than silently bypassed. Services-page items that arrived without links to individual service pages were surfaced and fixed. No gap was closed by assumption.

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 infer around it.

4. GTM integration via Header Footer Code Manager, confirmed before handoff. The agency required the Google Tag Manager script to be ported from the original production site and installed via the Header Footer Code Manager plugin. The plugin had been provisioned on staging but the GTM script itself had not been wired — a gap that would have gone undetected in a visual QA pass but would have silently broken the practice’s tracking from the first session after cutover. The integration was verified functional before the build went to the agency review queue. We used Header Footer Code Manager over theme-template embedding because it centralises all third-party scripts — changes survive theme updates and the agency can review or modify placements without touching code.

The trailing-slash enforcement and the /portland-pediatric-dental-blog/ path had to be confirmed before handoff — both were invisible to a visual QA pass but would surface in every crawl and every returning parent’s bookmark after cutover. Resolving the duplicate-URL surface before go-live, and catching the staging hostname in the footer link before the agency ever saw it, was what the internal QA round was for.

Results

The outcome, restated plainly: the agency’s spec was implemented as written across the full pediatric service structure, inside the quoted hours, with all backlog items resolved before sign-off. The site remains live.

Operational Integrity at handoff

The internal link-check run (issue #159) caught a footer button pointing to the staging hostname instead of the live your-first-visit path — a broken URL that would have gone undetected in a visual pass — and the parity diff surfaced that every page resolved both with and without a trailing slash, the duplicate-content signal the agency’s spec was built to prevent; both were fixed before handoff. 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 approximately 35 days from project open to final backlog sign-off, while the core build completed in the first 8 days.

Team

Delivery team

• Evgeniy Karpov — lead developer (full site build, template system, trailing-slash canonicalization)
• Anna Polunina — backlog QA and services-page linking fix
• Nikita Tumasevic — QA coordination and issue routing
• 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 the post-handoff fix rounds. All decisions on URL structure, redirect strategy, and service-page architecture belonged to the agency; our role was implementation fidelity to the spec they delivered.

For agencies considering a white-label WordPress build