Every recipe blog has a 2,000-word essay before the actual recipe. That's not because the author loves writing — it's because Google's search algorithm rewards long-form content, and ad networks pay by the scroll. More scrolling = more ad impressions = more revenue. The recipe itself is 200 words buried under a memoir about a trip to Tuscany.
Most recipe sites embed their recipe data in a machine-readable format called schema.org/Recipe JSON-LD. This is the same structured data that Google uses to show recipe cards in search results — cooking time, servings, ingredients, and step-by-step instructions. When you paste the page source, this tool finds that structured data and renders just the recipe. If there's no JSON-LD, it falls back to common WordPress recipe plugin markup (WPRM, Tasty Recipes, Mediavine Create) and then to plain-text pattern matching. Everything runs in your browser — no server, no cookies, no tracking.
The most reliable method is pasting the full page source (Ctrl+U → Ctrl+A → Ctrl+C). This gives the tool access to the JSON-LD data in the page's <head> section, which contains the cleanest version of the recipe. If you just copy-paste the visible text from the page, the tool will try to parse it as plain text — it looks for lines that start with quantities (numbers, fractions) as ingredients and numbered or sequential lines as instructions. This works for simple recipes but may miss some details. For best results, always paste the full source.