<\/p>\n
Recipe content creators and food bloggers accuse Google’s AI systems of appropriating recipes, images, and videos without proper attribution, sparking industry protests over traffic loss, revenue decline, and intellectual property concerns amidst ongoing regulatory debates.<\/p>\n<\/div>\n
Nick Fox, Google\u2019s Senior Vice President of Knowledge & Information, found himself at the centre of a fresh wave of criticism in early December when Adam Gallagher, co\u2011founder of long\u2011running recipe site Inspired Taste, publicly accused Google’s AI systems of appropriating recipes, photographs and videos without proper attribution or redirecting users to the original sites. The exchange , sparked by Fox\u2019s December 1 post announcing a set of publisher\u2011facing features , crystallised frustrations from food publishers who say Google\u2019s AI is displaying full recipes inside its interface, leaving creators with declining traffic and lost ad revenue. [1]<\/a><\/sup>[3]<\/a><\/sup><\/p>\n According to the original report and the LinkedIn thread that followed, Gallagher told Fox that he and other publishers were seeing \u201cbranded searches for us and multiple recipe sites with full plagiarized recipes riddled with errors, using our photos (Gemini Thinking model), our videos, using our brand name, with no citations to our domain recipe page at all, or the citations are incorrect altogether.\u201d Gallagher emphasised that Inspired Taste had been built over 15 years and said the practice effectively turned Google against the sites that sustained the open web. [1]<\/a><\/sup><\/p>\n Fox\u2019s December 1 announcement detailed several initiatives framed as help for publishers: a global rollout of Preferred Sources for Top Stories, subscription link highlighting across Gemini App and AI Overviews, and more inline links in AI Mode responses. Google suggested these moves drove higher click rates when users chose preferred sources. But recipe publishers point out the mismatch between those tools , which focus on news and AI Mode experiences , and the core problem of AI reproducing full instructional content for queries that are not Top Stories. [1]<\/a><\/sup><\/p>\n Industry and independent research lend weight to publishers\u2019 claims of traffic harm. Seer Interactive\u2019s analysis found organic click\u2011through rates for informational queries with AI Overviews fell dramatically , reported as a 61 percent drop for certain queries since mid\u20112024 , and case studies have shown reductions in organic clicks ranging from roughly a third to over half when AI overviews appear. Dotdash Meredith executives have likewise acknowledged measurable performance declines tied to AI Overviews. [1]<\/a><\/sup>[2]<\/a><\/sup><\/p>\n Food bloggers and creators have provided concrete anecdotes of the economic impact. Multiple reports say creators have seen steep drops in visitors , in some accounts as much as 40 percent year\u2011over\u2011year or larger declines over time , and describe AI summaries that sometimes contain incorrect instructions such as wrong baking times, which misleads home cooks and harms publisher reputations. Those accounts mirror the complaints aired by Gallagher and other bloggers. [2]<\/a><\/sup>[3]<\/a><\/sup>[6]<\/a><\/sup><\/p>\n Technically, Google\u2019s AI implementations rely on expansive internal systems that query and synthesise multiple sources. Executives have described a \u201cquery fanout\u201d technique and product infrastructure encompassing billions of items, while Google says AI Mode and AI Overviews aim to answer more queries directly within Google\u2019s interface. The company reported large user adoption for AI Mode and presented AI\u2011driven features as contributors to query growth and monetisation opportunities. [1]<\/a><\/sup><\/p>\n Google has defended elements of the approach by pointing to attribution features , such as \u201caccording to\u201d attributions and inline links , and to experiments that let users signal preferred publishers. Company spokespeople and executives including product leaders have argued that clicks originating from AI Overviews are of higher quality and that Google cares about \u201cthe health of the web.\u201d Yet creators say those measures are insufficient: attribution sometimes is missing or incorrect, and the display of complete recipes leaves \u201clittle reason to click\u201d through to the hosting site. [1]<\/a><\/sup><\/p>\n The asymmetry in Google\u2019s commercial arrangements compounds the dispute. Google announced a paid pilot with major news publishers in December that includes compensation for participating outlets, while recipe publishers have not been offered similar partnership or payment pathways despite reporting that AI systems reproduce their content and imagery. That gap has fuelled calls for more systematic redress and clearer reporting channels. [1]<\/a><\/sup><\/p>\n Copyright and legal questions shadow the debate. Observers point to broader litigation and industry disputes over image and text use in AI training and outputs , for example, Getty Images\u2019 litigation in the image space , and to open letters from publishers urging legislative scrutiny of AI Overviews and compensation for creators. Content owners argue that current US copyright procedures and enforcement are ill\u2011fitted to rapid AI extraction and reuse of web content. [4]<\/a><\/sup>[7]<\/a><\/sup><\/p>\n Creators also highlight how the recipe format is particularly vulnerable: standardised ingredient lists and step\u2011by\u2011step instructions are straightforward for models to extract and reproduce, and professional food photography can be displayed inside AI interfaces without clear credit. When AI outputs contain errors, the reputational damage falls on the named publisher even though the synthesis may be the product of the AI\u2019s processing rather than the original author\u2019s work. [1]<\/a><\/sup><\/p>\n The practical frustration for publishers is procedural as much as technical. Gallagher and others have demanded an \u201cofficial channel\u201d to report misuses and seek remediation; social\u2011media escalations have filled that void in the absence of a clear, fast process for creators to correct attributions or request removals. Google\u2019s guidance urging publishers to mobilise followers to star preferred sources has been criticised as placing the burden on creators rather than on the platform. [1]<\/a><\/sup><\/p>\n Possible remedies discussed within the publishing community range from stronger mandatory attribution requirements and clearer linking behaviour for AI summaries to compensation mechanisms akin to Google\u2019s news partnerships, plus industry standards for reporting and auditing AI outputs. Some experts have also called for regulatory involvement to reconcile AI capabilities with intellectual property rights and the economic ecosystem that sustains independent content creators. [1]<\/a><\/sup>[4]<\/a><\/sup>[7]<\/a><\/sup><\/p>\n The controversy over recipes is part of a broader reckoning between large AI platform operators and the creators whose work fuels those systems. Travel bloggers, niche reference sites and newsrooms have reported similar traffic declines when AI summaries replace direct links to their pages. The question for Google and the wider industry is how to balance user expectations for concise answers with the economic and moral imperative to preserve attribution, revenue and the incentives that sustain high\u2011quality original content. [1]<\/a><\/sup>[3]<\/a><\/sup>[5]<\/a><\/sup><\/p>\n For now, the dispute remains unresolved. Google has rolled out features it says support publishers and has entered paid partnerships with major news organisations, but recipe creators and many other independent publishers continue to report missing or incorrect citations, reproduced photos and embedded recipes that bypass their sites. The sector is seeking clearer operational channels and, in some quarters, legal and regulatory clarity about when and how AI may repurpose copyrighted work without compensation. [1]<\/a><\/sup>[5]<\/a><\/sup>[4]<\/a><\/sup><\/p>\n ##Reference Map:<\/p>\n\n