PublishedVerifiedEvery 6 weeksSources6 namedAuthored bySquareRank Team
Nutritionists · Program Page SEO · § 4.5.4
Nutrition Program Page SEO on Squarespace
Most nutrition program pages on Squarespace fail in two predictable ways. The program is named generically ("PCOS Reset", "Gut Rebalance") with no mechanism in the title, which produces a page with no citable thesis sentence and no search-query-shaped name. And the FAQ section is wrapped in FAQPage JSON-LD that no longer triggers rich results in general Search3 as of 2026-05-07 — the schema is doing nothing for the page and can dilute the broader trust signal. The fix is a named-mechanism program title, a Service-plus-Offer schema graph, and an FAQ section rendered as readable content with no FAQPage wrapper.
This is the 2026 walkthrough for the program-page layer of a credentialed dietitian's Squarespace install. Each section answers one of the failure modes — what a program page actually is in 2026, why the named-mechanism rule matters, the page shape that ranks, the Service schema graph, the Member Areas question, and the FAQ format that works post-FAQPage-retirement.
§01The frame
What a nutrition program page actually is in 2026
A nutrition program page is the public-facing sales and discovery page for a named, time-bounded, mechanism-driven offering delivered by a credentialed practitioner. It is not the Member Area where the program is delivered, and it is not the booking calendar. It is the page that ranks for 'PCOS nutrition program', that gets cited by AI engines when someone asks ChatGPT 'are there structured PCOS nutrition programs run by RDs', that pre-qualifies the prospect on credential, mechanism, timeline, and price, and that routes them into the booking or enrolment flow. Every credentialed dietitian who sells programs needs one per program, public, indexed, and crawler-accessible.
The clearest mental model is the difference between a service page and a program page. A service page describes an ongoing offering ("Medical Nutrition Therapy", "1:1 Nutrition Counselling") that the practitioner provides on a continuing basis. A program page describes a specific, named, finite cohort or course ("PCOS Metabolic Foundations: A 12-Week Program", "Gestational Diabetes Confidence: 6-Week Cohort") with a defined start, structure, and end. AI engines and search queries treat these differently — service-page queries are intent-led ("dietitian who specialises in PCOS"); program-page queries are mechanism-led ("12-week PCOS program with an RD"). The page formats follow the query difference.
The program-page format is also the natural conversion page on a dietitian site. A prospect arriving from "12-week PCOS program with an RD" has already committed to the format, the timeline, and the credential filter; the page's job is to convert on price, fit, and credibility, not to educate from scratch. The credibility lift comes from the credential graph (Person schema, RD byline, named mechanism) shared with every other page on the site, and the conversion lift comes from the program-specific content — timeline, what's included, named outcomes the program is built to support, refund policy, named practitioner delivering it.
The shape of a 2026 program page
Service
the canonical schema type for a named offering. Pair with Offer for commercial terms and provider for the credentialed Person reference.
the program landing page must be a public Squarespace page, not a Member-Area-gated page. Gated pages are typically noindexed and unreachable to crawlers.
The named-mechanism rule — why generic program names fail
Generic program names ('PCOS Reset', 'Gut Rebalance', 'Hormone Harmony') fail at two levels. They give the page no citable thesis sentence because the mechanism is not in the name, which means AI engines cannot extract a one-line summary that survives quoting out of context. And they fail the YMYL E-E-A-T audit because 'Reset' and 'Rebalance' imply outcomes the practitioner has not committed to a specific mechanism for — which reads as marketing copy rather than clinical work. The fix is a name that includes both the condition and the actual mechanism: 'PCOS Metabolic Foundations: A 12-Week Insulin-Sensitivity Program' or 'Gestational Diabetes Confidence: 6-Week Blood-Sugar Stability Cohort'.
The Search Quality Rater Guidelines5 treat YMYL E-E-A-T as a multi-signal evaluation, and the named-mechanism pattern lifts three signals at once: expertise (the practitioner has committed to a specific clinical mechanism), authority (the program addresses the condition through a defensible pathway), and trust (the name is honest about what the program does and does not do). Generic names lower all three signals; they read to a rater the same way they read to an experienced clinician — as marketing veneer over an unspecified intervention.
The AI-citation lift from named-mechanism program titles is observable in audits. Ask ChatGPT or Perplexity "are there structured 12-week PCOS programs run by RDs" and the engines cite the dietitians whose program pages have named mechanisms in the title and miss the dietitians with generic program names. The same mechanism logic applies to the rest of the program copy — "insulin-sensitivity support through low-glycaemic carbohydrate patterning and resistance-training rhythm" is citable; "feel better in your body" is not.
§03The page
The program page shape that ranks and converts
The shape is consistent across high-converting credentialed-dietitian program pages. Above the fold: program name with mechanism, one-sentence thesis, named credentialed practitioner, price, start date or cohort cadence, primary CTA. First 200 words: what the program is, who it is for, what mechanism it works through, what outcome it is built to support. Body: timeline and weekly structure, what is included (sessions, materials, tracking, support), the practitioner bio with credential and named modalities, named outcomes (hedged to 'support' verbs), a clear refund and cancellation policy, an FAQ section as readable content. Secondary CTA after the bio; tertiary CTA after the FAQ.
The first-200-words rule is the highest-leverage move on the page. AI engines extract from opening passages disproportionately, and a program-page opening that answers "what is this and who is it for" in a self-contained passage gets cited; one that opens with "Welcome! I'm so glad you found this program" does not. The opening should read like an answer card, not a welcome letter: "PCOS Metabolic Foundations is a 12-week structured program for women with PCOS who want to support insulin sensitivity through a defined low-glycaemic eating pattern and resistance-training rhythm. The program is delivered by Jordan Lee, RD, LD, with one 1:1 session per week and a structured weekly curriculum. Investment: $1,200 for the 12 weeks."
The pricing transparency is the second high-leverage move and the one practitioners most often resist. Hiding price behind a discovery call increases friction without improving conversion; the prospect either commits the call to ask the price (high cost), or they bounce because the price field is the highest-leverage filter they need. The audit-tested 2026 pattern is to publish the program price on the landing page, with a one-line note about insurance applicability where relevant, and let the discovery call cover fit and clinical specifics rather than commercial terms.
§04Schema
Service schema with named offering and credentialed provider
Ship one Service schema block per program page<InlineCite n={1} sourceId='schema-service' />. The Service carries serviceType naming the modality, name matching the program name, description matching the first-200-word thesis, provider referenced by @id to the practitioner Person, and offers as a sub-block of @type Offer carrying price, priceCurrency, availability, and validity dates. The credentialed-author signal inherits via provider, which is why the credential graph on the site-wide header (MedicalBusiness + Person with hasCredential and knowsAbout) is the prerequisite for any of the per-program schema to work.
Offer2 is the commercial-terms block. Price, priceCurrency, and availability are the three properties Google reads with confidence; validFrom and validUntil express cohort-specific date ranges. For a recurring cohort program, availability stays "InStock" with valid dates rolling forward; for a one-time cohort, validFrom and validUntil bracket the enrolment window and availability flips to "Discontinued" after.
JSON-LDService + Offer schema for a named cohort program — paste into page-level Code Injection footer
<script type="application/ld+json">{"@context":"https://schema.org","@type":"Service","name":"PCOS Metabolic Foundations: A 12-Week Insulin-Sensitivity Program","serviceType":"Medical Nutrition Therapy for Polycystic Ovary Syndrome","description":"A 12-week structured program supporting insulin sensitivity through low-glycaemic eating patterns and resistance-training rhythm, delivered by a Registered Dietitian.","provider":{"@id":"https://yourpractice.com/#practitioner"},"areaServed": ["Texas","Colorado"],"offers":{"@type":"Offer","price":"1200","priceCurrency":"USD","availability":"https://schema.org/InStock","validFrom":"2026-06-01"}}</script>
The provider reference is the credential lever. Because the practitioner's Person schema (with hasCredential and knowsAbout) lives in the site-wide header injection, referencing it by @id from each Service block is enough to attach the credential signal to every program on the site at once. Re-declaring the Person inside each Service block is duplicative and produces structured-data warnings; the @id reference is the clean pattern.
§05Delivery
Member Areas, gating, and the SEO question
Squarespace Member Areas<InlineCite n={4} sourceId='sq-member-areas' /> are the native paywall and gated-content layer. Member-gated pages are typically noindexed (Squarespace's default for gated content) and unreachable to crawlers, which means they are invisible to search and to AI engines. The implication for dietitian programs is operational: the program landing page must be a separate public page that ranks, gets cited, and routes prospects into the gated content — not the Member Area itself. The Member Area is the delivery layer; the public landing page is the discovery and conversion layer.
The architectural split looks like this: /programs/pcos-metabolic-foundations/ is the public landing page (indexed, crawled, schema-bearing, conversion-optimised). /members/pcos/ is the Member Area (gated, noindexed, the actual program content lives here). The booking or enrolment CTA on the public page routes through Squarespace Commerce or a third-party checkout to the Member Area subscription. The two pages have different jobs and should not be combined into one.
§06FAQ
FAQ format on program pages without FAQPage schema (2026)
Program-page FAQ sections answer the predictable enrolment questions — timeline, what's included, insurance applicability, refund policy, who the program is for. These FAQs belong on the page as readable content because prospects genuinely use them to pre-qualify themselves. They do NOT belong wrapped in FAQPage JSON-LD as of 2026-05-07, when Google retired FAQ rich results in general Search<InlineCite n={3} sourceId='google-faq-retirement' />. The rich result no longer triggers; the schema does nothing for visibility; and on YMYL pages the schema can dilute the page's overall trust signal because it signals 'this page is primarily an FAQ' when it is primarily a program landing page.
The clean 2026 pattern is Heading-3 questions with paragraph answers, rendered as ordinary content. No JSON-LD wrapper. The questions still work as anchor-link targets, still get extracted by AI engines reading the page content directly, and still help prospects scan the page to find the answer to their specific question. What is lost is the FAQ rich result in Search — which is the loss that happened to every site on the internet on 2026-05-07, not a loss specific to dietitians.
The honest list of questions to answer on a program FAQ: how long is the program; what is the weekly structure; what is included beyond the sessions; is this in-network with my insurance; what is the refund policy; who is the program for and who is it not for; do you take payment plans; what happens after the program ends. Eight questions is the right ceiling — more than that turns the FAQ into the body of the page, which signals the page is primarily an FAQ and dilutes the program-landing-page intent.
