For recipe site owners
When one of your readers pastes your recipe's address into this site, our fetcher asks your server for the page, reads the schema.org Recipe data you already publish, and shows that one reader the per-serving nutrition. This page says exactly what the fetcher is, what it does and does not read, and how to allow it if your firewall currently turns it away.
What the fetcher is
It identifies itself honestly on every request, as:
NutritionalValuesBot/1.0 (+https://nutritionalvalues.info/about/; reads schema.org Recipe data for one visitor at a time)
It reads your robots.txt and obeys it — on every redirect
as well as the first request. It fetches one page, once, when one reader
asks, with a short timeout and a cap on how much it reads. It never
crawls, never fetches ahead, and stores nothing about your page. It reads
the recipe's ingredient list only — the method stays on your page,
and our results link your readers back to it to cook the dish.
Allowing it
If your site refuses automated requests, your readers see "that site does not serve automated requests" when they try to import your recipe by its address. Allowing this one reader is one rule:
robots.txt
If you manage access with robots.txt, add:
User-agent: NutritionalValuesBot Allow: /
Cloudflare
Security → WAF → Custom rules → Create rule: if User Agent
contains NutritionalValuesBot, then Skip the
relevant protections (Bot Fight Mode / Super Bot Fight Mode is the usual
one turning it away). If you use "Verified bots only" settings, a skip
rule by user-agent is the way through.
Wordfence and similar WordPress firewalls
Firewall → Allowlisted entries: add a user-agent rule for
NutritionalValuesBot. On Sucuri it is Access Control →
Allowlist User Agents.
If you would rather not allow it
That is your call, and the fetcher respects it — a refusal is treated as an answer, never worked around. Two things still work for your readers regardless: they can paste your ingredient list into the analyser themselves, and any nutrition link you place on your page keeps working — that link carries the recipe inside the address, so following it involves no fetch of your site at all.
Give your readers the nutrition directly
Any recipe can be turned into a link that lands on its own per-serving nutrition breakdown — paste your ingredient list into the analyser, press Share, and put the resulting link on your page. Your readers get the nutrition and a rescaler for your recipe; nothing is fetched from your site when they use it.