PublishedVerifiedEvery 6 weeksSources7 namedAuthored bySquareRank Team
Nutritionists · Local SEO · § 4.5.2
RD Private Practice Local SEO on Squarespace
Dietitian local SEO breaks the generic LocalBusiness playbook in five places. Google Business Profile category choice between Dietitian and Nutritionist matters — they pull different query sets. NAP consistency runs across an unusually dense directory web (Academy of Nutrition and Dietetics, Find My Dietitian, Healthie, insurance-network directories). The right schema umbrella is MedicalBusiness with medicalSpecialty: "Dietetic"3. Telehealth across the Dietitian Licensure Compact6 turns single-city local SEO into multi-state coverage. And insurance pages are the highest-converting local lever in the entire vertical.
This is the 2026 walkthrough for the local layer of an RD private-practice Squarespace install. Each section answers one of those five gaps in a copy-paste-ready way, then routes into the adjacent leaves where the answer goes deeper. The mechanics are not novel — they are the same local SEO mechanics every Squarespace site needs — but the failure modes are specific to credentialed nutrition practice, and the install lives in the layer above the mechanics.
§01The lens
What makes dietitian local SEO different from generic local SEO
Three things separate dietitian local SEO from a generic LocalBusiness install. The primary category in Google Business Profile is a credential-anchored choice — Dietitian and Nutritionist are different categories with different query pools, and the credential the practitioner actually holds decides which one is honest and effective. The directory web is denser and more specialised than typical local-service verticals, because dietitians appear in nutrition-specific directories, insurance-network directories, and credentialing-body directories alongside general business directories. And the schema umbrella is MedicalBusiness with medicalSpecialty 'Dietetic', not bare LocalBusiness — the AI engines and Google's local-citation extraction layer read the subtype as a credential signal.
The category choice carries more weight than any single other GBP field1. Most dietitian listings under-specify here — defaulting to "Wellness Centre" or "Health Counsellor" because those sound neutral when Dietitian (for RDs) or Nutritionist (for state-licensed non-RD practitioners) would actually match more user queries. The fix is honest specificity. A Registered Dietitian's primary is Dietitian; that primary category surfaces the practice for "dietitian [city]" and the credentialed-source AI citation queries explored in the health AI citations leaf. Secondary categories pick up the modalities the practice advertises — Weight Loss Service if applicable, Wellness Centre, Health Counsellor.
The directory web is the second shift. A typical mid-career RD appears in Google Business Profile, the Academy of Nutrition and Dietetics' Find a Nutrition Expert directory5, Find My Dietitian, the practice-management platform's directory (Healthie, Practice Better, Nutrium where applicable), an insurance-network directory per major plan accepted, the state licensing board's public listing where state licensure applies, and the malpractice insurer's directory. NAP inconsistencies across that web — "Suite 4" vs "Ste. 4", credential abbreviation drift ("RD" vs "RDN" vs "Registered Dietitian Nutritionist") — read as conflicting signals and suppress the local pack. The audit and standardisation work is mechanical but unglamorous, and most practices skip it.
Why the install shape matters
Dietetic
the canonical medicalSpecialty value for credentialed dietitian practices on schema.org's MedicalSpecialty enumeration.
Google Business Profile setup for dietitians, step by step
Set the primary category to Dietitian if you are a Registered Dietitian, or Nutritionist if you hold a state-protected nutritionist title. Add secondary categories for modalities you actively advertise. Use a consistent NAP string that matches your Squarespace contact page and your Academy directory listing exactly, including credential abbreviation. Set service-area properties for telehealth coverage if applicable, and add an in-person address only if clients actually meet you there. The category choice and the address question between them decide which queries the listing competes for; the other GBP fields fine-tune the position.
The Dietitian-versus-Nutritionist choice1 is where credential precision shows up at the local-SEO layer. A Registered Dietitian listing as Nutritionist is technically truthful (RDs are nutritionists; the categories are not mutually exclusive in practice) but loses the credentialed-query traffic that "dietitian [city]" pulls. A non-RD nutritionist listing as Dietitian is dishonest — and increasingly flaggable by Google's category-verification layer, which has tightened around credential-protected categories since 2024. The honest, ranking-optimal choice is the credential that the practitioner actually holds, with the alternate category as a secondary if both apply.
The address question is where dietitians most often misconfigure. Three patterns: in-person solo practice (address visible, service area defined as the immediate metro), telehealth-only practice (address hidden under "I serve customers at their location" with a service-area definition that maps to the licensed states), and hybrid practice (address visible, service area extended to cover telehealth states). The default Squarespace contact-page address must match whatever GBP shows; mismatches are read as conflicting NAP signals and suppress rank in the local pack.
§03NAP
NAP consistency across the dietitian directory web
A typical RD practice is referenced from ten to fifteen directories before the website itself appears in search results. Google Business Profile, the Academy of Nutrition and Dietetics' directory, Find My Dietitian, the practice-management platform's listing, one insurance-network directory per major plan accepted, the state board's public listing, the malpractice insurer's directory, plus a long tail of nutrition-specific aggregators. Inconsistencies as small as 'RD' versus 'RD, LD' versus 'Registered Dietitian Nutritionist' read as conflicting credential signals. The audit and the fix is once-quarterly mechanical work.
The standard pattern is a tracking spreadsheet with one row per directory and five columns: canonical NAP value, canonical credential string, current value on the directory, last verified date, who controls the update. The canonical NAP is the most formal version (full street address with "Suite", phone in (xxx) xxx-xxxx format, practice name without abbreviation, credential string spelled out the same way every time — "Jordan Lee, RD, LD" if the practitioner holds both the RD and a state Licensed Dietitian credential). It lives on the Squarespace contact page and the GBP listing; every other directory gets edited to match. Updates can take weeks to propagate, so the audit cadence is quarterly.
The directories most worth standardising first are Google Business Profile (highest impact), the Academy of Nutrition and Dietetics' Find a Nutrition Expert directory (highest external credential authority, frequently cited by AI engines), the state licensing board (any mismatch there reads as a regulator-side problem), and the insurance-network directories where most billable patient referrals originate. The long tail of nutrition-specific aggregators can be audited annually rather than quarterly.
§04Schema
MedicalBusiness with Dietetic — the schema that signals credential
Ship MedicalBusiness as the umbrella type<InlineCite n={2} sourceId='schema-medical-business' />, with medicalSpecialty set to 'Dietetic', a connected Person schema for the practitioner carrying jobTitle plus hasCredential plus a knowsAbout array of real concentrations, and an areaServed value that matches your actual coverage. For in-person practices, areaServed is the metro area as a string. For telehealth practices, areaServed is an array of AdministrativeArea objects, one per licensed state. Google's structured-data documentation accepts this shape in JSON-LD and reads it for the local-pack citation card.
The areaServed property4 is the lever that turns single-city LocalBusiness markup into multi-state coverage markup. For a solo in-person RD, areaServed is a simple string ("Austin, TX" or "Travis County"). For a Registered Dietitian practising telehealth across multiple licensed states (including states the practitioner has joined via the Dietitian Licensure Compact6 where that is in effect), areaServed is an array of AdministrativeArea entries, one per licensed state, mirroring the state-page set on the Squarespace site itself. The state-page strategy and the areaServed array are the same coverage statement expressed two ways.
JSON-LDMedicalBusiness with Dietetic + multi-state areaServed — for a telehealth RD practice
<script type="application/ld+json">{"@context":"https://schema.org","@type":"MedicalBusiness","name":"Cedar & Sage Nutrition","medicalSpecialty":"Dietetic","url":"https://yourpractice.com/","telephone":"+1-512-555-0240","address":{"@type":"PostalAddress","streetAddress":"240 Cedar Lane Suite 6","addressLocality":"Austin","addressRegion":"TX","postalCode":"78704"},"areaServed": [{"@type":"AdministrativeArea","name":"Texas"},{"@type":"AdministrativeArea","name":"Colorado"}]}</script>
Google's local-business structured-data guidance7 recommends a single LocalBusiness (or subtype) block per location, on a page describing that location. For a single-location in-person RD, that is one MedicalBusiness block on the contact or location page. For a telehealth practice covering multiple states with state-specific landing pages, the parent telehealth page carries the umbrella MedicalBusiness with the multi-state areaServed, and each state page carries a narrower MedicalBusiness block with that state as the only areaServed value.
§05Telehealth
Telehealth, the Dietitian Licensure Compact, and state pages
The Dietitian Licensure Compact is the equivalent of PSYPACT for credentialed dietitians — an interstate agreement that streamlines multi-state licensure for participating states. The compact has been enacted in multiple states with more pending implementation; the current state list moves quarterly. The practical Squarespace implication: a Registered Dietitian whose licensure (direct state licensure plus any compact-extended privileges) covers multiple states needs a state-coverage page set, one page per state covered, each with state-specific content. Generic 'serving California, Texas, and Florida' single pages rank for nothing and are filtered out by Google's helpful-content layer.
The compact's current adoption status is the variable the marketing copy must respect6. State-level enacted-but-not-yet-implemented status is different from active-and-issuing-privileges status, and a dietitian claiming coverage of a state where the compact has been enacted but not yet activated is making a claim ahead of the legal reality. The audit step is binary: verify directly at the compact's official tracker that the practitioner is actually authorised in each claimed state, and only list those states in the schema's areaServed and in the page-set on the Squarespace site. If the practitioner holds direct state licensure in three states and the compact applies in two more, the page set covers all five — but the marketing copy distinguishes between "licensed in" (direct) and "authorised to practise via the Dietitian Licensure Compact in" (compact-extended).
The minimum bar for a state page to rank in 2026 is roughly 700 words of state-specific content: which insurance plans the practitioner accepts in that state, the named state licensing board, state-specific telehealth informed-consent requirements, local cultural context if relevant, and a clear booking path. State pages without that depth read as thin and get filtered. State pages with that depth and a connected MedicalBusiness schema block addressing that single state earn citations on "dietitian in [state]" queries from both Google and AI engines.
§06Insurance
Insurance pages — the highest-converting local lever for RDs
Insurance acceptance is the single highest-converting local query for a dietitian. 'Dietitian who takes Aetna in Austin' converts at multiples of 'dietitian in Austin' alone because the searcher has already pre-qualified the practice on the question that most often kills the booking. The 2026 lever is a dedicated page per major insurance plan accepted, with the plan name in the URL and the H1, the in-network specifics named (which CPT codes are billed, what counts as Medical Nutrition Therapy, expected session structure, copay range to the extent it can be stated), and a booking path that does not require a discovery call to surface the answer.
The insurance page set is the operational expression of the credential. Most plans cover Medical Nutrition Therapy when the practitioner is a Registered Dietitian and the diagnosis falls inside the covered set (diabetes, chronic kidney disease, and state-by-state additional conditions); the same plans do not cover counselling from uncredentialed nutritionists. The page therefore doubles as a credential proof point — "We are an in-network Aetna provider for Medical Nutrition Therapy, billed under CPT codes 97802 and 97803, performed by Jordan Lee, RD, LD" — which is precisely the credentialed, named-author, named-mechanism content shape AI engines cite from. Generic "we accept some insurance, please call" pages do neither.
The build pattern is one page per major plan accepted, linked from a parent /insurance/ page, each carrying its own MedicalBusiness reference back to the practice's @id and its own thin Service schema for the Medical Nutrition Therapy offering. The pages stay current on a quarterly cadence — plan acceptance and in-network status changes more often than dietitians expect, and a page claiming Aetna acceptance after the practice has been dropped from the network is a customer-experience problem that compounds into reviews. The program page leaf covers the related but distinct format for cash-pay programs.
