SelectorLink works in Data Preview but child selectors return empty data during final scrape

#1

Hi,

I am scraping a real estate website (Fincaraíz, Colombia) using Web Scraper Chrome extension.

I have a listing page with property cards. Each property has a link to its individual detail page.

My sitemap structure is approximately:

_root
└── link_datos (SelectorLink)
    ├── valor
    ├── admon
    ├── alcoba
    ├── baño
    ├── area
    ├── ...
    └── fecha_publica

The link_datos selector is configured as:

  • Type: Link
  • Link type: Link (read from the href attribute)
  • Selector: a.cl-data

The important part is that the child selectors work correctly in Data Preview.

For example, on an individual property page, my fecha_publica selector returns the following text correctly:

"Apartamento en Venta en Medellín es un Apartamento con 1 habitación, 2 baños y 112 m². Esta propiedad se encuentra disponible a la venta y fue ingresada por Angela Maria Gonzalez el 9 de enero de 2026. El precio de Venta es de $ 1.550.000.000."

So the element definitely exists and the selector can retrieve it.

However, when I run the actual scrape, the child data from the linked property pages is not extracted correctly. The same selector that works in Data Preview returns empty data in the final extraction.

I have already tried:

  • Increasing Page Load Delay from 2,000 ms to 5,000 ms.
  • Removing fecha_publica completely from the child selectors.
  • Testing the linked property page directly.
  • Confirming that link_datos is correctly extracting the actual href URLs.

The href values are correctly detected. For example, Data Preview shows URLs such as:

https://www.fincaraiz.com.co/apartamento-en-venta-en-el-poblado-medellin/193841991
https://www.fincaraiz.com.co/apartamento-en-venta-en-el-poblado-medellin/7274727

The problem is therefore not simply that the links cannot be found.

What is particularly confusing is:

Data Preview on the child page → works

Final scrape through SelectorLink → child data is missing

The website is React-based and some of its CSS classes appear to be dynamically generated, although the selectors work correctly when tested manually.

I would like to know:

  1. Is there a known difference between how Web Scraper handles SelectorLink child selectors in Data Preview versus the actual scraping process?
  2. Can dynamically rendered React content cause a selector to work in Data Preview but fail during the actual scrape?
  3. Is there a specific sitemap configuration or setting required when the data exists on the linked child page but is not returned during the final scrape?
  4. Is there a way to debug what Web Scraper actually sees/loads on the child page during the scraping process?

I can provide screenshots of the sitemap, selectors, Data Preview, and the final scrape results if needed.

Thanks.

Yo publicaría exactamente esa versión. Es suficientemente técnica para que alguien del equipo de Web Scraper pueda identificar si el problema está en SelectorLink, en el renderizado de React o en la diferencia entre preview y scrape.

#2

Hi,

To be able to comment on this issue, it would be helpful if you could share your sitemap JSON.

I have looked at the data point example provided and noticed that, for example, the text at the bottom of the listing is only rendered after scrolling down. You can test this by refreshing the page and clicking 'Element preview'. To solve this, you can add a scroll as the first step to be executed after opening the listing link.

image
image1213×84 5.69 KB