The cosmetic-dental site gets one decision wrong before content, before SEO, before the AACD badge ever loads. It picks a dental-niche template provider — ProSites, Sesame Communications, PBHS, or Smile Marketing — because the sales deck promised “dental-specialized” templates, before-and-after galleries that work, and HIPAA-safe forms. Then the citation ceiling lands. The editor that promised dental specialization is the same editor that gates schema, gates canonical, and gates the head tag where AI engines look first.
What's actually locked behind dental-niche templates in 2026
Dental-niche CMSs — ProSites, Sesame Communications, PBHS, Smile Marketing — host the majority of cosmetic-dental sites in 2026. Almost all run WordPress underneath, but the dental wrapper gates schema editing, canonical control, and head-tag access. AI engines see the gated output: incomplete entity graph, no FAQPage on veneer pages, missing Person + hasCredential blocks for AACD-accredited providers.
The gate matters because of where AI citation actually comes from. Closed CMSs that inject JSON-LD client-side or cap schema on the page hit the same wall the 12-platform 2026 leaderboard ranks Wix, Squarespace, and GoDaddy against — Wix at 8,000 characters of schema cap and 6.8-second mobile LCP; Squarespace with no editable canonical and no FAQPage schema; GoDaddy with no robots.txt access and no custom JSON-LD path at all. ProSites, Sesame, PBHS, and Smile Marketing are not on that named leaderboard, but the failure mode is the same closed-CMS pattern: a hosted editor that does not expose what AI crawlers need.
The dental-vertical evidence is in research/03. There is no 2026 dental-specific BuiltWith breakdown, but the industry pattern is clear: dental-niche template providers (ProSites, PBHS, Sesame Communications) host the majority of cosmetic-dental sites; many lock CMS internals; WordPress sits underneath in many cases. WebCraftDev’s 2026 dentist-website-cost teardown confirms WordPress as the most common dental platform once you peel off the dental-niche wrapper. The lock is not the underlying CMS — it is the wrapper above it.
That distinction is the wedge. WordPress with Yoast or Rank Math has shipped llms.txt natively since 2025/2026, exposes the canonical URL on every page, and runs FAQPage schema as a first-class feature. The same WordPress install behind a ProSites or Sesame template has none of those switches surfaced in the editor a dental practice ever sees.
ProSites vs Sesame vs PBHS vs Smile Marketing — feature lock comparison
All four ship dental-template plus hosted editor. Public 2026 documentation does not detail per-tier schema, canonical, or head-tag access — but the closed-CMS pattern is consistent across the category: schema and canonical edits are gated behind upgrade tiers or simply unavailable. The fix path is rarely “upgrade your ProSites tier.” (Inferred from the closed-CMS pattern; vendor-specific tier feature matrices are not publicly published in 2026.)
ProSites positions on dental-vertical specialization and a curated template library. Sesame Communications is the patient-engagement-plus-website bundle, with the website often the back end of the patient portal and the appointment booker. PBHS is the longest-tenured dental-template-plus-marketing shop in the US, with a reputation built on physician/dentist medical-legal compliance. Smile Marketing positions on lead capture and conversion-template variants, often paired with a paid-search service.
The four sell different stories at the front end. The closed-CMS pattern they share at the back end is the citation problem. From the AI-engine point of view, a Sesame site, a ProSites site, and a PBHS site all look like the same failure mode: a server that returns HTML with limited schema, limited or absent FAQPage markup, and a head tag the practice cannot edit.
The honest 2026 statement is this: research/04 documents the closed-CMS pattern across Wix, Squarespace, GoDaddy, and HubSpot in detail; research/03 documents the dental-niche providers (ProSites, PBHS, Sesame Communications) as the dominant CMS slice in cosmetic dentistry and confirms WordPress underneath in many cases. The category-level diagnosis travels. The vendor-specific feature audit — which exact tier on Sesame unlocks JSON-LD, whether PBHS Premium exposes the canonical URL — is not in the public record in 2026, and it changes per practice depending on what was sold five years ago and never renegotiated.
That is the audit the practice needs to commission. Not a lookup. A check.
Why 'WordPress underneath' isn't the same as WordPress
WordPress with Yoast or Rank Math has full schema control, native llms.txt, editable canonical per page, and median LCP that hits sub-2.0s on Bricks Builder + a lightweight theme. The same WordPress install wrapped in a ProSites or Sesame template has none of those switches surfaced. The dental wrapper is what gates the AI-citation features, not the engine underneath.
The platform-wedge logic for cosmetic dentistry runs through this gap. The WordPress underneath, locked by the dental template framing is the cross-hub link to the WordPress builders comparison: WordPress + Bricks Builder + Yoast/Rank Math sits at rank 4 on the 12-platform 2026 leaderboard with sub-2.0s LCP achievable, native llms.txt, and full schema control. ProSites and Sesame do not appear on that leaderboard because they are not standalone CMSs — they are dental-niche wrappers — but the underlying engine in many of their installs is the same WordPress that ranks 4th when configured directly.
The migration math falls out of that. A dental practice on a Sesame template that wants to ship full schema and rank in AI citations does not need a new CMS — it needs the wrapper off. A clean WordPress install with Bricks, Yoast or Rank Math, and a lightweight theme like Astra or Kadence delivers everything the closed dental CMS gated. Practices that want a stricter performance ceiling — sub-second LCP, JSON-LD in the initial HTML response with no plugin dependency — go a step further to a static rebuild on Astro, the same migration the Wix AI ceiling cluster maps for med-spas and B2B SaaS.
Either path — WordPress + Bricks or static Astro — restores what the dental wrapper hides: the head tag, the canonical, the schema layer, the robots.txt, and the llms.txt.
The migration audit: what to keep, what to rebuild
Keep: AACD accreditation status, before-and-after image library, patient testimonials with HIPAA releases on file, Google Business Profile (re-verify ownership only). Rebuild: every page’s schema layer including Person + hasCredential for AACD-accredited providers, FAQPage on veneer/implant landing pages, Organization + memberOf the AACD, sameAs to AACD member-directory profile, canonical URLs per page, llms.txt, and robots.txt.
The keep list is what makes the migration tractable. AACD accreditation is the credential, not the website — the badge survives the move. The before-and-after gallery is the most expensive content asset on a cosmetic-dental site, and it is image data that ports anywhere. The patient testimonials with HIPAA releases on file are likewise content, not platform-bound. The Google Business Profile is owned by the practice, not the agency or the CMS — re-verifying ownership is a 10-minute task on the Google side and ports zero risk to the migration timeline.
The rebuild list is where the citation work actually happens. AACD’s own ChatGPT-impact article — the lateral that the AACD-citations playbook covers in detail — makes the point that schema is what tells AI engines an AACD accreditation exists. Without it, the badge is a JPEG. With it, the entity graph carries Person → hasCredential → “AACD Accredited” → sameAs → AACD member-directory URL, and ChatGPT, Perplexity, and Claude can resolve the credential and weight the practice accordingly when answering “AACD-accredited cosmetic dentist near me.”
FAQPage schema does the same job for the procedural queries. Sample 2026 buyer prompts from research/03 include “Cosmetic dentist who does same-day veneers, NYC”, “Top All-on-4 implant specialist Houston”, “Best Invisalign provider near me”, “Implant dentist who does sedation, Phoenix” — every one of which is a question that maps cleanly to a Question/Answer pair in FAQPage schema on the right landing page. The closed dental CMS rarely ships FAQPage; the migration target ships it as a default block.
Organization schema with memberOf the AACD plus sameAs to the AACD directory profile completes the entity graph. This is the same entity-layer logic the Wave-1 vertical with the largest single-win LTV — financial-advisor playbook — uses to map NAPFA and XYPN credentials, just adapted to AACD as the dental-vertical equivalent.
The robots.txt and llms.txt fall out of the migration target. WordPress with Rank Math or Yoast generates llms.txt on every publish; Astro static-rebuild ships llms.txt as a build artifact. The closed dental CMS, in the public 2026 record, ships neither.
The 7-14 day dental migration playbook
Days 1-2: content extraction + image library export. Days 3-5: rebuild on WordPress + Bricks + Yoast or static Astro, including Person + hasCredential schema for every AACD-accredited provider, FAQPage on every procedure landing page, Organization with memberOf AACD. Days 6-9: redirect map (the page slugs are stable on the dental wrapper, port them) + Google Business Profile re-verification + AACD directory sameAs link. Days 10-14: AI-engine resolution check.
The 7-14 day window is consistent with the Wix migrations the Pillar-1 cluster describes — same calendar, different starting platform. The dental-specific work concentrates in days 3-5, where the entity graph for AACD-accredited providers gets built page-by-page. A practice with two AACD-accredited dentists and six common procedures (porcelain veneers, full-arch implants, Invisalign, smile makeover, teeth whitening, dental bonding) needs 8 entity blocks and 6 FAQPage blocks at minimum — work that compresses into roughly two days on a builder that exposes the head tag.
The redirect map is where dental migrations differ from a typical platform-migration audit. ProSites, Sesame, PBHS, and Smile Marketing all use stable, URL-friendly slugs on procedure pages — /porcelain-veneers, /dental-implants, /invisalign — so the redirect map is mostly a 1:1 carry-over. The exception is multi-location practices, where the closed dental CMS often nests location pages under a query string or a non-canonical path. That sub-tree gets restructured during migration, and the redirect map handles the legacy URLs.
The AI-engine resolution check on days 10-14 is the close. ChatGPT, Perplexity, and Claude all index on different cadences post-publish; the practice prompts the engines on the target buyer queries from research/03 (“AACD-accredited cosmetic dentist near me”, “Best veneers dentist in Beverly Hills”) and confirms the new entity graph resolves correctly. Engines that cite the practice on the new schema confirm the migration. Engines that still surface the old wrapper’s content get a second-pass sitemap submission.
The Wave-2 cosmetic-dental opportunity sits inside this window. Research/03 documents no 2026 dental-specific AI citation share study yet — which is the data drop the vertical-citation-playbooks hub is structured to capture. A practice that completes the migration in May 2026 enters the citation graph months ahead of the field, with the entity-graph layer that AACD’s own commentary already named as the survival mechanic.
The same closed-CMS-wrapper pattern shows up in adjacent verticals — the analogous niche-template trap on home-services HVAC and the analogous niche-template trap on real estate cover the same diagnostic with different sales decks above the engine. The cross-hub move into the WordPress comparison is the WordPress underneath, locked by the dental template reference, where the underlying-engine choice gets ranked against builder and theme combinations.
The overarching cluster context — how 8 verticals get cited in 2026 — frames why the platform-wedge approach lands harder in cosmetic dentistry than in most. A $7-50K case ticket on full-arch implants and 8-tooth veneers, AACD’s own commentary already pointing at the AI citation problem, and a CMS layer the practice can leave in 7-14 days. The ceiling is the wrapper. The fix is the migration.
