Skip to main content

Documentation Index

Fetch the complete documentation index at: https://waybackrevive.com/docs/llms.txt

Use this file to discover all available pages before exploring further.

Wayback Revive offers revisions to ensure the restored site accurately reflects the archived data. Revisions are scoped to content accuracy issues — they are not a channel for new work or design changes.

​
What qualifies as a revision

If a page was present in the Wayback Machine snapshot but is absent from the delivered site, that is a valid revision request. Include the archived URL as a reference when you submit.
If the restoration process introduced a rendering problem — broken layout, garbled text, or a missing image — that issue qualifies for a revision.
If the text or media on a delivered page visibly differs from the archived snapshot you agreed on, raise it as a content inconsistency revision.

​
What does not qualify

The following are outside the scope of revisions and require a separate service request:
  • Creating new content that was never in the archive
  • Design changes beyond the archived structure
  • Adding features or functionality not present in the original site

​
How to submit a revision request

1

Open a support ticket

Go to the support portal and open a new ticket. Use a single ticket per issue so each one can be tracked and resolved independently.
2

Describe the specific page or issue

State the exact page URL and describe what is wrong. Be as specific as possible — for example, “the header image on /about is missing” is more actionable than “some images are broken.”
3

Attach an archive reference if possible

If you have a Wayback Machine snapshot URL that shows the correct state of the page, include it. This helps the team verify the issue and resolve it faster.
4

Submit within the review timeframe

Revision requests must be submitted within the review period communicated at delivery. Requests received after that window may be treated as new work.