In what cases is it necessary to transfer a working site

• Moving to HTTPS. A secure connection is one of the most important aspects of the site. To transfer a site to HTTPS, correctly without losing positions and traffic is quite realistic.
• The structure of the resource has changed. Any adjustments to the structure may entail errors, the price of which – the fallout of pages from the index and a critical sag in traffic.
• The resource came under the filter of search engines. The problem, which can eliminate the transfer of the site to another domain. Made by a specialist.
• Move to a new CMS to optimize the resource.
• Move the site to another hosting.

Accompanying the relocation of the site by a specialist will avoid problems and losses.

What does the specialist before the transfer:

• Analysis of traffic sources
• Identifies significant sections and documents of the site;
• Technical audit of the site, to identify problems that should not be transferred further.

Fixing the state of the site at the time of the move will allow you to understand what key points to check and keep track of after the process is complete.

When the site has moved to HTTPS or a new CMS specialist checks:

• Presence and correctness of indexing management files robots.txt and sitemap.xml;
• Preservation and correctness of the addressing of the resource documents;
• Correctness of the basic meta tags and content;
• The absence of technical problems that interfere with the indexing of documents on the site;
• Controls the process of indexing;
• The work of the elements of statistical collection and proper tracking of targeted user actions in the resource.

We need to transfer the site – discuss the problem

What is important when transferring a site to save positions and traffic

• Not to lose the link mass. Save the volume of external links leading to the resource, given the thematic relationship of the acceptor and donor documents.
• Do not allow errors in the work of the site. Technical failures often generate a large number of pages, giving 404 errors. The presence of duplicates and 404 errors leads to problems with indexation.
• Save the settings of all pages, including meta tags and header structure, micro markup.
• Correctly reconfigure all systems based on the document address: linking blocks, canonical page addresses, interactive forms.
• Keep the correct configuration of all elements for collecting statistics and tracking users’ targeted actions on the site.

The main errors in the transfer of the site

The most common problem is the loss of traffic received from search engines.

The main causes:

Incorrectly configured redirects – as a result, the link mass and weight of documents is not inherited from the old resource, which affects the ranking of new documents, and as a consequence, the site loses position.
“Closing” robots.txt copied from test hosting.

When the site is moved from the test account, the robots.txt file, which completely blocks indexing by search engines, is moved to the main account. As a result, the site falls out of the index database, loses positions and recovery can take quite a long time.

Third-party scripts or services that do not use a secure connection via http after the move to https will be blocked. Therefore, when moving the site to https protocol, all third-party scripts or services must also work on a secure connection.
When you transfer a resource to the https protocol have not been corrected image addresses used on the site, which will also lead to problems.
Errors in the templates and meta tags. Lead to an incorrect display of text and headings that may lead to problems in ranking documents on the site in issuing search engines.

Templates may have lost elements of micro-parsing, incorrectly displayed or absent blocks of linking.

Canonical pages are incorrectly configured. This is an important element especially for large portals and online stores.

During our work we have supported moving of resources for different reasons, different volumes – from online stores to small sites – we have managed to work out a faultless algorithm of transition, which allows to save the traffic to the resource.