MenuMenaceBot
If MenuMenaceBot/1.0 turned up in your access log, this page is the whole
story: what it fetched, why, and how to make it stop.
Tell us to stop
Email hello@menumenace.com
with your domain. We remove every item we read from your site and add the domain to a
permanent block list — no argument, no forms, and we do not ask why. A
Disallow in your robots.txt for
MenuMenaceBot does the same thing without emailing anyone; we check it before
every fetch and treat a 401 or 403 on
robots.txt as a refusal too.
What it does
Menu Menace ranks restaurant menus by what you actually get for your money. When somebody looks up a restaurant we have no menu for, they can tap once to have us look for that restaurant's menu on the restaurant's own website — the address Google Business Profile lists for it. The bot reads the page, pulls out item names, sizes and prices, and stops.
What it takes, and what it does not
- Facts only. Item name, size and price. We do not store or republish your menu descriptions — that is the part of a menu that is genuinely yours as writing, and it is discarded as soon as the calorie estimate is made.
- No images, no logos, no reviews, no contact details.
- We link back. Every price we read carries your domain and the date we read it, on the item and on the public page for it.
- We never call it verified. A price read off a website is labelled an estimate — the calculator icon — until a person standing in your restaurant confirms it. If your site is out of date, the number is marked as ours to be wrong about, not yours.
How politely
robots.txtis read first, and honoured, includingCrawl-delay.- At most six requests to a site for one look-up, at least a second apart, and one look-up per restaurant per 14 to 90 days. There is no continuous crawl.
-
Plain
GETs. No cookies, no logins, and we never fill in or submit a form — including on a restaurant's own ordering page. -
User agent:
MenuMenaceBot/1.0 (+https://menumenace.com/bot). Anything else claiming to be us is not us. -
We read restaurants' own sites, including a hosted ordering page a restaurant
runs itself, on a platform like Square, Clover or SpotOn — but only where that page's
robots.txtallows it, and only on a platform whose terms of service we have read ourselves and that do not ban this kind of reading. Arobots.txtthat allows the fetch does not settle it: some ordering platforms allow the fetch there and we still leave them off, because their terms say no. - We never fetch delivery apps (DoorDash, Uber Eats, Grubhub and the like), review or social sites, or menu-aggregator sites. None of those is run by the restaurant, and a delivery app's prices are marked up, which would make our ranking wrong even where reading them were allowed.
- A bot wall, CAPTCHA, login page or rate limit stops us there. We do not solve it, retry around it, or come back sooner than our own schedule allows.
- Some pages need their own script to run before the prices show up. When that happens we may run the page's script once, in a sandboxed, locked-down browser that can load only that page's own site and the handful of hosts we've explicitly allowed for it — never anywhere a plain fetch could not already go.
Something we published about you is wrong
Email hello@menumenace.com with the venue. We fix or remove it. Owner corrections are applied quickly, and they are still labelled as estimates until a dated confirmation exists — that rule protects you as much as the reader.