We’d love to hear from you! Whether you have a question about a recipe, a suggestion, feedback, or just want to say hello — feel free to reach out.
Get in Touch
📧 Email: contact@homerecipedaily.com
What can you contact us for?
- Questions about any recipe on our website
- Suggestions for new recipes you’d like to see
- Feedback about your experience with our recipes
- Collaboration or partnership inquiries
- Reporting any issue with the website
We try to respond to all messages within 24-48 hours. Your feedback means a lot to us and helps us keep improving Home Recipe Daily!
Send us a Message
Thank you for visiting Home Recipe Daily. We look forward to hearing from you!
What Helps Us Give You a Useful Answer
A short message is fine. A message with a few concrete details is better, because it lets us skip the back-and-forth and get straight to the part that actually helps. If your question is about a recipe, the recipe name matters most. After that, the step where things went sideways, the ingredient you swapped, and the equipment you used all change the answer. A cake baked in a glass dish behaves differently from one baked in a dark metal pan. A sauce made with low-fat milk will not thicken the way a sauce made with cream does. None of that is a mistake on your part. It is just how cooking works, and it is exactly the kind of detail that turns a vague reply into a useful one.
It also helps to tell us what you already tried. Did you add more liquid, turn the heat down, or leave it in the oven a few extra minutes? That tells us where you are in the process, so we do not suggest something you have already done. If the dish is still on the stove, say so. If you are planning to cook it again tomorrow, say that too. The advice changes depending on whether you need a rescue right now or a better plan for next time.
Recipe Questions, Step by Step
Most recipe questions fall into a handful of buckets, and each one has its own useful details. For timing questions, tell us the size and shape of your pan, whether your oven runs hot, and how thick you cut the pieces. A tray of thick chicken thighs needs more time than a tray of thin cutlets, and no written time can cover both without that context. For texture questions, describe what you see and feel. Is the dough sticky, stiff, or tearing? Is the sauce thin, grainy, or separated? Those words point to different fixes, and guessing without them wastes a round of messages.
For ingredient swaps, the reason for the swap matters as much as the swap itself. Swapping because an ingredient is out of stock is different from swapping because of an allergy or a dietary preference, and the safest substitute is not always the same in both cases. Tell us both the original ingredient and what you used instead, plus the amount. A swap that works at one tablespoon can fail at one cup, especially with baking powder, gelatin, or anything that sets, rises, or thickens. We will tell you honestly when a swap is untested on our side, rather than dressing up a guess as a tested answer.
Corrections, Typos, and Things That Look Wrong
If you spot something that looks wrong in a recipe, we want to know. A missing ingredient in the list, a step number that skips ahead, a temperature that does not match the recipe card, or a photo that shows a different pan from the one described, all of it helps. Copy the line as written if you can, or describe where it sits in the recipe. That makes the fix fast, and it keeps the next reader from tripping over the same spot.
Corrections do not need to be formal. A plain note like “step four says two cups but the list says one” is perfect. We check corrections against the recipe as tested, not against the message alone, so a fix lands only when it matches what actually works in the kitchen. If a correction turns out to be a matter of taste, like a reader preferring less salt, we still read it, and it sometimes shows up as a note in the recipe for future cooks.
Suggestions for Recipes You Would Like to See
Requests drive a surprising share of what gets published here. If there is a dish you cook often, a weeknight dinner that needs a faster version, or a holiday classic you have never quite nailed, send the idea. A few details make a request much easier to act on. What kind of meal is it, breakfast, lunch, dinner, or dessert? How much time do you usually have? Are there ingredients you need to avoid, or equipment you do not own, like a slow cooker or a stand mixer? A request for a one-pot pasta that feeds four on a Tuesday is easier to build than a request for “something tasty,” and it is more likely to become a recipe you actually cook.
We also welcome suggestions that are not recipes at all. Maybe a guide would help more than a single dish, like how to store fresh herbs so they last the week, or how to pick a ripe avocado without squeezing every piece of fruit in the store. Those guides take longer to put together, but reader requests are often how they start.
Photos, Links, and Messages From Other Cooks
If you cooked one of our recipes and want to share how it turned out, we love seeing that. A photo of the finished dish, a note about a swap that worked, or a tip you discovered along the way can all help other readers. When you send a photo, a line about what you changed is worth more than the photo alone, because other cooks want to repeat your result, not just admire it. Links to your own blog or social media posts are welcome in that context, as long as the message itself is about the cooking.
Messages that are purely promotional, or that link to unrelated products and services, are a different matter. They slow down replies to genuine cooking questions, so they are not treated the same way. If your message is about a product you sell, say so plainly in the first line, and we will judge it on its merits rather than discovering the pitch halfway through.
Collaboration and Partnership Messages
Brands, publishers, and fellow food writers can use the same form. A useful collaboration message says what you are proposing, what it involves for us, and what it offers readers, in plain terms. Vague offers with no specifics tend to stall, not because they are unwelcome, but because there is nothing concrete to answer. If you represent a product, say what it is and how it relates to home cooking. If you are proposing a recipe exchange, a guest post, or a roundup inclusion, say which recipes or topics you have in mind.
We do not promise coverage, links, or reviews in exchange for samples or payment, and we do not accept content that reads like advertising dressed as a recipe. Anything published here has to stand on its own as cooking advice a reader would trust, with or without a sponsor behind it. That standard protects readers, and it protects collaborators too, because a recommendation that readers trust is worth more than one they scroll past.
If Part of the Site Is Not Working for You
Website problems are worth reporting, and the details that help are simple ones. Which page were you on, what were you trying to do, and what happened instead? A recipe page that will not load, a print button that produces a blank page, a video that plays without sound, or a form that clears your message when you submit it, each of those points to a different fix. The type of device you used, phone, tablet, or computer, and the browser you used, if you know it, narrow things down further.
You do not need to diagnose the problem yourself. A plain description of what you saw is enough. If an error message appeared, copying its wording helps, but a description like “the page went white after I tapped print” is already useful. We pass genuine site issues along for fixing, and reader reports are often how small glitches get found, because a problem that appears on one device may never appear on ours.
Before You Send Your Message
A quick check can save you a wait. Many common questions are already answered on the recipe page itself, in the notes under the recipe card, or in the frequently asked questions that sit below longer recipes. Ingredient amounts, pan sizes, storage advice, and reheating steps often live there, added after earlier readers asked the same thing. If your question is about a recipe you cooked a while ago, a look back at the page may surface an update that was added since your first visit.
None of that means you should hesitate to write. If the answer is not on the page, or if it is there but unclear, the message is worth sending. Unclear answers are a signal that the recipe needs a better note, and your question may be the one that prompts it. Every message here is read by a person, not sorted by an automated system, and cooking questions are never treated as an interruption. They are the reason the site keeps getting better, one clarified step at a time.
