If your Vercel bill is too high for a Next.js site that does not get much traffic, the problem is almost never the traffic. It is a handful of configuration choices that make every request, crawl, and content edit cost more than it should. This post walks through the usual culprits on Sanity-backed sites, how to confirm each one, and the order I would fix them in.
Symptoms that point to a config problem, not growth
The pattern is consistent. Usage climbs while analytics visitors stay flat. A month with one big content import costs more than a month with a campaign. The invoice has line items nobody on the team can explain. If any of that sounds familiar, you are paying for waste.
Before touching code, open the Usage page in the Vercel dashboard and note which metric is largest: data transfer, edge requests, function duration and invocations, image optimization, or ISR reads and writes.…