Frequently asked questions

Twelve direct answers. Each one starts with the answer itself — no “it depends”.

Last updated: 2026-10-06

Why do ?p=123 URLs 404 after a restore — and what is the fix?

Because a file downloader gives you files, and ?p=123 is a WordPress query route, not a file: without a router that matches path + query before WordPress parses its own query vars, the request falls through to the 404 page. The fix is a must-use router that serves every manifest URL — ?p=, ?cat=, ?tag= — as a page with a byte-exact canonical. That router ships in every package I deliver.

How do you keep permalinks after a Wayback restore?

Permalinks survive because I never convert query URLs into pretty URLs. Every address that existed in the archive keeps working byte-for-byte: same path, same query string, same canonical. A restored page never 301s to another restored page — redirects are reserved for pages the archive didn’t keep.

What is a redirect map for expired domains?

A table listing every URL of the old site and what happens to it now: 200 (restored), 301 (moved to the closest surviving page) or 410 (gone deliberately, with a reason). In my packages it is redirects.csv — one row per URL, with status, target and reason — so search engines and your client’s team see the same documented truth.

Do forms and search work?

No, and I say so up front. Forms render but don’t submit — action attributes are neutralized, so nothing sends data anywhere. Site search (?s=) returns an empty results page. The archive only holds what was captured; everything beyond it doesn’t exist.

Is the content exactly as archived?

Yes. The rule is archived-wins: content is served as the snapshot holds it. I don’t rewrite, improve or add anything. If the snapshot contains a typo or a mention of some service, it stays — that’s what “restoration” means as opposed to “editing”. The only exception is an optional paid cleanup of the previous owner’s contacts and names. Pages come into WordPress as HTML blocks: text is editable, a visual page builder is not included.

What about pages the archive missed?

They don’t disappear silently. Each one is either redirected 301 to the closest surviving page or made 410 with a documented reason in redirects.csv and qa/gaps.csv. The free coverage audit shows what is and isn’t recoverable before you pay anything.

Why not just use Archivarix?

For raw files, do — they are cheap and fast ($10 per 1,000 files). But their own WordPress page says that when importing articles, neither the original design nor the URL addresses are copied. If you need a WordPress site where every original URL resolves with a correct canonical, that’s a different job. I compared the two in detail, facts only: Archivarix alternative →

What about content rights?

I restore archives of domains you own or have rights to. Before payment you confirm that in writing; rights to the content remain the client’s responsibility. I don’t verify ownership of every asset — that’s stated in the terms, not hidden.

Do you work with PBN operators?

Yes — the service is built for PBN and SEO agencies working white-label. I restore the site; how you use it is your decision. Two boundaries: I work with domains you control, and I never promise traffic or ranking outcomes — the deliverable is the documented site itself.

How much does it cost?

One fixed price: $99 per site for any site up to 10,000 pages or 5 GB, white-label included; prepaid packs: 5 sites $425 ($85 each), 10 sites $790 ($79 each), 20 sites $1,380 ($69 each); larger sites — individual quote. The free audit checks archive coverage and the page count before you pay. Prepaid packs from $69 per site; monthly care from $29/mo per site. If the real volume turns out more than 20% bigger than the audit count and the site goes over 10,000 pages or 5 GB, you choose between paying the difference and a full refund. The floor is $69. Full pricing →

How long does it take?

Standard delivery is 2–3 business days for sites up to 2,000 pages, up to 7 business days for sites over 2,000 pages; the exact date is in the audit report, before payment; counted from payment and a confirmed config, whichever comes later. Rush (sites up to 500 pages) is +$30: work starts within one business day, delivery in 1–2 business days. The process doesn’t shrink: config, ledger and QA report are what make the delivery checkable, so they are never skipped. Working hours: Mon–Fri, 10:00–19:00 Kazakhstan time (UTC+5), except Kazakhstan public holidays.

Can you do it urgently without a config?

No. The YAML config defines the archive window and priority URLs; the ledger records what happened to every URL. Without them there is no QA report — and a restore without a QA report is guesswork. Urgency changes the price (+$30), not the process.

Something’s missing? Send the domain for a free audit and ask inside the form.