Catering Sites: 3 of 10 Say How Far Ahead to Order

A customer has 30 people coming on a Saturday and a number in their head. They open four caterer websites, and on three of them they cannot find out how far ahead they need to order. On 9 October 2026 we read 10 Singapore caterer pages that rank for buffet catering searches. Three said how far ahead to book. Four showed a per-pax price. One gave a delivery fee. None showed a halal certificate number.

The gap is not design and it is not speed. It is five facts a buyer needs before typing a message, and most of these pages supplied two of them.

What a catering buyer needs before they enquire

Five things decide whether an enquiry gets sent: what it costs per head, the smallest order you will take, how early you need the order, what delivery adds, and whether the halal claim can be checked. Everything else on a catering page is a photograph.

Those five are the questions that stop an order. A buyer with 30 guests and a Saturday deadline cannot act on "contact us for a quote". They can act on "$26 per pax, minimum 30, five working days". Our guide for caterers already argues that a licence and a certification are proof most caterers keep in a drawer. This study checks whether anyone has taken it out.

The five facts, counted

Every figure below comes from one run between 07:10 and 07:25 Singapore time on 9 October 2026: four searches through our own SearXNG metasearch, then the ranked page of each Singapore caterer fetched and read, then a technical audit of the same 10 sites. Counts are always given with their base.

#	What we looked for	The number
1	Pages stating how far ahead to order	3 of 10
2	Pages stating a last-minute turnaround instead	2 of 10
3	Pages saying nothing about time at all	3 of 10
4	Pages showing a per-pax price	4 of 10
5	Pages showing a minimum number of guests	7 of 10
6	Pages giving a delivery fee you could add up	1 of 10
7	Pages referring to halal status in some form	10 of 10
8	Pages showing a halal certificate number	0 of 10
9	Pages naming MUIS in visible text	3 of 10
10	Pages whose first paragraph named the service	8 of 10
11	Pages carrying business-entity schema	8 of 10
12	Sites blocking GPTBot, ClaudeBot, PerplexityBot or OAI-SearchBot	0 of 10

Row 6 is the one we did not expect. One page in ten told a buyer what delivery would cost.

Only 3 of 10 said how far ahead to order

Three pages gave a notice period: "at least 5 days in advance", "at least 5 working days in advance", and a third that gave three different figures in one page — 72 hours for self-collection, at least two weeks for full-service catering, and a minimum of three days on its own booking form.

That third page is the more interesting miss. Three numbers on one page is not transparency; it is a decision the reader has to make on your behalf, on a phone.

Two more pages answered a question about time that nobody had asked them. One advertised up to 500 guests "within just 4 hours". Another advertised the same 500 guests twice on one page, once at two hours and once at three.

Both are turnaround claims, and we have written about what a 24-hour promise costs you when the phone rings. A turnaround claim answers "can you come today". A notice period answers "am I too late". Opposite questions, and five of the ten pages answered neither.

Two others gave a reply time or a day-before confirmation. A reply inside two business days is useful once an enquiry exists. It does nothing for the buyer deciding whether to send one.

4 of 10 published a per-pax price, 7 showed a minimum

The four pages that priced per head ran from $15 to $70 a pax across all menu types, with one page labelling its figures "just an approximate idea". The mini-buffet band was tighter: the two pages that priced small orders showed $18.90 and $22.90 a pax before GST.

Minimums were the best-answered fact in the sample. Seven pages stated one, and the numbers ran from 10 guests for a mini buffet to 100 for a gala dinner, with 15, 20, 25, 30 and 40 all appearing somewhere.

So the catering market is not shy about the floor of an order. It is shy about the price of one. That is backwards for a buyer, who needs the price to decide and the minimum only to check.

A caterer knows why: the real price moves with menu, day, setup and distance. Our cleaning-sector study found the opposite habit in a trade with the same variability — nine of ten pages showed a price, five the minimum. Variability is not what decides it. What decides it is what you think the page is for.

One page named a delivery fee. One.

A single page in the sample gave an amount: a flat S$20 delivery fee. Two more said a delivery charge applied without saying what it was, one of them adding that it depended on the event location. Seven said nothing.

In our view this is the cheapest fix in the whole study. Delivery is a number you already know, it rarely changes, and it is the last surprise before a buyer commits. A page that quotes $22 a pax and goes silent on delivery has published a price that is not the price.

All 10 claimed halal. None showed a certificate number.

Every page in the sample referred to halal status. Three used the word MUIS in visible text. One carried the certification only as a logo image, with nothing in the page text at all.

Not one of the 10 pages showed a certificate number.

That matters more here than in most trades, because the claim is publicly checkable. MUIS states that it "provides Halal certification services and regulates Singapore Halal industry", and it publishes a search for halal-certified eating establishments. A buyer who wants to verify you can. A machine summarising your page cannot, because a logo is not text and "halal-certified" is not an identifier.

Publishing the certificate number and the certifying body costs one line. It turns a claim into a fact that matches a public register, which is the whole of what trust markup is trying to do.

This is marketing guidance, not advice on certification requirements. Your certifier's own guidance governs what you may display and how.

What the machines were given

Eight of the 10 pages carried business-entity structured data. Two did not: one declared a Place, a Person and an Article but no business, and one carried no structured data at all.

Two of the eight used a food or catering specific type rather than a generic one: a FoodEstablishment with a separate Certification on one, and a FoodService plus a CateringService on another. The rest used Organization or LocalBusiness.

Eight of the 10 first paragraphs named the service, and four named the service and Singapore together. One opened on a sentence about celebrations and sharing food without ever saying what the business sells. One had no paragraph of 15 words or more outside the header, menu and footer.

Three of the 10 sites served an llms.txt file. None blocked GPTBot, ClaudeBot, PerplexityBot or OAI-SearchBot. One used a hosting platform whose default robots.txt stacks 29 named user-agents — GPTBot, ClaudeBot, Google-Extended, CCBot and the ad crawlers among them — immediately above User-agent: *. Stacked that way they share the group that follows, so they get the same short disallow list as everyone else. It looks like a block and is not one, which is worth knowing before you copy what your platform did.

One site was built for something else again. Its robots.txt pointed crawlers at an agents.md file and a machine-ordering endpoint, told agents to use that endpoint for catalogue and cart, and added a line we had not seen on a Singapore service site before: "Checkouts are for humans." A machine-readable subdomain of the same site turned up in one of our four searches. One of ten, in catering, in October 2026.

The speed numbers, and why the lab figures are not the story

We collected a PageSpeed mobile score for 5 of the 10 sites. None reached 70. The five scored 14, 32, 50, 59 and 60, with lab LCP from 5.8 seconds to 54.6 seconds.

Read those lab numbers with care. For three of the five, Google also held real-user data, and the field LCP came back at 1,497 ms, 2,346 ms and 2,688 ms — including on the two sites whose lab LCP read 42.0 and 54.6 seconds. Real visitors on real connections were having a far better time than the lab test. Our Core Web Vitals guide explains which of the two to act on.

The number we would act on is plainer. Server response time before anything rendered ran from 166 ms to 12,630 ms, and 4 of the 10 sites took more than 2.5 seconds to answer at all. A page that has not started arriving is not a design problem.

What I would do this week

For a caterer, in this order:

• Put the notice period on the page that buyers land on. One sentence: the earliest you need the order, and the cut-off for next-day. If it differs by order type, say so in one table, not three places.
• Add the delivery line. A flat figure, a zone figure, or "free above X". Any of the three beats silence.
• Publish a per-pax figure next to each minimum. A "from" price with the menu it belongs to is enough. You already publish the minimum; the price is the half that decides.
• Write the certificate number and the certifying body into the text, not only the logo.
• Check how long your server takes to answer before anyone pays for a redesign.

Four sentences and a hosting check. None of it needs a new website.

What it costs

Honestly: publishing a notice period and a delivery fee will cost you enquiries. People who wanted it tomorrow, and people whose budget stops at the delivery line, will now not write to you.

In our view that is trading volume for qualified volume, which is a real trade and not a free win. If your business profits from talking every buyer through a custom quote, publishing the constraints works against you. If your team is losing hours to enquiries that were never going to book, it works for you. Decide which one you are before you edit the page. And a published number has to be kept true — a stale price is worse than no price.

Method and limits — read these before quoting

• Metasearch is not Google. Results came from SingRank's self-hosted SearXNG on 9 October 2026 for four searches: "buffet catering singapore", "mini buffet catering singapore price", "halal buffet catering singapore" and "buffet catering singapore for 30 pax". Several of its engines returned errors that morning. The ordering is blended, not Google's ranking and not its map pack.
• Ten sites, one page each. We kept Singapore caterers' own sites and dropped directories, listicles, food blogs, social pages and foreign results. We read the page that appeared for the search, not the whole site. A price or notice period published elsewhere on the site was not counted.
• Two replacements. A page from a business SingRank works for was replaced with the next result. So was one page that returned a 404 when we fetched it — and that one had quoted a halal certificate number in its search snippet. The claim was readable in search and not on the page, which is its own kind of miss.
• PageSpeed on 5 of 10. One audit timed out at 60 seconds, so the remaining five were run with PageSpeed skipped rather than retried. Field data existed for 3 of the 5.
• Raw HTML only. We did not run JavaScript, test firewalls or CDN blocking, place an order, or check any certification against the public register.
• Prices are as published on 9 October 2026 and will change. Quote them with the date or not at all.
• One day. A snapshot, not a trend.

Want these five checks on your page?

Send us the one catering page that should win your searches. We will run the same five checks on it and tell you which fact is missing and where it goes. It starts as a free visibility check through our contact page, and if you want us to do the work, our SEO, AEO and GEO programme is 10 articles a month at S$500/month with a three-month minimum, as the live page states today.

What we will not do is promise you a ranking, a citation or a booking. Google and the AI assistants choose their own answers, and a catering order is won by the food long before it is won by a web page.

These findings describe four searches and ten pages sampled on 9 October 2026. This page names no business and is not a rating of any company.

FAQ

How far ahead should a catering page tell buyers to order?

Whatever your kitchen actually needs, stated plainly. In our sample of 10 pages, the three that gave a notice period used 72 hours, three days, five days and five working days for different order types. The figure matters less than having one, because a buyer with a date cannot guess yours.

Should a Singapore caterer publish a per-pax price?

Publish a "from" price against each minimum. Four of the 10 pages we read on 9 October 2026 showed a per-pax figure, ranging from $15 to $70 across menu types. A "from" price with its menu named is enough to let a buyer self-qualify, and it stays true when the custom quote differs.

Does showing a halal certificate number help?

It makes a claim checkable. All 10 pages in our sample referred to halal status and none showed a certificate number. MUIS publishes a public search for halal-certified eating establishments, so the number connects your page to a register a buyer or a machine can consult. Follow your certifier's own display guidance.

What is agents.md on a catering site?

It is a file telling automated shopping agents how to read a store and where to order. One site in our 10 served one, alongside a machine-ordering endpoint and a note that checkouts still require a person. It is early, and we report it as one site in ten rather than a trend.

Can I cite these figures?

Yes. Please cite "SingRank, Singapore catering page study, 9 October 2026", link to this page, and quote each count with its base, such as 3 of 10. Keep the metasearch caveat. If you think a number here is wrong, tell us and we will re-run the check.