The fractional CFO advisory firm trying to be cited by ChatGPT for “best fractional CFO for SaaS startups under $5M ARR” runs into the same wall every time. The site is on CPASite Solutions, or GetNetSet, or a CountingWorks PRO subscription. Underneath, it is WordPress. On top, it is a template that does not let the firm edit JSON-LD, canonical tags, or robots.txt. The audit is short. The fix is a migration.
What is CPA template platform lock-in?
CPA template platform lock-in is the pattern where an accounting firm’s marketing site runs on a niche subscription template provider — CPASite Solutions, GetNetSet, CountingWorks PRO and analogs — that handles AICPA badges, IRS Circular 230 disclaimers, and tax-season copy out of the box but gates the schema, canonical, and robots edits AI citation now requires. The underlying CMS is usually WordPress, but the firm cannot reach it.
The wedge is structural, not editorial. The 2026 schema-completeness research from Growth Marshal (n=1,006 pages) showed pages with attribute-rich, vertical-specific schema cited at 61.7% versus 41.6% for generic Article/Organization/BreadcrumbList markup, with the gap widening to 54.2% versus 31.8% on lower-DR domains where most CPA firms sit. A site that ships only the Organization block its template provider injected by default is on the losing side of that gap, and the firm has no UI to fix it.
What CPA-niche template platforms actually lock
CPASite Solutions and GetNetSet are not generic page builders. They are vertical-specific subscriptions that bundle three things a generalist CMS cannot: AICPA-compliant copy and badging, IRS Circular 230 footer disclaimers and PTIN listings, and an annual tax-season content refresh keyed to the IRS bulletin calendar. That bundle is why the niche providers exist and why CPA firms keep paying for them. The lock-in starts where the bundle ends.
Schema is the first lock. Most CPA-niche templates inject one Organization block and sometimes a LocalBusiness block, populated from the firm’s contact-page fields. They do not inject FAQPage on service pages, Service blocks per offering, or Person blocks per individual CPA. There is no JSON-LD field in the editor. There is, on most providers, a “custom code” tab that sounds like the answer but turns out to be limited to the body section — not the head, where Google and AI crawlers expect schema and where deduplication of @type entries actually matters. AICPA-CIMA represents 431,000+ accounting professionals across 188 countries and the AICPA Directory is one of the surfaces ChatGPT pulls from for accountant queries; the firm’s own site needs Person and Service schema to map onto that directory’s entity graph, and the niche template does not let it.
Canonical tags are the second lock. The provider auto-generates the canonical from a URL pattern the firm cannot edit. For the standard pages (homepage, about, services index, contact) the auto-generated canonical is correct. For any non-default landing page — a fractional CFO sub-page targeting SaaS, a 280E cannabis tax page, an ERTC audit defense page, a K-1 partnership returns page — the firm needs to set a canonical that points to the correct primary URL, and the template will not surface the field. The firm’s options are to live with whatever canonical the template emits, or to leave.
Robots.txt is the third lock. CPASite Solutions, GetNetSet, and most analogs serve robots.txt as a platform-managed file with no editable view. The firm cannot add User-agent: GPTBot Allow: / or remove a 2024-era block list inherited from a theme update. The IRS RPO Preparer Directory, the AICPA Directory, and the AceCloud 15 Directories aggregator all link out to firm sites; if the firm’s own robots.txt blocks ClaudeBot or PerplexityBot — even by accident through an inherited template default — the AI engines that pull from those directories cannot fetch the destination page. The audit dies before it starts.
CPASite Solutions, GetNetSet, and the schema problem
The schema problem is where the audit usually lands first because it is the easiest to verify. Open the firm’s homepage in an incognito tab, view source, and search for application/ld+json. On a typical CPA-niche template the result is a single block: Organization or LocalBusiness, with name, address, telephone, and a logo URL. No sameAs array pointing at the firm’s AICPA member page, state CPA society listing, IRS RPO entry, or Ramsey trusted profile. No FAQPage block on the services page that has visible Q&A markup in the body. No Service block per offering. No Person block per individual CPA, which is where the AICPA Code of Professional Conduct disclaimers and state-board credential lines should be wired into the entity graph.
This pattern matches the analogous niche-template trap on the dental side — ProSites and Sesame ship a similar shell on similar WordPress underneath, locked in similar ways — and the analogous niche-template trap on HVAC. The vertical changes; the lock pattern repeats. WordPress core is server-rendered PHP that delivers content and JSON-LD in the initial HTML response, so the platform itself is not the problem. The niche template above WordPress is. This is the WordPress underneath, the niche template above wedge — the underlying stack would let Yoast Schema Aggregation (released March 2026) or Rank Math’s llms.txt feature ship a full schema map, but the niche template never installs them and never exposes the fields that would let them work.
The answer-capsule version is short. Yoast and Rank Math both let WordPress sites edit canonical, sitemap, robots.txt, and llms.txt natively in 2026. CPASite Solutions and GetNetSet sit on top of WordPress and do not surface any of those plugins to the firm.
Why is the schema gate the most damaging lock?
Because schema completeness is the strongest controllable lever for AI citation. The Growth Marshal February 2026 study put attribute-rich, vertical-specific schema at a 22-point citation-rate advantage over generic markup on low-DR domains — exactly where most CPA firms sit. A template that ships only an Organization block forfeits that advantage every day it stays live, regardless of how good the copy is.
Why the audit usually starts with “leave the template”
The honest output of a CPA-template GEO audit is rarely a fix-in-place plan. It is a migration plan. The audit confirms what the firm already suspects: the schema is gated, the canonical is auto-generated, the robots.txt is platform-managed, and the head injection point that would solve all three does not exist in the editor. Once those four findings are documented, the conversation is no longer about plugins or settings. It is about whether the firm migrates to a configurable WordPress install (with Yoast or Rank Math), to a Webflow build, or to a static Astro rebuild — three options with different cost and timeline profiles but all of which return head-tag access to the firm.
The migration calculus on a CPA-niche template is similar in shape to the vertical playbook the platform-wedge serves on the accounting side — the same firm running the migration is also building the prompt-targeting and directory-graph work the vertical playbook describes — and similar to how the dental-template wedge maps onto the cosmetic dentist vertical playbook. The wedge moves the firm to a stack that can ship the citation work. The vertical playbook tells the firm what citations to ship.
Practical migration windows: a configurable WordPress migration runs 14 to 21 days for a typical 12-page CPA site; a Webflow migration 10 to 14 days; an Astro static rebuild 7 to 14 days. Content portability is high in all three cases because the source CMS is WordPress underneath and the niche provider used standard WordPress export hooks. AICPA badges, IRS Circular 230 disclaimers, PTIN listings, and state-board credential lines all migrate verbatim as static assets and copy blocks. The 301 redirect map preserves any organic ranking the niche-template URL pattern earned.
Migration off a CPA template: the 14-day playbook
Day one to three is the audit and content extract. Pull the full page inventory, extract the body copy and image library through the niche provider’s WordPress export (every major CPA-template provider runs WordPress underneath and supports it), document every Circular 230 footer and AICPA disclaimer, and capture the existing canonical and meta tags so the new site can preserve or correct each one deliberately. Day four to seven is the rebuild on the target stack — configurable WordPress with Yoast, or Webflow, or static Astro. The work in this window is structural: head-tag access for JSON-LD, FAQPage block on every service page that has Q&A copy, Person block per CPA with AICPA member URL in sameAs, Service block per offering, and a robots.txt that explicitly allows GPTBot, ClaudeBot, PerplexityBot, and CCBot.
Day eight to twelve is the schema and entity-graph build. Wire each Person block to the firm’s AICPA Directory page, IRS RPO listing, state CPA society profile, and any RamseyTrusted entry — the four directories research/03 names as the citation surfaces AI engines pull from for accountant queries. Add a knowsAbout array to the Organization block enumerating the firm’s actual specializations (SaaS revenue recognition ASC 606, K-1 partnership returns, ERTC audit defense, 280E cannabis compliance, international tax for expats — whichever apply). The entity graph this builds is what gives ChatGPT the structured signal that the firm exists, is real, and is positioned to answer the prompt the buyer just typed.
Day thirteen and fourteen is launch and 301 redirect verification. Every URL on the niche-template site points to its new home. The Circular 230 footer and PTIN listing render verbatim. The AICPA badge image lives at its new path with the same alt text and outbound link. Lighthouse mobile score moves from the typical CPA-template 30s into the 80s or 90s depending on target stack. JSON-LD validates across every page in Google’s Rich Results Test and Schema.org’s validator.
The compliance angle for AICPA-bound firms
The compliance work during a migration is small and well-bounded. IRS Circular 230 governs solicitation, false advertising, and contingent-fee disclosures — none of which depend on the CMS. The AICPA Code of Professional Conduct restricts testimonial use depending on state, again CMS-agnostic. What needs care is the disclaimer language already on the template, which has to migrate verbatim: the Circular 230 footer notice, the PTIN listing format, the state-board credential lines, and any required language for fee structures or guarantees. None of that is template-locked. All of it is firm-owned copy.
The migration also preserves every external compliance touchpoint. The AICPA member URL in the firm’s sameAs graph stays valid; the IRS RPO Preparer Directory entry stays valid; the state CPA society listing stays valid; the RamseyTrusted profile, if the firm holds one, stays valid. The directories AI engines pull from for accountant queries do not know or care which CMS the firm’s site runs on. They care that the site is reachable, that the entity graph is consistent, and that the schema lines up with what the directory says about the firm. The niche template gates that work. The migration unlocks it.
This is the pattern the hub-up to vertical-citation playbooks covers across all eight verticals: a platform-wedge sits underneath a vertical playbook, and the platform-wedge has to ship before the vertical work can compound. For accountants in 2026, the platform-wedge is the CPA template lock-in. The audit is short. The migration is the answer.
