Google Jobs is Broken Again - August 2026 - Here is What We Know

If your Google Jobs traffic dropped over the last two weeks, you are not alone – Google Jobs is broken (again). So, it is most likely not something you did – good feeling, right? 

What is happening? 

Since the end of August, Google Jobs has, for large parts of the day, simply not been showing new jobs. Not your jobs specifically – just no new jobs from anyone. Job seekers noticed it first; Barry Schwartz picked it up on September 4, and by now I have enough client data, screenshots and third-party evidence to say that this is the most likely reason job boards are seeing organic traffic drops in September. Not (only) the August spam update, which is what I initially assumed.

Here's what happened, what it looks like in Search Console, how to tell it apart from the spam update, what happened the last two times Google Jobs broke, and some speculation at the end about why this might be happening right now.

You can reproduce it yourself (for now)

This morning, September 14, I ran a couple of searches from Barcelona. "marketing trabajo barcelona since yesterday", Jobs tab: nothing. "Last 3 days": nothing. This is Barcelona, a city of 1.6 million people, in a market where Indeed, InfoJobs and LinkedIn push hundreds of new marketing jobs every week.

Here is the last 3 days results:

Now switch the filter to "last week" and jobs show up. But look at the dates: 6 days ago, 5 days ago, 4 days ago, and a single one from 2 days ago via WhatJobs. So the index is not empty. Google has the jobs from last week. It just doesn't show the ones from the last 48 to 72 hours.

Then it gets weird. I ran the same "since yesterday" query a couple of hours later and suddenly there were results. And then other queries with a date filter went back to zero. This flapping has been the pattern the whole time: results come and go depending on the query, the location and the time of day. That is why someone in your team will tell you "it works for me" while your traffic chart says otherwise.

To me, this looks like an ingestion or indexing problem in the Google Jobs pipeline, not a ranking change. A ranking update does not make "posted yesterday" return zero results for an entire city. Something between "Google receives the job" and "the job becomes searchable with a fresh date" is not working reliably.

(Side note: in the screenshots, you can see the "Job sites" tab next to "Jobs". That is the SERP feature I covered in Google Testing Job Sites SERP Feature Above Google Jobs, and it has been working fine the whole time. More on that at the end.)

The biggest tell that something is broken is that for certain queries, like the one in the screenshot below, you see a Google Jobs search feature with jobs, but once you apply the "yesterday" filter, the Google Jobs feature completely disappears, which hints at a broken implementation rather than no jobs available.

What this looks like in Search Console

Here is the Google Jobs traffic of a US-based job platform, job pages only, over the last six weeks.

You see the normal weekly pattern through mid-August, a dip around the spam update, a recovery to the same level as before, and then the slide starts at the end of August, exactly when the first reports of Google Jobs not surfacing new jobs came in. By September 9, the site is below the lowest point of the previous six weeks, and it hasn't come back.

This is where I got it wrong at first. When the client sent me this chart, the spam update was the obvious suspect and it is true that spam dates usually hit job boards pretty hard due to our bad usage of programmatic SEO. 

It finished rolling out on August 21, and the first dip lines up with it. But the spam update dip recovered. The second drop did not. The second drop started a week after the update was complete, which isn't how spam updates usually behave (they hit hard at the start, as I described in The impact of the 2025 Google Spam Update on Job Boards).

One more thing before you conclude from the recovery reports that this is over. It is not. Search Console runs two to three days behind, so the chart above stops before the weekend. Google Analytics doesn't have that lag, and here is the Google Jobs traffic for another site in GA, up to and including today, Monday, September 14. Monday and Tuesday are normally the strongest days of the week for any job board. This Monday is the lowest point in the entire 4-week period.

So yes, jobs are slowly starting to show up again in some queries, but whatever is broken is not fixed. The feature is clearly not working properly. The fresh inventory trickling back in is nowhere near enough to move traffic, and I wouldn't call this a recovery until a Monday looks like a Monday again.

If you want to check your own site, go to the Performance report in Search Console, filter Search appearance by "Job listing" and "Job details", and compare the last 14 days with the previous 14 days. If those two are down and your category pages are flat, you are looking at this issue. If everything is down, including category pages and blog content, you may have a spam update problem on top of it.

The timeline: how this unfolded

I want to put the whole sequence in one place because the reports are scattered across Reddit threads, an SEO blog and a scraper's status page, and nobody has connected them so far.

Around August 17, a thread appears on r/TechSEO: a high-authority site with fewer than 100 job listings sees all of its previously indexed job pages move to "Crawled - currently not indexed". Nothing blocks crawling, Google renders the pages fine, the markup is unchanged. The poster suspects the spam update. In hindsight, this was probably the first visible symptom, but one site does not make a pattern. 

August 18 to 21: Google runs the August 2026 spam update. It took 2 days and 16 hours according to the Search Status Dashboard, the longest spam update this year. No companion blog post, no new policy. This is where I, and I assume most SEOs looking at job boards, initially filed the traffic drops.

Around August 27 to 31, the first job seeker report shows up on r/jobsearchhacks, titled "Google Jobs feed drying up?". The poster uses saved Google Jobs queries to find leads and notices that the queries still work but only return old postings. 12 upvotes, 20 comments. Small numbers, but this is job seekers, not SEOs, which tells you the problem was visible on the user side before anyone in our industry paid attention.

September 2 is the most important data point in the whole thread. The same poster runs "accounting jobs in Chicago". The Jobs tab shows no current results. Then he clicks on AI Mode, and there they are: current job summaries with links to the boards where they live. Google has the fresh jobs. The Jobs surface just does not show them.

Around September 3, people in the same thread report that Google Jobs email alerts have stopped arriving, some for about a week. That makes sense if you think about how alerts work: they fire when new jobs enter the index for your saved search. No new jobs in the index, no alerts. This I can confirm. 

September 4: Barry Schwartz publishes "Google Job Search Not Showing New Jobs?" on Search Engine Roundtable. He filters jobs in New York City for the past day and gets nothing, and only a handful for the past three days. He says it has been happening for about a week, which puts the onset around August 28. He also makes the obvious point: nonfarm payrolls jumped by 162,000 in August, so this is not the labor market. Barry also mentions that Google had a similar time-filter problem with regular search results and news in August. Keep that in mind for the hypotheses below.

September 4 to 10: SerpApi, the scraping API many of us use for rank monitoring, logs performance degradation across its Google APIs, including the Google Jobs API. On September 8, it reports elevated response times again, including Google Jobs. Now, SerpApi's problems are SerpApi's problems, and an API outage at a scraper is not an outage at Google. But their Google Jobs endpoint parses the same Jobs SERP you and I look at, and it started misbehaving in the same week. So, a CSS/HTML change broke down SerpAPI?

September 11: an SEO in the r/TechSEO thread reports that none of their current listings show up in Google Jobs and that a search for "cdl jobs" returns one listing, where there are normally at least a dozen. For non-US readers, CDL jobs are truck driver jobs. The US never has a shortage of truck driver jobs.

Also September 11, and this one is from my own inbox. Remember the alerts that stopped at the beginning of September? Mine came back. Google sent me "1 new job for product manager jobs near me" on the night of September 10 to 11. One job. And look at the posting date: August 28. The alert pipeline is running again, and what it offers as "new" is a two-week-old internship that had been sitting in the index since before the whole thing started. This is the alert system faithfully reporting what the index contains, which is nothing fresh. A bit old, am I right?

I find this the cleanest piece of evidence in the whole story, because alerts remove the "maybe it is your query, maybe it is your location" ambiguity. The alert is Google's own system telling you what entered the index for your saved search. When it stops firing, nothing entered. When it fires with a job from two weeks ago, the trickle has started but the pipeline is still mostly dry.

September 12: a recruitment agency posts on r/RecruitmentAgencies that Google Jobs has been returning zero results for days. Not their jobs, not anyone's jobs. The same day, the first signs of recovery appear in the jobsearchhacks thread: the past-three-days filter returns results again for some people, and at least one email alert resumed. Fresh inventory still looks thin.

September 14, today: SerpApi's dashboard still lists its Google Jobs API as "Partial Outage", with 98.77% uptime over the last 90 days. And my Barcelona queries return nothing in the morning and results a few hours later.

And Google? The Search Status Dashboard shows no crawling, indexing or serving incident for the whole period. Not a word. Which is exactly what happened in 2024 and 2025 as well.

Spam update or Google Jobs bug?

I want to be transparent about my own reasoning here, because I changed my mind while writing this.

Two weeks ago, I believed the traffic drops were the spam update. The timing fit: the update completed on August 21, and the sites I look at started sliding right after. That is also the default explanation every SEO reaches for when a confirmed update and a traffic drop are two days apart.

Here is why I no longer think the spam update alone explains it (it might be still related, but not the full explanation).

A spam update is a ranking system. It demotes sites, sometimes brutally, but it does not make "jobs posted since yesterday" return zero results in Barcelona, New York and Chicago for everyone at the same time. Rankings do not produce an empty result set for an entire city. And if your drop is concentrated on job pages while your category pages are stable (which I can confirm for most hit sites), that is the opposite of what a spam update targeting programmatic content would do.

Still, there is a small but. I would not rule the spam update out either, just not in the way we usually think about it. Spam updates are not only ranking changes. They are also the moment Google cleans up its systems: it throws out inventory that its classifiers flag, tightens what gets in, and reprocesses what is already there. If Google used this update to run a cleanup of the Jobs index, purging expired and duplicate listings and raising the bar for what gets admitted, then a stale index with new jobs trickling in slowly is exactly what the aftermath of that cleanup would look like. Reports of Job Boards getting completely flushed from the index explain this. 

So the two explanations are not competing. My current working theory is that the spam update kicked off a cleanup of the Jobs system, and that cleanup, or something that shipped with it, is what broke freshness. Whether the ranking part of the update also cost your site something on top is a separate question. If you are trying to separate the two on your own site, split your data by page type and by date. Ranking effects show up across page types and start on August 18 or 19. The freshness problem shows up on job pages only and starts around August 28.

So what is actually broken?

I don't have inside information, and Google isn't talking, so treat everything below as hypotheses.

All the symptoms point to the same component. Jobs older than three days are searchable. Jobs from the last one to three days are missing or appear hours late. Posting-age labels disappeared from some listings, as commenters on Barry's article noticed. Email alerts stopped, and when they came back they delivered two-week-old jobs as "new". That is one pipeline: the part that takes newly discovered JobPosting markup, assigns a datePosted, and adds the job to the Jobs index. If that step is slow or failing intermittently, you get exactly this picture: old inventory intact, fresh inventory missing, alerts silent, and results that appear and disappear depending on when the last batch made it through.

This isn't a crawling problem in the classic sense, and it isn't a structured data problem on your side either, because it affects everybody at the same time.

Barry's note about a similar time-filter bug in regular search and news in August is relevant here. If Google shipped something in August that changed how dates are processed or how time filters are evaluated, a jobs index that lives and dies by datePosted and validThrough would be the first place you notice it. I am speculating, but it is the most economical explanation I can come up with.

What I can rule out with some confidence: this is not a penalty, not a policy change against job boards, and not something a markup fix on your side will solve. Also, it's not a sign that Google Jobs is dying, because if it were, they would just turn off the feature, and we wouldn't see new jobs. It seems that something in the ingestion is still working.

What happened the last two times

This isn't the first time Google Jobs has gone dark, and that history helps set expectations.

In 2024, Google tested a new Google Jobs UX starting in January and rolled it out over the summer. Multiple job boards with high domain authority reported that their Google Jobs traffic completely dried up for two to three weeks, paired with a drop in crawl requests. After the launch, traffic came back, but not at the same level for every site, and some never fully recovered. I still have the charts in my logs.

In August 2025, I received reports from four large job sites that Googlebot either stopped visiting their job pages or reduced crawling sharply between August 20 and 21, with 20 to 30% week-over-week traffic losses on job pages only. I wrote about it at the time in Google Jobs Issues in August 2025?. No confirmation from Google, no dashboard entry, and then it quietly went back to normal.

Funny enough, all three incidents happened in the second half of August. Make of that what you want (I am not making anything of it, but it is a nice pattern).

Maybe the one person left at Google that handles Google Jobs went on holiday? 

Here is the practical takeaway from both episodes: once Google fixes whatever is broken on their side, traffic usually normalizes within about a week. The fresh jobs come back, alerts start firing, and the clicks follow. The 2024 episode was the exception at two to three weeks, and that one came with a full UX change. If the September 12 recovery reports are the real thing and not another flap, I would expect to see this in the Search Console data of most sites by the end of next week. If we are still seeing empty "since yesterday" results in two weeks, something bigger is going on.

But hopefully, once they fix it, they also fix the Index API approval. 

What to do while you wait

Not much, and that is the point. Every time this happens, I see job boards panic and start changing things: rewriting JobPosting markup, changing URL structures, resubmitting the entire job inventory through the Indexing API. Do not do that. You will not fix a Google-side pipeline problem from your side, and you will burn Indexing API quota you may need later.

What is worth doing is documenting. Note the dates: spam update August 18 to 21, first freshness reports around August 28, your own drop date. Pull the Job listing and Job details search appearance data before and after. Run "[occupation] jobs [your city] since yesterday" once a day in your main markets and take a screenshot. It is the cheapest monitoring you will ever set up, and it gives you a paper trail for conversations with management or employers about why applications from Google are down.

Or better yet – check out my Google Monitoring product which will take care of this for you. 

Some speculation to finish

Here is what I think, with the caveat that I have been wrong about Google's intentions before.

Google Jobs has a habit of breaking right before something changes. The 2024 outage came with the new UX. The Job Sites feature started showing up above Google Jobs in tests this year. Since October 2025, Google has stopped approving Indexing API quota increases, and I wrote in July about 50+ applications from new job boards with zero approvals, which I read as either a reaction to API abuse or a cleanup of the Jobs dataset ahead of something new (Google Indexing API Quota Freeze: What Job Boards Should Do). Manual actions on expired jobs also increased over the summer.

A couple of additional observations: I do see a lot of AI overviews triggered on top of transactional keywords related to job search. Maybe this update does that exactly. It rolled out a wider AI overview system for job search? 

I could be reading too much into a bug. But a quota freeze, a cleanup of expired jobs, AI Mode serving a lot of category pages and an unexplained outage of the classic Jobs index, all within twelve months, is a lot of coincidence for a feature that Google has barely touched since 2017.

If that reading is right, the freshness issue gets fixed once the migration is done, and, who knows, maybe we finally see Indexing API quota requests being approved again afterwards. I would settle for that.

If you are seeing the same behavior on your job board, or if your traffic has already recovered, send me your charts or join the LinkedIn discussion. I will update this post as the situation develops.

If you like this content, subscribe to my blog and be the first to know about all the latest topics in Google Jobs and Job Boards SEO.

External Links referenced:

Search Engine Roundtable, Sep 4: https://www.seroundtable.com/google-job-search-bug-42022.html

r/jobsearchhacks thread: https://www.reddit.com/r/jobsearchhacks/comments/1w3rc72/google_jobs_feed_drying_up/

r/TechSEO thread: https://www.reddit.com/r/TechSEO/comments/1vzu6mz/job_listings_moving_to_crawled_not_currently/

r/RecruitmentAgencies: https://www.reddit.com/r/RecruitmentAgencies/comments/1weihnl/whats_up_with_google_jobs/

Google Search Status Dashboard (spam update, Aug 18 to 21): https://status.search.google.com/summary

SerpApi status: https://status.serpapi.com/ and incident https://status.serpapi.com/incidents/f3wg5788kmb1