We set out to compare Parramatta cafe websites and found something more useful than a comparison.
Several of the cafes did not have one. Their entire web presence — the thing that appears when you search their name — was a page on a third-party menu platform, on somebody else’s domain.
On the day we checked, neither of the two aggregator pages we tested answered. One returned nothing at all. The other returned a 403, refusing the request.
That is the finding, and it is worth more than any amount of design commentary.
What renting your web presence actually means
A page on a menu aggregator feels like having a website. It has your name, your menu and your address, and it turns up in search.
Four things you do not have:
You do not control whether it answers. If the platform is down, blocking, or has changed its terms, your web presence is down. You will not be told, and you have no way to fix it.
You do not control what else is on it. Aggregator pages routinely show competitors — “other restaurants nearby” — on the page a customer reached by searching for you specifically. You are paying for the visit and they are monetising it.
You do not own the address. Search results, links and any accumulated authority attach to their domain. If you leave, none of it comes with you.
You cannot fix an error. A wrong price, an outdated menu, the wrong opening hours — you are in a queue behind their support process.
The honest counter-argument is real: an aggregator page costs nothing, appears immediately, and a cafe owner has a business to run. For a venue that does not deliver and gets its trade from the footpath, that may genuinely be enough.
But it is a decision, and most of the venues in this position did not make it. They were listed by the platform, the page ranked, and no separate site was ever built.
The one that had its own site
The one cafe in our sample with its own domain was measurably better placed on everything except one point.
It had its own menu on the page, structured data describing the business, prices visible, and a form. It answered in under half a second.
It had no tappable phone number in the markup at all.
For a cafe taking bookings by phone, that is the single most-used action on the site, and it was not a link. On a phone, a number that is not a link is a number the customer has to memorise, switch apps, and type.
★ Insight ─────────────────────────────────────
The two failure modes in this category sit at opposite ends and have the same cause: nobody has watched a customer use the thing. The aggregator venues have no site because nobody asked what happens when someone searches the business name. The venue with its own site has an unlinked phone number because it was checked on a desktop, where you would never notice. Both are ten-minute fixes and both are invisible from the owner’s chair.
─────────────────────────────────────────────────
The menu problem
The other thing worth checking, which we could not measure mechanically: whether the menu is text on a page or a PDF.
A PDF menu is a scanned or exported document that a phone opens slowly, renders at the wrong size, and that search engines read poorly if at all. It exists because the menu was designed for print and reused.
Text on a page loads instantly, resizes for the screen, can be read aloud, and gets indexed — which means your dishes become searchable. Somebody looking for a particular dish in Parramatta finds the venue that published theirs as text.
The five-minute check
- Search your business name. What is the first result? If it is somebody else’s domain, that is your website whether you chose it or not.
- Open your menu on a phone. If it downloads rather than displays, it is a PDF.
- Tap your phone number. Does the dialler open?
- Can a customer see today’s hours without opening a PDF or a social post?
- Is there a way to book that is not a phone call? Most venues want the call. A form catches the customer who is looking at 11pm.
The social-only variant
A third pattern, more common than either of the above, and it deserves naming: the venue whose web presence is a social profile.
It shares every weakness of the aggregator page — rented address, no control over availability, competitors adjacent — and adds two more.
The content is chronological, not structural. Your opening hours were posted in March and are now forty posts down. A customer cannot find them, and neither can a search engine.
It is invisible to the searches that matter. Somebody searching for a dish, or for a cafe in a suburb, is served pages, not posts. A social profile ranks for your business name, which is the search you had already won.
None of that argues against having the social profile, which is genuinely where hospitality discovery happens. It argues that the profile is a channel and not an address, and that the address has to exist somewhere you control — even if it is one page.
What we would do, in order
If your only presence is an aggregator page, register a domain and put up a single page: name, address, hours, menu as text, phone as a link, and a map. That is a day’s work and it is the highest-return thing available to a venue in this position, because it converts a rented presence into an owned one.
If you have a site with a PDF menu, convert the menu to text. Keep the PDF for anyone who wants to print it.
If you have a site with a text menu, check the phone number is a link and go and do something else — you are in better shape than most of your street.
Cosmos Web Tech builds websites for hospitality and small businesses across Parramatta, the Hills District and Western Sydney. Hosting comes from Cloud Geeks, ordering apps from Awesome Apps, and we are part of Ganda Tech Services.