20 Things You Should Check On Your Drupal Website before the Launch

Tweet When you’re building a website, it’s critical you test it thoroughly before handing it over to the customer. The matter is that any significant issue discovered by your client can reduce their trust to your company and even cost you sales if that problem was so serious that to prevent users from interaction on your site. If you don’t want this to happen to your Drupal project, check you’ve tested every issue of the following on it as these are often left out from testers’ attention. If you enabled commenting on your site, see that the link to your private policy is there as well. Make sure your 403 and 404 error pages show the appropriate message and are properly customized. If you are dealing with Drupal’s settings of content type, you should turn off the preview, see that there are the right menu and revisions enabled for every content type. Your Xmlsitemap has to be configured as well as updating together with content changes. Set your Pathauto patterns for all content types appropriately. Ensure there are meta descriptions and titles on your site and that these are available for home page, views and common content pages. Based on your current client support, make sure the client has all the necessary permissions, but not too many of them. Sidebar block promos, rotators and other unindexed nodes should be correctly blocked by Robots.txt file. Unless you’re building a community site, see that only admins are able to create new accounts. Set user passwords to strong passwords prior to the launch. Test content is to be removed carefully. Make sure your Google Analytics is working well. Utilize its real time function for anonymous user tracking, or block the client and IP. Disable all the unused and development modules. Enabled the proper JS and CSS aggregation before the site testing. Unless you are using Varnish, Drupal cache has to be enabled. Check the error log and resolves any related issues. If necessary, turn error reporting to ‘NOT show’ on the screen of production sites, or make it write to the log. See that the site search is working and finely themed. Clear your Drupal caches. Launch your broken link checker and ensure there are no broken links on your production site. Link Checker is good for this. Your production QA checklist may include much more items, but the items put above are those things to check first, before moving to browser testing, SEO or other aspects that need your attention before the launch of a Drupal project.