Moving off Weebly changes your URLs, and if you do nothing about it, every old link in Google's index and every inbound link from other sites will land on a 404. That destroys the search rankings you spent years building. The fix is straightforward: map every old Weebly URL to its new address and add permanent 301 redirects in your .htaccess file so both visitors and search engines are quietly forwarded to the right page. This guide shows you exactly how to build that URL map and write correct, tested redirect rules so you keep your rankings after leaving Weebly.
- Why Migrations Hurt SEO If You Are Not Careful
- Understand Weebly's URL Structure
- Build a URL Map Before You Switch
- 301 vs 302: Always Use 301 for a Permanent Move
- Writing the Redirects in .htaccess
- Redirecting an Entire Old Path or Blog
- WordPress-Specific Options
- Preserve On-Page SEO Too
- After Go-Live: Tell the Search Engines
- Test Your Redirects
Never Let an Old URL Return a 404
Every URL that ranked, that someone linked to, or that Google has indexed must resolve to a live page on your new site with a 301 (permanent) redirect. A 404 tells search engines the content is gone for good and the ranking is dropped. A 301 tells them the content moved here permanently and passes the accumulated ranking signal to the new URL. Get your redirect map right and a migration can be nearly invisible to your search traffic.
01. Why Migrations Hurt SEO If You Are Not Careful
Search engines rank individual URLs, not "your website" in the abstract. When Google has been sending traffic to yourdomain.com/services.html for three years, that specific URL has accumulated authority - it has inbound links pointing at it, it has a history of clicks, and it has a settled position in the results. When you migrate off Weebly, your new platform almost always uses different URLs (WordPress prefers /services/ without the .html), and that is where the damage happens.
If you migrate without a redirect plan, three things go wrong at once:
- 404 errors - Anyone who clicks an old link (from Google, from another site, from a bookmark) hits a "page not found" error instead of your content
- Lost link equity - The ranking value built up on the old URL does not automatically transfer to the new one. Without a 301, that authority is simply orphaned
- Dropped rankings - Once Google recrawls and finds the old URLs returning 404s, it drops them from the index, and your traffic falls off a cliff
The fix has two halves, and you need both: preserve the content (keep the same pages, text, and images on the new site) and preserve the addresses (301-redirect every old URL to its new home). This guide focuses on the second half, which is where most of the technical work lives.
Do not wait until after your traffic drops to set up redirects. The moment your new site goes live on your domain, the old Weebly URLs stop resolving. Have your redirect rules written and ready to deploy at the same instant you switch DNS, not days later. Every day of 404s is a day of lost rankings that can take weeks to recover.
02. Understand Weebly's URL Structure
Before you can map old URLs to new ones, you need to know exactly what Weebly's URLs look like. Weebly follows a few consistent patterns:
- Pages get a
.htmlextension - Your About page lives at/about.html, your Services page at/services.html, and so on. This is the single biggest difference from WordPress, which drops the extension entirely - The home page is the domain root -
/or/index.html, which usually needs no redirect since the root stays the root - Blog posts use a dated path - Weebly blog posts commonly follow
/blog/YYYY/MM/post-title.html(for example/blog/2024/03/spring-sale.html). Some older Weebly sites use/blog/post-title.htmlwithout the date - Blog category and archive pages - Weebly generates
/blog/category/name.htmlstyle URLs for post categories
Here is what a typical Weebly site's URL set looks like:
/ (home page)
/about.html
/services.html
/contact.html
/blog.html (blog index)
/blog/2024/03/spring-sale.html
/blog/2023/11/holiday-hours.htmlThe .html extension and the dated blog path are the two Weebly quirks that generate the most redirects. If you keep this in mind while choosing your new WordPress permalink structure, you can often reduce the number of redirects you need to write - see Section 07.
03. Build a URL Map Before You Switch
A URL map is simply a two-column list: every URL that exists on your old Weebly site on the left, and where it should point on your new site on the right. You build this before you migrate so that on go-live day you already know every redirect you need. Do not try to remember your URLs from memory - crawl the live site so you capture everything, including old blog posts you have forgotten about.
Ways to collect every old URL
- Your sitemap.xml - Weebly publishes a sitemap at
yourdomain.com/sitemap.xml. Open it in a browser and you get a machine-readable list of every page Weebly considers public. This is the fastest starting point - Google Search Console - Open the Pages report (under Indexing) to see every URL Google has actually indexed. These are the URLs that matter most for SEO because they are the ones already ranking and receiving traffic
- Screaming Frog SEO Spider - The free tier crawls up to 500 URLs, which covers most small business sites. Point it at your Weebly domain and it will discover every internal link, its status code, its title tag, and its meta description in one pass
- A site crawler like HTTrack or wget - If you already downloaded a full copy of your site for backup, the file list is effectively your URL list
What the map looks like
Put your old URLs and their destinations in a spreadsheet. Keep it simple - old URL, new URL, and a notes column:
Old Weebly URL New URL Notes
/about.html /about/ direct match
/services.html /services/ direct match
/contact.html /contact/ direct match
/blog.html /blog/ blog index
/blog/2024/03/spring-sale.html /spring-sale/ post -> post
/products.html /shop/ renamed pagePrioritize the URLs that actually have traffic and inbound links. If your Google Search Console Pages report shows only 20 of your 60 pages have ever received a click or impression, those 20 are the ones you absolutely cannot afford to leave as 404s. Redirect everything, but sanity-check the high-value URLs by hand.
04. 301 vs 302: Always Use 301 for a Permanent Move
There are two common redirect types, and using the wrong one on a migration will cost you rankings:
- 301 Moved Permanently - Tells browsers and search engines the page has moved for good. Search engines transfer the ranking signal (link equity) to the new URL and eventually replace the old URL in their index with the new one. This is what you want for a Weebly migration.
- 302 Found (Temporary) - Tells search engines the move is temporary and the original URL will be back. Because of that, a 302 generally does not pass ranking signal to the new URL, and search engines keep the old URL indexed. Use this only for genuinely temporary situations (a maintenance page, an A/B test), never for a permanent migration
When you leave Weebly, the move is permanent - the old .html URLs are never coming back. So every rule in this guide uses a 301. In Apache .htaccess, the Redirect 301 directive and the [R=301] flag on a RewriteRule both produce a proper 301 response.
If you write a RewriteRule with just [R] or [R=302], Apache issues a temporary redirect and your link equity does not transfer. Always spell out [R=301,L] so the redirect is unambiguously permanent and rule processing stops there.
05. Writing the Redirects in .htaccess
On Apache-based hosting (which includes Ultra Web Hosting's shared and WordPress plans), redirects live in a file named .htaccess in your public_html directory - the same folder that holds your site's files. The leading dot makes it a hidden file, so enable "show hidden files" (dotfiles) in cPanel File Manager to see it. If a WordPress install already created a .htaccess, add your redirect rules above the # BEGIN WordPress block so WordPress does not overwrite them.
Simple one-to-one redirects
The Redirect 301 directive is the easiest way to map one old URL to one new URL. The syntax is Redirect 301 /old-path /new-path:
# Map each old Weebly .html page to its new clean URL
Redirect 301 /about.html /about/
Redirect 301 /services.html /services/
Redirect 301 /contact.html /contact/
Redirect 301 /products.html /shop/This is perfect when you have a manageable list of pages and you want each redirect spelled out explicitly. It is easy to read and easy to audit later.
Stripping .html site-wide with mod_rewrite
If every old page followed the /name.html to /name/ pattern, you do not have to list them one by one. A single mod_rewrite rule can strip the .html extension from any request and 301-redirect to the clean version:
RewriteEngine On
RewriteRule ^(.*)\.html$ /$1/ [R=301,L]Here is what each piece does:
RewriteEngine On- turns on the rewrite module (include it once at the top)^(.*)\.html$- matches any path ending in.htmland captures the part before.htmlinto$1. The backslash before.htmlescapes the dot so it matches a literal period, not "any character"/$1/- rebuilds the URL as the captured name wrapped in slashes (so/about.htmlbecomes/about/)[R=301,L]- issues a permanent 301 redirect and stops processing further rules (L= last)
The blanket .html rule above will also rewrite /index.html to /index/, which may not exist. If your Weebly home page was served at /index.html, add an explicit rule for it before the blanket rule so it wins: Redirect 301 /index.html /. Order matters - Apache applies redirect rules top to bottom.
Redirecting the dated Weebly blog path
Weebly's dated blog URLs (/blog/2024/03/spring-sale.html) rarely match WordPress permalinks, so these usually need explicit rules. If WordPress serves the same post at /spring-sale/, a direct redirect handles it:
# Individual Weebly blog posts -> WordPress post slugs
Redirect 301 /blog/2024/03/spring-sale.html /spring-sale/
Redirect 301 /blog/2023/11/holiday-hours.html /holiday-hours/For deeper background on how .htaccess works, see our Complete Guide to .htaccess, and for more redirect recipes see How to Create Redirects via .htaccess.
06. Redirecting an Entire Old Path or Blog
Sometimes you do not want to map posts one by one - you want to send an entire section somewhere. This is where mod_rewrite patterns earn their keep.
Send an entire old folder to one page
If you dropped your old Weebly blog entirely and want every old blog URL to land on your new blog index, match the whole path and redirect it:
RewriteEngine On
RewriteRule ^blog/.*$ /blog/ [R=301,L]This catches anything under /blog/ - all the dated posts, category pages, and archives - and sends them to /blog/. It is a blunt instrument (visitors lose the specific post), so prefer per-post redirects for content that still exists. Use the catch-all only for content you genuinely retired.
Preserve the post slug while restructuring the path
If your Weebly posts were at /blog/YYYY/MM/slug.html and your WordPress posts are at /blog/slug/, you can capture the slug and drop the date with one pattern:
RewriteEngine On
RewriteRule ^blog/[0-9]{4}/[0-9]{2}/(.+)\.html$ /blog/$1/ [R=301,L]Breaking that down:
^blog/- the path must start withblog/[0-9]{4}/[0-9]{2}/- matches the four-digit year and two-digit month segments(.+)\.html$- captures the post slug (everything up to.html) into$1/blog/$1/- rebuilds the clean WordPress URL from the captured slug
So /blog/2024/03/spring-sale.html becomes /blog/spring-sale/ automatically, no matter how many posts you have, as long as the WordPress slug matches the Weebly slug.
Combine approaches: write explicit Redirect 301 lines for your handful of important static pages, then add one or two RewriteRule patterns to handle the bulk of your blog posts. You do not have to pick just one method.
07. WordPress-Specific Options
If your new site is WordPress, you have options beyond hand-editing .htaccess.
The Redirection plugin
The free Redirection plugin gives you a point-and-click interface for managing 301 redirects without touching any files. You paste in the old URL and the new URL, and it handles the rest. It also logs every 404 that hits your site, which is invaluable after a migration - you can watch for old Weebly URLs you missed and add redirects for them as they show up. For non-technical site owners, this is often the easiest path.
The Redirection plugin's 404 log is the best safety net during a migration. Leave it running for a few weeks after go-live, check it every few days, and add a redirect for any old URL that keeps appearing. This catches the pages you forgot were ever indexed.
Match your slugs to minimize redirects
The single most effective way to reduce redirect work is to make your new WordPress slugs identical to your old Weebly page names. If your Weebly page was /about.html, name the WordPress page so its permalink is /about/. Then a single site-wide .html-stripping rule (Section 05) covers everything and you barely need per-page redirects at all.
Set your permalink structure in Settings > Permalinks. For a business site migrating from Weebly, the Post name option (/%postname%/) produces the cleanest URLs and is the easiest to map from Weebly's page names.
08. Preserve On-Page SEO Too
Redirects handle the addresses, but rankings also depend on what is on each page. When you rebuild a page on your new platform, carry these elements across faithfully or you will see rankings slip even with perfect redirects in place:
- Title tags - Copy each page's
<title>text over exactly. This is one of the strongest on-page ranking signals. In WordPress, an SEO plugin like Yoast or Rank Math lets you set the title for each page - Meta descriptions - Bring over your existing meta descriptions. They do not directly affect ranking, but they drive click-through from the results page
- H1 headings - Keep the same main heading on each page. Search engines use the H1 to understand what the page is about
- Body content - Migrate the actual text word for word where you can. Thin or rewritten content can lose the keyword relevance that earned the ranking
- Image alt text - Re-add the
altattributes on your images. This helps image search and accessibility, and Weebly's export does not always preserve it
Set canonical URLs
A canonical tag tells search engines which URL is the definitive version of a page, preventing duplicate-content confusion when a page is reachable at more than one address. WordPress SEO plugins add self-referencing canonical tags automatically, so on most WordPress sites you get this for free. Confirm each important page outputs a <link rel="canonical" href="..."> pointing at its own clean new URL:
<link rel="canonical" href="https://www.yourdomain.com/about/" />Preserving content and preserving URLs work together. A perfect 301 to a page whose content was gutted still loses rankings, and perfectly migrated content at a URL that 404s loses rankings too. You need both halves for the migration to be invisible to search.
09. After Go-Live: Tell the Search Engines
Once your new site is live and your redirects are in place, help the search engines find the new structure quickly instead of waiting for them to stumble across it.
- Submit your new sitemap.xml - WordPress SEO plugins generate a sitemap at
yourdomain.com/sitemap.xml(or/sitemap_index.xml). Submit that URL in Google Search Console under Sitemaps, and do the same in Bing Webmaster Tools - Use the URL Inspection tool - In Google Search Console, inspect a few of your most important new URLs and click "Request Indexing" to nudge Google to crawl them sooner
- Monitor the Coverage / Pages report - Watch for a spike in 404s or "Not found" URLs in the weeks after go-live. Each one is an old URL you may have missed a redirect for - add it and the error clears on the next crawl
- Watch your rankings and traffic - Expect a little turbulence for a week or two while Google recrawls and processes the redirects. If content and URLs were preserved correctly, rankings should settle back to where they were
Do not remove your 301 redirects after a few months. Inbound links from other sites still point at the old Weebly URLs, and those links keep passing value only as long as the redirect is in place. Treat the redirect rules as a permanent part of your site. Removing them later re-breaks every old link.
10. Test Your Redirects
Never assume a redirect works - verify it. The cleanest way is curl -I, which fetches only the HTTP response headers so you can see the exact status code and the destination:
curl -I https://www.yourdomain.com/about.htmlA correctly configured 301 returns a response that starts like this:
HTTP/2 301
location: https://www.yourdomain.com/about/The two things to confirm are the 301 status (not 302, not 200, not 404) and a location header pointing at the correct new URL. If you see 302, your rule used a temporary redirect and needs [R=301,L] or Redirect 301. If you see 200, the redirect is not firing at all - re-check the path in your rule. If you see 404, either the redirect is missing or the destination page does not exist.
Watch out for redirect chains. If /about.html redirects to /about which then redirects to /about/, you have two hops where you want one. Chains dilute link equity slightly and slow the page. Point each old URL directly at its final destination in a single 301.
Online redirect checkers
If you are not comfortable on the command line, browser-based tools like httpstatus.io or redirect-checker.org do the same job. Paste an old URL and they show you the full redirect chain and the final status code. Spot-check your most important pages, then rely on Google Search Console's Coverage report to surface anything you missed.
Need a Hand With Your Redirects?
If you are migrating off Weebly and want help building your URL map or writing correct .htaccess rules, our support team can review your redirect plan and make sure your rankings survive the move. Open a ticket and tell us your old and new URL structure.
Open a Support TicketQuick Recap: Preserving SEO After Weebly
If you only do 5 things from this guide, do these:
- Crawl and map - List every old Weebly URL (sitemap.xml, Search Console, Screaming Frog) and map each to its new address before you switch
- Always 301 - Use permanent 301 redirects, never 302, so ranking signal transfers to the new URLs
- Write the .htaccess rules - Explicit
Redirect 301lines for key pages, a mod_rewrite.html-stripping rule for the bulk, plus rules for the dated blog paths - Preserve content - Carry over title tags, meta descriptions, H1s, body text, alt text, and set canonical URLs
- Tell Google and test - Submit the new sitemap, watch the Coverage report for 404s, and verify each redirect with
curl -I
This article is the SEO and redirects deep-dive that pairs with our complete guide to migrating from Weebly. Start there for the full picture, then use this guide when it is time to lock in your redirects.
