moai-ref-seo

Fetch each route's canonical declaration and confirm it returns that same page with no redirect in between. The declared value must equal the address actually served, and trailing-slash or parameter variants should redirect permanently to one chosen form.

Derive types from the page's actual role, emit each type's mandatory core fields completely, and use absolute resolving addresses. Every claim in the serialized data needs a visible counterpart on the same page, since unverifiable assertions are scored as negative signals.

No. Derive the absolute addresses in robots.txt from the incoming request's host so every environment describes itself correctly, and generate the sitemap from the routes actually served. A hardcoded host is correct in exactly one environment and wrong everywhere else.

No. Keyboard operability, focus indicators, and form labeling are delegated to the accessibility surface, and generative-engine optimization is deliberately excluded as insufficiently settled. This reference stays at the protocol and output layer: addresses, headers, markup, and serialized data.

Uniqueness is the entire purpose of per-page metadata, so a scaffold default reused on every route defeats it. Collect titles and descriptions across all routes before shipping and fail the check if duplicates or placeholder strings survive.