How to get the recipe without the story

You searched for banana bread. You got 1,800 words about a grandmother in Ohio, four full-width photographs, two video autoplays and a newsletter popup. The ingredients are somewhere past all of it.

Here's why that happens — it's not what most people think — and four ways to skip it.

Three reasons, and only one of them is about writing.

A recipe is barely copyrightable.In US law a list of ingredients is a statement of fact, and facts can't be owned. Anyone may republish “225 g flour, 2 eggs, 150 g sugar” and the method in their own words. What is protected is original expression around it — the headnote, the story, the photographs. So the story isn't padding around the recipe; legally it's the only part of the page the writer owns. Strip it and you've taken away the thing that made publishing the recipe worth doing.

The page is paid for by advertising, per view.A longer page holds more ad slots and more scroll depth, and both are billed. A food writer who publishes a bare ingredient list earns a fraction of what the same recipe earns wrapped in 1,500 words. That is not greed, it's the rate card.

Search rewards it.Google's guidance asks for demonstrated first-hand experience, and a page that shows the dish being made four times, in someone's own kitchen, with their own photographs, satisfies that in a way a bare list never will. The long intro is partly a signal aimed at a crawler, not at you.

So: the format is a rational response to how the web pays for writing. The people you're annoyed at are mostly doing the only thing that works.

Most well-built recipe sites have one, near the top, and it's the fastest path. It also keeps the writer's page view intact, which is the polite option. If you use one site a lot, this is the answer — nothing below beats it for a single visit.

Safari's Reader (the icon at the left of the address bar), Firefox's Reader View, Edge's Immersive Reader. Strips ads, popups and sidebars, keeps the text and images. It won't reorder anything — the story is still above the ingredients — but the page becomes scrollable at speed instead of a minefield.

Nearly every recipe page on the web carries a hidden, machine- readable copy of the recipe: a schema.org/Recipeblock in the HTML, holding the ingredients, the steps, the yield and the times as plain data. It's how Google builds those recipe cards in search results.

It's also why every “recipe extractor” tool works at all, including this one. If you're technical, view source and search for Recipe — the whole thing is sitting right there in JSON. Publishers put it there deliberately; reading it is what it's for.

This is the one we built. Paste the link and you get the recipe as a prep table: ingredients down the left, each step a merged cell spanning exactly what it combines, the whole dish readable in one look. Not just the story removed — the recipe re-laid-out so you never scroll between the ingredient list and the instructions again.

Every table links back to the original page, credited by name. That matters to us: the writer did the work, and the deal has to stay worth taking on their side too. If a publisher would rather not be in the library, we take them out.

There's a Chrome extensionthat does it in one click from whatever page you're already on.

The story isn't the enemy — it's a load-bearing part of how recipes get published at all, and some of it is genuinely worth reading. It just isn't what you need at the stove, with your hands covered in flour, trying to remember whether the butter was already in.

Read the story when you're choosing. Use the table when you're cooking.