Why are online recipes so long — and how do you get to the actual part?

You type «carbonara with cream — please not authentic» into Google. Click the first result. What you see, in this order:

1. A cookie banner, big, with three buttons
2. A newsletter pop-up asking whether you want recipes by email
3. A hero image, beautifully plated, watermarked
4. A first paragraph: «When I think of carbonara, I think of my holiday in Tuscany in 2018, when we drove around in a rental car…»
5. An anecdote about the mother-in-law
6. Three tips on what you should not do
7. A «step-by-step» image gallery that drops an ad banner after every third picture
8. An autoplay video from a different blogger that has nothing to do with the recipe at hand
9. Finally: the recipe — ingredients, steps. In a card, with a «Jump to recipe» button right at the top that you missed earlier.

This isn't random. This is strategy. Every element has a reason — usually not the one that helps you cook better.

Food blogs don't make money from cooking. They make money from ad slots on the page the recipe sits on. Concretely:

• Ad banners pay per 1,000 views — in the food segment typically 5–30 dollars, depending on region and season.
• Paid mentions pay for product placements — the brand-name butter, the premium cheese-grater link, the affiliate link to the pasta maker.
• Pre-video ads pay separately per play — hence the autoplay video that starts automatically the moment you land on the page.

The longer the text, the more ad slots. The longer you stay on the page, the higher the ad price. A plain recipe card — ingredients, steps, image — would mean 30 seconds of reading time and maybe one ad impression. A blogger's carbonara story with 8 images, 2 videos and 1,800 words around it produces maybe 4 minutes of reading time and 6–8 ad impressions.

The difference — multiplied by 50,000 clicks a month — is the difference between a hobby and a full-time job. No one can blame a food blog for having a business model. But the business model isn't: make your recipe simply readable.

If ads were the only reason, long texts wouldn't work for Google. But they do. Here's what Google rewards on a recipe page:

• Recognisable author experience. Whoever writes «I've made this carbonara 30 times and noticed that…» signals practice. A page that only shows ingredients and steps says nothing about who's behind it.
• «Helpful content» (Google update 2022). Google favours content made for people, not just for search engines. Ironically, many SEO agencies read this as «write longer, more personal texts» — which again produces exactly what isn't helpful.
• Dwell time. How long someone stays on the page before clicking back to Google. If the recipe is right at the top and read in 30 seconds, the visitor bounces back quickly → a bad signal for Google. If the recipe is right at the bottom and takes 4 minutes of scrolling, the visitor stays → a good signal for Google. Even if you're frustrated the whole time.
• Longer texts statistically rank better. No official rule, but in practice the top-10 results average 1,500+ words.

The problem behind it: Google doesn't measure «how fast you find the recipe», but «how long you stay on the page». The easiest way to keep someone on the page for a long time is a story they have to read first.

You feel the consequence in the kitchen, when your hands already have flour on them. You search for «the next step» and scroll past:

• a newsletter pop-up («not this time»)
• a banner for dishwasher tabs
• three pictures of egg-yolk stages
• a paragraph on whether to use parmesan or pecorino
• then the actual step 4 of 7

This is cognitive load. Studies on decision fatigue (e.g. Roy Baumeister) show: every little click, every little decision («dismiss or not?») uses up the attention you actually need at the stove. The result: you dismiss a few pop-ups too quickly, miss «salt first, then cheese», and the sauce ends up under-seasoned.

That many blogs have a «Jump to recipe» button right at the top is the industry's admission gesture: yes, we know you only want the recipe. But the money comes from the banners in between — and the button is voluntary.

The question isn't whether food blogs are wrong. It's: how do you get to the recipe without reading the rest?

1. Your browser's reader mode. Safari (the «aA» icon → «Show Reader»), Firefox (the icon with a page in the address bar) and Chrome on Android (three-dot menu → «Simplified view») strip the page down to plain text. Banners, videos, cookie banners disappear. Problem: many food blogs build the recipe card in such a custom way that reader mode doesn't display it cleanly — then only the story remains, not the recipe.

2. Print (Ctrl+P / Cmd+P). Most food blogs have a hidden «Print» button on the recipe card. Click it → a print-optimised layout opens with only ingredients and steps. Works in about 70 % of cases. Problem: in the kitchen you're rarely standing next to a printer, and switching tabs with floury fingers is exactly what we wanted to avoid.

3. A recipe app that _pulls the recipe out automatically_. Every larger recipe site adds structured recipe data on top of the visible text — so Google can show stars and cooking time in the search results. A recipe app can read exactly this data and save only that. Banners, story, pop-up stay in the source, the recipe lands cleanly with you.

The first two ways help in individual cases. The third is the clean solution — and the one mangia takes.

You paste a recipe's address into mangia. What happens then:

1. mangia opens the page and looks for the structured recipe data that almost all big food blogs supply for Google. A hit in 95 % of cases.
2. If nothing is found, mangia reads on automatically: it reads the text, recognises ingredients (small amounts + units), steps (numbered paragraphs, imperative) and the preview image — and creates the recipe just as cleanly.
3. What you get: title, image, ingredients, steps, servings, cooking time. Clean.
4. What you don't get: the Tuscany anecdote, the banners, the image gallery with egg-yolk stages.

If you want to keep a particular story (mother-in-law, occasion, variation idea) — every recipe in mangia has a notes field. You can save the one paragraph that matters to you there. What you don't want stays outside.

In the kitchen that means: when you tap «Start cooking» in mangia, you see the current step large, the ingredients for it next to it, and nothing else. No pop-ups, no banners, nothing to dismiss. What food blogs can't deliver for business reasons — that's the standard at mangia.