Salisbury Tax and Services: A Deliberately Small 13-Page Site

Bertha Fuentes runs Salisbury Tax and Services in Salisbury, Maryland. The practice does tax preparation, bookkeeping, notary work, translation, secretarial services and business licensing, and it works bilingually — which for a meaningful share of her clients is the deciding factor, not a nice-to-have.

The interesting constraint here was scope, and it runs against the incentive of anyone selling this work. An agency paid by page count will always find a reason to build 60 pages. This practice sells six services from one office. Sixty pages would have meant padding, near-duplicate town pages for markets she does not target, and a site whose thin pages drag on the strong ones. The right build was a small one.

Thirteen URLs. Six service pages, one per service line, each written for a buyer who has a specific job in mind rather than a general interest in accountancy. Server-rendered, so the copy is in the initial HTML response.

Schema doing real work on a small site

The structured data is where a 13-page site earns its keep. Deployed: LocalBusiness with an OfferCatalog containing six Offer and Service nodes, PostalAddress, GeoCoordinates, OpeningHoursSpecification, areaServed expressed as both the city and a 50-mile GeoCircle, the founder as a Person entity carrying an EducationalOccupationalCredential, FAQPage and BreadcrumbList.

The detail worth singling out is knowsLanguage, which declares English, Spanish and Portuguese. Plenty of sites say "se habla español" in a header image or a footer line. That sentence is not machine-readable, and an image certainly is not. Stating it in schema means a system answering "is there a Spanish-speaking tax preparer in Salisbury" has a structured fact to work from rather than a phrase it has to notice and interpret. It is one property, and it is the difference between a capability being visible to software and merely being visible to a human who already found the page.

The GeoCircle does similar work. A 50-mile radius from a fixed coordinate states the service territory as geometry, which is unambiguous in a way that a list of town names in a paragraph is not.

Thirteen URLs, six service pages, server-rendered, with the schema stack above live and verifiable in the page source as of 16 August 2026. That is the site, and for this practice it is the correct size of site.

What is not done yet

Two gaps, named here because a case study that reads as finished when it is not is just an advertisement. There is no llms.txt on this site yet — we sell llms.txt implementation and it has not been shipped here. And there are no location pages yet, so the practice is currently competing on the strength of its own address rather than on dedicated coverage of the surrounding towns.

Both are on the list, in that order. If either were being hidden, you would find them yourself in about ninety seconds, which is a reasonable test to apply to anything an agency tells you.

The general point this build makes: not every business needs 134 pages. Matching the site to what is actually sold beats padding it to look substantial, and a small site with correct structured data outperforms a large one without it.