<?xml version="1.0" encoding="UTF-8"?>
<response><data><post><id>167</id><slug>extracting-json-ld-from-product-pages-part-9-167</slug><title>Extracting JSON-LD from product pages, part 9</title><excerpt>This is part 9 of our series, and this time we focus on edge cases readers asked about. Many product pages already contain a clean, structured description of themselves in a script tag meant for…</excerpt><seriesName>Extracting JSON-LD from product pages</seriesName><seriesPart>9</seriesPart><sections><item><heading>Introduction</heading><paragraphs><item>This is part 9 of our series, and this time we focus on edge cases readers asked about. Many product pages already contain a clean, structured description of themselves in a script tag meant for search engines. Reading it is often more reliable than parsing the visible HTML.</item></paragraphs></item><item><heading>A practical approach</heading><paragraphs><item>Write small, focused tests for your parsers using saved HTML fixtures. They run in milliseconds and catch layout changes long before a full crawl would.</item><item>Keep configuration such as base URLs, delays and selectors out of your code. Changing a delay should not require a redeploy.</item><item>Validate the data you extract. Prices without currencies, dates without time zones and empty fields are common sources of silent errors downstream.</item></paragraphs></item><item><heading>Going further</heading><paragraphs><item>Be careful with relative URLs. Resolve every link against the page it came from, not against the site root, or you will request pages that do not exist.</item><item>Always identify your client honestly with a descriptive User-Agent, and keep your request rate modest. A crawler that behaves like a considerate visitor is far less likely to cause problems for the site operator.</item></paragraphs></item><item><heading>Key takeaway</heading><paragraphs><item>Select script[type='application/ld+json'], parse every block, and pick the one whose @type matches what you need. Fall back to HTML only for missing fields.</item></paragraphs></item></sections><authorId>9</authorId><authorName>Mateo Hughes</authorName><authorSlug>mateo-hughes</authorSlug><category>Data Engineering</category><tags><item>ethics</item><item>selenium</item></tags><publishedAt>2025-03-13T00:00:00.000Z</publishedAt><wordCount>201</wordCount><readingTimeMinutes>2</readingTimeMinutes></post></data></response>
