blocked-page-recovery

Recover blocked or paywalled web pages via Wayback Machine, archive.today, and Jina Reader fallbacks.

Updated Aug 22, 2026
One-click install
npx skills add https://github.com/vivekgoquest/hermes-agent-stable --skill blocked-page-recovery-vivekgoquest
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: blocked-page-recovery
Source: https://github.com/vivekgoquest/hermes-agent-stable/tree/main/skills/research/blocked-page-recovery
Command: npx skills add https://github.com/vivekgoquest/hermes-agent-stable --skill blocked-page-recovery-vivekgoquest

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Web pages often fail to fetch due to 403/429 errors, Cloudflare interstitials, paywalls, or bot detection, leaving you without the content you need. This Skill recovers copies of those pages from third-party archive and rendering services instead of giving up or retrying the same blocked URL. ## Core Features & Use Cases - Fallback Ladder: Tries the Wayback Machine first, then archive.today domain rotation, then Jina Reader (when JINA_API_KEY is set), with an API-first pivot and real browser as last resorts. - Fake-Success Detection: Validates every recovered body using byte floors, interstitial title checks, and redirect-stub detection so dead Google Cache pages, AMP stubs, and rate-limit HTML are never mistaken for real content. - Provenance Discipline: Labels every result as a dated snapshot or live render so citations never present stale archives as current pages. - Use Case: A news article returns a paywall or Cloudflare "Just a moment..." page. Run the bundled script to pull the archived copy from Wayback or archive.today, complete with its snapshot timestamp for accurate citation. ## Quick Start Ask the agent to recover the blocked article at a given URL using the recover_page.py script and cite the result with its archive timestamp.

Frequently Asked Questions about blocked-page-recovery

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I recover a webpage blocked by a paywall or Cloudflare?▼

Run the bundled recover_page.py script with the blocked URL. It tries the Wayback Machine first, then rotates through archive.today domains (archive.ph, .md, .li, .is), then Jina Reader if JINA_API_KEY is set, returning the first validated copy.

How to bypass a 403 or 429 error when fetching a URL?▼

Instead of retrying the blocked URL, fetch a third-party copy. The Wayback Machine available API returns the closest snapshot, and archive.today often holds user-submitted archives of paywalled articles that Wayback lacks.

Does the Jina Reader route work without an API key?▼

No. Anonymous access to r.jina.ai returns 401 with a Turnstile challenge, so the script skips the Jina route entirely when JINA_API_KEY is unset. A valid Bearer key is required for the server-side live re-render.

Why does Google Cache not work for recovering pages anymore?▼

Google Cache has been dead since mid-2024. webcache.googleusercontent.com returns HTTP 200 with a Google Search interstitial and JS redirect, not a cached page, so the script rejects it as a fake success.

Can I cite an archived snapshot as the current live page?▼

No. Snapshots from Wayback or archive.today must be cited with their archive date, since they may be stale. For current data like prices or breaking news, treat a snapshot as context and explicitly note its age.

What should I try when no archive copy of a page exists?▼

Pivot to the site's data endpoints: look for /api/, /graphql, .json variants, RSS/Atom feeds, or sitemap.xml, which WAFs protect less aggressively than HTML. As a last resort, use a real browser tool.