The crawler uses caching to avoid reprocessing unchanged pages.
When caching is enabled, the crawler makes conditional requests using your server’s ETag and Last-Modified headers. If a page hasn’t changed since the last crawl, the crawler doesn’t download or parse the page again and reuses the existing records for that page instead. Only updated pages count towards billable crawls.
Caching is enabled by default in the crawler configuration.