Web Development for CPA and Tax Prep Practices

Tax practitioner sites face the YMYL bar plus credential transparency. Every claim has to be verifiable. CPA license numbers, EA enrollment numbers, and PTINs matter and should be displayed where they are public.

Reference build: Handled Tax

We built the Handled Tax site for Amanda’s solo CPA practice in the Bentonville and Pea Ridge corridor. The build replaced a TaxDome-only marketing surface with a real publishing platform. FastAPI plus SQLite blog admin at /admin/ (modeled on the ARCW pattern) gives Amanda direct publishing control without going through a vendor portal.

Specialty pages, not generic services pages

Generic “Tax Services” pages lose. Specialty pages win:

Trust signal discipline

AccountingService plus Person schema with CPA license number, jurisdiction, and PTIN/EA where public. Phone obfuscation plus form honeypot to keep scrapers off the contact channel. TaxDome client portal embed swapped for a clean “book a call” CTA on the marketing surface. Review schema only included when verifiable third-party reviews exist; fabricated AggregateRating is a Google policy hit.

Pricing

Production builds from $997. Full Visibility Stack from $397/month. See full pricing.

Tax prep FAQ

Can we publish client testimonials?
Yes if they are real, attributed, and consent-documented. Avoid revealing client tax situations even with names withheld; tax matters are sensitive enough that even generic anonymized stories can identify specific clients in a small market.
Should we display CPA license numbers publicly?
Yes. License numbers are public record through state boards of accountancy. Displaying them is a trust signal, not a risk. Hide them and the prospect wonders why.
Do we need separate pages per IRS form?
Not for every form, but yes for the high-search-volume specialty filings (W-7 ITIN, 5471, 5472, 8865, 1116). Tax pros searching for help with these specific forms convert at very high rates.