Google’s Indexing API (a tool that tells Googlebot to crawl specific URLs faster than a standard sitemap) requires separate approval before job boards can use it at meaningful scale. In 2026, that approval process appears to have stalled. SEO consultant Nick LeRoy and job board consultant Alexander Chukovski report that over 100 job boards have submitted requests and received no response, no rejection, and no timeline from Google.
What Is the Indexing API and Why Do Job Boards Need It?
Google’s own job posting documentation recommends the Indexing API over sitemaps for job posting URLs, stating it “prompts Googlebot to crawl your page sooner.” For job boards, where listings are posted and expire within days or weeks, faster indexing directly determines whether a posting appears in search results while it is still live.
The API comes with a default quota of 200 requests, which Google describes as intended for “onboarding and submission testing.” To use it beyond that limit, operators must submit a Google Form requesting additional quota. The quota page states the “quota may increase or decrease based on the document quality,” but does not describe the review process, a typical wait time, or any way to check request status.
How Long Have Job Boards Been Waiting?
Reports of unanswered requests date to at least May 2026. In a September 19 thread on X, LeRoy stated he and Chukovski have “100+ job boards as data points” and “hypothesize that Google hasn’t approved any submissions in 2026.” Both have been open that this is a hypothesis, not confirmed internal data.
- LeRoy, July 2026 newsletter: Resubmitted requests for SEOJobs.com and PPCJobs.com six months earlier. “Not an approval. Not a rejection. Not a request for more information.”
- Chukovski, July 2026: Had “visibility over at least 50 different applications” since October 2025, none approved. He stated he has no inside information at Google.
- May 22, 2026, Google Search Central Community: An operator reported submitting the form multiple times over six to nine months with no response and no change to their default quota.
- September 2, 2026, forum: An operator said they received no acknowledgment, no reference number, and no visible status on their request.
- September 8, 2026, forum: Another job board reported the same outcome.
- September 10, 2026, forum: A Belgian job board reported that a request submitted on August 21 had received no approval or rejection.
Search Engine Journal contacted Google with specific questions: whether job site requests are being actively reviewed, typical review timelines, how applicants can check status, and whether requests submitted before approval are handled differently. As of publication, Google had not responded.
What Does Google Say Officially?
Google’s John Mueller responded in May 2026 after LeRoy raised the issue on Bluesky: “I’m not aware of any particular issues, but I know the indexing API is inundated by bloggers trying to act like legitimate sites, so I imagine they’re just a bit more cautious nowadays.” His reply did not describe the current review process or any approval backlog.
Google updated its Indexing API documentation on September 4, 2024, clarifying in its changelog that the default quota is “for initial setup and testing.” A spam warning was added to the API quickstart on September 11, 2024. According to Search Engine Journal, any future change to the approval process would most likely appear first on the Indexing API quota page or in the documentation changelog, where the 2024 clarification was logged.
A Google Diamond Product Expert, a volunteer role and not official Google staff, told one September 10 forum poster that a 404 response from the getMetadata endpoint (a follow-up call used to verify whether Google recorded a crawl notification) is “a strong sign the project hasn’t been approved.” That is not an official Google statement.
What Is the HTTP 200 / 404 Pattern Operators Are Reporting?
Multiple operators, including LeRoy in July 2026 and forum posters from September 2 and September 10, describe the same sequence: a publish request to the Indexing API returns HTTP 200 (meaning the server received the request), but a follow-up call to the getMetadata endpoint for the same URL returns 404 (meaning Google has no record of receiving a notification for that URL).
Google’s usage documentation states that HTTP 200 “means that Google may try to recrawl this URL soon” and that the getMetadata endpoint shows “the last time [Google] received a notification for a URL.” The documentation does not clarify whether requests submitted before approval are processed differently. The Belgian job board, per Search Engine Journal, observed the same 200/404 pattern across two entirely separate technical setups, which reduces the likelihood this is a local configuration error.
What This Means for AI-Search Visibility
The plain-language version: if your job board is waiting on Indexing API approval, Google may be silently discarding your crawl requests while the HTTP response codes suggest everything worked.
Think of it like mailing a package and receiving a delivery confirmation, but the recipient’s mailbox is full and nothing actually arrived. The HTTP 200 says “sent.” The 404 from getMetadata says “never recorded.” For a job listing that expires in 72 hours, that gap means the posting may never appear in search results while it is still actionable.
The compounding issue for AI-search visibility is this: AI answer engines, including Google’s AI Overviews and third-party AI tools that retrieve live web content, draw from what is indexed. A job posting that never gets properly crawled and indexed never enters the content pool those systems query. The Indexing API’s original purpose, to accelerate crawl time compared to sitemaps, was precisely the feature that made it valuable for time-sensitive content.
Two observations are worth noting here, beyond what the sources report directly. First, the documentation disconnect is the more serious structural problem. Google’s job posting guide actively directs operators toward the Indexing API for faster indexing while the approval process for using it at scale has no visible queue, no status system, and no feedback loop. Operators are being steered toward a tool they cannot fully use without knowing it. Second, Mueller’s characterization of the applicant pool as flooded with “bloggers trying to act like legitimate sites” suggests Google is applying broad caution across all applicants. That may be a reasonable anti-spam measure. But from the outside, a blanket slowdown with no communication is indistinguishable from a broken process. Those are different problems and they require different responses from Google.
Until Google clarifies the approval status, the most reliable fallback remains what its own job posting guide still recommends alongside the API: submit a sitemap with accurate lastmod timestamps. It is slower, but it is a known, documented quantity.
What to Check Before Relying on the Indexing API for Job Postings
- Check your project’s current quota in the Google API Console to see whether you are still on the 200-request testing limit or have received an increase.
- After each publish request that returns HTTP 200, immediately follow up with a getMetadata call for the same URL to confirm Google recorded the notification (a 404 response here is a warning sign).
- Use the URL Inspection tool in Google Search Console to verify whether Google has actually crawled and indexed the page after your API call.
- Submit a sitemap with accurate lastmod dates as a parallel fallback, as Google’s job posting guide recommends alongside the API.
- Check the Google Search Central Community threads for whether your response pattern matches what other job boards are reporting.
- Monitor Google’s Indexing API documentation changelog (developers.google.com) for any updates to the quota or approval pages, where the 2024 clarification was logged.
What to Watch Next
According to Search Engine Journal, if Google updates its approval process, the change would most likely appear first on the Indexing API quota page or in the documentation changelog. LeRoy and Chukovski have indicated they will continue tracking outcomes across their combined dataset of over 100 job boards. Whether the silence reflects a longer-than-normal review queue or a structural pause in approvals is still unknown without a statement from Google.
Lam Nguyen · Hingewise
Sources:
Search Engine Journal, September 19, 2026: Job Boards Say Google Indexing API Requests Get No Response
Google Search Developers, Job Posting Structured Data Guide: developers.google.com
This article was drafted with AI assistance from the sources cited above and checked against them before publishing. The "What this means for AI-search visibility" section is Hingewise's editorial analysis, built on the frameworks and positions we use in our GEO work. How we work: Editorial policy.