What it is
A rules-based catalog check that normalizes a representative sample, flags source-data problems, tests the selected output format separately, and identifies mapping inputs that need merchant review.
Catalog Scanner
Find the catalog gaps that make products harder to compare.
Incomplete product codes, prices, stock, descriptions, attributes, or product grouping can give AI search tools and shopping agents an unreliable picture. Upload a representative catalog file; the free scanner separates source-data defects from problems with the selected output, flags anything inferred, and points to the right cleanup path. A converted file alone does not prove full AI-commerce readiness.
Paid report
$150 USD$99 USD
Use code LAUNCH99 at checkout for $51 USD off the $150 USD standard price; the paid Catalog Scanner report is $99 USD.
The free scanner preview remains free.
For merchants with a product export, catalog sample, or API response ready to check.
Service code: AP-CATALOG-SCANNER · Brand: Autonomous Path · Availability: available online
Sold by Autonomous Path. This is a digitally delivered service. Review our delivery and refund policy and terms.
What it solves
Missing descriptions, weak descriptive-attribute coverage, broken product grouping, or invalid, duplicate, or inferred product codes, prices, and stock can make products harder for AI search tools and shopping agents to identify and compare. Catalog Scanner shows whether the problem starts in the source record, a mapping input, or the selected output before the same gap spreads into more channels.
Who it is for
Merchants who already have a feed export, product file, API payload, or catalog sample they want checked.
Deliverables
- Normalized sample assessment
- Missing, invalid, duplicate, and inferred values grouped by severity
- Mapping-prep notes for descriptions, categories, attributes, provided metafields, and grouping in the submitted sample
- Optional PDF issue register and cleanup order
- Recommendation for catalog cleanup, storefront scanning, or no paid work yet
What is not included
- Silent unsupported value filling
- Claims that one converted feed equals full readiness
- Storefront theme fixes or custom protocol implementation by default
Timeline
Starts
Report packaging starts after checkoutExpected result
PDF access expected within one dayCatalog Scanner uses the saved rules-based catalog result rather than making you wait on a manual audit queue. Most reports are available shortly after payment confirmation; the one-day window covers payment sync and delivery buffer.
- Rules-based catalog result is rebuilt from saved source evidence
- PDF findings report is attached to the account
- Download access appears after payment confirmation
- Inferred values and unsupported gaps remain clearly flagged
Questions about timing or delivery? Email support@autonomouspath.ai.
Launch version
The sequence can start two ways: run the free Catalog Scanner preview first, or go straight to the paid Catalog Scanner report when you already have a source catalog ready. Either path keeps the report tied to catalog evidence before cleanup scope starts.
Fix the confirmed problem. Keep the claim narrow.
This work addresses the pages, product data, or setup described in scope. It cannot promise how a third-party platform will rank, approve, activate, accept, or display the store.
Sample full report
See how product file problems are prioritized.
Open the current sample to see each catalog problem found, why it is a problem, how to fix it, and how to verify the cleanup.
Current ruleset
Problem groups
Source records
Fix verification
- Current source-record, normalization, rejection, target-failure, and inferred-value counts.
- Recurring problems with the affected product codes or file entries and the business consequence.
- Source-owned cleanup steps plus a specific scanner rerun or target check for verification.
- Recommended cleanup order and clear limits on what the report proves.
Sample data is illustrative. A paid Catalog Scanner report documents the submitted product file and selected-format checks only; it does not connect to an account, change products, guarantee Merchant Center acceptance, or prove full store readiness.
How the steps fit
Bring the catalog file first. Buy deeper detail only when you need it.
The free scanner shows the main issue categories. The paid report adds a saved issue register and cleanup order. Remediation begins only after the affected records are known.
Scan the storefront when the weak layer is unknown.
Site Scanner samples product, policy, and company pages and compares visible details with structured data and catalog basics.
- Use it when the issue could be page access, content, schema, policies, or product data.
- See what the scan verified and which pages it could not reach.
- Get one priority issue without choosing a protocol.
Check the product file when the catalog is already suspect.
Upload or paste a representative sample to find missing fields, invalid values, inferred data, missing or target-invalid descriptions, absent descriptive attributes, variant grouping, and mapping-prep needs.
- Best when a feed export, Merchant Center sample, or catalog file is already in hand.
- Checks source records, submitted content and mapping inputs, and selected-format failures separately.
- Keeps catalog findings separate from storefront and policy claims.
Buy deeper detail or scope the repair.
The paid report lists affected URLs or records and preserves the fix order. Use remediation only when the scanner has already located the problem.
- Site Scanner for broader storefront coverage and paid report delivery.
- Catalog Scanner for a saved PDF issue register before catalog cleanup.
- AI Search Remediation follows confirmed site findings; Catalog Remediation follows confirmed catalog findings or approved mapping-prep evidence; monitoring follows a clear baseline.
Proof point
A sample result from a realistic messy export.
The sample contains product records that need cleanup.
This proof card is based on the repo's realistic `messy-merchant-export.csv` fixture against the Google catalog-readiness check. It shows the kind of rules-based output Catalog Scanner surfaces before any paid Catalog Scanner report scope is proposed.
The file parses, but several records still need work.
- Source rows are normalized into a shared canonical product shape
- Target checks are kept separate from source-catalog lint findings
- Inferred values and rejected rows remain visible for review
- Results identify the checked target profile without claiming platform acceptance
The result stays tied to the catalog file.
- Typical issues include missing or invalid image URLs, inferred values, identifiers, and price cleanup.
- Recommended next service: Catalog Scanner.
- Guardrail: this sample does not claim Merchant Center approval or broader AI search readiness.