Redirects on a Static Host: Custom Redirect

When you delete a page, rename a file, or restructure your website, you need to send visitors and search engines from the old URL to the new one. That's a redirect. On a traditional web server with PHP or Apache, redirects go in an .htaccess  file. On a pure static host, you don't have that option. Here's what you can do instead.

Custom 404 pages handle the case where you can't set up a redirect. But redirects matter for SEO when you can.

Why Redirects Matter for SEO

Search engines build up a sense of your pages' importance over time, based on links and traffic. If you delete a page that has any of that history, that value disappears with it. A redirect tells search engines, "this page moved to this new URL, please transfer the value over there."

The right kind of redirect is a 301 (permanent). Google passes nearly all of the link equity through a 301. A 302 (temporary) is for cases where you'll move the page back later, and Google passes less value through it.

How to Set Up a Custom Redirect

Setting up a redirect on Static.app is quick and requires zero coding.

1. Navigate to the Pages section in your dashboard.
2. Open the Page Settings for the old page you want to redirect away from.
3. Tick the Custom Redirect checkbox.
4. Select your Redirect Type from the dropdown menu.
5. Choose your destination by selecting one of the following options:
   • Existing page: Select another page or file already hosted on your Static.app site directly from the list.
   • Custom URL: Enter a complete external web address (e.g., https://example.com/new-home ).
6. Click Save Changes.

Choosing the Right Redirect Type

When setting up your redirect, you will be prompted to choose a status code. Here is what they mean:

• 301 (Permanent): This is the gold standard for SEO. It tells Google the move is permanent and passes nearly all of your link equity to the new page.
• 302 (Temporary): Use this only if you plan to move the page back to its original URL later. Google passes less value through a 302.
• 307 (Temporary) & 308 (Permanent): These function similarly to 302s and 301s, but they strictly preserve the original HTTP request method used by the visitor's browser. For standard website restructuring, a 301 is usually your best bet.

Automatic Platform Redirects

You don't need to set up a manual redirect for everything. For example, the migration from a free .static.domains  URL to your own custom domain is handled automatically by Static.app. We set up the redirect so any existing backlinks transfer their value cleanly without you having to configure a thing.

When you need a redirect

• You renamed a file (about.html   → about-us.html  )
• You moved a file to a folder (contact.html   → contact/index.html  )
• You changed your URL structure (/blog/2024/post.html  → /posts/post.html  )
• You moved a custom domain (the subdomain → custom domain migration covered separately)
• You consolidated two pages into one

How to find what needs redirecting

After any URL change, watch Google Search Console for "Not found (404)" errors in the Pages report. Each error is a URL that used to exist and now doesn't. For each one, decide:

• Is there a new page that covers the same topic? Redirect to it.
• Is the page just gone with no replacement? Let it 404.

If you delete pages without redirects, you may see a temporary traffic drop while Google removes the old URLs from its index. That's normal. Don't panic-redirect everything to your homepage; that's worse than letting the 404 stand.