Results you can quantify and track
Ranking Out
(703) 389-5362 The offer
Live Project · Planning & Build Stage

The Local SEO Plan Behind a Medical Practice Website We’re Building Right Now

A new in-home physical therapy practice. No website yet. No rankings, no reviews, no traffic history. This page documents the seven-phase plan we’re implementing — the architecture, the page counts, the quality gates, and the reasons we are not building the 200-page keyword matrix most agencies would sell.

Read the Seven Phases See the Roadmap
  • 7Phases planned
  • 36Pages at launch
  • 78Pages at maturity
  • 200+Pages avoided
Where This Project Stands

Nothing is live yet. This is the plan.

Most agency case studies are written after the fact, once the numbers are flattering. This one is published from the planning stage — before launch, before rankings, before a single lead. You can see the decisions as they are being made.

PhaseWhat it coversStatus
Design & Build Three page templates, approved before the site is built In progress
Phase 1 36-page launch architecture In progress
Phase 2 20 local service pages Gated on Phase 1 data
Phase 3 10 nested condition pages Gated on Phase 2 data
Phase 4 12 selective local pages Gated on Phase 3 data
Phase 5 Google Business Profile, reviews, citations Runs in parallel
Phase 6 Conversion optimization and maintenance Starts at launch
Phase 7 Resource content Optional · annual review

Why publish a plan instead of a result?

Because the plan is the part you can actually evaluate. Anyone can show a traffic graph and claim credit for it. Far fewer can explain, in advance, why a site should launch with 36 pages instead of 200 — and hold to it when the client asks for more.

The Brief

A brand-new website. Nothing to inherit, nothing to fix.

The client is a mobile in-home physical therapy practice serving Nassau County, New York. The engagement starts from a genuinely blank page.

This is a new build, not a redesign

No existing site. No legacy URLs. No redirect map. No historical Search Console data to lean on. Every ranking, every review and every tracked lead has to be created from zero — which means every architectural decision has to be right the first time, because there is no traffic data to correct it with.

What a new build actually changes

FactorRedesign / migrationNew build (this project)
Existing rankingsProtect themNone to protect
Redirect mapMandatory, high-riskNot applicable
Keyword dataHistorical Search Console availableZero — research only
Page count decisionConstrained by what existsCompletely open — and that is the danger
Biggest riskLosing traffic at cutoverOverbuilding before any evidence exists

That last row is the whole reason this framework is phased. When you can build anything, the temptation is to build everything. A 20-town by 10-service matrix is 200 pages, it can be generated in an afternoon, and it looks like enormous value on a proposal. It is also the fastest way to get a new healthcare site treated as a doorway network.

The constraint that drives every decision

This practice treats patients in their homes. It has no clinic in any of the towns it serves. That single fact dictates the URL structure, the page templates, the schema, the Google Business Profile setup and the copy on more than twenty pages.

The End Goal

Local leads. Not pages, not rankings.

A practice that shows up when a patient in the service area searches for help — and turns that search into a phone call.

Everything in this framework serves that one outcome. The seven phases are ordered so each one earns the right to the next, and no page gets built before there is evidence it should exist.

The build order, in one line

Services -> Service Areas -> Local Services -> Subservices -> GBP/Reviews -> CRO -> Resources

Money pages first. Pages that answer “what do you do,” “where do you do it,” and “how do I book” come before anything educational. Blog and resource content is not skipped — it is deliberately delayed until the foundation is earning.

Priority order

  1. Core service pages
  2. Service-area pages
  3. Local service pages
  4. Nested subservice pages
  5. Google Business Profile optimization
  6. Reviews
  7. Citations
  8. Conversion tracking
  9. Ongoing SEO maintenance
  10. Resources and educational content (last)
The Model

Five buckets that must never bleed into each other

Most local SEO failures come from collapsing two buckets into one — usually by turning service-area pages into service pages, or by building “location” pages for a business with no locations.

1

Services

What the business does. Core service pages, built in Phase 1, measured on county-level service rankings.

2

Service Areas

Where the business serves. Town and county pages, Phase 1, measured on [service] [town] rankings and map pack presence.

3

Subservices & Conditions

What problems patients need solved. Condition pages, Phase 3, measured on long-tail condition queries.

4

GBP, Reviews & Citations

Local map pack authority. Off-site work in Phase 5, aligned from Phase 1, measured on map rank and review velocity.

5

CRO & Tracking

Turning traffic into leads. Sitewide from Phase 1, ongoing in Phase 6, measured on calls, forms and conversion rate.

!

Why separation matters

Each bucket has a different job, a different page type and a different success measure. Merge them and you cannot tell which part is failing.

The Non-Negotiable

A service-area business is not a clinic

This practice delivers care in patients’ homes. It has no clinic in Hicksville, no office in Garden City, no location in Plainview. The site must never suggest otherwise — and that single distinction drives decisions on more than twenty pages.

Correct language

  • In-home physical therapy in Hicksville, NY
  • Mobile physical therapist serving Garden City
  • At-home orthopedic physical therapy in Plainview

Never

  • Visit our Hicksville clinic
  • Our Garden City office
  • Our Plainview location

Why it matters, in order of severity

  1. Trust and compliance — claiming locations that do not exist is a misrepresentation, and this is healthcare.
  2. Google Business Profile alignment — GBP is configured as a service-area business. A site implying twenty storefronts contradicts it.
  3. Schema integrity — no per-town LocalBusiness entities, no fabricated addresses.
  4. User experience — a patient who drives to a nonexistent office is a lost patient and a bad review.
The Roadmap

78 pages after four build phases. The full matrix would be 200+.

That gap is the strategy.

36Phase 1Launch
56Phase 2+20 local
66Phase 3+10 conditions
78Phase 4+12 selective
78–80Phase 5Off-site
200+Full matrixNever a target
PhaseWhat it addsRunning total
1 — Launch Foundation3636
2 — Local Service Expansion2056
3 — Nested Subservice Pages1066
4 — Selective Local Expansion1278
5 — GBP / Reviews / Authority0–278–80
6 — CRO / Ongoing Maintenanceflexibleflexible
7 — Resources (optional)3–6 articles

Every phase is gated on the last one’s data

Phase 2 does not start until the Phase 1 thirty-day report exists. Phase 3 waits on the Phase 2 sixty-day report. Phase 4 waits on Phase 3’s ninety-day data. The operating principle after launch is the same every time: build the strongest opportunities first, monitor results, expand on evidence.

The Framework

The seven phases, expanded

Each phase opens to its full work order — the goal, the individual steps, the templates, the quality gates, and the decision points that determine whether the next phase happens at all.

Parallel

Design & Build In progress

Design three templates. Approve them. Build them. Then build the other 33 pages.

3templates
Goal: client sign-off on three page designs before the full site is built Done when: three templates are live on staging and approved in writing

Runs alongside Phase 1. Every page on this site is one of three layouts — approve those three and the rest is production, not design.

1. Homepage                        /
2. One core service page           /services/physical-therapy/
3. One location/service-area page  /service-areas/[town]-ny/

Work order

  1. Pre-design requirements — confirm the SEO architecture, the content each page needs, and the platform stack before anyone opens a design tool
  2. Design the three templates — desktop and mobile, with a slot for every required section
  3. Design QA and client approval — internal review against the content checklist, then written sign-off
  4. Development handoff and build — built as reusable templates, not one-off pages
  5. Build QA — four separate passes: development, SEO/content, accessibility, performance
  6. Client build approval — written sign-off on the developed templates
  7. Full-site rollout and change control — the remaining 33 pages, with a formal change process
  8. Acceptance criteria and quality control

Gates

  • Gate 1 — Requirements locked. Architecture and content requirements confirmed.
  • Gate 2 — Designs approved. Written sign-off on all three.
  • Gate 3 — Templates built. Live on staging, passing all four QA checklists.
  • Gate 4 — Build approved. Written sign-off on the developed templates.
  • Gate 5 — Rollout. Remaining 33 pages built from approved templates.

The modularity test

Could you produce the next town’s page by duplicating and changing content only — no layout work? If not, it is not a template. It is a page that happens to look like one.

Why changes get expensive after approval

A change to the location template touches 21 pages. A header change touches all 36. Every change request is priced on pages affected, not on the effort of the single edit.

Phase 1

Launch SEO Architecture In progress

Tell Google five things and no more. Not too thin, not overbuilt.

36pages
Goal: a clean, crawlable local-service SEO foundation Done when: 36 pages live, indexed, tracked, and monitoring is running

The launch foundation communicates the business type, the primary service, the local service footprint, the provider’s trust signals, and the conversion path. That is the sweet spot. A five-page site cannot establish a 20-town service footprint. An 80-page matrix means dozens of near-identical pages competing with each other before there is a single data point to justify any of them.

The 36 pages

HOME  /
|
+-- SERVICES HUB  /services/
|   +-- /services/physical-therapy/
|   +-- /services/chronic-pain-management/
|   +-- /services/orthopedic-physical-therapy/
|   +-- /services/sports-physical-therapy/
|
+-- SERVICE AREAS HUB  /service-areas/
|   +-- /service-areas/nassau-county-ny/
|   +-- 20 town service-area pages
|
+-- ABOUT US  /about-us/
+-- CONTACT US  /contact-us/
+-- INSURANCE & PAYMENT  /insurance-payment/
+-- FAQS  /faqs/
|
+-- UTILITY / COMPLIANCE
    +-- /privacy-policy/
    +-- /terms-of-use/
    +-- /accessibility-statement/
    +-- /thank-you/   (noindex - form redirect target)

Work order

  1. Scope and page inventory — lock the business model, the town list, and the 36-page build
  2. Keyword map and URL structure — one primary keyword per page, no duplicates, clean URLs
  3. Core page templates — the 14 non-service-area pages
  4. Service-area templates — the 22 town and county pages
  5. On-page SEO and internal linking — title and meta patterns, link flow, no orphans
  6. Trust, compliance and tracking — credentials, disclaimers, GA4, GTM, call tracking
  7. Technical SEO and pre-launch QA — Core Web Vitals, sitemap, indexability, full crawl
  8. Launch day runbook — the step-by-step go-live sequence
  9. Post-launch 30-day monitoring — week-by-week checks
  10. Acceptance criteria and Phase 2 backlog

Launch-support addenda

Non-page work that does not add pages but does block launch.

  • Schema, accessibility and media
  • Access, security and backups
  • Local search alignment (GBP and NAP)
  • Launch QA and verification

Writing templates

  • Core Service Page
  • Town Service Area Page
  • County Hub Page
  • Template Rules and Quarterly Audit
  • Post-Launch Report

Phase gates

  • Gate A — Scope locked. Page list and town list approved in writing.
  • Gate B — Content complete. All 36 pages written, zero placeholder text.
  • Gate C — Build QA passed. Staging crawl clean, compliance signed off.
  • Gate D — Live. Site indexable, tracking firing, live crawl clean.
  • Gate E — Phase 1 accepted. 30-day report delivered.

Ground rules

  1. This is a service-area business, not a clinic. No fake location pages, ever.
  2. No town-by-service matrix at launch. Phase 2 adds those, based on real data.
  3. Every town page needs unique local detail. Find-and-replace town names fails this build.
  4. Tracking is installed and tested before launch, not after.
  5. Nothing goes live with a staging noindex or Disallow: / still in place.

The single most common launch failure

Shipping with a staging noindex or Disallow: / still in place. It is a checkbox on the runbook for a reason — the site can look perfect and be invisible for weeks before anyone notices.

Phase 2

Local Service Page Expansion Gated

Five priority towns by four core services. Twenty pages, not eighty.

+20to 56 total
Starts when: the Phase 1 thirty-day report exists Done when: 20 pages live, indexed, and the sixty-day report is delivered

Phase 2 targets genuinely more specific intent — orthopedic physical therapy Hicksville NY, chronic pain management Garden City NY — while avoiding the trap. Building all 80 town-by-service combinations at once means most end up too similar to be useful, and the site starts to look like a doorway network.

URL pattern:  /service-areas/[town]-ny/[service]/

5 priority towns  x  4 core services  =  20 pages

Work order

  1. Performance review and town selection — the five towns come from Phase 1 data, not from opinion
  2. Page inventory, URLs and keyword map
  3. Content production and quality rules — including the three-way duplication test
  4. Internal linking, breadcrumbs and schema
  5. Technical and content QA
  6. Publishing and Search Console submission
  7. Tracking and rank monitoring
  8. 60-day monitoring and the Phase 3 decision

The three-way duplication test

Every Phase 2 page must be meaningfully different from its parent service page, its parent town page, and its sibling pages. If it cannot clear all three, the page gets merged or dropped — not published thin.

The availability gate

Before any page is built, an availability matrix confirms the service is genuinely offered in that town. Any blank cell means that page does not get built. No aspirational coverage.

Phase 3

Nested Subservice & Condition Pages Gated

Global authority pages for the problems patients actually search.

+10to 66 total
Starts when: the Phase 2 sixty-day report exists Done when: 10 condition pages live and the ninety-day report is delivered

Ten condition pages, nested under their parent service to reflect a real clinical hierarchy.

URL pattern:  /services/[parent-service]/[subservice]/

Physical Therapy
+-- Post-Surgical Rehabilitation
+-- Balance & Fall Prevention
+-- Senior Physical Therapy

Chronic Pain Management
+-- Back Pain Physical Therapy
+-- Neck Pain Physical Therapy
+-- Sciatica Treatment

Orthopedic Physical Therapy
+-- Knee Pain Rehab
+-- Shoulder Pain Rehab
+-- Hip Pain Rehab

Sports Physical Therapy
+-- Sports Injury Rehab

Nesting is architecture, not a ranking tactic

Google does not require nested URLs and does not reward them with a ranking boost. Nesting is chosen here because these services have a real clinical hierarchy and the URL should reflect it — for hierarchy, user understanding, crawlable internal linking, breadcrumbs, content organization and future scalability.

One subservice equals one canonical URL

Post-surgical rehabilitation fits under both Physical Therapy and Orthopedic PT. It gets one URL under Physical Therapy, cross-linked from Orthopedic. Two URLs for one topic is self-competition.

Work order

  1. Performance review and page selection
  2. URL structure, keywords and breadcrumbs
  3. Content requirements by page — per-page required sections for all ten
  4. Internal linking and parent page updates
  5. On-page SEO, schema and compliance — including provider clinical sign-off
  6. Technical and content QA
  7. Publishing and Search Console
  8. Tracking and rank monitoring
  9. 90-day monitoring and the Phase 4 decision
  10. Acceptance criteria and quality control
Phase 4

Selective Local Expansion Gated

Localize proven winners only. Three signals must converge first.

+12to 78 total
Starts when: the Phase 3 ninety-day report exists Note: building nothing is a legitimate outcome

Phase 3 creates global authority pages. Phase 4 creates local versions of the ones that earned it.

The signal to build

The global subservice page is getting impressions.
The town page is getting traffic.
Patients from that town are calling about that problem.

   |
   v  then, and only then

/service-areas/garden-city-ny/back-pain-physical-therapy/

The URL asymmetry is intentional

Global subservice URLs nest, because the clinical hierarchy is real:
/services/chronic-pain-management/back-pain-physical-therapy/

Local subservice URLs stay shallow, because a third level adds depth without meaning:
/service-areas/garden-city-ny/back-pain-physical-therapy/

Four options at this decision point

OptionBuildTotal
A — Wider town coverage5 towns x 4 core services = 2086
B — Deeper local intent (recommended)3 towns x 4 top subservices = 1278
C — Hybrid1278
D — Build nothing, optimize instead066

Option D is a real answer. If the data says existing pages are under-converting rather than under-ranking, the correct Phase 4 is no new pages at all.

Work order

  1. Performance review and path selection — choose A, B, C or D on evidence
  2. Town and subservice selection — scorecards, not preferences
  3. Page inventory and URL rules
  4. Content production and quality rules — must differ from both the global subservice page and the town page
  5. Internal linking and breadcrumbs
  6. On-page SEO, schema and compliance
  7. Technical and content QA
  8. Publishing by town cluster
  9. Tracking and rank monitoring
  10. 90-day monitoring and the next-phase decision
  11. Acceptance criteria and quality control
Phase 5

GBP, Reviews & Local Authority Parallel

Off-site work. Runs alongside the build, not after it.

0–2pages
Goal: map pack visibility and local trust Main rule: this phase is not page-building

Phase 5 drives map pack visibility and local trust, and it can start any time after launch. If the map pack is weak while organic is fine, Google Business Profile and reviews are the bottleneck, and running Phase 5 beats building more pages.

Work order

  1. GBP audit and category selection — with competitor research
  2. GBP services and service areas — aligned to the website, no fabricated coverage
  3. GBP description and photos
  4. Review generation system — no incentives, no gating, no fake reviews
  5. Review response SOP — including what can never be disclosed in a public reply
  6. Citations and NAP consistency
  7. Website trust and local authority
  8. GBP posts — minimum twice monthly, weekly is better
  9. Automation and tracking — missed-call text-back, form auto-response, UTM discipline
  10. Map pack rank tracking — proximity, county, town-plus-service
  11. Monthly and quarterly maintenance
  12. Acceptance criteria and quality control

Healthcare review compliance

A review response can never confirm that someone was a patient or reference their condition — even when the reviewer disclosed it themselves. The response templates in this phase exist specifically so that nobody has to improvise it in the moment.

Phase 6

CRO & Ongoing SEO Maintenance From launch

No end date. The rule: optimize before expanding.

ongoing
Cadence: monthly, quarterly, annual Ends: never

Phase 6 never finishes. It is the monthly system that stops everything else from decaying, and it shares one session with Phase 5 — the GBP checklist and the site checklist are the same meeting, not two.

Work order

  1. Reporting cadence and data review — monthly, quarterly, annual
  2. Conversion path audit — quarterly, by template
  3. CTR optimization — high-impression, low-CTR pages first
  4. Conversion rate optimization — high-traffic, low-conversion pages first
  5. Content refresh and internal linking
  6. Technical SEO and mobile maintenance
  7. Tracking accuracy QA — a real test form and a real test call, every month
  8. GBP and local authority upkeep
  9. Monthly action plan and new-page decisions — nine questions that must all be true before a new page is approved
  10. Quarterly and annual reviews
  11. Acceptance criteria and quality control

Phase 6 fails through neglect, not error

Nothing breaks visibly when the monthly session stops. Rankings and leads slide about four months later and nobody can say when it started. A named owner is the only real control.

Phase 7

Resources & Educational Content Optional

Blogs are not skipped. They are deliberately delayed.

3–6articles
Decided at: the annual review Only if: visibility is fine but trust or conversion is the gap

An article about back pain competes for attention and internal link equity with the page that actually books appointments for back pain. Published first, it dilutes. Published after the service pages rank, it feeds them.

A Resources section, not a generic blog — the framing matters. “Resources” signals patient education tied to the practice’s services. A blog invites unfocused posting.

/resources/

What to Expect During In-Home Physical Therapy
In-Home PT After Surgery
Physical Therapy for Seniors at Home
Balance and Fall Prevention at Home
How Physical Therapy Helps Back Pain

Each article maps to an existing service or subservice page and links to it. None of them exist to rank on their own — they exist to answer the questions that stop a patient from calling, and to pass authority to the page that converts.

When it starts

At the annual review, and only if the data says visibility is fine but trust or conversion is the gap. If leads are still constrained by rankings or map pack presence, Phase 5 and Phase 6 work comes first.

The Rules

Ten principles the whole framework answers to

If a decision conflicts with one of these, the decision is wrong.

  • Build service-area pages, not fake location pages
  • Do not create every possible town, service and subservice page
  • Use data before expanding
  • Prioritize useful, unique pages
  • Keep URLs clean and logical
  • Use nested URLs for global subservice pages
  • Keep local subservice URLs shallow
  • Optimize GBP and reviews for map pack rankings
  • Track calls, forms and conversions
  • Add resource content later, not before the core site is strong

The test that matters

Every page must answer a question a real patient actually asks, in a way that no other page on the site already answers. If it cannot, it does not get built — regardless of search volume.

Planning a new website for a local service business?

This is the framework we use. If you are launching from zero — or inheriting a site that was built as a keyword matrix — we can walk you through what the first ninety days should look like.

Talk to Us Re-read the Phases