Most CPA Firms Don't Need More Schema. They Need a Better-Connected Graph.

Search "schema markup" and you will find lists of dozens of types an accounting firm could add. Most firms do not need to begin with a longer checklist. They need a cleaner graph.

We would fix two relationships first: the firm and its offices, then the professionals who work there.

First, what schema actually is

Schema markup is structured data: a block of code that describes the people, organizations, places, and content represented on a page. It does not change what visitors see, but it can help search engines and other systems interpret the relationships more explicitly. Think of it as an explicit label attached to information the page already shows.

That last part is a rule, not a throwaway. Schema should describe visible, supportable information rather than inventing claims behind the page. For an accounting firm, the useful part is making relationships clearer: this person works for this firm, holds this role, and practices in these areas.

Start with the business

Use Organization for the parent firm and AccountingService, a subtype of LocalBusiness, for each real, staffed, customer-facing office. Give every node a stable @id, and make sure the name, address, phone number, and hours agree with the website, the Google Business Profile, and the firm's major directory listings.

Local business markup does not guarantee a map-pack ranking. It gives search systems a clearer, structured version of facts they can also find elsewhere, and its value increases when those sources agree. If the firm has multiple staffed offices, represent each one separately and connect it back to the parent organization. A virtual office, a mailbox, or a service area is not a branch.

Then connect the people

Each important professional should have a substantive biography that clearly states their role, credentials, specialties, and relationship to the firm. Use Person markup to describe those same visible facts and connect the person back to the organization.

The schema does not prove that someone is qualified, and it does not guarantee that an AI assistant will recommend them. It removes ambiguity. Is this person currently employed by the firm? Is the credential attached to them or just sitting nearby in the text? Does the specialty belong to the person or to the practice generally?

That distinction matters. In our 556-firm study, 94.2 percent of reachable sites had no Person schema at all. The expertise usually existed on the page. The structured connection between the person, the firm, the credential, and the specialty did not.

Be careful with reviews

There is a strong temptation to add Review or AggregateRating schema so a star rating shows up in search. Google does not provide self-review stars when a business controls the reviews about itself, so adding AggregateRating to your own firm is not a shortcut to a richer result. At best Google ignores it for that feature, and misleading or policy-violating markup creates unnecessary risk. Display legitimate reviews for visitors and link to the source.

Other types can still be useful

Do not add a schema type solely because a plugin makes it available. Service, FAQPage, Article, and BreadcrumbList can all be useful when they accurately describe the visible page and connect to the same organization graph. They are not substitutes for getting the core entities right.

The problem is not the number of types. It is unsupported, duplicated, contradictory, or disconnected markup. We see firms with schema on every page but no stable identifiers linking one node to another. Every block validates independently, and the site still fails to express a coherent relationship between the firm, its offices, its services, and its people.

How to check yours

Use Google's Rich Results Test to check markup tied to supported Google search features. Then use the Schema Markup Validator to inspect the complete graph, including types and properties Google's tool does not report. Our free audit flags missing and malformed structured data across the whole site.

Validation is only the first check. The bar is not "the validator turned green." The markup should describe what visitors can actually verify on the page, use stable identifiers, and connect the firm, its locations, and its professionals into one consistent graph.

Most CPA firms do not need forty more schema types. They need the first few to tell one consistent story. Building that graph for an accounting firm is what our SEO for CPAs work does.