#Change Tracking
3 messages · Page 1 of 1 (latest)
I'm curious why you're trying to avoid doing a full scrape. Are you concerned about the credit cost, or something else?
Realistically, the only way to know if something has changed is to fully scrape it (which is cheap), and then compare it against a previous scrape.
i'm mainly concerned about speed / latency in my application. firecrawl is consistenly taking 10-20 seconds per url. it'd be ideal if i could get it down to a few seconds by maybe storing the data after scraping it and then just having some tool that can quickly check whether i need to rescrape or just return what's in the database