Wayback Machine Save Page Now fetcher
Save Page Now is the Internet Archive feature that captures a specific URL on demand when a person requests a snapshot through the Wayback Machine. Unlike background archival crawling, this fetch happens because someone asked for it right now, making it a user-triggered archival fetch. It appears in logs as an archive.org-identifying request tied to a save request rather than a scheduled crawl.
What this means
Save Page Now lets anyone capture a live snapshot of a single URL through the Wayback Machine. When triggered, the Internet Archive fetches that exact page and stores it. This is different from the background crawling that discovers and re-captures pages on its own schedule.
Because the fetch happens on a person's immediate request, it is best understood as a user-triggered archival fetch — one URL, captured now.
Why the distinction matters
Reading Save Page Now as broad archival crawl coverage overstates how much of your site is being preserved — it is a single requested URL. Reading it as a human visit inflates audience metrics with what is really an automation event.
In logs it appears as an archive.org-identifying request. The exact agent token used for on-demand saves is not exhaustively published, so this entry is marked partially verified; the on-demand, single-URL nature is the reliable signal.
- Triggered by a person requesting one snapshot
- Captures a single URL, not a site-wide crawl
- Distinct from scheduled archival crawling
How it appears in analytics and logs
A Save Page Now fetch means a person requested an immediate snapshot of one URL. It is a single user-triggered archival fetch, not a broad crawl and not human page-view traffic.
Diagnostic use case
Recognise on-demand Internet Archive snapshot fetches in logs and separate them from scheduled archival crawling and from search indexing.
What WebmasterID can help detect
WebmasterID classifies on-demand archive fetches server-side as bot/automation events, so a one-off snapshot request does not inflate human analytics or look like crawl coverage.
Common mistakes
- Treating a single Save Page Now fetch as full-site archival coverage.
- Counting the on-demand fetch as a human page view.
- Assuming robots.txt blocks a user-requested save the same way it gates crawling.
Privacy and accuracy notes
The fetch is identified by user-agent and archival context only. Even though a person triggered it, no visitor identity is exposed; WebmasterID records it as a bot/automation event.
Related pages
- archive.org_bot — Internet Archive web crawler
archive.org_bot is a user-agent associated with Internet Archive crawling that fetches public web pages for preservation in collections such as the Wayback Machine. It is an archival agent, distinct from search-engine indexing crawlers, and identifies via an archive.org URL in its user-agent. Operators see it when their public pages are captured for long-term snapshots.
- ia_archiver and the Internet Archive crawler
ia_archiver is a long-standing user-agent token associated with crawling for the Internet Archive's Wayback Machine and related collections. The Internet Archive operates archival crawlers that fetch public pages to preserve snapshots over time. The token has historic ties to the Alexa crawler that fed early Archive collections, so log entries may show ia_archiver or archive.org-related agents depending on the crawl source.
- User-triggered fetchers vs crawlers
Google groups its automated agents into common crawlers, special-case crawlers, and user-triggered fetchers. User-triggered fetchers act because a person asked for something now — like reading a page aloud or fetching a preview — and are treated differently from indexing crawlers, including how they relate to robots.txt. Understanding the distinction prevents wrong robots.txt and analytics decisions.
- Bot vs human
How automated and user-triggered fetches are separated from real visitors.
Sources and verification notes
- Internet Archive — Save Page NowOn-demand snapshot capture; exact save-fetch user-agent token not exhaustively published.
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.