Being technically able to scrape a site doesn't automatically make every way of doing it reasonable. A few habits separate responsible scraping from the kind that gets IPs and whole projects blocked.
Check robots.txt and terms first
Most sites publish a robots.txt file indicating which paths they'd rather bots avoid, and many also have explicit terms of service around automated access. Reading both before scraping avoids obvious conflicts.
Don't hit servers harder than a person would
Sending requests as fast as your code can fire them puts real load on someone else's infrastructure. Rate-limiting your own requests to something closer to human browsing speed is both more polite and less likely to get you blocked.
Only take what you need
Scraping an entire site when you only need a specific data field wastes bandwidth on both ends and increases your footprint unnecessarily. Targeted requests are lighter and less noticeable.
Respect data ownership
Being able to extract data doesn't mean you're free to republish or resell it without considering the source site's rights over their own content — that's a separate legal question from whether the scraping itself is technically permitted.