Start with your deployed store
Your public interface, catalog backend and checkout may be separate. Document their contracts before choosing protocols.
Where the decision gets specific
A visually complete page may expose little useful static HTML, while a separate feed is accurate and healthy. The L0 scanner can only assess the public sample it receives. Validate authenticated APIs and production transactions through your own approved tools.
Make the audit repeatable
Select a small sample that covers normal products, variants and an unavailable item. Record the exact page, market, time and expected values. Run the public check, then compare its findings with your own authoritative records. For each issue, identify whether the repair belongs in source data, a template, a mapping or an account setting. Preserve the report before making changes so that the next check measures a real difference.
What public evidence cannot establish
The L0 scanner cannot inspect private feed acceptance, authenticated account configuration, payment authority or completed orders. A blocked page is not proof of a missing capability. Confirm those questions through official merchant tools and scoped provider documentation. Treat any suggested candidate as a capability to investigate, not a ready-made endorsement.