Sitemap scraping extracts page URLs from a website's XML sitemap into a table. It gives you a starting inventory for metadata checks, product research, or a later page-extraction workflow; it does not fetch the content of every listed page.
A site may publish a sitemap directly or a sitemap index that points to several sitemap files. Use the actual sitemap URL exposed by the site instead of assuming every website uses the same path.
What the list tells you
The Sitemaps protocol distinguishes a page URL entry from an index entry pointing to another sitemap. A page entry can include a last-modified value, but that field is optional and supplied by the website.
In Datablist, Sitemap Scraper returns Page Url and Page Last Modified when available. A missing timestamp is not an error by itself. A supplied date is not proof that the page's product price, company details, or other fields changed on that date.
For a redesign audit, use the outdated-website checklist to inspect actual page problems. Neither a sitemap timestamp nor an old footer is enough to decide that a website needs replacing.
An illustrative product inventory might contain one URL with a last-modified date and another with an empty date. Both still need page-level checks before being treated as usable product records. Keep the original URL and collection time alongside any later extracted fields.
Configure a bounded import
Create a collection and choose Sitemap Scraper from the source catalog. Paste the sitemap or index address into Sitemap URL. For an index, the source follows the linked sitemap files.
Use Regex Filter when you need only a particular URL pattern. For example, /products/ matches that segment where it occurs in a URL. Test the pattern against known wanted and unwanted URLs, especially when categories, locales, or query parameters share similar paths.
Set Limit for the batch you intend to inspect, map the output properties, and run the import. A configured limit bounds the import; it does not certify that the resulting collection contains every page on the site. Check current source usage and credit requirements before starting.
Review the imported URLs
Compare a sample with the website. Look for repeated URLs, redirected pages, unwanted languages, non-product pages, and fetch failures. An XML download failure and a successful import with no matching URLs need different investigations: check access and file format for the former, then the filter and sitemap contents for the latter.
Do not remove URL parameters blindly. They can distinguish variants or versions. Decide what one record represents before deduplicating the inventory.
Extract page data as a separate step
For titles and descriptions, run Fetch Meta Data from URLs on the existing URL rows. For custom product or company fields, use an enrichment such as AI Agent with the page URL mapped in its prompt and explicit expected outputs.
A source creates rows from source settings; an enrichment processes rows you already have. AI Agent - Site Scraper is appropriate for generating records from a listing page, rather than automatically inspecting every sitemap URL in your collection.
Export accepted URLs, extracted fields, and unresolved outcomes together. If the site has no usable sitemap, Google search scraping may provide candidate pages, but it also needs coverage checks. See cleaning web-scraping data before downstream use.