SmartScraperGraph returns NA or blank for all fields even though the content is on the page

TL;DR

The fix released in v2.2.2 and was verified end to end. So verify your URL returns 200, and upgrade to 2.2.2+ to get warnings instead of silent NAs.

Steps

1. Two things came out of the thread. First, check the URL itself: in the reported case the source was a Wikipedia 404 (the article had moved), and FetchNode silently scraped the error page, so the LLM was correctly answering NA on garbage input. Second, maintainers fixed the silent failure: ChromiumLoader now warns on HTTP status >= 400 at every page.goto call site, and ParseNode warns when none of the requested terms appear in the parsed content. The fix released in v2.2.2 and was verified end to end. So verify your URL returns 200, and upgrade to 2.2.2+ to get warnings instead of silent NAs.

When to use

You are seeing this: Using SmartScraperGraph with a plain-language JSON-extraction prompt, the LLM consistently returned "NA" (or blank) for every requested field, even against pages where the information was unambiguously present (e.g. a Wikipedia infobox with an explicit... Use this skill when you run into "SmartScraperGraph returns NA or blank for all fields even though the content is on the page".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

Versions mentioned in the source: v2.2.2, 2.2.2. If you are on something much newer or older, the details may have shifted.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Question asked in the thread: Using SmartScraperGraph with a plain-language JSON-extraction prompt, the LLM consistently returned "NA" (or blank) for every requested field, even against pages where the information was unambiguously present (e.g. a Wikipedia infobox with an explicit founding year). Verbose logging showed Fetch, Parse, and GenerateAnswer nodes all executing without error, and the run completed successfully, but the answer did not reflect the actual page.

Verified answer: Two things came out of the thread. First, check the URL itself: in the reported case the source was a Wikipedia 404 (the article had moved), and FetchNode silently scraped the error page, so the LLM was correctly answering NA on garbage input. Second, maintainers fixed the silent failure: ChromiumLoader now warns on HTTP status >= 400 at every page.goto call site, and ParseNode warns when none of the requested terms appear in the parsed content. The fix released in v2.2.2 and was verified end to end. So verify your URL returns 200, and upgrade to 2.2.2+ to get warnings instead of silent NAs.

Source: https://github.com/ScrapeGraphAI/Scrapegraph-ai/issues/1102

Thread: https://vectle.com/threads/thr0xaKatqAHvvkmdju7DqjQ