A useful starting point
The quick answer
- Check whether the banner comes from the homepage or every saved page.
- Review the scripts that supply it on the original site.
- For your own archive, change the relevant source or working copy and retest.
Why the banner can return
Consent choices are usually associated with a site’s browser storage and origin. A file opened from disk has a different context from the live website. Different browsers also handle local-file storage in different ways, so test the behavior on the device where you will read the copy.
A banner can load directly from page markup, a consent plugin or a tag manager. Removing one loader affects only that route. Start with the actual source of the banner rather than assuming every prompt comes from the same script.
What Zipasite does with Google Tag Manager
Zipasite keeps recognised Google Tag Manager loaders on index.html and removes recognised loaders from other saved pages. The homepage may therefore show a banner while connected. Banners supplied by other scripts can remain.
This behavior follows the saved-page handling in the current tool. It is separate from a universal consent solution. A custom wrapper, inline script or third-party plugin may need its own review.
Check one page at a time
- Open the homepage and an inner page from the same extracted archive.
- Record which page shows the prompt.
- Test with the device temporarily offline to identify network dependence.
- Compare the page scripts with the consent setup on the source site.
- Repeat the check in the browser intended for the archive.
Prepare a cleaner copy of your own site
For a site you control, a dedicated static export can omit live analytics and consent integrations at the source. If you edit an extracted copy, work on a duplicate and identify the specific script or component responsible. Preserve the original archive for comparison.
Simply hiding an overlay can leave its scripts running underneath. Review the loader and the behavior together. Recheck scrolling, navigation and keyboard focus after a change, because some banners also lock the page behind them.
Keep the reader’s expectations clear
Saved scripts may contact external services while the device is connected. An offline reading copy and a privacy-clean export have different requirements. Document the changes you make and the behaviors you actually test before sharing the folder.