Vantload Downloader – website

The landing page for Vantload Downloader. Plain HTML, CSS and a little JavaScript: no build step, no dependencies, no cookies, no analytics. It works on GitHub Pages and Cloudflare Pages as-is.

index.html              the page
idm-alternative/, resume-failed-chrome-downloads/, download-hls-m3u8-video-windows/
                        guide pages for search (each is index.html in its own folder; same header/footer/CSS as the home page)
404.html                not-found page
robots.txt, sitemap.xml SEO
favicon.ico
_headers                security + cache headers (Cloudflare Pages reads this; GitHub Pages ignores it)
.nojekyll               tells GitHub Pages to serve files untouched
assets/css/style.css
assets/js/config.js     ← the links you edit (download, privacy, contact, Chrome Store…)
assets/js/main.js       connection demo, quality picker, lightbox, mobile menu
assets/img/             real screenshots of the app (WebP), logo, favicons, social card

Hosting

The official address is https://vantload.pages.dev/ (Cloudflare Pages, connected to this repo's main branch, so every push redeploys). A copy also exists on GitHub Pages at https://zainasghar-fs.github.io/Vantload/; it is not the canonical address.

Publish on GitHub Pages

1. Create a new repository named vantload (don't reuse vantload-downloader: that repo serves the privacy policy the Chrome Web Store listing points at, and its address must keep working).

2. Push this folder to it:

   git remote add origin https://github.com/zainasghar-fs/Vantload.git
   git push -u origin main
   

3. Repo → Settings → Pages → Source: Deploy from a branch → main / (root) → Save.

4. The site goes live at https://vantload.pages.dev/.

If you pick a different repo name or a custom domain

The canonical/Open Graph/sitemap addresses are written out in full. Replace https://vantload.pages.dev/ in index.html, 404.html, robots.txt and sitemap.xml:

Get-ChildItem index.html,404.html,robots.txt,sitemap.xml | ForEach-Object {
  (Get-Content $_ -Raw).Replace('https://vantload.pages.dev/','https://YOUR-NEW-ADDRESS/') | Set-Content $_ -NoNewline
}

Also change GITHUB_URL / DOWNLOAD_URL in assets/js/config.js and the two releases/latest links in index.html (they are the no-JavaScript fallbacks).

Publish on Cloudflare Pages (later)

Connect the repo, framework preset None, build command empty, output directory /. _headers is picked up automatically.

Before announcing it

• Installer is a GitHub Release asset; the Download buttons link straight to it (DOWNLOAD_URL). Each new release must keep the file name VantloadDownloaderSetup.exe.
• Chrome Web Store link is set in assets/js/config.js.
• Check the repo's Pages URL matches the one above (see "different repo name").
• Optional: sign the installer. Until then the page tells visitors about the SmartScreen "unknown publisher" notice (FAQ).

Adding a release to the history

The page shows only the newest three releases (older ones live on GitHub). In index.html, find id="changelog", copy one <li class="rel"> block to the top of the list and delete the oldest block, so three remain. Move the green "Latest" pill (<span class="pill pill-latest">Latest</span>) onto the new entry, and update the two "Version x.y.z" lines in the hero and final call to action. Then attach the installer (same file name) to a new GitHub release.

What the page claims (so it stays true)

Everything is something the app does today: up to 32 connections (default 8), pause/resume, Start/Pause Queue, multi-select, per-download speed limit, categories/filters/search, tray icon, optional start with Windows, light/dark/system theme, MP4/MKV picker with width×height labels, Chrome extension, single installer with .NET + yt-dlp + ffmpeg bundled. It deliberately does not mention a scheduler, automatic retry, clipboard monitoring, cookies/login support or other browsers. Add those lines only after they exist.

The screenshots are real captures of the shipping app (demo downloads, no personal data).

Search (SEO) notes

• The home page targets "download manager for Windows", "download accelerator" and the like; the three guides target "IDM alternative", "resume failed Chrome download" and "download HLS / .m3u8 video". Keep the copy accurate: only claim what the app does, and say what it doesn't (scheduler, site grabber, other browsers). Don't add a meta keywords tag (Google ignores it) and don't stuff keywords.
• Guide pages use root-absolute links (/assets/..., /idm-alternative/), so keep each in its own folder.
• New page = add it to sitemap.xml and to the footer links on every page. Update its "Last updated" date when the content changes.
• If a feature ships that changes a comparison (e.g. a scheduler, Firefox support), update the table in idm-alternative/index.html.