Restaurant visits are same-day and weather-driven — nobody books a terrace table in the rain. Showing today's local weather beside the menu is genuinely useful rather than ornamental, and a live count tells someone the page they are reading is current.
What you are trying to do here is get a booking or a walk-in today. Three widgets below do that; the other 15 in the set mostly do not, so they are not on this page. No app from the Wix App Market. Wix renders raw HTML and script tags inside an embed element, so there is nothing to install and nothing to pay for.
On Wix this goes in an Embed a Widget element in the footer area — local conditions are a glanceable sidebar item, not a content block.
On Wix this goes in an Embed a Widget element on the page — a live count only changes behaviour when it sits in the same line of sight as the price or the button.
On Wix this goes in an HTML embed block inside the blog post — it belongs directly under the article body, which means the blog-post template rather than a global widget area.
Weather near the top beside hours and the booking link. Use the comments widget as a lightweight guestbook under the menu if you do not want to manage a review platform.
For a single page, open the Wix Editor, click Add Elements → Embed Code → Embed HTML, paste the widget code into Enter Code, and resize the box to fit. For every page, go to your dashboard's Settings → Custom Code, add the code, choose All pages and place it at Body - end. Wix's help center notes that Custom Code requires a Premium plan with a connected domain; Embed HTML works on any Wix site.
Wix lets you arrange elements separately in the mobile editor. After adding an Embed HTML element, switch to mobile view and check the box isn't cropped or overlapping your images. You can resize it or hide it on mobile if it gets in the way.
Use Preview to check placement, then publish and test the live site, because embedded code runs fully only on the published site. Run PageSpeed Insights on the published page before and after adding the widget.
People check a restaurant site to see the menu, the opening hours and whether it's worth going today. Widgets help when they add same-day information: local weather is genuinely useful for terrace seating or outdoor events, a countdown can show when a special or event starts, and a live count shows the page is current.
Keep the menu, hours, address and booking link at the top. Put the weather widget beside opening hours or the terrace section, a countdown beside the event it relates to, and a visitor count in the footer. On mobile, make sure none of them push the booking button down.
A countdown that has expired, or an event that already happened, makes the whole site look abandoned. Remove countdowns when the date passes and update specials regularly. Live widgets like weather update on their own, which is part of why they suit restaurant sites.
Track booking clicks, calls and direction requests over a few weeks before and after. Those actions show whether visitors are turning into guests, which matters far more than page views.
Yes, if weather affects the visit, such as terrace seating, outdoor events or seasonal menus. Show it beside your opening hours so diners can plan. If your restaurant is indoors-only, skip it and keep the page focused on the menu and booking.
Begin with the weather widget beside your opening hours if you have outdoor seating, and a countdown for your next event or special. Keep the booking button above both on mobile. After a month, compare booking clicks and calls with the month before.
Every FeedPulse widget and badge is free to use with no signup: copy the embed code from the widget's page, paste it into your site and it starts working. There's no trial period and no card required. Some widgets that rely on outside data, such as weather or market prices, refresh on a schedule rather than every second, so they stay fast and free to run.
Give any new widget about four weeks before judging it. Compare the action that matters for your site, such as inquiries, bookings, sales or pages per visit, with the four weeks before you added it. Keep widgets that clearly help, move ones that might help in a better spot, and remove ones that made no difference. A page with fewer, useful widgets usually beats a page with many.
FeedPulse widgets show aggregate information such as visitor counts, countries and pages, not names or exact locations. Even so, mention any third-party widget in your privacy policy, and check whether your cookie notice needs updating for the tools you use.
Delete the block, section or embed element that contains the code and publish. Nothing else on your site depends on it. Your public FeedPulse stats page keeps the history it has already collected.
Start with one. A single widget in the right place is easier to judge, keeps the page fast and doesn't compete with your content. Once you've seen whether it helps, add a second only if it does a different job, for example pairing a visitor count with a countdown for a real offer. Avoid stacking several widgets that all say the same thing, such as two different visitor counters, because they make the page busier without adding information.
Widgets should never hide important information that isn't available elsewhere on the page. Keep your opening hours, prices and contact details as normal text, not only inside a widget. Check that widget colors have enough contrast against your background, and that the page still makes sense if a visitor's browser blocks third-party scripts. A widget should add to the page, not be the only place key information lives.
weather widget — Restaurant visits are same-day and weather-driven — nobody books a terrace table in the rain. Showing today's local weather beside the menu is genuinely useful rather than ornamental, and a live count tells someone the page they are reading is current.
Weather near the top beside hours and the booking link. Use the comments widget as a lightweight guestbook under the menu if you do not want to manage a review platform.
No app from the Wix App Market. Wix renders raw HTML and script tags inside an embed element, so there is nothing to install and nothing to pay for.