curryhouse.co.uk

The main types of curry recipes differ in three practical ways: how thick the sauce is, how the spices are built up, and whether the dish leans sour, sweet, or hot. On a British Indian restaurant menu, bhuna is thick and dry, dhansak is sweet-and-sour with lentils, rogan josh is a medium sauce with a red spice base, and chicken tikka masala is a mild, creamy tomato sauce with pre-grilled meat. If you want to cook restaurant-style curry at home, the reliable path is to fry whole or ground spices in oil first, then add onion and tomato, then simmer your meat or vegetables until the sauce reaches the texture you want.

The main restaurant-style curries and how they differ

The names describe the cooking method or the sauce character more than a fixed recipe, so two restaurants can serve noticeably different versions of the same dish.

The basic steps that apply to most curries

1. Heat oil or ghee and fry the spices. Whole spices such as cumin or cardamom go in first; ground spices go in later and for less time. The expected result is a fragrant oil, not a burnt, bitter paste.
2. Add onion and cook until softened and coloured. This builds the body of the sauce. For a bhuna-style result, keep cooking until the onion is well browned.
3. Add tomato, garlic, and ginger. Cook until the tomato breaks down and the oil separates slightly at the edges. This is the point where the sauce stops tasting raw.
4. Add your main ingredient. Meat usually needs longer simmering; vegetables and pre-cooked chicken need less.
5. Simmer and adjust. Add stock or water for a thinner sauce, or keep cooking uncovered for a thicker one. Finish with salt, lemon, or yoghurt to balance.

Common spices and what they do

• Curry powder is a pre-mixed blend. It makes Indian-style meals more affordable and quicker, but it is less flexible than building your own mix. The Curry House notes that curry powder historically made dishes cheaper and less authentic.
• Cumin, coriander, and turmeric form a common base. Turmeric adds colour more than flavour.
• Chilli powder or fresh chillies control heat. Add them early for a rounded heat, or near the end for a sharper one.
• Garam masala is usually added near the end so its aroma survives the cooking.

To adjust thickness, reduce the sauce uncovered rather than adding flour, which can make it gluey. To adjust heat, add chilli in small amounts and taste as you go.

Choosing a recipe as a beginner

Start with a dish whose sauce is forgiving. A rogan josh or a simple tomato-based chicken curry lets you practise frying spices and building a sauce without the risk of a dry pan. A dhansak is a good second step because the lentils thicken the sauce for you. A bhuna is harder to get right first time because there is little liquid to hide behind, so the spices can catch and burn.

Serve with plain rice or bread, and add a yoghurt or cucumber side to cool the heat.

Common reasons a curry fails

• Burnt spices. Ground spices scorch in seconds. Lower the heat and add them with a splash of water or tomato if the pan is too hot.
• Flat, bland flavour. Usually under-salted or under-cooked onion and tomato. Salt in stages and cook the base until the oil separates.
• Watery sauce. Too much liquid added at once. Simmer uncovered, or remove the meat and reduce the sauce separately.
• Harsh, raw spice taste. The spices were not fried long enough before the liquid went in.

If you want the historical context behind these dishes, The Curry House also covers how curry reached Victorian London through East India Company officers and later became a restaurant staple.

Start by matching the book to your kitchen reality, not to the cuisine's reputation. If you cook weeknight dinners and want results close to a takeaway, look for a restaurant-style curry cookbook that explains base sauces and spice mixes. If you want to cook from scratch across many regional dishes, look for a book that teaches techniques and ingredient logic rather than listing 100 recipes. The Curry House (curryhouse.co.uk) is one example of a site built around restaurant-style curry recipes, free recipes, a glossary of Indian restaurant terms and curries, and a glossary of spices — useful as a reference point for what "restaurant-style" actually means before you buy a book that claims it.

Decide which style of curry cookbook you need

Curry cookbooks split along one main fault line: restaurant-style vs. home/regional cooking. They teach different skills and suit different cooks.

The Curry House's own framing is telling: it separates "restaurant-style recipes" from "recipes from the Raj" and keeps a glossary of Indian restaurant terms and curries alongside a glossary of spices. That separation is the same one you should look for in a book — a book that blurs restaurant-style and traditional cooking usually does neither well.

Check whether the book teaches foundations or just lists dishes

A cookbook that only lists named dishes (bhuna, dhansak, rogan josh, chicken tikka masala) leaves you dependent on that exact recipe. A book worth keeping explains the reusable parts:

• Spice mixes and their ratios — a house blend you can scale, not a different mix per recipe.
• A base sauce or gravy method, if it is restaurant-style. This is the single biggest time-saver and the main thing that makes home results taste like a takeaway.
• Technique notes — when to add spices, how to avoid burning them, how to finish a dish.
• Substitutions — what to do when a spice or ingredient is unavailable.

If a book's sample pages show only ingredient lists and steps, with no explanation of the base or the blends, expect to follow it rigidly rather than learn from it.

Judge difficulty, ingredients, and portion sizes before buying

Use the preview and table of contents to answer three practical questions.

1. Difficulty. Count how many recipes need a pre-made component (base gravy, marinade, spice mix) versus how many are one-pan. A book where every recipe depends on a base you haven't made yet is a project, not a weeknight book.
2. Ingredient availability. Scan the ingredient lists for things you can't buy locally. A glossary of spices helps here — it tells you what a spice is and often what it can be swapped for.
3. Yield and scaling. Check whether recipes serve 2, 4, or 6, and whether the book says how to scale. Curry often improves overnight, so a book that cooks in larger batches and tells you so is more useful for a household of one or two.

Paper vs. digital: pick by how you use it

The Curry House lists its Victorian London guide at £5.99 in paperback and £1.99 on Kindle — a typical gap, and a useful reminder that if you mainly want to search terms and skim, the cheaper digital edition does that job. If you cook with the book open on the counter and move between pages constantly, paper usually wins.

A quick filter before you buy

• Read the table of contents: does it have a foundations/spice/base chapter, or only dishes?
• Read one full recipe end to end: can you follow it without guessing?
• Check the glossary or index: can you look up a term you don't know?
• Check the edition and price separately — don't assume the digital version is included with the print one, or that either is free.
• Read reviews specifically for accuracy of quantities and whether results matched the photos.

If a book passes the foundations check and its recipes match the way you actually cook on a normal week, it is worth buying. If it only passes on reputation or photography, borrow it first.

If you're new to Ahrefs and want to run your first SEO audit, the fastest path is: open Site Explorer, enter your target URL, review the Overview for a health snapshot, then dig into Organic Keywords, Top Pages, and Site Audit to find specific problems. From there, build a short prioritized to-do list instead of trying to fix everything at once.

This tutorial walks through that workflow using a realistic starting scenario, explains what the numbers mean, and shows how to turn findings into actions.

Before You Start: Pick a Narrow Scope

A common beginner mistake is auditing an entire large website on day one. The reports become overwhelming, and you can't tell which issues matter.

Instead, choose one of these starting points:

• A single important page (your homepage or a key product/service page)
• A small site (under ~50 pages, e.g., a personal blog or small business site)
• One section of a bigger site (e.g., /blog/)

For this tutorial, assume you're auditing a small business site with about 30 pages. The same steps scale up later.

You'll need an Ahrefs account to follow along. Ahrefs offers paid plans, and pricing and feature limits change over time, so check the current Pricing page for what's included in each tier before committing.

Step 1: Enter Your Target in Site Explorer

Site Explorer is Ahrefs' core tool for analyzing any website or URL.

1. Open Site Explorer from the top navigation.
2. In the search box, paste your domain (e.g., example.com).
3. Choose the Exact URL or Domain mode depending on scope. For a full-site view, use Domain or Prefix; for a single page, use Exact URL.
4. Press Enter.

You'll land on the Overview report. Don't try to absorb everything — focus on four numbers first.

Reading the Overview Snapshot

Important caveat: Ahrefs' traffic and keyword numbers are estimates based on its own data. They won't match Google Search Console or your analytics exactly. Treat them as directional, not absolute.

Step 2: See What You Already Rank For

Go to Organic Keywords in the left sidebar. This shows queries where your site appears in search results.

Sort by Traffic (descending) to see which pages bring the most estimated visitors. Then look for:

• Keywords ranking in positions 4–15 — these are often the easiest wins. A small content or on-page improvement can push them onto page one.
• Keywords with high volume but low position — potential opportunities if the topic is relevant.
• Irrelevant keywords — if you rank for something off-topic, it may signal thin or mismatched content.

Write down 5–10 of the position 4–15 keywords. These become your first optimization targets.

Step 3: Find Your Best and Weakest Pages

Open Top Pages. This ranks your URLs by estimated organic traffic.

Look for two things:

1. Your top performers — understand what topics and formats work. Can you create more content like this?
2. Pages with traffic but poor rankings — these may need on-page fixes (title, headings, internal links).

If a page gets zero traffic and targets a topic you care about, it's a candidate for a rewrite or consolidation.

Step 4: Run a Technical Site Audit

Now move to Site Audit. This crawls your site and flags technical and on-page issues.

1. Click Site Audit → New project.
2. Enter your domain and set crawl settings (default is usually fine for a small site).
3. Start the crawl and wait for it to finish.

Once complete, you'll see a Health Score and a list of issues grouped by category.

Which Issues to Fix First

Not all issues are equal. Prioritize in this order:

Ignore low-impact warnings (like minor meta description length) until the big items are handled.

Step 5: Turn Findings Into a To-Do List

You now have raw data. Convert it into a short, actionable list. Example:

1. Fix 3 broken links found in Site Audit.
2. Rewrite title tags on 5 pages with duplicate titles.
3. Improve 4 pages ranking in positions 6–12 by adding missing subtopics and internal links.
4. Remove or update 2 thin pages with no traffic.

Keep the list to 5–10 items max for your first audit. Finishing a short list beats starting a long one.

Common Beginner Mistakes

• Chasing every red flag. Site Audit flags many minor issues. Fix what affects rankings and users first.
• Trusting estimates as exact numbers. Ahrefs data is modeled, not measured from your analytics.
• Auditing a huge site too early. Start small to learn the interface.
• Ignoring search intent. A page can be technically perfect but still fail if it doesn't match what searchers want.
• Forgetting to re-crawl. After fixes, run Site Audit again to confirm improvements.

Where to Go Next

Once your first audit is done:

• Compare with competitors using Site Explorer's Competing Domains and Content Gap reports.
• Track keyword rankings over time with Rank Tracker.
• Explore backlink opportunities in the Backlinks and Link Intersect reports.
• Set up recurring Site Audit crawls so new issues surface automatically.

Your first audit isn't about perfection — it's about building a repeatable habit: enter a target, read the key reports, pick the highest-impact fixes, and act. Do that once a month and your site's health compounds.

The fastest way to choose a BuzzFeed recipe is to filter it against three real constraints before you get attached to it: the time you actually have, the equipment already in your kitchen, and the ingredients you can get without a special trip. BuzzFeed's recipe output is huge and video-first, which makes almost everything look easy and fast. Your job is to separate the recipe that looks good from the one that fits your Tuesday night.

Here's a practical way to do that, step by step.

Start With Your Real Constraints, Not the Video

Before browsing, write down three numbers and one list:

• Minutes of hands-on time you're willing to spend (not total time — hands-on is what actually tires you out).
• Total time until you want to eat.
• How many people you're feeding.
• Equipment you have — oven, stovetop burners free, one pot or several, sheet pan, blender, air fryer, slow cooker.

Then judge each recipe against that list. A 20-minute video often hides 10 minutes of chopping and a 15-minute simmer. If the recipe says "simmer until thickened" without a time, assume 10–20 minutes and decide whether that fits.

Quick filter questions

Ask these before you commit:

1. Does it need an appliance I don't have or don't want to clean?
2. Does it use more than one pot or pan? (Fine on a weekend, painful on a weeknight.)
3. Is there a long passive step — marinating, chilling, proofing, roasting — that pushes dinner past when I want to eat?
4. Can I do the chopping while something else cooks, or is it all front-loaded?

Read the Ingredient List for Hidden Work

BuzzFeed recipes often lean on a few convenience items. That's not a flaw, but you need to spot them before you start.

Watch for:

• Specialty sauces or pastes (chili crisp, gochujang, tahini, fish sauce) — great if you own them, a detour if you don't.
• Fresh herbs sold in bunches bigger than the recipe needs.
• "Optional" garnishes that the video treats as mandatory for the look.
• Vague quantities like "a handful" or "to taste" — fine for a confident cook, harder if you're following closely.

Realistic substitutions to keep in your back pocket

If a swap changes the chemistry — baking, custards, breads — don't improvise. Pick a different recipe instead.

Use the Format to Gauge How Much Guidance You'll Get

BuzzFeed publishes recipes in a few shapes, and each tells you something about how much hand-holding you'll get.

• Short video (Tasty-style): Fast and visual, but often skips temperatures, times, and doneness cues. Best when you already know the technique.
• List-style post ("17 Dinners You Can Make in 30 Minutes"): Good for browsing and inspiration. The actual instructions may be thin or link out.
• Step-by-step article: Usually the most reliable for a first attempt — more text, more detail, fewer surprises.

Rule of thumb: if you've never made the dish before, favor the step-by-step version. If you've made it many times, the short video is enough.

Check Serving Size and Scaling Before You Shop

Serving size is where a lot of weeknight cooking goes wrong.

• If the recipe serves 4 and you're cooking for 2, halving works for most stovetop dishes but not always for baking, sauces, or anything cooked in a fixed-size pan.
• If you're scaling up, remember that browning and reducing take longer in a bigger batch. Crowding a pan steams food instead of searing it.
• Seasonings, salt, and spicy elements rarely scale linearly. Start with less, taste, adjust.

Write down the scaled amounts before you cook so you're not doing math with hot oil in front of you.

Skim Comments and Creator Notes for Failure Points

This is the highest-value two minutes you'll spend. Look for repeated themes:

• "Needed way more time than stated."
• "Too salty / too sweet as written."
• "The sauce broke."
• "I added X and it was better."

When several people mention the same fix, treat it as the real recipe. Creator notes at the top of a post often carry the same information — read them before the steps, not after.

Save Two Backups So One Missing Item Doesn't Sink Dinner

Pick your main recipe, then line up two alternates that share most of the same ingredients. That way, if the store is out of one thing or you're missing an item at home, you pivot instead of ordering out.

A simple planning template:

Tonight's main: _______________
Hands-on time: ___ min | Total: ___ min | Serves: ___
Equipment needed: _______________
Missing ingredients: _______________
Substitutions planned: _______________
Backup 1: _______________
Backup 2: _______________

A Worked Example (Hypothetical)

Say you have 30 minutes, one skillet, and a pound of ground meat. You see a video for a creamy pasta that looks great — but it needs a blender, two pots, and 45 minutes of simmering. It fails your filter. You scroll to a one-pan skillet dish with pantry spices and a 20-minute cook time. That one passes. Your backups are a stir-fry and a sheet-pan dinner, both using the same protein and whatever vegetables you have.

That's the whole method: match time, equipment, and ingredients first; use format and comments to judge reliability; keep backups ready.

The Short Version

• Filter by hands-on time, equipment, and servings before you fall for the video.
• Scan ingredients for specialty items and decide on swaps in advance.
• Prefer step-by-step posts for first attempts, short videos for familiar dishes.
• Scale carefully, especially for baking and sauces.
• Read comments and creator notes for the real cook times and fixes.
• Always have two backup recipes that share ingredients.

Do this once or twice and it becomes automatic — you'll stop starting recipes you can't finish and start cooking the ones that actually fit your night.

印度餐厅菜单上的咖喱菜名，主要区别在酱汁浓稠度、香料组合和辣度，而不是食材本身。同一道菜（比如 chicken）可以做成 bhuna、dhansak、rogan josh 或 tikka masala，味道差别很大。看懂这几个名字，你就能按口味直接点菜，不用每次问服务员或碰运气。

常见咖喱菜名的区别

以下区分依据 The Curry House 网站提供的印度餐厅术语表（glossary of Indian restaurant curries）和菜谱资料。

一个简单的判断方法：酱汁越稠、越甜，辣度通常越低（korma、tikka masala）；酱汁越稀、酸味越明显，辣度通常越高（vindaloo、madras）。bhuna 和 jalfrezi 属于“干香型”，香料贴在食材上，不是泡在酱里。

Tandoori 和咖喱菜不是一回事

点餐时容易混淆的一点：tandoori 指用泥炉（tandoor）烤制的菜，本身不带咖喱酱。

• Tandoori chicken：腌过后烤，外皮焦香、偏干，通常配柠檬和洋葱，不浇酱。
• Chicken tikka：tandoori 的块状版本，同样烤制、无酱。
• Chicken tikka masala：把烤好的 tikka 放进奶油番茄酱里——所以它同时有烤制和酱汁两种特征。

如果你想要“有酱汁、能配饭”的菜，选咖喱类；如果想吃烤肉的焦香口感，选 tandoori 或 tikka。两者可以一起点，tandoori 当开胃菜，咖喱当主菜。

按口味偏好选菜

• 怕辣、想要顺口：korma、tikka masala、passanda（奶油坚果酱）。
• 想要辣但不要酸：madras、jalfrezi。
• 能接受高辣和酸味：vindaloo。
• 喜欢香料味浓、不爱太多酱：bhuna、jalfrezi。
• 想要甜酸平衡、口感丰富：dhansak。
• 想要番茄红椒的温和底味：rogan josh。

辣度在不同餐厅之间会有浮动，同一道 madras 在两家的辣度可能不同。第一次去一家店，可以先点中辣档的菜试水。

配菜和主食怎么搭

一顿完整的印度餐厅点餐通常包含：

• 主食：米饭（basmati、pilau）或面饼（naan、roti、paratha）。酱汁多的菜配米饭或 naan；干香型的 bhuna、jalfrezi 配 roti 更合适。
• 配菜（side）：bombay potatoes、saag aloo、dal（扁豆）、raita（酸奶黄瓜，用来解辣）。
• 前菜：papadum 配酸辣酱、onion bhaji、tandoori 类。
• 饮品：lassi（酸奶饮）或芒果 lassi 能中和辣味。

一个实用搭配：一份咖喱主菜 + 一份米饭或 naan + 一份蔬菜 side + raita。两个人点两份不同辣度的咖喱，可以互相尝、也避免整桌都太辣。

点餐时可以直接用的判断

看到不认识的菜名，按这个顺序判断：先看酱汁是稠是稀（决定口感），再看是否含扁豆或菠萝（dhansak 偏甜酸），最后看辣度档位（vindaloo、madras 偏高，korma、tikka masala 偏低）。Tandoori 和 tikka 是烤制、无酱，tikka masala 是烤制加酱。按这个逻辑，你基本能在不看菜单描述的情况下点出符合自己口味的菜。