# 202 Accepted: received now, processed later

> 202 Accepted means the server received the request and queued it for processing, but the work is not finished and may never complete.

URL: https://yes-seo.com/http-status-codes/202

**202 Accepted** means the server has received the request and queued it, but hasn’t finished the work, and may never complete it. It’s the standard response for asynchronous jobs: “got it, check back later.”

## Definition

[RFC 9110, section 15.3.3](https://www.rfc-editor.org/rfc/rfc9110#section-15.3.3) calls 202 “intentionally noncommittal.” The request has been accepted for processing, the outcome is unknown, and HTTP has no built-in way to report back later. So the response should describe the current state and, ideally, link to a status resource the client can poll:

```
HTTP/1.1 202 Accepted
Location: /api/v1/jobs/7731
Content-Type: application/json

{"job":7731,"state":"queued","status_url":"/api/v1/jobs/7731"}
```

## Where you’ll see it

- Batch work: exports, imports, video encoding, bulk email sends.

- Webhooks and event APIs that acknowledge receipt at once and process later.

- **IndexNow**: a 202 means the URLs were received but the key is still being validated; once your key file is confirmed, submissions normally get 200.

- Long-running requests behind proxies: instead of timing out with [504](https://yes-seo.com/http-status-codes/504) or Cloudflare’s [524](https://yes-seo.com/http-status-codes/524), return 202 and finish the job in the background.

## SEO impact

[Google’s documentation](https://developers.google.com/search/docs/crawling-indexing/http-network-errors) treats 202 like 201: Googlebot waits for content for a limited time, then passes on whatever it received. A public page that answers 202 with a “processing…” placeholder risks being indexed as that placeholder or flagged as a soft 404. Some bot-protection layers also answer suspicious clients with a 202 and a challenge page instead of the content; if that catches crawlers, your real pages never reach the index. Public pages should return [200](https://yes-seo.com/http-status-codes/200) with the full content.

## How to check

Paste URLs into the [HTTP status checker](https://yes-seo.com/http-status-checker) to make sure your pages return 200, not 202. For IndexNow, the [IndexNow submitter](https://yes-seo.com/indexnow-submitter) lets you verify that your key file is reachable on your site, which is what IndexNow validates, before you submit URLs.

## Frequently asked questions

### Does 202 mean my request succeeded?

Only that it was accepted for processing. The work may still fail later, so check the status URL or job ID the server returned.

### Why did IndexNow return 202?

IndexNow uses 202 to say it received your URLs but is still validating your key. Make sure the key file is reachable at your site; later submissions should then return 200.

### Is a 202 bad for SEO?

On API endpoints it’s irrelevant. On public pages it is a problem: Google waits only briefly for content and may index a placeholder or treat it as a soft 404. Pages should return 200.