Skip to main content
Where to find this: Dashboard → Website Builder → Settings (gear icon) → URL Redirects → View/Edit

Why redirects matter

When you change a page URL or delete a page, anyone with the old link gets a “Page Not Found” error. This includes:
  • Google search results still pointing to old URLs
  • Social media posts you’ve shared
  • Backlinks from other websites
  • Bookmarks parents have saved
  • QR codes on printed materials
A redirect automatically sends visitors from the old URL to the new one - no broken links, no lost traffic.
SEO impact: Broken links hurt your search rankings. Google sees 404 errors as a sign of poor site maintenance. Redirects preserve your SEO value by telling Google “this page moved here.”

Setting up redirects

1

Open Website Settings

In the Website Builder, click the Settings gear icon in the left sidebar.
2

Open URL Redirects

Scroll to URL Redirects and click View/Edit. The redirect manager opens.
URL redirects modal
3

Add a Redirect

Fill in both fields:Click the + button to add the redirect. If an entry can’t be saved, a message tells you why and nothing is saved. See If a redirect won’t save.
4

Save and Publish

Close the modal and click Publish to activate your redirects.

Redirect examples

Renaming a page

You renamed “Summer Camp” to “Summer Camp 2026”:

Deleting a page

You removed your “Evaluations” page and want visitors to see “Programs” instead:

Redirecting to external site

You want an old page to go to your booking calendar:
External URLs: When redirecting to a different website, enter the full URL including https://.

Moving from an old website (.html and .php pages)

If your old site used addresses that end in a file name, like /about.html or /index.php, you can redirect those too: Capital letters in the old address don’t matter, so /About-Us.html and /about-us.html both land on the new page. Anything after a ? in the old link (like tracking tags) is carried over to the new address. An old .html address with no redirect still shows the normal page-not-found screen.

Using wildcards

Wildcards let you redirect multiple pages at once using * as a placeholder. Example: You restructured your site and moved all camp pages under a new path: This redirects:
  • /camps/summer → /programs/camps/summer
  • /camps/winter → /programs/camps/winter
  • /camps/spring-break → /programs/camps/spring-break
Wildcard syntax: Use /* at the end of a path to match all sub-pages. For example, /old-section/* catches everything under that section.

When to use redirects

Common mistakes to avoid

Don’t create chains where one redirect leads to another redirect. This slows down page loading and confuses search engines. Always redirect directly to the final destination.Bad: /old → /temporary → /final Good: /old → /final
A loop where pages redirect to each other would break the page completely. CoachIQ refuses a redirect to itself and a loop between two redirects with a message, so these can’t be saved. Longer chains are still worth checking yourself.
Always include the / at the start of your paths.Correct: /summer-camp Incorrect: summer-camp
Be very careful redirecting / (your home page). This affects your entire site’s entry point. Only do this if you’re absolutely sure.

If a redirect won’t save

Each of these is refused with a message on screen, and nothing is saved until you fix it:

Testing your redirects

After publishing, test your redirects:
  1. Open an incognito/private browser window
  2. Visit your old URL directly (e.g., yourdomain.com/old-page)
  3. Verify you land on the new page
  4. Check that the browser URL shows the new address
Pro tip: Keep a list of your redirects somewhere (spreadsheet, notes) so you remember what points where. This helps when troubleshooting or making future changes.

Common questions

There’s no hard limit, but keep your redirect list manageable. Too many redirects can slow site performance and become difficult to maintain.
Slightly. Each redirect adds a small delay (usually milliseconds). This is almost always worth it compared to broken links, but avoid unnecessary redirect chains.
Yes, you can include anchor links. For example: /old-faq → /about#faq would redirect to the FAQ section of your About page.
In the URL Redirects modal, click the X button next to the redirect you want to remove, then publish your changes.
Yes, but it takes time. Google will eventually crawl the redirect and update its index. You can speed this up by requesting re-indexing in Google Search Console.