GoHighLevel 301 Redirects: Complete Setup Guide for WordPress Migrations

We have reviewed dozens of WP-to-GHL migrations that went wrong. The root cause is almost always the same: redirects were set up after the DNS cutover instead of before, or the redirect list was incomplete. Every URL your site has ever ranked for needs a redirect in place before you change a single DNS record.

This is the process we use on every migration. It is not complicated - but it is a checklist that has to be followed in order.

---

Why 301 Redirects Matter for SEO

Link equity (PageRank) passes through 301 redirects - not through 302 temporary redirects, and not through no redirect at all. When you move from WordPress to GoHighLevel, every page that exists on your current domain has a history: backlinks pointing to it, indexed entries in Google, and in many cases direct traffic from bookmarks and social shares.

• Every indexed URL without a redirect becomes a 404. Google deindexes 404s within a few weeks.
• Users hitting old bookmarks, social shares, or links from other sites get a broken experience.
• One missed redirect on a page with external backlinks can erase months of ranking work.
• 302 redirects do not pass link equity - make sure every redirect in GHL is set to 301.

The goal is a clean transfer of every signal Google has associated with your old URLs to their new GHL equivalents. That only happens with accurate, complete 301 redirects in place before the DNS switch.

---

Where GoHighLevel Handles Redirects

In your GHL sub-account: Settings > Websites > Redirects. Each entry has three fields:

• Source URL - the old WordPress path, starting with / (e.g. /old-page/)
• Destination URL - the new GHL page URL, full URL or path (e.g. https://yourdomain.com/new-page)
• Type - set to 301

You can add redirects individually or import in bulk via CSV. For any migration with more than 20 pages, use the CSV import. Adding them one at a time is slow and error-prone.

---

Step 1 - Export Every WordPress URL

You need a complete list of every URL your site serves before you build the redirect map. There are three methods, listed from most thorough to least:

1. Screaming Frog crawl - crawls all internal links and finds URLs that may not be in your sitemap. Best for any site with more than 20 pages. The free version handles up to 500 URLs. Export as CSV.
2. Yoast or RankMath sitemap export - gets all published pages and posts. Misses drafts, old URLs, and paginated pages.
3. WordPress All-in-One Migration export - gets everything including unpublished content.

Recommendation: Use Screaming Frog for any site over 20 pages. You want every URL the site has ever served, not just the ones you think are important. The pages you overlook are usually the ones with backlinks you have forgotten about.

---

Step 2 - Build Your Redirect Map

Create a spreadsheet with four columns: Old URL (WordPress path) | New URL (GHL destination) | Priority | Status.

Sort every URL from your Screaming Frog export into three priority tiers:

• High: pages with external backlinks (check Ahrefs Site Explorer or the Google Search Console Links report) or significant organic traffic (check GSC Performance > Pages). These get redirects first, no exceptions.
• Medium: pages that are indexed in Google but have no external links. Still need redirects - Google has a record of these URLs.
• Low: internal-only pages with no traffic or backlinks - tag pages, author archives, admin pages.

For the destination URL: map each old page to the most topically relevant GHL page. Do not map everything to the homepage. Google treats mass redirects to an unrelated page as soft 404s and ignores the redirect equity. If a blog category page no longer exists in GHL, redirect it to the main blog index - not the homepage.

---

Step 3 - Implement Redirects in GHL

Step-by-step in the GHL interface:

1. Log into your GHL sub-account.
2. Click the gear icon (Settings) in the bottom left.
3. Navigate to Websites > Redirects.
4. Click Add Redirect for individual entries, or use the Import button for bulk CSV.

For sites with 50+ redirects, use the CSV bulk import. Format: two columns, no header row. Column A is the source path (e.g. /old-page/), Column B is the destination URL (e.g. https://yourdomain.com/new-page). Save as .csv and upload via the Import button.

Test one redirect before importing the full list to confirm the format is correct. A formatting error in the CSV can silently fail or create broken entries.

---

Step 4 - Test Before DNS Cutover

Set up all redirects while WordPress is still live on the domain. Then use httpstatus.io or redirect-checker.org to verify each redirect returns a 301 to the correct destination.

Two things to check for and fix before you touch DNS:

• Chains: A redirects to B which redirects to C. Fix these to go A directly to C. Chains dilute link equity and slow page load.
• Loops: A redirects to B which redirects back to A. These cause browser errors and block Googlebot.

Run through your entire high-priority list. Spot-check medium and low priority. If any redirect is returning a 302 instead of a 301, fix it in GHL before proceeding.

---

The 4 Redirect Mistakes That Kill Rankings

1. Redirecting everything to the homepage. Google treats this as a soft 404 and ignores the redirect. Every redirect needs to point to a topically relevant destination page.
2. Forgetting paginated pages. /page/2/, /page/3/, /category/name/page/2/ - these pages accumulate links over time and need redirects too. Pull them from your Screaming Frog crawl; they will not appear in your sitemap.
3. Missing blog category and tag pages. Category pages often have backlinks from roundup posts and directories. /category/marketing/ or /tag/seo/ with a single referring domain still needs a 301.
4. Ignoring trailing slash variants. /services and /services/ are treated as different URLs by many servers. Set up redirects for both patterns so either version resolves correctly.

Monitoring After Launch

The work does not stop at DNS cutover. The first 7 days post-cutover are when problems surface:

• Check the GSC Coverage report daily for new 404 errors. Any new 404 after launch is a missed redirect.
• Check GSC Performance > Pages and look for click drops on your top pages. A page that drops to zero clicks after launch almost always has a broken redirect.
• Verify your top 5 ranking pages still resolve correctly in a browser. Visit each one directly.
• If any page drops in rankings: check the redirect chain first, not just whether a redirect exists. A chain or a 302 will cause rankings to slide even when a redirect is technically in place.

Expect minor fluctuations in the first 2-4 weeks as Google re-crawls and re-evaluates. Drops beyond 4 weeks that do not recover need investigation - start with the Coverage report and work backward to the specific URLs that stopped ranking.

---

The Full Migration Context

Redirect setup is one step in a complete migration. For the full WordPress-to-GHL process including pre-migration audit, blog content transfer, DNS cutover sequence, and post-launch monitoring, see our WordPress to GoHighLevel migration guide.

---

Written by Tim Hershberger, founder of Automate the Journey. Tim has been helping small businesses since 2007 - 700+ clients across marketing, automation, and sales systems. He now focuses on GoHighLevel for service businesses, with 500+ automation builds delivered. Get a custom recommendation to see how we can help.