Cake Sites: 4 of 10 Say How Many It Feeds

Four of ten customised cake Singapore pages tell a buyer how many people a cake feeds. The other six sell cake by the inch and leave someone who knows only their guest count to guess. Somebody planning a birthday party knows how many people are coming; they do not know what a 6-inch cake is.

That is the gap we went looking for. On 8–9 November 2026 we ran four buyer searches through our own metasearch, kept the Singapore cake businesses in the results, and read 13 of their websites. Ten pages answered a plain fetch. Of those ten, four gave a serving count, seven showed a price, and four said how long a custom cake takes.

The sharper finding is what happens on the pages that do answer. Two of them describe a 6-inch cake. One recommends it for 4 to 6 people. The other says 6 to 8. Same size, same island, same week, and a 50% difference in what the buyer should order.

Key takeaways from 13 Singapore cake websites

Every figure below comes from pages we fetched ourselves on 8–9 November 2026. Counts are shown with their base, because a sample of ten is a sample of ten.

#	Finding	The number
1	Sites whose page our plain fetch could read	10 of 13
2	Pages saying how many people a cake size feeds	4 of 10
3	Pages showing at least one cake price	7 of 10
4	Pages stating a lead time or order notice for a custom cake	4 of 10
5	Pages stating a delivery fee or free-delivery figure	5 of 10
6	Pages with a question heading or an FAQ block	5 of 10
7	Pages declaring a business entity in structured data	7 of 10
8	Pages using the specific Bakery type rather than a generic one	1 of 10
9	Readable robots.txt files blocking GPTBot, ClaudeBot, OAI-SearchBot or PerplexityBot	0 of 8
10	Sites serving an llms.txt file	4 of 13
11	Of those four files, ones that mention a cake, a price or a lead time	2 of 4

Row 2 is the one we would put in front of a cake shop owner. Row 11 is the one we would put in front of anyone selling AI-readiness work.

What we measured, and on which pages

We measured the page a buyer actually lands on, not a terms page three clicks deep.

Four searches went through SingRank's self-hosted SearXNG metasearch: "customised cake singapore", "birthday cake delivery singapore", "halal customised cake singapore" and "customised cake singapore price". From the results we kept businesses that bake and sell cakes in Singapore, and dropped food guides, listicles, marketplaces, classifieds, social platforms and two overseas bakeries the metasearch mixed in. No business SingRank works for appeared.

That left 13 sites. For each we fetched the homepage, or the custom-cake page when that was the result holding the slot, and read it as plain HTML. Then we checked robots.txt, llms.txt and agents.md, and ran our own audit for structured data and page basics. Our technology notes set out how we fetch.

One pillar is missing. Our page-speed measurement returned a quota error on every site, so we have no speed data and say nothing about it below. We would rather show the hole than fill it with an estimate.

How many sites say how many people a cake feeds?

Four of the ten readable pages gave servings for at least one size. Six sold cake by the inch and left the arithmetic to the buyer.

The four answered in four different places: a size filter carrying "(6-8 pax)" next to the inches, a size-and-menu page pairing every tier with a count down to a 3.5-inch bento at 1 to 2 servings, a sentence about a 5-inch serving 4 to 10 people, and a table recommending 4 to 6 people for 6 inches. Two further sites linked to a size guide without putting a number on the page we read.

This is the highest-value line on a cake website, in our view. The buyer has a fixed number in their head and it is guests, not inches. A page that will not convert one into the other hands that job to a food guide, a forum thread, or an assistant quoting a different bakery's chart. We measured the same shape of failure in Singapore catering, where 3 of 10 sites said how far ahead to order.

Why the same 6-inch cake feeds 4 on one site and 8 on another

Because a serving is a judgement, not a measurement, and nobody publishes the judgement.

A 6-inch round holds a fixed volume of sponge. Whether that is four portions or eight depends on how the baker expects it to be cut, how tall the cake is, how rich it is, and whether it is the only dessert on the table. Both answers can be honest. Neither page said which assumption it was using.

That is the fixable part. A count with its assumption attached — "6 inch: 6 to 8 dessert portions, or 4 to 6 if it is the only dessert" — beats either number alone, and it survives being lifted out of context, which matters when a machine quotes one line and drops the rest. We would add the sentence nobody writes: whether a size can still be changed after the order goes in. None of the ten said that.

Three of 13 sites would not let our fetch read the page

Two sites answered with HTTP 403 and a browser-challenge page nine words long. A third never completed a connection, on repeated attempts.

All three hold slots in the searches we ran, so something crawled them at some point. From outside we cannot tell whether this is deliberate bot protection, a rule tuned tightly, a content delivery network decision, or a temporary state. A system that cannot read your page has nothing to quote, and will answer the buyer from a site it can read. We found the same pattern in Singapore maid agencies, and the fix is never on the marketing side: it is a conversation with whoever runs your hosting or firewall.

The robots.txt side was the opposite of a problem. Of the eight files we could read, none blocked GPTBot, ClaudeBot, OAI-SearchBot or PerplexityBot. One site had no robots.txt at all. One of the eight, on a hosted website platform, stacks 29 named user-agents — GPTBot, ClaudeBot, Google-Extended, CCBot and the ad crawlers among them — directly above User-agent: *. Stacked that way they share the permissive group that follows, so a list of AI crawler names in your robots.txt is not a block.

Who shows a price, and who gives a lead time

Seven of ten pages showed at least one cake price. Four of ten gave a lead time for custom work.

Lowest prices on display ran from $18 for a single-serving size to a $140 starting price on another site. That spread is honest, because these are different products. What makes a page useful is whether a buyer can tell which number applies to them.

Lead times were the weaker half. The four that gave one said: two days with a same-day cut-off, one to two days as a minimum with about a week for most custom work, at least seven working days, and at least three days. One of those four contradicted itself, with three days on the page and at least seven days in its own FAQ. A buyer reading both learns only that nobody checked. Two of the ten pages carried a price, a lead time and a serving count together, and those are the two we would expect an assistant to quote.

Halal: three claims, one named certifier

Three of the ten pages made a halal claim. One named the certifier.

That page wrote "MUIS HALAL-CERTIFIED" in plain text and carried a question heading asking whether its cakes are certified. A second said it is halal-certified without naming who certified it. A third used "Halal Customised Cakes" in its page title with no certification statement on the page we read. Two other pages said plainly that they are not halal certified, which we count as a clear answer rather than a gap.

Naming the certifier matters because in Singapore there is one. MUIS states that it "provides Halal certification services and regulates Singapore Halal industry", and publishes a directory of certified establishments. A claim with a certifier named is checkable in a minute. A claim without one asks the buyer to take your word for it, on the exact point they came to verify. The buyer-side half of today's work found 12 of 142 cake searches asking for halal, three times the number that named an area. If you are certified, put the certifier on the page in text, not inside a logo image. This is marketing guidance, not legal, religious or compliance advice; confirm your own status and wording with MUIS.

What the machine-readable files actually say

Four of the 13 sites served an llms.txt file. Two of the four mention a cake.

One was written for the bakery: unit number, street, postcode, nearest MRT station, the cake types made, and the WhatsApp number to order on. A machine reading it learns what the business is and how to buy. Two others, on the same e-commerce platform, served files identical to each other apart from the shop name. Both explain how an AI agent should use that platform's shopping skill, connect a shopper's account and run a checkout. Neither mentions cake, price, lead time, servings or halal. A fourth was generated by a different website platform and at least described customised halal cakes and pastries. One site also serves an agents.md path that returns its homepage as HTML instead of a markdown file, which is a missing file dressed as a present one.

We noted the same platform-generated pattern in Singapore facial salons and furniture retailers. What is new here is the comparison: where these files existed, they were more likely to describe a checkout protocol than the thing the shop sells. Google's own position is the reason we put these files last on the job list. Its guidance on AI features says "There are no additional technical requirements" and "You don't need to create new machine readable files, AI text files, or markup to appear in these features", adding that there is "no special schema.org structured data that you need to add" either. Our llms.txt guide goes further into when it is still worth having, and we have no evidence that any assistant acts on any of these files.

What we would fix first on a cake website

Three edits, in this order, and none needs a developer.

Put servings next to every size, with the assumption. "8 inch: 12 to 16 dessert portions" beats "8 inch". If the sizes already sit in a filter or a chart, copy the line onto the cake page too.
Put the lead time and the cut-off in one sentence on the cake page. Then read your FAQ and make it agree. One of ten pages disagreed with itself, and that costs more trust than silence.
Open by naming the cake and Singapore. Four of ten did. Our study of 109 Singapore local pages found the opening paragraph and the question heading the two weakest signals in every trade we have measured, and this sample is no better.

Here is the part that costs us. None of this is work you need an agency for. It is three sentences on one page, and if that is all your site is missing we would tell you so and leave you to it. What we sell is useful after those sentences exist, not instead of them. The buyer-side half of today's work, what 142 cake searches ask for, says which pages to write next, and our nearest industry guides are the ones for caterers and florists, because both sell an occasion against a deadline.

Method and limits — read these before quoting

Metasearch is not Google. Results came from SingRank's self-hosted SearXNG. Seven of its engines returned errors on every run, so the ordering reflects the engines that answered, not Google's ranking and not its Maps pack.
Thirteen sites, ten readable pages. One page either way moves a count by 10 percentage points.
One page per site, one morning. Fetched 8 November 2026 between 23:04 and 23:15 UTC, which is the morning of 9 November in Singapore. A snapshot, not a trend.
Raw HTML only. We did not run JavaScript, so content that appears only after scripts execute was not measured and would change some counts.
No speed data. Our page-speed tool returned a quota error on all 13 sites. That pillar is absent, not zero.
Serving counts are the sites' own. We cut no cakes. We recorded what each page claims.
Our groupings are ours. "Answers the question" and "makes a halal claim" are our readings of real page text, and another reader could mark a row differently.

This page names no business. It describes pages, not companies, and alleges nothing against anyone. Our method page sets out how we separate findings from assumptions.

Want these checks on your own cake page?

Send us the one page that should win "customised cake singapore", or your own category's equivalent. We will run the same checks and tell you in writing which line is missing. That starts as a free visibility check through our contact page.

If you want the pages written and measured for you, our SEO, AEO and GEO programme is S$750 a month with 20 articles a month, a three-month minimum, then month to month. What we will not do is promise a ranking or an AI mention. As our GEO page puts it: AI platforms choose their own answers.

FAQ

How many Singapore cake sites say how many people a cake feeds?

Four of the ten readable pages in our 8–9 November 2026 sample gave a serving count for at least one size. Six priced cake by the inch with no guest number on the page we read, and two of those six linked to a separate size guide instead of answering in place.

How many people does a 6-inch cake feed in Singapore?

The sites disagree. In our sample one page recommended a 6-inch cake for 4 to 6 people and another gave 6 to 8. Both can be honest, because a serving depends on cutting, height and whether cake is the only dessert. Ask your baker which assumption their chart uses.

How far ahead should a custom cake be ordered in Singapore?

Four of ten pages gave a figure, ranging from two days to at least seven working days, with about a week quoted as typical for custom work. One page contradicted its own FAQ. Treat the lead time on the specific cake page as the one that counts, and confirm it when you enquire.

Does a cake website need an llms.txt or agents.md file?

Not before the cake page answers the buyer. Four of our 13 sites served an llms.txt and only two of those four mentioned a cake, a price or a lead time. Two were platform templates about agent checkout, and we have no evidence that assistants act on these files.

Can I cite these figures?

Yes. Please cite "SingRank, Singapore Custom Cake Website Study 2026" with a link to this page and the collection date, 8–9 November 2026. Quote each count with its base, such as 4 of 10 pages, and keep the metasearch caveat. Challenges to a number are welcome through our contact page.