This tutorial shows how to turn Target product detail URLs into a reviewable CSV with product names, descriptions, category levels, prices, unit pricing, and image URLs. Import the Target Product Details Scraper template, replace the sample URLs, choose an export folder, and validate the first rows before scaling.
Plan the run
Target product data scraping prerequisites
Start with an approved list of product detail URLs. The workflow is not a category crawler; it expects pages where one product is the main subject. If you need URL discovery first, collect links separately and feed final detail URLs into this scraper.
You also need UScraper, a stable network connection, and a destination folder. If price or availability matters, set the store or ZIP context in the browser profile and document it beside your export.
Treat this like an internal data collection procedure, not a blind bulk download. Keep volume modest, pace requests respectfully, review Target terms and robots guidance, and get legal approval before using scraped product data in commercial workflows.
Workflow map
How the Target product details scraper works
The bundled JSON defines a page-by-page loop: set the viewport, navigate to a URL, wait, confirm the body exists, inject JavaScript, export structured columns, then continue.
| Workflow stage | What to check | Why it matters |
|---|---|---|
| Navigate | Product detail URLs in the Navigate block | The scraper works best when each URL is a real Target product page. |
| Wait and sleep | Page-load timeout and short delay | Product data can hydrate after the first document load event. |
| Inject JavaScript | Product JSON-LD, visible text, breadcrumbs, images, and price helpers | The script tries stable sources first, then falls back to visible page content. |
| Structured Export | Column list and save location | This is where CSV names, append mode, and folder path are controlled. |
| Loop Continue | One URL per iteration | Keeps multi-URL runs predictable and easier to debug. |
Use UScraper when you want editable blocks, local CSV output, and a workflow analysts can inspect without writing a scraper. The template exposes waits, URL input, extraction logic, file name, append mode, and columns in one graph.
Runbook
Export Target product details to CSV
Import the template
Open Target Product Details Scraper, download the JSON template, and import it into UScraper. Confirm that Navigate, wait blocks, Inject JavaScript, Structured Export, and Loop Continue appear.
Replace the sample URLs
In the Navigate block, replace the sample values with your own Target product detail URLs. Keep the first test to two or three products so missing selectors are easy to diagnose.
Set the export path
Open Structured Export, choose the folder where reports should land, and keep the default target-product-scraper.csv name unless you need a dated batch file.
Run a dry test
Start the workflow, wait for the browser to finish each product page, then open the CSV and compare each row against the rendered page.
Scale cautiously
Once names, descriptions, prices, categories, images, and unit pricing are correct, add URLs in small batches. Save a copy before editing extraction logic.
target-product-scraper.csvColumn
PruductName
Product title from the page, product JSON-LD, or fallback data.
Column
ProductDescription
Cleaned product description or meta description.
Column
Category1-Category4
Breadcrumb levels for product category context.
Column
ProductPricing
Visible price or offer price when available.
Column
Img1-Img5
Primary and supporting product image URLs.
Column
Unit_Pricing
Unit price such as price per ounce when exposed.
Sample rows
1 of many
| PruductName | ProductDescription | Category1-Category4 | ProductPricing | Img1-Img5 | Unit_Pricing |
|---|---|---|---|---|---|
| Baby-Cut Carrots - 1lb - Good & Gather | No fridge is complete without Baby-Cut Carrots from Good & Gather. | Grocery / Produce / Fresh Vegetables | $1.39 | ... | $0.09/ounce |
Quality checks
Validate product data before reporting
Do not judge the workflow by row count alone. Open five exported rows and compare them with live pages. Product name and price should be exact enough for analysis, category levels should match breadcrumbs, and image URLs should resolve.
If prices are business-critical, rerun under the expected store context. If descriptions matter, check that detail text is not clipped by a collapsed section. If images matter, confirm that Img1 is the primary image rather than a thumbnail or social preview.
| Symptom | Likely cause | Fix |
|---|---|---|
| Blank product name | Page failed to render or selector drifted | Increase wait time, inspect h1, and test JSON-LD extraction. |
| Price differs from a manual check | Store, delivery, or session context changed | Set the same store context, then rerun a small sample. |
| Image fields repeat | Page exposes the same image through several meta and image tags | Deduplicate URLs downstream or adjust the image collection logic. |
| Category columns are empty | Breadcrumb markup changed or is hidden | Re-map breadcrumb selectors before scaling. |
Tool choice
Target scraper API alternative or local desktop workflow?
Choose the tool based on the job. A hosted Target scraper API is usually better for scheduled pipelines, strict JSON contracts, proxy management, or engineering-owned ingestion. A visual cloud scraper can be better when projects already live in Octoparse or an actor queue.
UScraper is strongest when the deliverable is a CSV your team can inspect today. You can see every block, tune waits, edit export columns, and keep the output folder under your control before investing in a dedicated API integration.
Import the template, run a short URL list, and review the CSV locally. This avoids building a crawler for a report that may only run once.
Use a hosted API or actor when queue management, monitoring, retries, and service contracts matter more than local workflow control.
Every DOM-based approach needs maintenance. UScraper keeps that maintenance visible in the workflow graph; hosted providers absorb more of it but limit direct control.
Structured Export writes to your configured folder, which is useful for analysts who need a transparent local file before loading data into BI or spreadsheets.
Frequently asked questions
Target product pages can be public, but automated collection may still be restricted by Target terms, robots directives, copyright, consumer protection rules, and local law. Keep runs low volume, avoid private or restricted data, do not bypass access controls, and get legal review before commercial use.
You can also browse the UScraper template library or read more tutorials in the UScraper blog.