A When the site is closed...

[kexej28769@nongnue]

While the new site is replacing the old site, chances are the live site will be temporarily down. Downtime should be kept to a minimum, but when this happens, the web server should respond to any URL request with a 503 (Service Unavailable) server. This will tell search engine crawlers that the site is temporarily down for maintenance so they can come back to crawl the site later.

If the site is down for too long without returning a 503 server response and search engines crawl the website, organic search visibility will be negatively affected and recovery will not be immediate armenia number data the site is back up. In addition, when the website is temporarily down, it should also display an informational hold page that informs users that the website is temporarily down for maintenance.

Technical space testing
As soon as the new site goes live, take a quick look at it:

robots.txt file to ensure that search engines are not blocked from crawling.
Top pages redirect (for example, are requests for the top pages of the old site redirected correctly?)
Top pages Canonical tags
Server responses for top pages
Noindex/nofollow directives, if they are unintentional.
Spot checks need to be done on both mobile and desktop sites, unless the site is fully responsive.

Search Console actions
The following activities should take place as soon as the new website goes live:

Test and upload XML sitemap
Set the preferred domain location (w
Configure URL parameters to quickly deal with any potential duplicate content issues.
Upload the disapproved file (if applicable)
Use the change of address tool (if changing domains)
Pro Tip: Use the "Fetch as Google" feature for each different type of page (e.g. homepage, category, subcategory, product page) to ensure that Googlebot can render the pages without any issues. Review any reported blocked resources and don't forget to use Fetch and Render for desktop and mobile, especially if the mobile website is not responsive.



Blocked resources prevent Googlebot from rendering the page content.


Step 5: Post-launch review
After the new site goes live, a new round of in-depth testing should be conducted. These are mostly the same as those mentioned in the "Phase 3: Pre-launch Testing" section.

However, the main difference during this stage is that you now have access to a lot more data and tools. Don’t underestimate the amount of effort you have to put in during this stage, as any issues you encounter now directly affect the site’s performance in the SERPs. On the other hand, the sooner an issue is identified, the sooner it will be resolved.