Application (non-public) part of the site - SEO content checks

The same as SIT-05, just in the SEO module. Classifying a page as an application (non-public) part of the site is done EXCLUSIVELY by the rule engine (SIT-05) - the SEO module has its own, independent HTML extraction and performs no second classification. This check only reads that result and merges the SEO findings of the same page accordingly.

On a page that SIT-05 flagged, the following merge into this single finding: a missing title (SEO-01), a missing meta description (SEO-02), a missing or unreachable sharing preview (SEO-06), images without alt text or dimensions (SEO-10), a missing mobile viewport setting (SEO-11), an invalid lang attribute (SEO-14), and images in an outdated format or without loading="lazy" (SEO-37, SEO-38).

What the check does not do:

• Does not classify pages again. It only reads what SIT-05 already decided - see that page for the full reasoning behind the four signals.
• Does not merge redirects, canonical, security headers or performance (SEO-04, SEO-09, SEO-13, SEO-30…33, SEO-20/SEO-21) - those are technical checks that stay unchanged on an application page.
• Does not appear on a page the SEO module never analysed - typically when the module runs standalone over a subset of pages.

Same reasoning as SIT-05: this is not a recommendation, so there is nothing to document an effect on AI or on classic search for. It is information that SEO content checks are not evaluated on this page, because its content is typically managed by the application, not by you.

Splitting this into SIT-05 and SEO-39 (two codes instead of one) mirrors how the product is built: the rule engine and the SEO module have separate check registries, separate scores and separate clear-and-replace on rerun (config/scoring.json). Merging them into one code across both modules would mean touching both architectures for no added benefit - the customer sees both cards side by side in their respective chapters (AI readiness, SEO) and both say the same thing in one breath.

The procedure is the same as for SIT-05: first check in a private browser window whether the page really looks like an application part. If so, there is nothing to do. If it is meant to be public and the classification is a mistake (typically because of noindex), remove it and run the audit again - the SEO content checks will then apply here too.