A caterer's site works best as a grid: event types on one axis, cuisines and dietary menus on the other, and service-area pages that show where you travel. Each page answers the questions its buyer actually asks.
Event-type pages
A wedding catering page should cover plated, buffet and family-style service, cocktail hour options, tastings, staffing and rentals, and the venues you know. A corporate catering page should cover delivery windows, minimum orders, labeled individual meals, setup and pickup, and recurring orders. Private party, holiday party and memorial reception pages each have their own timing and menus. Add a short FAQ to each one built from the questions you hear on the phone.
Drop-off versus full-service
Drop-off catering and full-service catering are different purchases. One is a delivery with a set menu and a minimum; the other includes staff, equipment and a banquet event order. Say clearly which you offer on each page so a buyer looking for one is not sent to the other.
Cuisine and dietary pages
Kosher, halal, vegan and allergen-aware catering are real searches with real stakes for the guest. Build those pages only when the claim is accurate: if your kosher menu is prepared under a specific supervision, say so; if your kitchen also handles nuts, say what you can do instead. A guest with a nut allergy or a family keeping kosher will ask about it at the tasting, and the page should already say what the kitchen told them.
Service-area pages without doorway content
City pages that swap the town name in identical text are what Google calls doorway pages. A useful service-area page names the venues you have catered in that area, the delivery radius and any travel fee policy, local menu requests you see there and photos from events in that town. If you cannot write that for a place, a line in the main service-area list is enough.