WP Wayback Pro: Recover Your Wordpress Site

Your host purged the account. The migration failed. You inherited a client project and the backups left with the previous developer. Whatever happened, the site is gone and there is no database dump.

And then someone says the thing everyone says: isn't it all on the Wayback Machine?

It usually is. That is the cruel part. Years of your work sit on archive.org, fully readable, and completely useless to you - because getting it out means opening a snapshot, copying the text, retyping the title, guessing the date, re-picking the category, fixing the slug, and doing that four hundred more times.

WP Wayback Pro does that job for you, and does it properly. Not "dump some text into drafts" - it rebuilds your site with original slugs, real publish dates, every category, the tags, the navigation menus and the comments.

How it works

Type in your lost domain and hit Scan.

1. It finds everything. Queries the Wayback Machine's CDX index and pulls back every archived URL for your domain.
2. It filters out the noise. Stylesheets, scripts, images, fonts, feeds, /wp-admin/, wp-login, XML-RPC, sitemaps, robots.txt, favicons, /page/2/ pagination, author archives, tag and category archives, cart and checkout pages, search queries - gone before you ever see the list.
3. It classifies each item as a post or a page, recognising the usual page slugs so your pages don't land in your blog feed.
4. You review it. Preview any item and see exactly what was extracted before anything is written to your database.
5. You import in batches with a live progress bar and a running log.
6. You rebuild the menus last, and they wire themselves to the posts you just imported.

Domain in, site out.

Original slugs - this is the whole ballgame

Anyone can extract text. What matters is where it lands.

WP Wayback Pro derives the slug from the archived URL and imports the post at that slug. /how-to-brew-cold-brew/ comes back as /how-to-brew-cold-brew/ - not -2, not /post-417/.

Every inbound link that ever pointed at your article still resolves. Every citation, every backlink you spent years earning, every result still sitting in Google's index. Your site doesn't come back as a stranger. It comes back as itself.

Dated permalinks are handled too: /2019/07/my-post/ yields my-post, with a guard so a numeric segment never becomes your slug.

Real publish dates

Nothing gives away a botched restoration like four hundred posts published on the same Tuesday afternoon. The parser pulls the original publication date out of the archived markup, so your archive widget works, your chronology makes sense, and your 2018 tutorial doesn't claim to be brand new.

A parser that survives your theme

Archived HTML is messy and every theme is different, so the plugin doesn't bet on one selector and hope. It runs a strategy chain in priority order:

• Known content containers first - entry-content, post-content, article-content, article-body, the-content, content-area, single-content, td-post-content
• Then <article>
• Then <main>
• Then a text-density heuristic that finds the block carrying the most real paragraph text

Every preview tells you which strategy fired, so when something looks off you know exactly why.

Titles get the same treatment - entry-title first, then the first <h1>, then <title> - with the "| My Site Name" suffix stripped off.

And it cleans as it goes. Share buttons, related-posts blocks, author boxes, post navigation, breadcrumbs, newsletter boxes, ad blocks, sidebars, widgets and comment forms are stripped out. Wayback's own toolbar markup never makes it in, because snapshots are fetched through the id_ modifier that returns the original page rather than the archive wrapper. Archived asset URLs are rewritten back to their originals, so your content isn't hardcoded to web.archive.org forever.

Every category. Plural.

Most restoration attempts grab the first category and move on. If a post lived in Recipes, Breakfast and Gluten Free, you got Recipes.

WP Wayback Pro restores all of them, and separately restores tags, correctly telling the two apart instead of dumping everything into one taxonomy. Your archives, category feeds and internal navigation come back structurally intact.

Navigation menus, with hierarchy

The feature nobody expects and everybody appreciates.

The menu builder reads your archived navigation and rebuilds it in WordPress, including submenu hierarchy. Items are matched to your freshly imported posts by slug, so they become proper post links instead of dead hardcoded URLs. Genuine external links stay as custom links.

Run it after your content import and your site doesn't just have its posts back. It has its shape back.

Comments

Best effort, and it says so plainly - comment markup varies wildly between themes, so some will be missed and dates can be approximate. When it works, it brings back authors and original dates, de-duplicates by content so re-running never stacks copies, and flags every restored comment in the database so you can review or bulk-remove them later.

Years of reader discussion under a post is not a small thing to get back.

Review before you commit

For any item, before importing, the preview shows you the extracted title and content, which parser strategy was used, the detected categories and tags, and the comment count.

Then you can edit inline: title, slug, date, category and post type. Spotted a page the classifier called a post? Change it. Your edits are applied at import time - you're not correcting things afterwards, you're correcting them before they exist.

Safe by design

Restoration tools get one shot at your database. This one assumes you'll want to run it more than once.

Dry run mode, for both content and menus. Everything is reported, nothing is written, and the log states clearly when a dry run finishes that nothing was imported.

Status-aware duplicate handling, with four policies: skip everything with an existing slug (the default), replace drafts and trashed items only while leaving published posts untouched, replace everything, or import a second copy. There's a confirmation prompt before overwriting published posts, and dry run reports what would happen to each duplicate.

Trashed posts count as existing - because WordPress still reserves their slug. This is the trap that silently ruins restorations: import over a trashed post naively and WordPress hands you a -2 suffix and a broken URL. WP Wayback Pro detects it and restores the post from the trash first, so the slug stays clean.

Small batches (up to ten items at a time) mean your server never chokes on one enormous request, and archive.org isn't hammered - there's a deliberate throttle between fetches, because rate-limited clients restore nothing.

Progress lives in the database, not your browser tab. Reload mid-import and the job is still there. Stop cleanly after the current batch, or start over whenever you want a fresh run.

The fetcher is stubborn in the right way too: if a snapshot comes back thin or non-200, it automatically retries the standard snapshot URL and keeps whichever response actually contains the page.

What it doesn't do

Image files are not downloaded. Image URLs in your restored posts are rewritten to point at their original locations rather than at archive.org. If those original files are gone, you'll need to replace those images yourself.

That's the honest trade. Pulling thousands of archived images into your media library is slow, fragile and storage-hungry. Restoring your words, structure and URLs is the hard problem worth solving well. Images are the easy problem you can solve at your own pace.

A realistic run

Install, activate, add your licence. Scan the domain. Spot-check a handful of previews - a long post, a short one, a page - to confirm the parser is finding the right container on your old theme. Run a dry run and read the log. Import for real, in batches. Rebuild your menus last so every item binds to a real post. Then set a homepage, review the flagged comments, and replace any missing images.

An afternoon. Not a fortnight.

Who it's for

• Anyone who lost a site to a purged host, a failed migration, a hack, or an expired account with no backup
• Agencies and freelancers inheriting projects with no assets and a client who assumed "the website" was a thing that could be handed over
• Domain rebuilders restoring a genuine content history onto an acquired domain instead of starting from an empty index
• Anyone consolidating an old project that still has good writing on it, sitting in the archive, waiting

Your content already exists. The only question is whether you spend two weeks retyping it - and still lose the slugs, dates, taxonomies, menus and comments - or get it back properly this afternoon.

The Wayback Machine kept your site. WP Wayback Pro gives it back.

Licensing

One licence covers one domain and all its subdomains, forever. One-time purchase, lifetime updates. No subscription, no annual renewal.

Moving to a new site? Click "Deactivate on this site", then activate on the new one. The licensing is deliberately portable, because the people buying this plugin are by definition people whose sites have already moved somewhere unexpected once.