Google Is Hiring People to Write Discover. Your Food Brand Has to Be the Source.

Google is staffing up to put its own AI-written stories into Discover. Search Engine Journal's Matt G. Southern found the job listings. One is for a Staff ML Engineer on the Discover Feed Recommendation team, which the listing says "leads by recommending AI-generated content (AIGC) to fulfill user interests." That engineer will check the content for factuality, freshness, coherence and tone.

Another listing wants a principal UX lead, base pay $275,000 to $382,000, to build what Google calls a "proactive, hyper-personalized concierge experience." A data science listing for the same product puts Discover at "more than 500 million daily active users."

For years Discover has been where a recipe post with a good photo went to meet strangers. A small sauce company, a farm with a blog, a bakery that writes up its fall menu. You never asked for the traffic and you never paid for it. Some of those cards are about to be Google's summary of everybody's posts, yours included.

What the listings say, and what they don't

None of the listings gives a timeline. None says how much of the feed the AI stories will fill. Google Careers doesn't show when the roles went up, and listings close or change. This is a hiring plan, and a hiring plan can stall.

It does fit a pattern. Google launched AI previews on trending topics in Discover in October 2025, in the U.S., South Korea and India. On September 18, Robby Stein, Google's VP of Product for Search, announced a test of a "Dive deeper" button that opens a short topic overview with links to related stories. Each step puts more of Google's own writing between the reader and yours.

The UX listing carries one line worth holding Google to. It asks the hire to balance the AI against "keeping human voices and sources at the center." That's the opening for a small food brand, and it's narrower than it sounds. A summary needs something to summarize. Google's quality team is grading those stories on freshness and factuality, and a model can't make up a fresh fact about your brand that's also true. Somebody has to publish it first.

Google can't summarize what you haven't published yet

Generated cards know fall is squash season. They don't know your butternut and green chile soup goes back on the menu Thursday. They don't know the squash came from a farm forty minutes up the road, or that you burned the first batch and changed the roast time. Those facts live in one place until you post them.

So be the place. Put the new thing on your own domain first, dated, with a photo you shot. Then let Instagram and the rest have it. If Google wants to write a fresh card about your new flavor, your harvest or your price change, the freshest source it can find should be a page you own. A big brand's committee-approved paragraph is exactly what a model writes well. The batch notes from a 40-person company are what it can't.

That's the part of an ai content strategy most brands skip. They ask what AI can write for them. The better question is what only they can write, and how fast they get it onto a page Google can index.

I checked my own site this morning

Google's own Discover documentation is short. No special tags or structured data are required. A page has to be indexed and meet the content policies. Google recommends images "At least 1200 px wide," more than 300,000 total pixels, and says large images are enabled by the "max-image-preview:large" setting or by AMP.

So I pulled the code on my own site. The hero image on yesterday's article goes out at 1440 by 804, which clears the width bar with room to spare. Then I looked for that setting on the homepage and three articles. It isn't on any of them. My Squarespace setup doesn't add it, and I never did either. I've been publishing big photos every day and never told Google it could show them big.

I'd bet most small food brands sit in the same spot. Nobody opens the page source on a site that seems to work.

What to do this week

Open Search Console and look at the Discover report. It shows impressions, clicks and click-through rate for anything that's appeared in Discover in the last 16 months, as long as you've crossed Google's minimum impressions threshold. If there's no Discover report, you either haven't shown up there or haven't crossed the threshold, and the rest of this is about getting on it. If there is one, write down the last three months of clicks today. That's your baseline before Google's stories start sharing the feed.

Add the large image setting. One robots meta tag in the page header does the job. Open view-source after and confirm it landed.

Put a signup box on every page Discover sends people to. A recipe, a harvest post, a new flavor page. A stranger from Discover who leaves without giving you an email address is a stranger Google can send somewhere else next time. A list is the one audience nobody else edits.

Publish the dated fact first, on your own site, before the social post. I made the case for counting this traffic before you lose track of it when Google tagged Gemini's links, and the same logic applies here. You can't defend a channel you never measured. And when a platform changes the terms on a link, the post has to do the selling on its own, which I wrote about when Facebook metered your link.

Your food and beverage marketing agency should know what share of your traffic comes from Discover. If they can't tell you, ask before the month ends.

Discover setup is one of the first things I check when a food brand hires me. If you want yours checked, DM me.