New job postings have all but disappeared from Google’s job search vertical for roughly a week, according to Search Engine Roundtable founder Barry Schwartz. The gap matters because employers and job boards feed that vertical through JobPosting structured data, and a display bug there cuts off visibility regardless of how clean the markup is.
Schwartz filtered New York City listings by “past day” and found zero results, then widened to a three-day window and still saw only a handful. He noted the timing looks inconsistent with the underlying labor market: the same week’s jobs report showed nonfarm payrolls up 162,000 in August, well above the 53,000 consensus, with unemployment holding at 4.1 percent. New openings clearly exist. Google’s job search surface is simply not showing them.
A Reddit thread titled “Google Jobs feed drying up?” collected similar reports. One user described saved queries returning only old postings, with no new results generated in days. Another said the “x days ago” freshness tag is missing from listings newer than eight days old, which makes it impossible to confirm posting dates inside the interface itself. That detail points to a metadata or indexing issue rather than a simple drop in employer submissions.
Schwartz linked the bug to a separate time-filter glitch he had flagged earlier in August, which affected date filtering in regular web and News search results. If the same underlying system handles freshness signals across search, News, and Jobs, one indexing fault could be surfacing as three distinct symptoms depending on which vertical a user checks. Google has not confirmed a connection, and no root cause has been published.
For SEO teams managing job boards or career pages, the practical risk is not a markup problem. Sites can implement JobPosting schema correctly, per Google’s own documentation, and still see zero new-listing visibility if Google’s ingestion or freshness pipeline for the Jobs vertical is broken. That distinction matters for anyone deciding whether to re-audit structured data this week: the fix, if there is one, sits on Google’s side, not the publisher’s.
The bug also carries a measurement risk beyond visibility. Job boards that report click-through or impression data to employers as a service metric should expect a dip that has nothing to do with employer demand or content quality, and should be prepared to explain that gap rather than let a client assume the listing underperformed.
Google has not issued a statement on the reported bug at the time of writing. Until it does, teams that rely on Jobs vertical traffic should treat the past week’s numbers as unreliable for trend analysis, and should recheck listing visibility in Search Console once Google confirms a fix rather than resubmitting sitemaps or re-validating schema in the meantime.
Search Engine Roundtable’s Barry Schwartz first reported the Google job search visibility bug on September 4, 2026.