Frequently asked questions
Twelve direct answers. Each one starts with the answer itself — no “it depends”.
Last updated: 2026-09-23
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 we deliver.
How do you keep permalinks after a Wayback restore?
Permalinks survive because we 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 our 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 we 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. We 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”.
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. We compared the two in detail, facts only: Archivarix alternative →
What about content rights?
We restore archives of domains you own or have rights to. The order form includes a checkbox confirming that; rights to the content remain the client’s responsibility. We don’t verify ownership of every asset — that’s stated in the terms, not hidden.
Do you work with PBN operators?
Yes — PBN and SEO agencies are our main white-label clients. We restore the site; how you use it is your decision. Two boundaries: we work with domains you control, and we never promise traffic or ranking outcomes — the deliverable is the documented site itself.
How much does it cost?
$99–149 for a standard site, $69–89 white-label for agencies, $69 launch offer for the first 5 clients, $150–200+ for large archives, retainer $29–49/mo per site. The floor is $69; discounts only for prepaid packages. Full pricing →
How long does it take?
Standard delivery is 3–5 days from a confirmed config to a ready package. A rush order is +$30 — but the process doesn’t shrink: config, ledger and QA report are what make the delivery checkable, so they are never skipped.
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.