blocked-page-recovery

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

Updated Sep 20, 2026
One-click install
npx skills add https://github.com/GreenyZA/neo-light --skill blocked-page-recovery-greenyza
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: blocked-page-recovery
Source: https://github.com/GreenyZA/neo-light/tree/main/.hermes-home/skills/research/blocked-page-recovery
Command: npx skills add https://github.com/GreenyZA/neo-light --skill blocked-page-recovery-greenyza

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 blocked pages from third-party archive and rendering services instead of giving up or looping on the same URL. ## Core Features & Use Cases - Fallback Ladder: Tries recovery routes cheapest-first — Wayback Machine, archive.today domain rotation, Jina Reader (with JINA_API_KEY), then an API-first pivot to /api/, /graphql, or RSS endpoints. - Fake-Success Detection: Validates every recovered body with byte floors, interstitial-title rejection, 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 snapshot or live so archived copies are always cited with their timestamp and never presented as current data. - 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, with its snapshot date preserved for citation. ## Quick Start Ask the agent to recover the blocked article at a given URL using the blocked-page-recovery script and report which route succeeded with its provenance.

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 page blocked by Cloudflare or a 403 error?▼

Query the Wayback Machine availability API first for a dated snapshot, then rotate through archive.today domains (archive.ph, .md, .li, .is). The bundled recover_page.py script runs this ladder automatically and validates each body before declaring success.

How to bypass a paywall to read an archived article?▼

archive.today often holds user-submitted copies of paywalled news articles that Wayback lacks. Fetch https://archive.ph/newest/{URL} and rotate domains on rate limits, validating the body since 429 responses still ship multi-KB HTML.

Does the Wayback Machine work for JavaScript-only sites?▼

Wayback snapshots do not render JS-only SPAs, so recovery fails for those pages. Use Jina Reader (r.jina.ai) with a JINA_API_KEY instead, since it re-renders the live page server-side in a real browser and returns markdown.

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

Google Cache was discontinued in mid-2024. webcache.googleusercontent.com now returns HTTP 200 with a Google Search interstitial and JS redirect, not a cached copy, so it must never be treated as a successful recovery.

Can I cite an archived snapshot as current information?▼

No. Snapshots from Wayback or archive.today are dated copies that may be stale. Always cite them with their snapshot date, and for current data like prices or breaking news, state explicitly that the snapshot is context, not an answer.