For recipe site owners
Everything here is complementary to your site, not competition for it: no recipes are published, nothing ranks yours against anyone else's, and every tool links your readers back to your page. What this site adds is the thing you cannot credibly add yourself — an independent reading of your recipe's numbers, computed from your own ingredient list against USDA data, that any reader can check line by line.
An independent nutrition review your readers can check
Your recipe plugin's nutrition figure is your site grading its own homework. A link to this site's analysis is a third party showing its working: every number is a database value times a weight, each ingredient's match is visible and correctable, and the serving count is the reader's to adjust. Paste your recipe in, press Share, and the link you get carries the whole recipe inside it — following it fetches nothing from your site and costs your readers nothing.
A nutrition label for your page
Paste your ingredient list into the
nutrition label generator and get a facts
panel as self-contained HTML to embed in your post, plus the schema.org
nutrition block for your recipe card — so the figure you
publish and the ingredients you list agree. Under the embedded panel, a
credit line links your readers to the full breakdown for that exact
recipe, where any number can be checked or challenged.
A technical checkup for your recipe pages
The Recipe Technical Optimizer reads a page of yours the way machines read it: the structured data Google needs for rich results, whether it still matches what the page shows, how nutrition tools parse each ingredient line, whether your published calories agree with your ingredients, and what the page carries besides the recipe — with concrete, line-by-line fixes on request.
Letting your readers import your recipes
When a reader pastes your recipe's address here, our fetcher asks your server for the page once, reads the schema.org Recipe data you already publish, and shows that one reader the ingredient list's nutrition — the method stays on your page, and the results link back to it to cook the dish. It identifies itself honestly on every request:
NutritionalValuesBot/1.0 (+https://nutritionalvalues.info/about/; reads schema.org Recipe data for one visitor at a time)
It obeys your robots.txt on every redirect as well as the
first request, never crawls or fetches ahead, and stores nothing about
your page. Most firewalls block all automated readers by default, so if
you want imports to work for your readers, allow that user-agent:
robots.txt
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).
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. Everything else on this page still works for your readers regardless: the share links and label embeds carry the recipe inside the address, so following them involves no fetch of your site at all.
What should exist next?
This set grows in the direction site owners point it. A pre-publish check for draft ingredient lists, a metric-and-cups conversion table generator for your recipe footers, and diet badges are all under consideration — say which would help you and it moves up the list.