Job location operators say their requests for endorsement to use Google’s Indexing API are going unanswered for months. Google’s records motionless recommends the API for job posting URLs.
SEO adviser Nick LeRoy, who runs SEOJobs.com and PPCJobs.com, drew new notice to the issue in a Sept. 19 thread on X. LeRoy wrote that neither job commission has been approved or stated a quota increase.
The reports go rear to at smallest May, and three additional appeared in Google’s assistance forum this month. For job sites, endorsement decides whether the API can be used beyond a quota Google describes as for testing. Google’s community Indexing API records does not province a representative endorsement timeframe.
What Job Site Operators Report
In his Sept. 19 thread, LeRoy stated he and job commission adviser Alexander Chukovski have “100+ job boards as data points.” The two “hypothesize that Google hasn’t approved any submissions in 2026,” he wrote.
That is their hypothesis, and LeRoy has been open concerning its limits. In a July matter of his newsletter, he stated he had resubmitted requests for the two sites six months earlier.
“Not an approval. Not a rejection. Not a petition for additional information,” LeRoy wrote. He added, “Can I verify the figure is zero? No.”
Chukovski, who sells SEO consulting to job boards, wrote in July that he had “visibility complete at smallest 50 distinct applications” since October 2025 and that none had gone through. He stated in the identical article that he has no inner information.
Other operators have shared akin delay times in the Google Search Central Community. On May 22, a job commission controller mentioned they had submitted the form multiple times complete the former six to nine months but hadn’t received any reply and motionless faced the default quota. Another job board’s post from September 8 reported the same.
On September 2nd, an controller stated they hadn’t received any acknowledgment, citation number, or apparent position on their request. Similarly, on September 10th, a Belgian job commission shared that a petition submitted on August 21st motionless hadn’t received any endorsement or rejection.
What Google’s Documentation Says
Google’s job posting organized data guide tells location owners to use the Indexing API. It reads:
“For job posting URLs, we propose using the Indexing API alternatively of sitemaps since the Indexing API prompts Googlebot to crawl your leaf sooner.”
That leaf doesn’t citation approval, but the Indexing API quickstart does. It says the API “provides a default 200 quota for API onboarding and submission testing, and it requires additional endorsement for use and asset provisioning.”
Google clarified this on Sept. 4, 2024. Its documentation changelog gives the logic as “to improved explain that the default quota is for first setup and testing.” On Sept. 11, 2024, Google added a spam alert to the quickstart, which I covered at the time.
Site owners petition endorsement through a Google Form connected from the quota page. On how requests are judged, that leaf says lone that the “quota may addition or decrease according to the document quality.”
The quickstart, quota, and use pages depict no way to inspect whether a petition is pending, approved, or rejected. The quota leaf points to the Google API Console, which shows a project’s current quota.
What Google Has Said
Google’s John Mueller responded in May, following LeRoy raised his stalled requests on Bluesky. Mueller replied:
“I’m not conscious of any particular issues, but I cognize the indexing API is inundated by bloggers trying to act akin lawful sites, so I ideate they’re fair a bit additional careful nowadays.”
The answer doesn’t depict the assessment process.
Search Engine Journal inquired alongside Google concerning whether job location requests are being reviewed, how lengthy the assessment procedure normally takes, if applicants can inspect the position of their requests, and whether publish requests are handled alternatively before approval. As of the period of publication, Google had not responded.
What An HTTP 200 Response Means
Google’s Indexing API use page defines an HTTP 200 reply narrowly, saying it “means that Google may try to recrawl this URL soon.”
Several operators study that a publish petition returns HTTP 200, afterward a follow-up call for the identical URL to the getMetadata endpoint returns 404. Google says that endpoint shows the final period it received a notification for a URL. Both the forum posters from September 2 and September 10 mentioned noticing the identical pattern, and the Belgian location saw it through two distinct setups. LeRoy additionally shared akin findings in July.
The use leaf doesn’t explain if requests sent previous to endorsement are treated differently. Google’s errors page provides a generic clarification for 404 errors and doesn’t nexus them to endorsement status.
A Google Diamond Product Expert told the September 10 poster that the 404 was a powerful sign the project hasn’t been approved, and mentioned that the archetypal 200 reply can be helpful for evaluation a setup. Keep in mind, Product Experts are volunteers, not authoritative Google staff, so their insights aren’t authoritative Google statements.
Why This Matters
Google’s job posting guide recommends using the Indexing API as a quicker substitute to sitemaps. The API’s own records says using it beyond evaluation requires additional approval. Operators who have requested admission study waiting months without any response, making it difficult to inform if they are merely in a dilatory queue or have been rejected. The guide additionally motionless recommends submitting a sitemap for complete location coverage.
Looking Ahead
Short of a declaration from Google, a alter to the endorsement procedure would most apt display up archetypal on the Indexing API quota leaf or in Google’s records changelog, anywhere the 2024 clarification was logged.
Featured Image: Sahabzady/Shutterstock
