A useful starting point
The quick answer
- Identify whether the destination is a local file or a web address.
- Check that the target page was included in the archive.
- Keep filenames and folders intact while testing navigation.
Identify the kind of link
| Destination | Meaning | Next check |
|---|---|---|
| another-page.html | A local saved page | The file exists at that path |
| https://… | A live web address | Coverage or an intentional external link |
| #section | An anchor in the current page | The destination element exists |
| A button-driven view | Application navigation | Scripts and required live data |
Check whether the target was saved
Open manifest.json and find the destination’s original address. A link to a page outside the saved collection can continue to open the live web. Review page-limit notes, access rules and retrieval issues before assuming the link rewrite failed.
If your sample reached its page limit, create a larger archive and check the important destination again. An entered section address influences the starting points, while discovery still follows the domain. For a strict path boundary, choose a crawler with path filters.
Check local paths and filenames
Extract the original ZIP into a new folder and test the same link there. A working fresh copy points to a moved or renamed file in the earlier copy. Zipasite’s filenames can include a short hash to distinguish original addresses; keep those names when you move the folder.
A fragment such as #installation points to an element within a page. If the relevant content is generated after loading, the fragment may depend on the live application. Compare the saved markup and the JavaScript behavior before editing the link.
Record a useful issue
- The page where you clicked the link.
- The visible link text and target address.
- Whether the target is listed as saved in the manifest.
- The result from a fresh extraction.
- Whether the issue also appears on the live site.