/
Redirect Supply vs GitHub Pages redirects: Real 301s for your static site
GitHub Pages doesn't support server configuration files like .htaccess, so it can't send real HTTP redirects. The common workaround, the jekyll-redirect-from plugin, creates small HTML pages that forward visitors with a meta refresh. Redirect Supply sends proper 301 redirects for your custom domain, page by page, with HTTPS handled for you and nothing to commit.
Redirect Supply vs GitHub Pages: what search engines actually see
Decision factor
Redirect Supply
GitHub Pages
Choose based on
Redirect type
Real HTTP redirects: 301, 302, 307, or 308
No server redirects; the plugin generates HTML pages with a meta refresh
Whether search engines should see a clear permanent move
Server configuration
None needed
.htaccess and .conf files aren't supported
Whether you need rules beyond one page at a time
Making a change
Edit the rule in the dashboard
Edit front matter, commit, and wait for the site to rebuild
Who updates redirects, and how often
Redirecting an old domain
Map every page of the old domain to its new URL
Needs a Pages site with a redirect page for each old URL
Moving a project to a new domain
Best fit
Custom domains moving, merging, or rebranding
Small redirects inside a site staying on GitHub Pages
If you want real 301s, Redirect Supply
Why Redirect Supply
Choose Redirect Supply for redirects that stay out of your way. Every old URL lands on the right page, every domain runs on HTTPS, and nothing breaks when your website moves.
GitHub Pages or Redirect Supply? The short answer
Keep GitHub Pages redirects for a few renamed pages inside a site that stays on GitHub Pages, where a meta refresh is good enough.
Switch to Redirect Supply if you're moving a custom domain, need real 301s for SEO, or want to redirect many pages without a redirect file for each one. There's a free plan to start, HTTPS included.
For moving a project site without losing its rankings, that makes it a Redirect Supply job.
FAQs
Questions about GitHub Pages redirects and Redirect Supply
Does GitHub Pages support 301 redirects?
Not directly. GitHub Pages doesn't support server configuration files like .htaccess or .conf. The jekyll-redirect-from plugin creates HTML pages that send visitors on with a meta refresh instead of an HTTP 301. Redirect Supply returns real 301 redirects for any custom domain you connect.
What's the difference between a meta refresh and a 301 redirect?
A 301 is sent by the server before any page loads, telling browsers and search engines that the URL has moved for good. A meta refresh is an HTML page that loads first and then forwards the visitor, which search engines treat as a weaker signal. Read more about client-side redirects.
Can Redirect Supply redirect my username.github.io URL?
No. Redirect Supply works with domains whose DNS records you control, and github.io belongs to GitHub. For a custom domain, like yourproject.com, Redirect Supply can redirect every page with a real 301 once you point its DNS records to it.
How do I move a GitHub Pages site with a custom domain?
Publish the new site, then add the old custom domain to Redirect Supply and map each old page to its new URL. Update the domain's DNS records and remove the custom domain from the GitHub Pages settings.
Can I use .htaccess on GitHub Pages?
No. GitHub Pages doesn't support server configuration files for security reasons, so .htaccess rules are ignored. See the .htaccess comparison if you're moving from an Apache server.
Can I move my redirect_from rules into Redirect Supply?
Yes. Each redirect_from entry pairs an old path with the page it sits on. List those pairs in a CSV using Redirect Supply's import format and import the file.
Have more questions?
Daniel Kouba
Founder of FREAKS
Vojtech Elias
Reflektor Studio
