Skip to content

Module 08 · Platform

Your own website, with a live menu, on your own domain

Cheers doesn't stop at the guest app: your venue also gets a standalone website running on your own domain. The menu, the daily specials, the opening hours and the news all come from the same backoffice you already use — change it there and the website changes with it. No separate web developer, no separate hosting, and no six-month-old PDF menu on the front page. There's a live example to look at: demo.cheers.hu.

Who it is for

For restaurants, cafés and canteens where guests look you up before they set off — and for anyone whose current site hasn't been touched in years, or who is represented today by a social page alone. It matters most where there's a daily menu or a frequently changing offer: that's the part that hurts to maintain by hand, and the part that goes stale fastest.

How it works

  1. We put your brand on it

    Your logo, colors, font and favicon come straight from your venue's profile onto the site, along with the header and footer menu items. Pages are assembled from ready-made blocks — hero, story, gallery, FAQ, contact — so you're not picking a template, we're putting together what actually matters at your place.

  2. We connect the menu and the content

    The menu block pulls your venue's real offer: a fixed menu or the daily menu, with photos, prices and a sold-out flag. The hours block brings the real opening hours and the address, and the news feed brings your own articles. Set up once, kept current by the backoffice from then on.

  3. We point your domain at it

    A subdomain needs a CNAME record, a root domain needs an A record at your provider — that part is set by you or whoever manages your domain. The system checks the record against your domain's own nameservers, so there's no cache to wait out, and the SSL certificate is issued and renewed automatically.

What you get out of it

  • The menu keeps itself current

    You're not swapping PDFs any more. Whatever you change in the backoffice — a price, a new dish, a sold-out item, a vegan or gluten-free tag — shows up on the website the same way. The daily menu can be browsed ahead, up to two weeks, with today and tomorrow marked out.

  • Google sees the whole page

    Pages are rendered on the server, so a crawler gets the same text your guest does. Every venue gets its own sitemap and robots.txt, every subpage its own title and description, and the FAQ turns into structured data on its own — none of it a separate SEO project.

  • Opening hours that don't lie

    The open/closed state and the hours come live from the system, and the address sits next to a link that opens the map. On a public holiday you don't edit the website, only the place you keep up to date anyway.

  • Cookie consent is handled too

    The consent bar is part of the website: it asks category by category, nothing is pre-ticked, and measurement only starts after consent. Google Consent Mode v2 is supported, and the wording can be overridden per venue.

More detail

  • Multiple languages and a switcher
  • Your own domain and aliases
  • Automatic SSL certificate
  • News feed from your own articles
  • Booking and order buttons

Frequently asked questions

  • Do I need a web developer, and what happens to my current site?

    No. The site is served and maintained by the Cheers system; what you supply is the content and the branding — no code, no hosting, no update cycle to manage. You don't have to switch off your current site right away either: the new one can go live on a subdomain, and you only point your main address at it once you're happy with it.

  • Can I use my own domain, and what do I have to set up?

    Yes — your own domain and any number of extra addresses, the www variant for example, can be attached, and the secondary ones redirect to the main address automatically. What you add is one DNS record at your domain provider: a CNAME for a subdomain, an A record for a root domain. Verification queries your domain's own nameservers, so a record you have just added can be accepted straight away, and the certificate is issued on the next sync cycle — minutes in practice, though DNS propagation itself depends on your provider.

  • Do the menu and the opening hours really update themselves?

    Yes, because the site doesn't store a copy, it reads from the system. The same fixed menu, daily menu, price, photo and sold-out flag you maintain in the backoffice is what appears, and the same goes for the opening hours and the open/closed state. The tags travel too: halal, vegan, vegetarian, kosher, gluten-free, lactose-free, sugar-free. Events, on the other hand, are hand-written content — you type those onto the page yourself.

  • Will it be found on Google, and does it work in several languages?

    The page is generated on the server, so search engines see the full content, and every venue gets its own sitemap, robots.txt and structured data. It serves several languages too: the switcher remembers the guest's choice, and the language versions reference each other with hreflang. Publishing clears the cache immediately, so a fix goes live right away rather than tomorrow.

Let's see what your venue's website would look like.

In the free assessment we go through your domain, your menu and what content should go on the site.

Back to the module