Skip to main content
A scan checks a store’s catalog and storefront signals, then turns findings into issues that teams can review and resolve. Issues are the primary review surface in Atlios. They help teams focus on the catalog work that needs attention, including missing data, invalid values, duplicate identifiers, weak image metadata, and live-page findings such as a product page that cannot be reached or is blocked from indexing. Storefront verification also confirms a fix on the rendered page after a meta title or meta description fix applies. Those two fields are the whole rendered-page confirmation scope. Other fix types are confirmed against Shopify, not against the page.

​
Scan coverage

A scan checks product data, variant data, cross-product conflicts, and product images. It does not fetch your live product pages: those are read separately, after Atlios applies a meta title or meta description fix. Coverage can expand over time as new quality rules are added.

​
Issue review

Each issue should answer three questions:
  • What is wrong or worth reviewing?
  • Which product, variant, or storefront page is affected?
  • What action should the team take next?

​
Issue sources

Most issues come from catalog scans. If you connect Google Merchant Center, Google’s product disapprovals and account warnings appear in the same inbox, prefixed GMC:. Filter by rule to focus on one source. When the scan and Google flag the same field on the same product, Atlios merges them into one issue that carries both source badges. It counts once, and resolving it clears both signals.

​
Suppression

Some issues are valid exceptions for a specific store or product. Suppression lets teams intentionally quiet those issues without losing scan history.