What should you watch for when an AI writes recipes for your food blog?

In short: A recipe site has no news cycle; the source of topics isn't a feed but the dishes the site hasn't covered yet. The real risks are writing the same dish twice, broken measurements and an image that doesn't show the food. In Wiozen Content Bot, setting up the recipe category with only a content brief and no RSS covers most of this: the bot suggests topics itself, checks each one against every post on the site with no time limit, and the editor pass leaves measurements, times and steps alone. The bot doesn't add Recipe schema; that needs a recipe plugin.

Should I add RSS feeds to a recipe category?

Usually not. The bot's repeat check treats two kinds of topics differently. Topics from RSS and Google Trends count as news: they're compared only with the last 30 days of posts, by the full title rather than the focus keyword. That's right for a news site where the same story comes back every month, but it leaves a gap for recipes: a lentil soup coming in from another food blog's feed can be written again a month later under a different title.

Topics the bot suggests itself are compared with every post on the site (published, draft, scheduled, pending and private) with no time limit, looking at the main part of the title and the focus keyword in your SEO plugin separately. Since a category can be saved with just a brief, leaving the RSS field empty is enough. With no topics coming from sources, the bot suggests one itself on every run.

When suggesting, the model sees up to 600 existing topics, the same category first. If everything it suggests is already on the site, the bot asks up to 4 more times and expects the model to split the category into narrower subtopics that haven't been written yet. On a site with hundreds of recipes that means going from "soups" to something like "winter soups with pulses".

Doesn't the word "recipe" confuse the repeat check?

No. Words that appear in at least a fifth of the site's posts (and in at least 3 posts) are treated as filler and left out of the comparison. On a recipe site that's typically "recipe", "how", "make". So "Lentil Soup Recipe" and "How to Make Lentil Soup" are caught as the same topic. The list isn't built per language; it comes from the site's own titles, so on a Turkish site "tarifi" and "nasıl" drop out the same way.

Titles that aren't identical but share words go to the model. If "Herb Oven Baked Chicken Drumsticks" is suggested while "Oven Baked Chicken Drumsticks" is on the site, the bot shows the model up to 5 similar posts and asks whether they answer the same question. If the model doesn't answer, a strict word rule applies: when one title contains the other with a single extra word, they're the same, but single-word titles aren't checked for containment ("Chicken" and "Chicken Stir Fry" stay separate). Every skipped topic is written to the Log tab along with the post it resembled. More detail is in the topic-finding guide.

What should the content brief say?

The plugin's own example brief happens to be for a recipe site: home cooking with easy-to-find ingredients, and every article with an ingredient list, step-by-step instructions, tips and a serving suggestion. Add what's specific to your site:

• Units: cups and tablespoons, or grams and millilitres. If you don't say, it can change from article to article.
• Servings: ask for the number of servings in every recipe.
• Sub-types: soups, salads, baking and so on. When topics run out, the bot carves narrow topics out of this list.
• What to avoid, for example brand names or hard-to-find ingredients.

Numbered lists and tables are allowed in the body, so steps and ingredients come out properly formatted. General rules for writing a brief are in the content brief guide.

Can the editor pass break measurements and steps?

With the editor pass on, a second model call checks the article against its sources and removes unsupported claims. For recipes that could be dangerous: in the plugin's first version the editor once removed every measurement in a recipe. The current prompt is explicit: recipe measurements, quantities, times, temperatures and steps need no source, the editor leaves them alone and never turns a concrete detail into a vague one.

The copy check also allows for ingredient lists. When comparing the article with its source, the bot looks for eight identical words in a row, but it ignores sequences that contain two or more numbers; lines like "2 cups flour, 1 tablespoon butter" are naturally the same everywhere. For topics the bot suggested itself, the comparison only uses the research snippets.

None of this means the model can't get a measurement wrong. The model doesn't test recipes, and the prompt forbids invented experience such as "we tried it and loved it". In baking and desserts a wrong ratio ruins the recipe, so it's worth keeping those categories as drafts, reading them before publishing and adding a detail from your own kitchen.

Will the featured image show the dish?

The model that writes the article also writes the image description, and the prompt gives the recipe case as an explicit example: the image should show that dish itself. Desk scenes with a calculator, notebook and pen are banned. For each article the bot picks one of 8 scene patterns (close-up, top-down flat lay, wide shot of the place and so on) and skips those used in the category's last 5 articles, so the front page doesn't turn into the same plate on the same wooden table. There's no text or logo in the image. More in the featured image guide.

Does it add Recipe schema or a recipe card?

No. The bot adds only FAQPage structured data to the article (from its FAQ section). Recipe cards that show cooking time, servings and ratings in search results need Recipe schema, and a recipe plugin produces that. The bot saves the recipe as normal post content, not inside a recipe plugin's block; if you want the schema, you fill in the time and servings fields in that plugin. Choosing a theme for a recipe site, and the schema question, are covered in Wiozen Theme's recipe blog guide.

Frequently asked questions

Download the Content Bot, set up the recipe category without RSS, and read the first recipes as drafts before publishing.

Create your account

More guides: How can you use an AI API from Turkey without a credit card? · How do you connect an OpenAI-compatible API to a tool you already use? · How do you calculate the cost of an AI API? · What should I do if my AI API key has leaked? · How do you generate images with an AI API, and what does one image cost? · Why does my AI API return a 429 error, and how do I fix it? · Why do long AI API requests time out: streaming or non-streaming? · Anthropic Messages API or OpenAI Chat Completions: which one should I use? · What is a context window, and what is a 1 million token context good for? · Which AI model should I choose: deciding by price, context and quality · Why does a reasoning model return an empty answer, and why are thinking tokens charged? · Why is my API balance running out faster than expected? Tracking spend request by request · How do you convert a web page to Markdown to feed it to an AI model? · How do you get AI to write and publish articles in WordPress automatically? · How do you find blog topics from RSS feeds and Google Trends? · Does AI-written content show up on Google and in AI answers? · How do you get internal links into AI-written WordPress articles? · How do you get AI to generate a different featured image for every WordPress post? · How do you write a content brief when an AI writes your blog posts? · How do you fix errors when connecting a WordPress plugin to your AI API account? · Why does my AI article bot stop halfway in WordPress? "Run is stuck" and LiteSpeed · Why are my scheduled WordPress posts late? WP-Cron and a real server cron · How do I get an AI article bot to write blog posts in English or another language? · What does "Content Bot cannot generate articles" mean? Reading the bot's log