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 plugin. WordPress accepts raw HTML in a Custom HTML block, which is all this needs.
On WordPress this goes in your sidebar — local conditions are a glanceable sidebar item, not a content block.
On WordPress this goes in the post or page itself — a live count only changes behaviour when it sits in the same line of sight as the price or the button.
On WordPress this goes in your single-post template, under the content — 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.
Every FeedPulse widget is one line of embed code, so WordPress needs no plugin. In the block editor, add a Custom HTML block where you want the widget, paste the code and update the page. To show it on every page, go to Appearance → Widgets and add a Custom HTML block to your sidebar or footer area. If you use a block theme without widget areas, open Appearance → Editor, edit the Footer template part, and add the Custom HTML block there.
Caching plugins and hosts that cache full pages don't usually affect embedded widgets, because the widget loads its data in the visitor's browser after the page arrives. If a newly added widget doesn't appear, clear your caching plugin's cache and your host's cache, then check the page in a private window. Optimization plugins that combine or delay JavaScript can occasionally delay a widget; if that happens, exclude the widget's script from delay or combine settings.
If you have a staging site, add the widget there first. Otherwise add it to one page, check it on desktop and mobile, then roll it out to your sidebar or footer. Run a PageSpeed Insights test on that page before and after so you know the real effect on your site.
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 plugin. WordPress accepts raw HTML in a Custom HTML block, which is all this needs.