A customer once asked me, mid-build, "can you just use Helvetica?" The brand had no specific type identity, the customer wanted something safe, and Helvetica is famously safe. Helvetica is also wrong for almost every small business website built in 2026, and explaining why takes a minute.
This piece is about how we choose typefaces for a small business website. It's not a deep typography essay; the world has those already. It's the practical rules we apply, what to pick, what to avoid, and the ten-second test for whether a pair is working.
What we use, mostly
Three families show up repeatedly across the sites we ship:
Source Serif 4 for headings on editorial-warm sites. The Copper Fox, La Quinzaine, our own marketing site — anywhere we want a register that reads as quietly considered, slightly old-world, magazine-adjacent. Source Serif is generous, slightly humanist, and renders beautifully across sizes.
Geist Sans for body and UI on the same sites. The pairing of a humanist serif with a contemporary geometric sans is conventional but it works because the contrast is real — the serif carries the editorial register, the sans handles utility text without competing.
Geist Mono for data, code-like content, eyebrow labels. Where the design wants a small typewriter-y mark of precision — meta tabs, version stamps, "stamped" filing tags, bylines.
That's the ThemeSmith default. About 70% of the sites we ship use this stack or something close. The remaining 30% need something else, and that's where the choosing gets interesting.
When the default is wrong
A few cases where we move away from Source Serif + Geist:
For a high-energy brand — gym, sports nutrition, indie game studio — the editorial-warm register is wrong. We swap to a more contemporary display face for headings (Space Grotesk, Inter, or a slightly louder grotesque) and keep Geist for body.
For a luxury brand — fine jewellery, prestige automotive, weddings — Source Serif is too soft. We swap to a more refined classical face (Cormorant, Crimson, Tangerine for accents) that reads as more formal.
For a technical brand — software, infrastructure, B2B tooling — both serifs and warm sans are wrong. We use Inter, Geist, or IBM Plex Sans throughout, with no serif element.
For a heritage brand with existing wordmark — established companies with type already in their identity — we don't impose ours. We work with what they have.
The rule is: the typeface choice serves the brand register, not the design system's defaults. Defaults are starting points, not destinations.
Why never Helvetica
Helvetica is technically a fine typeface. It's also the wrong typeface for most small business websites in 2026 for three reasons.
It's category-default. Helvetica is the typeface every templated site has used for fifteen years. A site set in Helvetica reads as having defaulted rather than chosen. Even if the customer thinks they're choosing it, the visitor reads it as a non-choice.
It's tonally cold. Helvetica was designed in 1957 to be neutral, modernist, anonymous. That's the opposite of what most small businesses want their site to feel like. Small businesses are warm, specific, run by people. Helvetica reads as institutional.
It renders badly at body sizes on screen.This is the technical part. Helvetica's metrics were optimised for print at metal-type sizes; on screen at 14-18px body, it has slightly tight letterspacing and slightly small x-height that make body copy harder to read than alternatives like Inter or Geist that were designed for screen rendering.
The alternative we'd pick if the customer specifically wanted "clean modern sans" is Inter or Geist. Both are categorically better for screen use than Helvetica, free to use, and don't carry the templated-default association.
The pairing test
When we pair a heading face with a body face, we do a ten-second test. Open both faces side by side. Look at the vertical proportions — the relationship between x-height (the height of a lowercase 'x') and cap height (the height of an uppercase letter).
If the two faces have roughly similar x-height proportions, they pair. If they're noticeably different, they fight.
This is the simplest type-pairing rule that produces good results. Two faces with similar x-heights but different shapes — Source Serif and Geist Sans, for example — sit comfortably together because the visual rhythm of the pair is consistent even though the visual style is different.
Two faces with different x-heights — Cormorant and Helvetica, for example — produce visual jitter where the proportions don't quite line up. The reader doesn't consciously notice but reads the layout as slightly chaotic.
The full version of type-pairing involves much more (counter shape, axis, contrast ratio, weight balance), but the x-height test catches 80% of bad pairings in ten seconds.
What we never do
A few rules we hold ourselves to:
Never more than three typefaces on one site. Two is the strong default (heading + body). Three only when there's a clear functional role for the third (mono for data, accent display for a single section). Four typefaces is design panic.
Never use a pure decorative display face for body copy. Decorative faces (Lobster, Pacifico, Playfair Display Italic) are for headlines and never longer than a sentence or two. Body copy in a decorative face is unreadable.
Never use the system default fallback as the design. A site whose CSS reads font-family: -apple-system, BlinkMacSystemFont, sans-serifis a site that's defaulted instead of chosen. We always pick a specific font. (And we self-host it, so the choice doesn't depend on the visitor's device.)
Never stretch or compress letterforms. If the heading is too wide for the column, we change the font size or break the line, not the letter shape. Stretching letterforms is amateur-hour and visibly so.
Never use bold on body copy as emphasis. Body copy emphasis is italic, or a slight increase in weight (regular → medium, not regular → bold). Bold within paragraphs creates visual jumps that fight the reading rhythm. We use bold for headings and key terms only, in paragraphs almost never.
What we ask the customer
When a customer's brief doesn't specify type preferences, we ask one question: what magazines or websites do you read that feel right to you? Their answers tell us the register without them having to articulate it.
A customer who reads Apartamento, The Gentlewoman, and The New Yorker gets a serif-led, editorial-warm system. A customer who reads Wired, Verge, and Stratechery gets a sans-led, contemporary-tech system. A customer who reads Vogue Italia, 032c, and Pitchfork gets a louder, more contrasted system.
The question reveals more than asking about typefaces directly.Most customers can't name a typeface they like; everyone can name a magazine they read.
The practical rule
If you're choosing type for your own small business site without us, the rule is simple:
- Pick one heading face that fits your brand register. Warm? Serif. Tech? Sans. Luxury? Classical serif.
- Pick one body face with similar x-height that doesn't fight the heading. When in doubt, Inter or Geist for sans body, Source Serif or Crimson for serif body.
- Maybe pick one mono face for data (Geist Mono, IBM Plex Mono).
- Self-host all of them. Don't depend on Google Fonts CDN; the third-party request slows the page and introduces a privacy concern.
- Test the pair at 14-18px body size on a phone. If it reads cleanly there, it'll read cleanly everywhere.
That's it. The whole craft of small business type selection compresses to those five steps. Most templated sites get all five wrong. You can do better in twenty minutes.