docs(scrape): add freshness and liveness guidance#5
Open
hmishra2250 wants to merge 2 commits into
Open
Conversation
This was referenced Jul 19, 2026
Closed
Closed
Add a reference explaining the maxAge caching/freshness tradeoff, a 5-step checklist for freshness-sensitive actions, and a worked job-posting example that classifies active/removed/unknown from rendered content and redirect evidence. A fresh scrape proves a page rendered, not that the underlying business object is live; there is no liveness field. Link it from firecrawl-build-scrape/SKILL.md. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
hmishra2250
force-pushed
the
feat/freshness-liveness-guidance
branch
from
July 20, 2026 09:59
4cec16f to
53757d8
Compare
hmishra2250
marked this pull request as ready for review
July 20, 2026 10:01
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Agents need a clear way to choose between cache speed and a fresher retrieval, without treating a successful scrape as proof that the state represented by a page is current.
What changed
maxAge: 0as the way to bypass Firecrawl index reuse;unknown;This changes agent guidance only. It does not change Firecrawl API behavior or the cache/metadata contract.
Related: firecrawl/firecrawl-docs#1145, firecrawl/firecrawl-mcp-server#321, firecrawl/firecrawl#4082.
Validation
node --check.git diff --checkpasses.