Website visitors like to feel safe, the safer they feel, the longer they stay on your site and the more likely they are to come to you for your products or services. Fairly recently, the various browsers (Chrome, Firefox, Edge, etc) have begun to flag sites that don’t have SSL certificates as ‘Not Secure’, placing a warning in the address bar. This is inevitably going to worry some of your visitors, but is reasonably simple to sort out.
SSL provides secure, encrypted connections between networked computers; between the web server and the user’s web browser software. This is particularly important on eCommerce sites, where personal data linked with financial information is being transmitted. To apply SSL encryption, you need an SSL certificate, these are available from a number of certificate authorities and come in various ‘strengths’ – the more secure they are, the more expensive they become.
If you’re running an eCommerce site, most payment companies like PayPal, Stripe, Authorize.net, etc will require you to have a secure connection before accepting payments.
For most WordPress sites a free SSL certificate is more than enough, the browser software will show the secure padlock in the address bar and your visitors will feel safe. But if you’re going to handle credit card payments yourself, you’ll need to talk to your server administrator and one of the certificate authorities – here is a good place to read more.
If all you’re looking for is a padlock in the browser address bar and an https:// address, then you just need a basic certificate. These can be applied in a number of ways …
Once you’ve applied your SSL certificate, you may well have to tell WordPress to serve up the site with an https address, otherwise it’ll just carry on serving the pages ‘insecurely’. First, test to see whether you need to make any changes by opening the site in your browser. If the padloack appears that’s a good first step. Now try manually entering the site address with http:// at the front. Hopefully, it’ll autmatically redirect and you’ll be served the pages with the padlock showing. Job done. If not, read on …
By far the simplest way to force an SSL certificated WordPress site to serve up its pages via https is to use a plugin. There are a number of plugins that can do this. One of the most popular is Really Simple SSL, it takes away all the hassle, click that link, install and follow the instructions. Once you’ve done that, check the site is showing a padlock and redirecting to https when you enter the address with an http at the front.
Hopefully your site is now reporting as secure. There are a few cases where some things will still need tweaking – For example, if you set your site up and had it running before you applied the SSL certificate and changes, your theme and possibly plugins, may have http links in their settings; your logo and/or favicon for example. Go through all your settings, changing any http references to https, save and reload the site. If you’re still having problems, give us a call, it’s often a simple fix and we’re great at spotting such things.
Whilst the main point of having an SSL certificate is to provide encrypted traffic, according to most SEO experts, secured sites seem to rank higher. This does make sense; people will naturally visit a secure site over a non-secure one and will stay longer, Google will ‘see’ this via its analytics engine and will therefore rank the site more highly.
Necessary cookies are absolutely essential for the website to function properly. These cookies ensure basic functionalities and security features of the website, anonymously.
Cookie | Duration | Description |
---|---|---|
cookielawinfo-checbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checkbox-advertisement | 1 year | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Advertisement". |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
laravel_session | laravel uses laravel_session to identify a session instance for a user, this can be changed | |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
XSRF-TOKEN | 2 hours | The cookie is set by Wix website building platform on Wix website. The cookie is used for security purposes. |
__cfduid | 1 month | The cookie is used by cdn services like CloudFare to identify individual clients behind a shared IP address and apply security settings on a per-client basis. It does not correspond to any user ID in the web application and does not store any personally identifiable information. |
Functional cookies help to perform certain functionalities like sharing the content of the website on social media platforms, collect feedbacks, and other third-party features.
Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.
Cookie | Duration | Description |
---|---|---|
YSC | session | This cookies is set by Youtube and is used to track the views of embedded videos. |
_gat | 1 minute | This cookies is installed by Google Universal Analytics to throttle the request rate to limit the colllection of data on high traffic sites. |
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.
Cookie | Duration | Description |
---|---|---|
_ga | 2 years | This cookie is installed by Google Analytics. The cookie is used to calculate visitor, session, campaign data and keep track of site usage for the site's analytics report. The cookies store information anonymously and assign a randomly generated number to identify unique visitors. |
_gid | 1 day | This cookie is installed by Google Analytics. The cookie is used to store information of how visitors use a website and helps in creating an analytics report of how the website is doing. The data collected including the number visitors, the source where they have come from, and the pages visted in an anonymous form. |
Advertisement cookies are used to provide visitors with relevant ads and marketing campaigns. These cookies track visitors across websites and collect information to provide customized ads.
Cookie | Duration | Description |
---|---|---|
IDE | 1 year 24 days | Used by Google DoubleClick and stores information about how the user uses the website and any other advertisement before visiting the website. This is used to present users with ads that are relevant to them according to the user profile. |
test_cookie | 15 minutes | This cookie is set by doubleclick.net. The purpose of the cookie is to determine if the user's browser supports cookies. |
VISITOR_INFO1_LIVE | 5 months 27 days | This cookie is set by Youtube. Used to track the information of the embedded YouTube videos on a website. |
Other uncategorized cookies are those that are being analyzed and have not been classified into a category as yet.
Cookie | Duration | Description |
---|---|---|
CONSENT | 16 years 9 months 6 days 9 hours 9 minutes | No description |