<?xml version="1.0" encoding="UTF-8"?>
<response><data><post><id>107</id><slug>extracting-json-ld-from-product-pages-part-6-107</slug><title>Extracting JSON-LD from product pages, part 6</title><excerpt>In part 6 we take the ideas from earlier instalments and apply them to a larger, messier site. Many product pages already contain a clean, structured description of themselves in a script tag meant…</excerpt><seriesName>Extracting JSON-LD from product pages</seriesName><seriesPart>6</seriesPart><sections><item><heading>Introduction</heading><paragraphs><item>In part 6 we take the ideas from earlier instalments and apply them to a larger, messier site. 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>Putting it into practice</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>Character encodings still cause trouble. Decode responses using the charset the server declares, and normalise text before comparing or storing it.</item><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></paragraphs></item><item><heading>Going further</heading><paragraphs><item>Dynamic pages render content after the initial HTML arrives. A browser automation tool can wait for a specific element to appear, which is far more reliable than sleeping for a fixed amount of time.</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>12</authorId><authorName>Yuki Andersson</authorName><authorSlug>yuki-andersson</authorSlug><category>Data Engineering</category><tags><item>ethics</item><item>scrapy</item></tags><publishedAt>2026-08-13T00:00:00.000Z</publishedAt><wordCount>213</wordCount><readingTimeMinutes>2</readingTimeMinutes></post></data></response>
