WebCheck does not parse canonical links or noindex directives. Its required- and forbidden-text checks can look for a chosen phrase in one HTTP response, but they do not validate SEO tags or their meaning.
Why this matters
A deployment can leave a public page reachable while changing how search engines should index or attribute it. A page may still return HTTP 200 even when its canonical link or noindex directive has changed.
What WebCheck can do
You can monitor a public page's HTTP status and ask whether a specific, case-sensitive phrase appears or does not appear in its server response. That can catch a narrow text regression when you know the exact text to check.
It is not a reliable canonical or indexability audit: WebCheck does not extract a <link rel="canonical"> value, interpret robots meta tags or compare an expected directive with the page.
Use the right tool for the scope
Use a crawler when you need to inspect canonical and indexability directives across many URLs, follow internal links or review the wider effect of a deployment. WebCheck is for recurring operational checks on the explicit targets you configure.
Important limitation
A successful HTTP check confirms the configured response conditions for that request. It does not establish that search engines can index the page correctly, or that every URL on the site has the intended canonical.