SSL implementation

SSL implementation is switching a site from insecure http to secure https (the “padlock” in the address bar). We install the SSL certificate, set up the redirect from http to https, remove “mixed content” (when some images or scripts load over the old http and break the “padlock”), and update internal links and the sitemap. The certificate itself is now often free (Let’s Encrypt), and many hostings install it in one click — but “installing a certificate” and “correctly switching the site to https” are different things. After a one-click install the site often opens, but: on some pages the “padlock” disappears, forms or the cart stop working, integration with ads and analytics breaks, and http and https duplicates get into search. We switch the site to https completely and verify there are no such problems. If you have a simple site and your hosting already gives SSL in one click — we will honestly say that you can manage on your own. Browsers mark http sites as “Not secure”, and search engines prefer https. Picture this: a visitor sees “Not secure” next to the address before paying and closes the site — after SSL implementation there is a “padlock” and trust. The base price starts from 7,000 ₽: for a simple site the work is inexpensive, while on online stores, multi-domain setups and old CMSs with plugins there is more of it — and that is where a higher price is justified.

• The browser says “Not secure” — visitors do not trust payments, abandon the cart, and you get fewer leads.
• The site is on http — search engines rank it lower than secure competitors.
• The certificate was installed in one click, but the “padlock” is not lit on some pages — mixed content breaks the protection, and the warning is still visible.
• After switching to https, duplicates appeared (http and https versions) — search gets confused, rankings get “smeared”.

• Installing the SSL certificate (we help choose a free or paid one for the task)
• Switching the site to https with redirection of all http traffic (301)
• Removing mixed content — the “padlock” is lit on all pages, forms and the cart work
• Updating internal links, sitemap and robots to https
• A check: forms, payments, analytics and ads work over https
• Setting up HSTS (the browser opens the site over https right away, without trying http) and verifying the certificate
• Making sure no http/https duplicates appear in search

• Visitors trust payments and forms — fewer abandoned carts and lost leads
• A plus for SEO — search engines prefer https
• Visitor data (forms, payments) is transmitted in encrypted form
• No duplicates or protection errors — the switch to https went cleanly, without losing traffic

• You leave a request and give access to the site and the hosting
• We install the certificate, switch to https, remove mixed content
• We set up the redirects, check forms/payments/analytics and hand it over

• SSL is free — why pay for implementation?

  The certificate itself is often free (Let’s Encrypt), and installing it in one click is only half the job. The problem is that after such an install many sites lose the “padlock” on some pages, their forms and cart break, analytics and ads fall off, and http/https duplicates get into search. You pay for correctly switching to https as a whole: redirects, removing mixed content, updating links and the sitemap, and checking that everything works. If the site is simple and the install went without problems — we will honestly say that you can manage on your own.

• What is “mixed content” and why is the “padlock” not lit?

  It is when a page opens over https, but part of its content (images, scripts, styles) loads over the old http. The browser considers such a page not fully secure and does not show the “padlock” or complains, and some elements may not work. We find and switch all the content to https so that the protection works on all pages.

• Will the switch to https affect rankings?

  In the long run, positively: https is a ranking factor. During the switch it is important to set up the http→https redirects correctly and remove duplicates, otherwise temporary fluctuations are possible. That is exactly what we do carefully, so the switch goes without losses.