Copy of the sitemap in old XML format and generation of the new one We will make a copy of the old sitemap in XML format and prepare it to upload to the server at the time of publication. This file will serve to indicate to Google the need to continue tracking these old URLs in order for it to carry out its migration, in addition to allowing us to track the progress of the migration. The new sitemap will also be generated in XML format as in any other properly optimized site, which will help the new URLs to be indexed quickly.
Report of SEO indicators phone database prior to migration At the time of migration, just before proceeding with it we must take a picture of the status of the site in terms of: Coverage status, both indexing status and errors. KPIs of the site, technical and business. Indicators of authority. To do this, we will set up a control panel with the status and trend of these indicators that will help us to monitor the migration once it has started. At this time, we will be able to assess success and detect problems early. Tasks for publication This phase of the migration will be executed immediately after the new site is published. It is about redoing the checks made in pre-production, but this time in production.
Review of how redirects work After publishing, the correct operation of the implemented redirections is checked again in production . An attempt is made to check as many old URLs as possible, prioritizing those with the highest traffic performance. If erroneous redirects are detected, we will have to report them immediately so that they can be implemented as soon as possible. Let's remember that for each URL tested, ideally, there should be only one 301 redirect to the planned URL.
1 post • Page 1 of 1