How to merge two websites on the Internet

 One day you may decide that you need a website integration strategy, that is when you have had your business for a long time say ten years ago over the past decade, in this case your website has established a high domain authority with a lot of valuable links , but at a crossroads, when you decide to rebrand and purchase a new domain name, your first thought is likely to lose all of the value your original site has built over the past 10 years.

Why do you need to merge two websites

Before we talk about how to merge two websites, let’s first talk about some of the reasons for merging, as there are a lot of reasons why you should look for a website merging strategy, here we will mention some of them:

You have purchased another high-quality domain and want to combine the content of your original site and the new domain.

You have a very old site since you started it with some permissions and a new site you're currently using, and you want to combine the two.

You are renaming your company and you have purchased a new domain name.

How to integrate your websites

If you are wondering how to merge two websites, it is time to get going, let's go step by step through your website integration strategy, to prevent confusion, we will refer to site A and site B, site A is your original site, Site B is the site where you integrate:

Step 1: Create a sitemap for the site you have integrated a

Creating a sitemap will help you take an inventory of all the pages you'll be migrating.

Step Two: Make the new field the one you are proud of

Your new domain, or the domain you're migrating to (Site B), should be one you're proud of and have great value and links. You'll want to design your site from top to bottom, keeping things like:

Overall Design: Navigation that supports whatever content you embed from your old site 

Site speed.

Step Three: Make Your New Domain Exist

Before merging your two sites, you'll need to make sure that the new domain (site B) you'll be merging into is live and ready to go.

Step 4: Set your new URLs

You will need to use the sitemap of your original old site (Site A), to determine where you want the URLs to go on your new site. This is one of the most tedious parts of the process, but a necessary part of your website integration strategy. Also the list you will use to create your redirect (301) list later.

Step Five: Update the internal links

You will also need to take the time to change the internal links on your new site, if your new URL links to your old site, be sure to change it to the new URL.

Step Six: Transfer Your Site

Next, it's time to move your site, if your site is small or medium, moving your entire site at once will help Google 's algorithms detect the transfer and index your pages faster, however, if your site is bigger you can definitely move your content section by section The other allowing you to fix problems that appear right away.

Step 7: Create your own 301 redirects

With the sitemap of your old site (Site A) and the sitemap of your new site (Site B), you can start creating your own (301) redirects. In some cases, the only thing that will change is the domain name , the URLs may stay the same, if so, this is a simple step, and you can redirect (301) everything in one line of code.

Step 8: Update your robots.txt files

On your old site (site A) you will want to remove all redirects (robots.txt) This will ensure that bots (Google) can detect new redirects to your new site, on your new site (site B) you will need to make sure that Your (robots.txt) file allows access. 

Step 9: Submit a change of address

The next step is to submit your change of address to ( Google Search Console ).

Step 10: Submit sitemaps

To keep your website integration traffic, you will need to submit both sitemaps, from site A and site B, and this will help Google detect the redirects, if you want to know the status of the sitemaps you sent, You can use the Google Sitemaps report.

Step Eleven: Monitor Your Indexed Pages

You can keep track of new pages that have been indexed using an index coverage report (Google).

Comments



Font Size
+
16
-
lines height
+
2
-