200 OK

What it means

200 is the normal response for a successful page load or API call. The meaning of the body depends on the request method.

Common causes

• The resource exists and was returned successfully.

How to fix it

1. No fix needed.
2. If an error page returns 200, change it to the correct 4xx or 5xx code.

Example response

HTTP/1.1 200 OK
Content-Type: text/plain; charset=utf-8

Worked example

A client submits a valid request and receives this successful response. It should follow the code's semantics: use the returned content when present, or rely on headers and avoid parsing a body when the response promises none.

How to read this response

1. Find the status line in your browser's Network panel, API client, or server access log.
2. Read the response body and headers shown above; headers such as Location, Allow, Retry-After, and WWW-Authenticate explain the next step.
3. Use the code's class to orient your diagnosis: informational, successful, redirected, request-related, or server-side.

SEO impact

Only real, indexable pages should return 200. Error pages that return 200 are treated as soft 404s by search engines.

How to check a status code

Enter a URL in the HTTP Status Checker to see its status code, every redirect hop, and response time. For redirect-heavy pages, the Website Speed Test shows how much time redirects add.

Frequently asked questions

What it means: HTTP 200

200 OK: The request succeeded and the response contains the requested content.

Common causes: 200

The resource exists and was returned successfully.

How to fix it: HTTP 200

No fix needed. If an error page returns 200, change it to the correct 4xx or 5xx code.

Tools