Redirects

Types of Redirects

Landingsite supports two types of redirects:

Path-Level Redirects

Redirect specific URLs on your website to other pages. For example, redirect /old-page to /new-page. These are configured in your website settings.

Path-level redirects are useful for:

• Fixing broken links from old URLs
• Redirecting stale Google search results to the correct page
• Creating short URLs that point to longer page paths

Domain-Level Redirects

Redirect an entire domain to another. These are configured in your domain settings.

Domain-level redirects are useful when:

• You have changed your domain and want the old one to forward to the new one
• You own multiple domains and want them all to point to your main site

Important: a domain-level redirect forwards visitors to the destination domain. After the page loads, the browser will show the destination URL, not the original domain you redirected from.

Landingsite does not currently support a masked redirect, domain alias, or parked second live domain that keeps the original domain visible in the browser while serving the same website.

A Landingsite website can have only one connected live domain at a time. If you want the site to stay visible at yourdomain.com, that domain must be the website’s connected live domain instead of a redirect.

Domain-level redirects normally preserve the path. For example, oldsite.com/pricing can forward to newsite.com/pricing instead of always dumping every visitor onto the homepage.

If you want a second domain to send visitors to the same site, connect one domain as the live domain and use a domain-level redirect on the other one. See Connecting a Domain.

How to Add a Redirect

Adding a Domain Redirect

1. Open the domain’s settings.
2. Find the redirect setting for that domain.
3. Enter the full destination URL you want visitors sent to.
4. Save the change.

Use a domain-level redirect when you want one whole domain to forward to another site or domain.

Do not use a website path redirect for this. Website path redirects are only for paths like /old-page and can break if you paste a full domain there.

Important: if the old domain was recently detached from a website or just switched from serving a site to forwarding somewhere else, you may still briefly see the old not found or not published result because of edge/browser caching. Try a hard refresh or private/incognito window first and give the redirect a little time to propagate.

Adding a Path Redirect

1. Go to your website Settings.
2. Find the redirects section.
3. Enter the source path (the old URL) and the destination path (where it should go).
4. Save the redirect.

The redirect takes effect immediately for all visitors.

Important: path redirects should use paths only, such as /old-page or /new-page.

Do not paste full URLs like https://example.com/page into the path redirect fields. If you include the domain inside the path, the redirect can become malformed and may send visitors to a broken URL.

Redirect Safety Tips

• Redirect old paths like /old-page to a different path such as /new-page.
• Use /path format for both sides of a path redirect — not full https://... URLs.
• Do not create a redirect that sends the homepage or a path back to itself.
• If a redirect points visitors back to the same URL they started from, it can create a redirect loop and make the site appear down.

When to Use Redirects

Stale Google Search Results

If Google is showing an old URL that returns a 404 error, adding a redirect is the fastest fix. Rather than waiting for Google to re-crawl and update its index, a redirect sends visitors to the right page immediately.

Moved or Renamed Pages

If you rename or remove a page, add a redirect from the old URL to the new one so that any existing links or bookmarks continue to work.

If One Live Page Is Broken but the Homepage Works

If your homepage loads normally but one specific page suddenly shows a 404, a “publish your website” message, or a wrong destination, check your website redirects before assuming DNS is broken.

A bad path redirect can send visitors away from the real page even when that page exists and the domain itself is connected correctly.

Common examples:

• redirecting /about to the wrong page
• redirecting /about-us when your real page lives at /about
• pasting a full https://... URL into a path redirect field
• creating two redirects that bounce between old and new paths

If a page stopped working right after redirect edits, remove the suspicious redirect first and test the page again.

Trailing-Slash URLs

Trailing slashes are handled for you. Every Landingsite site serves its pages without a trailing slash, and any URL that arrives with one is permanently redirected (301) to the slash-free version:

• /developers/ → /developers
• /faq/ → /faq

This applies to every page on every site automatically. There is nothing to configure, and you do not need to add redirect rules for it.

You also cannot add one. Path redirects are stored without trailing slashes, so a rule from /developers/ to /developers becomes a rule pointing at itself and is rejected — the redirects screen will tell you the two paths are the same once trailing slashes are normalized.

If an SEO tool reported both /developers/ and /developers as separate pages with duplicate titles or descriptions, re-run the crawl. Only the slash-free URL answers now; the other one redirects to it.