Product sitemap
Use an approved sitemap as the inventory discovery surface.
When to use it
A practical fit for your existing workflow.
Large stores whose product URLs are complete in XML sitemaps but whose offer data must be read from product pages.
Input contract
Fields and structure
Use stable field names and meanings across every refresh. Legend normalizes the values, but the source contract should not drift silently.
Required or expected
XML urlset or sitemapindexCanonical product URLsStable hostAccessible lastmod values where available
Recommended fields
loclastmodchangefreqnested sitemap locations
Supported variations
- Several product sitemaps
- Category-specific sitemap partitions
- Incremental discovery from lastmod
- Removal detection
Copyable example
Product sitemap
Replace the demonstration values with your own catalogue data. No customer, order, or payment data belongs in an inventory feed.
XML
<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
<url>
<loc>https://merchant.example/products/demo-001</loc>
<lastmod>2026-07-20</lastmod>
</url>
</urlset>From source to live offer
Connection workflow
Every route uses the same quality gates before an offer becomes public.
Approve the merchant domain and sitemap scope.
Read canonical product URLs and modification hints.
Extract offer data only from approved product pages.
Track additions, removals, stale pages, and parser failures.
Before publication
Validation checklist
These checks keep bad prices, stale stock, and uncertain product matches out of the public marketplace.
- This connector is planned and not yet self-service.
- URLs must remain on approved hosts.
- A sitemap discovers pages; it does not replace offer validation.
- Robots, rate limits, and source access rules remain authoritative.
Other connection paths