Spine Surgery Practice WordPress Build — 10 Templates

Client (end user): Endoscopic Spine Florida — a minimally invasive and endoscopic spine surgery practice in Tampa, FL
Engagement: White-label development for a US marketing agency
Delivered: November 2024 – February 2025 · ~90 days · ~70 hours across build, content population, and fix-and-feedback phases

The Craft of a Build

A new WordPress build from Adobe XD for a Tampa spine surgery practice — 10 templates, ~70 hours across ~90 days, Elementor on WP Engine. The structural load was the conditions-and-treatments URL taxonomy: two content tracks sharing one prefix under a single filterable lander, with draft-only entries suppressed from the live catalogue until their content arrived.

This case study is a record of such a build — a new WordPress site for an endoscopic spine surgery practice in Tampa, Florida, delivered for a US marketing agency from Adobe XD designs.

Snapshot

The Brief

A US marketing agency retained by a two-surgeon endoscopic spine surgery practice in Tampa handed us Adobe XD design files — a desktop set, a set for inner pages, and a mobile set — together with a tracking spreadsheet referencing all URL changes and content assignments. The build sat on a WP Engine environment; the page builder was Elementor Pro; the SEO plugin was Rank Math. The agency designed the site around the practice’s two board-certified spine surgeons, Dr. Aaron Smith (DO, FACOS) and Dr. Scott Glickman, and structured the service taxonomy around the spine surgery vertical’s two content tracks: spinal conditions (diagnoses the patient may present with) and surgical treatments (minimally invasive and endoscopic procedures the practice performs).

The build scope was defined by the Adobe XD files and a parallel tracking spreadsheet that specified URL structure, template assignments, and content delivery stages. The core ask was to build all pages against ten templates — including a filterable Conditions & Treatments lander capable of filtering by category — and then accept a post-build reconciliation stretch: URL adjustments, content additions, pre-launch backlog items, and meta title/description uploads across the full site before launch. Throughout, remain outside the end-client-facing loop; surface all ambiguity back to the agency; do not improvise medical copy or procedure nomenclature.

How We Did It

1. Ten templates, multi-track content architecture, one build pipeline. The agency’s medical site library provided ten templates mapped across the site: Homepage, About Us, Doctor Page (applied twice — once per surgeon), Meet the Team, Conditions & Treatments lander, Condition Template (one per spine condition: herniated discs, degenerative disc disease, spinal stenosis, scoliosis, sciatica, and others), Treatment Template (one per procedure: endoscopic discectomy, posterior spinal fusion and fixation, anterior cervical discectomy and arthroplasty, cervical artificial disc replacement, minimally invasive spine surgery, and others), Blog Lander, Blog Post, Financing & Insurance, FAQs, Contact Us, Request Appointment, and supporting default pages. Each page was built on its assigned template from the Adobe XD design; no page was hand-rolled outside the template system.

2. Custom URL architecture for the Conditions & Treatments taxonomy. The agency’s specification required all condition and treatment posts to resolve under /conditions-treatments/<slug>/ — a URL structure that standard WordPress posts cannot produce natively for a custom post type. The solution was a Custom Permalinks plugin implementation — chosen over a custom post type with rewrite rules because the conditions-vs-treatments split was a content-category distinction, not a structural content-model change, and a CPT would have added rewrite-rule complexity without improving the filter behaviour — with each post assigned a custom permalink matching the required path. Category tags (condition/treatment) powered the filterable lander, so the filter’s GET-parameter URL (/conditions-treatments/?category=conditions) would resolve and be indexable. Additionally, the lander was built to suppress the read-more button and page link for any entry without published content — the agency had specified that not all conditions and treatments would have copy at launch, and those entries should not carry a live link until their pages were populated.

3. Content population and site-wide accuracy pass. After the initial template build, the agency issued a series of content additions: blog posts on SI Joint Education, Herniated Nucleus Pulposus, Minimally Invasive Spine Surgery, and Sciatica; additional condition and treatment records in the taxonomy; URL slug adjustments flagged in the tracking spreadsheet; address and contact details (updated practice address at 11603 Sheldon Road, Tampa, FL 33626; phone number corrections site-wide); a Nearby Hotel Accommodations page for out-of-area surgical patients; and meta titles and descriptions uploaded across the full site from a separate agency-supplied spreadsheet. A Lorem ipsum crawl across the staging environment identified placeholder text remaining on blog, about, and conditions-and-treatments pages; all were replaced before handoff.

4. Pre-launch QA closed against the issues backlog. In the final approach to launch, the agency supplied an Issues Backlog spreadsheet with pre-launch tasks spanning blog draft cleanup, doctor profile template restructuring (rebuilding the doctor block as an Elementor inner template rather than a hardcoded layout), navigation clickability fixes (parent menu items were not resolving to their pages), social media footer link reconciliation, and sitemap cleanup for the blog and FAQ sections. The QA was marked urgent by the project lead: the agency was preparing to deliver the site to the end client, and all items had to close before the end-client presentation. Nikita Tumasevic resolved the backlog; Anna Polunina ran the verification pass; the issues backlog and pre-launch checklist closed before the agency’s delivery date.

The Custom Permalinks implementation for /conditions-treatments/ was the discipline that made the taxonomy work. Without a custom permalink per post, the filterable lander’s GET-parameter URL would not resolve indexably — the filter category logic depended on the URL structure resolving correctly before any other QA pass could run.

Operational Integrity at handoff

The QA load for this build ran heaviest on two categories: a site-wide lorem ipsum crawl (issue #180) cleared all placeholder text across pages, posts, and Elementor data before handoff, and a sitemap contamination flag — conditions-and-treatments posts were appearing in /post-sitemap.xml instead of a dedicated custom-type map (issue #103) — was caught and corrected before the agency pre-launch review. 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.

Results

The outcome, restated plainly: the agency’s spine surgery site shipped on WP Engine across ten templates, with a custom-built conditions-and-treatments taxonomy that resolved the required URL architecture and supported the filterable lander. The issues backlog closed before the agency’s end-client presentation. No overrun on the ~70-hour estimate.

Process

Phases overlap — content population and URL reconciliation began while remaining inner pages were still under construction, which is why the calendar timeline is ~90 days rather than the sum of individual phases.

Team

Delivery team

• Nikita Tumasevic — lead developer across build, taxonomy implementation, and fix-and-feedback phases
• Anna Polunina — QA verification and content-accuracy pass
• Evgeniy Karpov — development support
• 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