200 200 OK

The request succeeded and the server returned the requested resource.

When you'll see it

Any normal successful request: a page that loads, an image that downloads, an API call that returns data. It's what you want from every public page.

That the page really has its content. A 200 on an error or empty page is a soft 404, and search engines may treat it as one.
That the canonical URL itself answers 200 directly, without a redirect first.
That the Content-Type matches what the page actually sends.

HTTP/1.1 200 OK
Content-Type: text/html; charset=utf-8
Cache-Control: max-age=300

The ideal status code. Pages returning 200 are crawled and indexed normally.