Wayback Machine to live WordPress. ?p= / ?id= recovered. 301s mapped.
Dead client site or a drop you bought: one restore. Packs if you have a list. Live WP, original URLs, admin access. Archive HTML in the dashboard. Not a ZIP.
Restore from Wayback. Network care.
Two offers. Price is fixed before work starts. No surprise add-ons.
Larger than a 10-pack, or a monthly flow — send the list in Telegram. All services.
Case studies
Numbers from delivered restores
Domains masked. Metrics from delivery logs and machine-checked verify reports. See all cases.
Domains anonymized as patterns. Every number here comes from a delivery log or a machine-generated verify report.
How a restore runs
Check. Capture. Live WP. Handoff.
Same sequence for one client domain or a 10-pack. Cost and gaps before production.
Check archive
Last-good snapshot. Whether ?p= / ?id= exist. What will not come back. Named before capture — not a written CDX report.
Capture + strip
Full archive walk to that date, parametric URLs included. Wayback chrome, old contacts and shop pages, logo and favicon — stripped.
Go live
Live WordPress on your domain. Original URLs stay 200. SSL, Cloudflare, nameservers you change.
Handoff
Admin access. What came back and what the archive never had. Revision rounds follow the tier.
The engine
wayback2wp — our own restoration pipeline
Not an agency workflow. Proprietary software built in-house, run the same way for one domain or a batch of twelve.
CDX index walking
Full Wayback CDX traversal to the last-good snapshot — not a one-page scrape.
Parametric URL recovery
?p= and ?id= pages rebuilt as first-class URLs standard tools skip.
Automated cleanup
Wayback chrome, old-owner contacts, and dead shop pages stripped by rule, not by hand.
Original-URL deploy
WordPress ships with the site's original routing — permalinks answer 200.
Every restore ships with a machine-checked verify report: sampled URLs, ?p= checks, sitemap vs manifest. The pipeline is also the base of a self-serve recoverability checker in development.
The problem
The archive is not the problem. A restore that drops ?p= and rewrites original URLs is.
Agencies do not need a folder of HTML. They need a live domain that can index. Broken URL structure and filler content burn that. I put the archive on live WordPress and keep original URLs.
Typical restore
- Missed deadline. Freelancer gone. Client domain still dark.
- ZIP of HTML. Looks restored. You cannot edit a page.
- ?p= / ?id= dropped. Catalog pages never make the scrape.
- No 301 map. Dead URLs sit as 404s.
- Unrelated filler. Generated copy stuffed into gaps.
- Wayback junk in source. /web/ timestamps. Old-owner contacts still live.
What you actually get
- Live WordPress. Admin access. Original URLs. Not an HTML dump.
- ?p= and ?id= recovered. First-class pages in the capture.
- No unrelated filler. Gaps stay gaps.
- Original URLs stay live. WP permalinks 301 to those originals.
- SSL + Cloudflare. Hosting configured on delivery.
- Fixed price before work. Telegram. Reply in one business day.
FAQ
What agencies ask before a batch
Restore pipeline, original URLs, packs of 3 or 10+, and what is not promised. If it is not here, message Telegram @wpservicelab.
Brief
Send the domains. Scope and price before any work.
Domain plus a Wayback link. For a batch, list them. I confirm scope and price before work starts. Response within one business day.
Send the domain list
Straight to my inbox. For a batch, list the domains.
Direct channels
Telegram is fastest. Upwork if you need escrow.