A status code alone doesn’t prove a page works. Error pages, empty product lists, maintenance notices and a hacked page can all be served with HTTP 200. A keyword such as “Add to cart” that only appears when the page works, or an error text that must not appear, turns those into failures.
Pick text that is stable and specific: a button label, a product name, a line in the footer rendered by the application. Avoid text that changes with A/B tests, prices or language.
Keyword checks read the HTML the server returns. Text added later by JavaScript in the browser isn’t in it; check that with a browser-based synthetic check instead.