How to set up 301 redirects in Base44

Base44 supports real 301 redirects. On the Starter plan and above you can add up to 50 page redirects per app, either for a single path or for a prefix and everything under it, and point them at another page on your app or at an external URL. You can also redirect a whole connected domain to another one on the same app.

Some guides still say Base44 can’t do 301s. As of September 2026, Base44’s domain documentation describes redirects in detail. Redirects are one item on the Base44 SEO checklist.

When you need a redirect#

• You rename a page. Changing /pricing to /plans breaks every link and search result that points at /pricing. Base44’s own example is exactly that.
• You restructure a section. Moving /blog/* to /articles/* is one prefix rule.
• You moved from another platform and the old URLs are still in Google, or linked from other sites.
• A path needs to serve a file hosted elsewhere, such as ads.txt for an ad network.

Without a redirect, those old URLs return an error page or, worse, a page that looks empty. Google may report the latter as a soft 404.

Add a page redirect#

1. Open your app’s Dashboard and go to Domains.
2. In the Page redirects section, click Add redirect.
3. Choose the type:
   • Single path redirects the exact source path, such as /old-pricing.
   • Prefix redirects “the source path and everything under it, keeping the rest of the address.” Prefix rules start below the root, such as /blog.
4. Enter the destination: a path on your app or a full external URL.
5. Click Save redirect.

Base44 says redirects “usually start working within a few minutes of saving them.” Check one:

curl -sI https://yourdomain.com/old-pricing | grep -iE '^(HTTP|location)'
# HTTP/2 301
# location: https://yourdomain.com/plans

A few rules from the docs:

• Up to 50 redirects per app. Use prefix rules for whole sections so you don’t run out.
• One hop. “Redirects resolve in one hop, so each rule sends visitors straight to its final destination.” You don’t need to worry about chains building up when you redirect a page that was itself a redirect target.
• External targets count as one hop too, since they leave your app entirely.

Redirect a whole domain#

If your app has two verified domains, say an old brand and a new one, you can send all traffic from one to the other:

1. On the Domains page, find the domain you want to redirect from in Custom domains.
2. Click More actions next to it and choose Redirect domain.
3. Pick the destination domain.

“A whole-domain redirect needs at least 2 verified domains on the same app,” and the option only appears once the second one is verified. To undo it, open Redirect domain again and choose No redirect.

The www redirect you can’t change#

Base44 always redirects www to the root domain, and the docs say there’s no setting to stop or reverse it. That’s fine for SEO as long as you’re consistent: treat the root as your canonical address everywhere. If you need finer control, the docs suggest handling it at your DNS or hosting provider outside Base44.

After you add redirects#

1. Update your own internal links to point at the new URLs directly. A redirect is a safety net for links you can’t change.
2. Check that the old URLs have dropped out of your sitemap and the new ones are in it.
3. In Google Search Console, inspect a couple of the old URLs after a week or two. They should show “Page with redirect”, which is the expected status.

What to do next#

Make a list of every URL that changed in your last restructure or migration, add a redirect for each, and test them with the curl command above. If you’re moving the app onto a new domain, the custom domain guide covers the rest of the move.