{"id":16578,"date":"2026-09-02T11:38:02","date_gmt":"2026-09-02T08:38:02","guid":{"rendered":"https:\/\/alienroad.com\/google-bilgi-bankasi\/site-move-url-change\/"},"modified":"2026-09-05T02:45:49","modified_gmt":"2026-09-04T23:45:49","slug":"site-move-url-change","status":"publish","type":"ar_kb","link":"https:\/\/alienroad.com\/google-bilgi-bankasi\/site-move-url-change\/","title":{"rendered":"How to move a site"},"content":{"rendered":"<p>\n  This document describes how to change the URLs of existing pages on your site while minimizing<br \/>\n  negative impact on your Google Search results. Examples of this kind of site move include:\n<\/p>\n<ul>\n<li>URL changes from <code>HTTP<\/code> to <code>HTTPS<\/code>.<\/li>\n<li>\n    Domain name changes such as <code>example.com<\/code> to <code>example.net<\/code> or merging<br \/>\n    multiple domains or hostnames.\n  <\/li>\n<li>\n    URL paths changes: <code>example.com\/page.php?id=1<\/code> to<br \/>\n    <code>example.com\/widget<\/code>, or <code>example.com\/page.html<\/code> to<br \/>\n    <code>example.com\/page.htm<\/code><\/li>\n<\/ul>\n<aside class=\"note\">\n  <b>Not changing the URLs?<\/b> If you are making infrastructure changes such as changing your<br \/>\n  hosting,<br \/>\n  <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/changing-your-hosting\/\">start here instead<\/a>.<br \/>\n<\/aside>\n<h2 id=\"overview\" tabindex=\"-1\">Overview<\/h2>\n<ol>\n<li>\n    <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/site-move-url-change\/#general_recommendations_for_site_moves\"><b>General best practices for site moves<\/b><\/a>.<br \/>\n    Know what to expect, and how it might affect your users and rankings. If moving from HTTP<br \/>\n    to HTTPS, review the<br \/>\n    <a href=\"https:\/\/web.dev\/articles\/enable-https\" class=\"external-link\">best practices for HTTPS<\/a>.\n  <\/li>\n<li><a href=\"#prepare-new-site\"><b>Prepare the new site<\/b><\/a> and test it thoroughly.<\/li>\n<li>\n    <a href=\"#prepare-url-mapping\"><b>Prepare a URL mapping<\/b><\/a> from the current URLs to<br \/>\n    their corresponding new format.<\/li>\n<li>\n    <a href=\"#start-site-move\"><b>Start the site move<\/b><\/a> by configuring the server to<br \/>\n    redirect from the old URLs to the new ones.<\/li>\n<li><a href=\"#monitor\"><b>Monitor the traffic<\/b><\/a> on both the old and new URLs.<\/li>\n<\/ol>\n<h2 class=\"numbered\" id=\"general_recommendations_for_site_moves\" tabindex=\"-1\">\n  General best practices for site moves<br \/>\n<\/h2>\n<ul>\n<li>\n    <b>Split your move into smaller steps, if that makes sense for your site.<\/b><br \/>\n    If your site is large and it&#8217;s technically possible, we recommend initially moving just a<br \/>\n    piece of the site to test any effects on traffic and search indexing. After that you can<br \/>\n    move the rest of your site all at once or in chunks. When choosing the initial test section<br \/>\n    of the site, pick a section that changes less frequently and isn&#8217;t significantly affected by<br \/>\n    frequent or unpredictable events. Also keep in mind that while moving just one section is a<br \/>\n    great way to test your move, it&#8217;s not necessarily representative of a whole site move when<br \/>\n    it comes to Search. The more pages that you move, the more likely you&#8217;ll encounter<br \/>\n    additional problems to solve. Careful planning can minimize problems.\n  <\/li>\n<li>\n    <b>Change only one thing at a time<\/b><br \/>\n    Plan your changes to your site one after the other, not everything at the same time. For<br \/>\n    example, if you want to move your site to a new domain name, change your content management<br \/>\n    system (CMS), and update your site to use a new layout, do them one at a time: move to a new<br \/>\n    domain, then change your site&#8217;s layout.\n  <\/li>\n<li>\n    <b>Time your move to coincide with lower traffic, if possible.<\/b><br \/>\n    If your traffic is seasonal or dips on certain weekdays, it makes sense to move your site<br \/>\n    during the recurring traffic dips. This means that fewer people will be affected by<br \/>\n    potential issues that can happen during the site move, and more of your server&#8217;s resources<br \/>\n    can be dedicated to Googlebot crawling your site.\n  <\/li>\n<li>\n    <b>Expect temporary fluctuation in site ranking during the move.<\/b><br \/>\n    With any significant change to a site, you may experience ranking fluctuations while<br \/>\n    Google recrawls and reindexes your site. As a general rule: for medium-sized websites, it can<br \/>\n    take a few weeks or more for Google to gradually start showing the new URLs instead of the old<br \/>\n    ones (and for larger sites, even longer). The speed at which Googlebot and our systems discover<br \/>\n    and process moved URLs largely depends on the number of URLs and your server speed.<br \/>\n    <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/build-submit-sitemap\/\">Submitting a sitemap<\/a> can<br \/>\n    help make the discovery process quicker, and it&#8217;s fine to move your site in sections.\n  <\/li>\n<li>\n    <b>Don&#8217;t worry about link credit.<\/b><br \/>\n    <code>301<\/code> and<br \/>\n    <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/redirects-and-google\/#permanent-server-side-redirects\">other permanent redirects<\/a><br \/>\n    don&#8217;t cause a loss in<br \/>\n    <a href=\"https:\/\/wikipedia.org\/wiki\/PageRank\" class=\"external-link\">PageRank<\/a>.\n  <\/li>\n<li>\n    <b>Make use of Search Console.<\/b><br \/>\n    Search Console is your friend, especially during a site move. Verify data for each property<br \/>\n    separately in Search Console. Use the<br \/>\n    <a href=\"https:\/\/support.google.com\/webmasters\/answer\/7440203\" class=\"external-link\">Index Status report<\/a><br \/>\n    for a broad look. Use the<br \/>\n    <a href=\"https:\/\/support.google.com\/webmasters\/answer\/7451001\" class=\"external-link\">Sitemaps report<\/a><br \/>\n    to view how many URLs submitted in a sitemap have been indexed.\n  <\/li>\n<li>\n    <b>Be patient, give it time<\/b><br \/>\n    To consider a site move complete, Googlebot will have to visit every URL on your old and new<br \/>\n    site at least once. There are no fixed crawl frequencies; how fast Googlebot crawls depends<br \/>\n    on the size of your site, and the speed of crawling that&#8217;s possible. The move takes place on<br \/>\n    a per-URL basis.\n  <\/li>\n<\/ul>\n<h2 class=\"numbered\" id=\"prepare-new-site\" tabindex=\"-1\">Prepare the new site<\/h2>\n<p>\n  The details of site preparation vary for each site move, but typically you&#8217;ll do one or more<br \/>\n  of the following:\n<\/p>\n<ul>\n<li>\n    <b>Set up the CMS<\/b> (preferably the same as the old site used) and import the content from<br \/>\n    the old site.\n  <\/li>\n<li>\n    <b>Transfer images and downloads<\/b> (such as PDF documents) that you host.<br \/>\n    These might already be getting traffic from Google Search or links, and it&#8217;s useful to tell<br \/>\n    users and Googlebot about their new location.\n  <\/li>\n<li>\n    <b>For a move to HTTPS<\/b>, get and configure the required TLS certificates on your server.\n  <\/li>\n<li>\n<p>\n      <b>Set up a robots.txt for your new site<\/b> and make sure the rules in the new site&#8217;s<br \/>\n      robots.txt file correctly reflect the parts you want blocked from crawling.\n    <\/p>\n<p>\n      Note that some site owners block all crawling while in development. If you follow this<br \/>\n      strategy, make sure you prepare what the robots.txt file should look like once the site<br \/>\n      move starts. Likewise, if you use <code>noindex<\/code> rules during development, prepare a<br \/>\n      list of URLs from which you&#8217;ll remove the <code>noindex<\/code> rules when you start the<br \/>\n      site move.\n    <\/p>\n<\/li>\n<li>\n<p>\n      <b>Provide errors for deleted or merged content<\/b> if you&#8217;re not moving to the new site<br \/>\n      all your old content, make sure those URLs correctly return an HTTP <code>404<\/code> o<br \/>\n      <code>410<\/code> error response code on the new site.\n    <\/p>\n<\/li>\n<li>\n<p>\n      <b>Ensure correct Search Console settings<\/b> that may help with the site move.\n    <\/p>\n<p>\n      If you haven&#8217;t already,<br \/>\n      <a href=\"https:\/\/support.google.com\/webmasters\/answer\/9008080\" class=\"external-link\">verify<\/a><br \/>\n      both the old and new sites in Search Console. Be sure to verify all variants of both the<br \/>\n      old and new sites. For example, verify <code>www.example.com<\/code> and<br \/>\n      <code>example.com<\/code>, and include both the HTTPS and HTTP site variants if you use<br \/>\n      HTTPS URLs. Do this for both old and new sites.\n    <\/p>\n<ul>\n<li>\n<p><b>Review the Search Console verification<\/b><\/p>\n<p>\n          Make sure your Search Console verification will continue to work after the site move.<br \/>\n          If you&#8217;re using a different method of verification, keep in mind that verification<br \/>\n          tokens may be different when the URL changes.\n        <\/p>\n<p>\n          If you&#8217;re using the<br \/>\n          <a href=\"https:\/\/support.google.com\/webmasters\/answer\/9008080#html_verification\" class=\"external-link\">HTML file method<\/a><br \/>\n          to verify ownership of your site in Search Console, make sure you don&#8217;t forget to<br \/>\n          include your current verification file in your new copy of the site.\n        <\/p>\n<p>\n          Likewise, if you verify ownership with an include file that references the<br \/>\n          <a href=\"https:\/\/support.google.com\/webmasters\/answer\/9008080#meta_tag_verification\" class=\"external-link\"><code>meta<\/code> tag<\/a><br \/>\n          o<br \/>\n          <a href=\"https:\/\/support.google.com\/webmasters\/answer\/9008080#google_analytics_verification\" class=\"external-link\">Google Analytics<\/a><br \/>\n          to verify ownership, ensure the new CMS copy includes these as well.\n        <\/p>\n<\/li>\n<li>\n<p>\n          <b>Review any configured settings in Search Console<\/b> that you may have made for the<br \/>\n          old site, and  make sure the new site&#8217;s settings are updated to reflect those changes<br \/>\n          as well. For example:\n        <\/p>\n<ul>\n<li>\n            <a href=\"https:\/\/support.google.com\/webmasters\/webmasters\/answer\/48620\" class=\"external-link\">Crawl rate<\/a>:<br \/>\n            Set the crawl rate to &#8220;Let Googlebot determine&#8221; for both the old and new site.\n          <\/li>\n<li>\n            <a href=\"https:\/\/support.google.com\/webmasters\/webmasters\/answer\/2648487\" class=\"external-link\">Disavowed backlinks<\/a>:<br \/>\n            If you&#8217;ve uploaded a file to disavow links on your old site, we recommend that you<br \/>\n            re-upload it again using the Search Console account of the new site.\n          <\/li>\n<\/ul>\n<\/li>\n<li>\n<p>\n          <b>Clean up your recently purchased domain<\/b>; you&#8217;ll want to make sure it&#8217;s clean of<br \/>\n          any outstanding issues from the previous owner. Check the following settings:\n        <\/p>\n<ul>\n<li>\n            <a href=\"https:\/\/support.google.com\/webmasters\/answer\/9044175\" class=\"external-link\">Manual action<\/a><br \/>\n            for previous spam. If there are any manual actions applied to the new site, address<br \/>\n            any problems listed there and file a<br \/>\n            <a href=\"https:\/\/support.google.com\/webmasters\/answer\/35843\" class=\"external-link\">reconsideration request<\/a>.\n          <\/li>\n<li>\n            <a href=\"https:\/\/support.google.com\/webmasters\/answer\/9689846\" class=\"external-link\">Removed URLs<\/a>.<br \/>\n            Make sure that there aren&#8217;t any URL removals left over from the previous owner,<br \/>\n            especially a site-wide URL removal.\n          <\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n<li>\n<p>\n      <b>Use web analytics<\/b> to analyze usage on both the old and new sites. Web<br \/>\n      analytics software can help with this. Typically, web analytics configuration consists of<br \/>\n      a piece of JavaScript embedded in your pages. The details for tracking different sites<br \/>\n      varies depending on your analytics software and its logging, processing, or filtering<br \/>\n      settings. Check with your analytics software provider for help. Additionally, if you have<br \/>\n      been planning to make any configuration changes to your analytics software, now is a good<br \/>\n      time. If you use Google Analytics, consider creating a new profile for your new site if<br \/>\n      you want clean separation in your content reports.\n    <\/p>\n<\/li>\n<li>\n    <b>Ensure that your server has enough computing resources<\/b>: after a migration, Google<br \/>\n    will temporarily crawl your new site more heavily than usual. This is because your site<br \/>\n    redirects traffic from the old to the new site, and any crawls of the old site will be<br \/>\n    redirected to the new site, in addition to any other crawling. Ensure that your new site has<br \/>\n    sufficient capacity to handle the increased traffic from Google. If your site is<br \/>\n    particularly large, get in touch with your hosting providers and give them a heads-up about<br \/>\n    the site move you&#8217;re planning.\n  <\/li>\n<\/ul>\n<h2 class=\"numbered\" id=\"prepare-url-mapping\" tabindex=\"-1\">Prepare URL mapping<\/h2>\n<p>\n  It&#8217;s important to map your old site&#8217;s URLs to the URLs for the new site. This section<br \/>\n  describes a number of general approaches you can take to correctly assess the URLs on your two<br \/>\n  sites and facilitate mapping. The exact details of how you generate this mapping will vary<br \/>\n  depending on your current website infrastructure and the details of the site move.\n<\/p>\n<h3 id=\"determine-your-current-urls\" tabindex=\"-1\">Determine your old URLs<\/h3>\n<p>\n    In the simplest of site moves, you may not need to generate a list of your old URLs. For<br \/>\n    example, you could use a wildcard server-side redirect if you&#8217;re changing your site&#8217;s domain<br \/>\n    (for example, moving from <code>example.com<\/code> to <code>example.net<\/code>).\n<\/p>\n<p>\n  In more complex site moves, you will need to generate a list of old URLs and map them to their<br \/>\n  new destinations. How you get a listing of old URLs depends on your current website&#8217;s<br \/>\n  configuration, but here are some handy tips:\n<\/p>\n<ul>\n<li>\n    <b>Start with your important URLs<\/b>. To find them:<\/p>\n<ul>\n<li>\n        Look in your <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/sitemaps-overview\/\">sitemaps<\/a><br \/>\n        because it&#8217;s likely your most important URLs have been submitted in Search Console<br \/>\n        that way\n      <\/li>\n<li>\n        Check your server logs or analytics software for the URLs that get the most traffic\n      <\/li>\n<li>\n        Check the<br \/>\n        <a href=\"https:\/\/support.google.com\/webmasters\/answer\/9049606\" class=\"external-link\">Links to your site feature<\/a><br \/>\n        in Search Console for pages that have internal and external links\n      <\/li>\n<\/ul>\n<\/li>\n<li>\n    <b>Use your content management system,<\/b> which can typically provide a straightforward way to<br \/>\n    get a listing of all URLs that host content.\n  <\/li>\n<li>\n    <b>Check your server logs<\/b> for URLs that were visited at least once recently. Pick a<br \/>\n    time period that makes sense for your site, keeping in mind seasonal variation of traffic.\n  <\/li>\n<li>\n    <b>Include images and videos<\/b>\u2014Make sure that you include URLs of embedded content in<br \/>\n    your site move plans: videos, images, JavaScript, and CSS files. These URLs need to be<br \/>\n    moved in the same way as all other content on your website.\n  <\/li>\n<\/ul>\n<h3 id=\"create-a-mapping-of-old-to-new-urls\" tabindex=\"-1\">Create a mapping of old to new URLs<\/h3>\n<p>\n  Once you have the listing of old URLs, decide where each one should redirect to. How you store<br \/>\n  this mapping depends on your servers and the site move. You might use a database, or configure<br \/>\n  some URL rewriting rules on your system for common redirect patterns.\n<\/p>\n<h3 id=\"update-url-annotations\" tabindex=\"-1\">Update all URL details on the new site<\/h3>\n<p>\n  Once you have your URL mapping defined, you&#8217;ll want to do three things to get the pages ready<br \/>\n  for receiving traffic.\n<\/p>\n<ol>\n<li>\n    <b>Update annotations<\/b> to point to the new URLs in the HTML or sitemaps entry for each<br \/>\n    page:<\/p>\n<ol>\n<li>\n        Each new URL should have a self-referencing<br \/>\n        <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/specify-canonical\/\"><code>rel=\"canonical\" &lt;link&gt;<\/code><\/a> tag.\n      <\/li>\n<li>\n        If the site you moved has multilingual or multinational pages annotated using<br \/>\n        <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/localized-versions\/\"><code>rel-alternate-hreflang<\/code> annotations<\/a>,<br \/>\n        be sure to update the annotations to use the new URLs.\n      <\/li>\n<\/ol>\n<\/li>\n<li>\n    <b>Update internal links.<\/b><br \/>\n    Change the internal links on the new site from the old URLs to the new URLs. You can use the<br \/>\n    mapping generated earlier to help find and update the links as needed.\n  <\/li>\n<li>\n    <b>Save the following lists for your final move<\/b>:<\/p>\n<ul>\n<li>\n        A sitemap file containing the new URLs in the mapping. See our documentation about<br \/>\n        <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/build-submit-sitemap\/\">building a sitemap<\/a>.\n      <\/li>\n<li>\n        A list of sites linking to your old URLs. You can find the<br \/>\n        <a href=\"https:\/\/support.google.com\/webmasters\/answer\/9049606\" class=\"external-link\">links to your site<\/a><br \/>\n        in Search Console.\n      <\/li>\n<\/ul>\n<\/li>\n<\/ol>\n<h3 id=\"a-note-about-redirects\" tabindex=\"-1\">Plan your redirect strategy<\/h3>\n<p>\n  Once you have a mapping and your new site is ready, the next step is to plan your redirect<br \/>\n  strategy. We recommend server side<br \/>\n  <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/redirects-and-google\/\">permanent redirects<\/a><br \/>\n  from the old URLs to the new URLs as you indicated in your mapping. Check with your server<br \/>\n  administrator (or hosting company) about what kind of server side redirects you can<br \/>\n  technically do. It might be redirect rules in your <code>.htaccess<\/code> files if your server<br \/>\n  is using <a href=\"https:\/\/httpd.apache.org\/\" class=\"external-link\">Apache HTTP server<\/a> o<br \/>\n  redirect functions in your CMS.\n<\/p>\n<p>\n  If none of the server side redirect setups are possible, you can fall back to client side<br \/>\n  redirects as a last resort.\n<\/p>\n<p><b>Decide how you will move your site<\/b> &ndash; all at once, or in sections:<\/p>\n<ul>\n<li>\n    <b>Small or medium sites:<\/b> We recommend moving all URLs on your site simultaneously<br \/>\n    instead of moving one section at a time. This helps users interact with the site better in<br \/>\n    its new form, and helps our algorithms detect the site move and update our index faster.\n  <\/li>\n<li>\n    <b>Large sites:<\/b> You can choose to move larger sites one section at a time. This can make<br \/>\n    it easier to monitor, detect, and fix problems faster.\n  <\/li>\n<\/ul>\n<p>Keep in mind the following:<\/p>\n<ul>\n<li>\n    <b>Use server side permanent redirects<\/b> if technically possible. Although Googlebot<br \/>\n    supports<br \/>\n    <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/redirects-and-google\/\">several kinds of redirects<\/a>, we<br \/>\n    recommend that you use HTTP permanent redirects if possible, such as <code>301<\/code> and<br \/>\n    <code>308<\/code>.\n  <\/li>\n<li>\n    <b>Avoid chaining redirects.<\/b> While Googlebot can<br \/>\n    <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/how-http-status-codes-affect-googles-crawlers\/#3xx-redirection\" class=\"external-link\">follow up to 10 hops<\/a><br \/>\n    in a &#8220;chain&#8221; of  multiple redirects (for example, Page 1<br \/>\n    <span aria-label=\"and then\">&gt;<\/span> Page 2<br \/>\n    <span aria-label=\"and then\">&gt;<\/span> Page 3), we advise redirecting to the final<br \/>\n    destination directly. If this is not possible, keep the number of redirects in the chain<br \/>\n    low, ideally no more than 3 and fewer than 5. Chaining redirects adds latency for users,<br \/>\n    and not all user agents and browsers support long redirect chains.\n  <\/li>\n<\/ul>\n<h2 class=\"numbered\" id=\"start-site-move\" tabindex=\"-1\">Start the site move<\/h2>\n<p>\n  Once the URL mapping is accurate and you finalized the plan for how you&#8217;re going to<br \/>\n  redirect, you&#8217;re ready to move.\n<\/p>\n<ol>\n<li>\n    <b>Implement or turn on the redirects<\/b>: depending on your redirect<br \/>\n    strategy, this might mean you push an update to your server configuration files or you<br \/>\n    update your CMS, likely with custom code.<\/p>\n<aside class=\"tip\">\n      <b>Avoid irrelevant redirects<\/b><\/p>\n<p>\n        Don&#8217;t redirect many old URLs to one irrelevant single URL destination, such as the home page of the<br \/>\n        new site. This can confuse users and might be treated as a<br \/>\n        <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/troubleshoot-google-search-crawling-errors\/#soft-404-errors\"><code>soft 404<\/code> error<\/a>.<br \/>\n        However, if you have consolidated content previously hosted on multiple pages to a new<br \/>\n        single page, you can redirect the older URLs to that new, consolidated page.\n      <\/p>\n<\/aside>\n<\/li>\n<li>\n    <b><br \/>\n      Check the <code>rel=\"canonical\"<\/code> <code>link<\/code> annotations and<br \/>\n      <code>robots<\/code> <code>meta<\/code> rules:<br \/>\n    <\/b><br \/>\n    Once the redirects are active, ensure that the <code>rel=\"canonical\"<\/code><br \/>\n    <code>link<\/code> annotations on the new site are using the new URLs. Similarly, if you<br \/>\n    added <code>noindex<\/code> <code>robots<\/code> <code>meta<\/code> rules to the new site to<br \/>\n    avoid prematurely indexing the new URLs, make sure to update them.\n  <\/li>\n<li>\n    <b>Test the redirects.<\/b> You can use the<br \/>\n    <a href=\"https:\/\/support.google.com\/webmasters\/answer\/9012289\" class=\"external-link\">URL Inspection Tool<\/a><br \/>\n    for testing individual URLs, or command line tools or scripts to test large numbers of URLs.\n  <\/li>\n<li>\n    <b><br \/>\n      If you&#8217;re changing domain names or subdomains, submit a<br \/>\n      <a href=\"https:\/\/support.google.com\/webmasters\/answer\/9370220\" class=\"external-link\">Change of Address<\/a><br \/>\n      in Search Console for the old site<\/b>.<\/p>\n<p>\n        You only need this tool when moving from one domain or subdomain to another (such as<br \/>\n        <code>example.com<\/code> to <code>example.net<\/code>, or <code>a.example.com<\/code> to<br \/>\n        <code>b.example.com<\/code>). You don&#8217;t need it for HTTP to<br \/>\n        HTTPS moves, switching between www and non-www on the same domain, or moving paths<br \/>\n        within the same domain.\n      <\/p>\n<aside class=\"note\">\n      <b>For domain migrations<\/b>: If you&#8217;re moving to a new domain name, make sure to<br \/>\n      submit <b>Change of Address<\/b> requests for all verified variants of the old domain<br \/>\n      (including subdomains and www\/non-www versions) to the new domain (for example, from<br \/>\n      <code>en.example.com<\/code>, <code>www.example.com<\/code>,<br \/>\n      and <code>example.com<\/code> to <code>new-example.net<\/code>), even if you&#8217;re not actively<br \/>\n      using these variants. Ensure that you have all of these variants verified in Search Console.<br \/>\n    <\/aside>\n<\/li>\n<li>\n<p>\n      <b>Keep the redirects for as long as possible<\/b>, generally at least 1 year.<br \/>\n      This timeframe allows Google to transfer all signals to the new URLs, including recrawling<br \/>\n      and reassigning links on other sites that point to your old URLs.\n    <\/p>\n<p>\n      From users&#8217; perspective, consider keeping redirects indefinitely. However, redirects are<br \/>\n      slow for users, so try to update your own links and any high-volume links from other<br \/>\n      websites to point to the new URLs.\n    <\/p>\n<\/li>\n<li>\n    <b>Submit the new sitemap in Search Console<\/b>. This will help Google learn about the new<br \/>\n    URLs. At this point you can remove your old sitemap, since Google will use the new sitemap<br \/>\n    going forward.\n  <\/li>\n<\/ol>\n<p>\n  The time it takes Googlebot and our systems to discover and process all URLs in the site<br \/>\n  move depends on how fast your servers are and how many URLs are involved. As a general rule,<br \/>\n  a small to medium-sized website can take a few weeks for most pages to move, and larger sites<br \/>\n  take longer. The speed at which Googlebot and our systems discover and process moved URLs<br \/>\n  depends on the number of URLs and the server speed.\n<\/p>\n<aside class=\"tip\">\n  Note that the visibility of your content in Search may fluctuate temporarily during the move.<br \/>\n  This is normal and a site&#8217;s rankings will settle down over time.<br \/>\n<\/aside>\n<h3 id=\"update-incoming-links\" tabindex=\"-1\">Update links<\/h3>\n<p>\n  Immediately after the site move is started, try to update as many links as possible to improve<br \/>\n  the user experience and reduce your server load. These include:\n<\/p>\n<ul>\n<li>\n    Internal links: based on the URL mapping you previously created, replace all URLs that<br \/>\n    pointed to your own pages.\n  <\/li>\n<li>\n    External links: Try to contact the sites in the saved list of sites linking to your current<br \/>\n    content, asking them to update their links to your new site. Consider prioritizing your<br \/>\n    efforts by the number of inbound visits for each link.\n  <\/li>\n<li>Profile links such as from Facebook, Twitter, and LinkedIn.<\/li>\n<li>Ad campaigns to point to the new landing pages.<\/li>\n<\/ul>\n<h2 class=\"numbered\" id=\"monitor\" tabindex=\"-1\">Monitor traffic<\/h2>\n<p>\n  Once you&#8217;ve started the site move, monitor how the user and crawler traffic changes on the new<br \/>\n  site and also the old site. Ideally the traffic on the old site will go down, while on the new<br \/>\n  site the traffic goes up. You can monitor user and crawler activity on the sites with<br \/>\n  <a href=\"https:\/\/search.google.com\/search-console\/\" class=\"external-link\">Search Console<\/a><br \/>\n  and other tools.\n<\/p>\n<h3 id=\"search-console\" tabindex=\"-1\">Use Search Console to monitor traffic<\/h3>\n<p>Many features of Search Console help you monitor a site move, including:<\/p>\n<ul>\n<li>\n    <a href=\"https:\/\/search.google.com\/search-console\/sitemaps\" class=\"external-link\">Sitemaps<\/a>:<br \/>\n    Submit the two sitemaps you saved earlier from the mapping. Initially, the sitemap<br \/>\n    containing the new URLs would have zero pages indexed, while the sitemap of the old URLs<br \/>\n    would have many pages indexed. Over time the number of pages indexed from the old URLs<br \/>\n    sitemap would drop to zero with a corresponding increase of indexing of the new URLs. Note<br \/>\n    that Search Console may show warnings for the sitemap that contains the old URLs about the<br \/>\n    URLs redirecting; this is normal and you can ignore these warnings: you are, in fact, moving<br \/>\n    to new URLs after all.\n  <\/li>\n<li>\n    <a href=\"https:\/\/search.google.com\/search-console\/index\" class=\"external-link\">Index Coverage report<\/a>:<br \/>\n    The graphs would reflect the site move, showing a drop in indexed URL counts on the old site<br \/>\n    and an increase of indexing on the new site. Check regularly for any unexpected crawl<br \/>\n    errors.\n  <\/li>\n<li>\n    <a href=\"https:\/\/search.google.com\/search-console\/performance\/search-analytics\" class=\"external-link\">Search queries<\/a>:<br \/>\n    As more pages of the new site get indexed and start ranking, the search queries<br \/>\n    reports would start showing the URLs on the new site getting search impressions and clicks.\n  <\/li>\n<\/ul>\n<h3 id=\"use-other-tools-to-monitor-traffic\" tabindex=\"-1\">Use other tools to monitor traffic<\/h3>\n<p>\n  Keep an eye on your server access and error logs. In particular, check for crawling by<br \/>\n  Googlebot, any URLs that unexpectedly return HTTP error status codes, and normal user traffic.\n<\/p>\n<p>\n  If you installed any web analytics software on your site, or if your CMS provides analytics,<br \/>\n  it&#8217;s also recommended that you review traffic this way so that you can see the progress of<br \/>\n  traffic from your old to new site. In particular, Google Analytics offers real-time reporting,<br \/>\n  and this is a handy feature to use during the initial site move phase. You should expect to<br \/>\n  see traffic drop on the old site and rise on the new site.\n<\/p>\n<h2 id=\"more-resources\" tabindex=\"-1\">More resources<\/h2>\n<p>\n  Site migrations can be overwhelming and complicated, so there are lots of takes on how to<br \/>\n  proceed. We found<br \/>\n  <a href=\"https:\/\/www.aleydasolis.com\/en\/search-engine-optimization\/seo-for-web-migrations\/\" class=\"external-link\">Aleyda Solis&#8217; site migration checklists<\/a><br \/>\n  particularly useful, and also the<br \/>\n  <a href=\"https:\/\/www.screamingfrog.co.uk\/how-to-use-the-seo-spider-in-a-site-migration\/\" class=\"external-link\">Screaming Frog tool guide<\/a> for site migrations.\n<\/p>\n<p>\n  <b>If you&#8217;re stuck at any point, look for help on Google Search Central.<\/b><br \/>\n  There is plenty of good advice on<br \/>\n  <a href=\"https:\/\/developers.google.com\/search\/help\">our help page<\/a> and specific cases answered in<br \/>\n  our<br \/>\n  <a href=\"https:\/\/support.google.com\/webmasters\/community\" class=\"external-link\">user forums<\/a>.<br \/>\n  If you can&#8217;t find an answer, you can ask a question to one of our Google Search specialists<br \/>\n  during our<br \/>\n  <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/submit-a-question-idea-for-google-seo-office-hours\/\">SEO office hours<\/a>.\n<\/p>\n<h2 id=\"troubleshooting\" tabindex=\"-1\">Troubleshooting your site move<\/h2>\n<p>\n  Here are some common mistakes when migrating a site with URL changes (including HTTP to<br \/>\n  HTTPS). These mistakes can prevent your new site from being indexed completely.\n<\/p>\n<table class=\"responsive\">\n<tbody>\n<tr>\n<th colspan=2>Common mistakes<\/th>\n<\/tr>\n<tr>\n<td>\n<h3 id=\"noindex-or-robots.txt-blocks\" tabindex=\"-1\"><code>noindex<\/code> or robots.txt blocks<\/h3>\n<\/td>\n<td>\n<p>\n          Don&#8217;t forget to remove any <code>noindex<\/code> or robots.txt blocks that were only<br \/>\n          needed for the migration.\n        <\/p>\n<p>\n          It&#8217;s fine if you don&#8217;t have a robots.txt file on your site, but be sure to return a<br \/>\n          proper <code>404<\/code> HTTP status code if the robots.txt file doesn&#8217;t exist.\n        <\/p>\n<p><b>To test:<\/b><\/p>\n<ul>\n<li>\n            Examine your robots.txt file in your HTTPS site and see if anything needs to be<br \/>\n            changed.\n          <\/li>\n<li>\n            Use the<br \/>\n            <a href=\"https:\/\/support.google.com\/webmasters\/answer\/9012289\" class=\"external-link\">URL inspection tool<\/a><br \/>\n            for any pages that seem to be missing from Google in the new site.\n          <\/li>\n<\/ul>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<h3 id=\"incorrect-redirects\" tabindex=\"-1\">Incorrect redirects<\/h3>\n<\/td>\n<td>\n<p>\n          Check your redirects from the old site to the new one. We frequently see people<br \/>\n          redirecting to the wrong (non-existent) URLs on the new site.\n        <\/p>\n<p>\n          You can use Search Console to see if there are an unusually high number of &#8220;Not found&#8221;<br \/>\n          errors reported, or you can use other tools such as<br \/>\n          <a href=\"https:\/\/www.screamingfrog.co.uk\/seo-spider\/\" class=\"external-link\">Screaming Frog<\/a><br \/>\n          to crawl your own site and see if the redirects work as expected.\n        <\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<h3 id=\"other-crawl-errors\" tabindex=\"-1\">Other crawl errors<\/h3>\n<\/td>\n<td>\n<p>\n          Examine the <a href=\"https:\/\/search.google.com\/search-console\/index\" class=\"external-link\">Index Coverage report<\/a><br \/>\n          for a spike in other errors on your new site during migration events.\n        <\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<h3 id=\"insufficient-server-capacity\" tabindex=\"-1\">Insufficient server capacity<\/h3>\n<\/td>\n<td>\n<p>\n          After a migration, Google will crawl your new site more heavily than usual. This is<br \/>\n          because your site redirects traffic from the old to the new site, and any crawls of<br \/>\n          the old site will be redirected to the new site, in addition to any other crawling.<br \/>\n          Ensure that your site has sufficient capacity to handle the increased traffic from<br \/>\n          Google.\n        <\/p>\n<\/td>\n<\/tr>\n<tr>\n<td>\n<h3 id=\"not-updating-sitemaps\" tabindex=\"-1\">Not updating sitemaps<\/h3>\n<\/td>\n<td>\n<p>Be sure that your sitemaps are all updated with the new URLs.<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n","protected":false},"excerpt":{"rendered":"<p>Learn how to change the URLs of existing site pages, including domain name changes. Explore moving a website with little impact on search results.<\/p>\n","protected":false},"menu_order":52,"template":"","meta":{"footnotes":""},"ar_kb_kategori":[692],"ar_kb_etiket":[588,570,559],"class_list":["post-16578","ar_kb","type-ar_kb","status-publish","has-post-thumbnail","hentry","ar_kb_kategori-site-moves-site-moves-and-changes","ar_kb_etiket-migration","ar_kb_etiket-redirects","ar_kb_etiket-search-console"],"_links":{"self":[{"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb\/16578","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb"}],"about":[{"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/types\/ar_kb"}],"version-history":[{"count":2,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb\/16578\/revisions"}],"predecessor-version":[{"id":25573,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb\/16578\/revisions\/25573"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/media\/26341"}],"wp:attachment":[{"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/media?parent=16578"}],"wp:term":[{"taxonomy":"ar_kb_kategori","embeddable":true,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb_kategori?post=16578"},{"taxonomy":"ar_kb_etiket","embeddable":true,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb_etiket?post=16578"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}