<link rel = "stylesheet" id = "gtranslate-style-css" href = "https://websetnet.b-cdn.net/wp-content/plugins/gtranslate/gtranslate-style24.css" type = "tekst / css "media =" all ">

Should You Switch Your Site to HTTPS? Here’s Why You Should or Shouldn’t

sikker

Der er to typer af SEO'er:

Those who love the technical stuff…

…and those who hate it.

If you fall into the first category, you’re probably already experienced with HTTPS.

If you’re in the second category of SEOs, you might be a lidt skræmt af det.

If you are intimidated, it’s for a good reason, and I completely understand it.

Der er nogle dele af HTTPS, der er komplekse, men det meste er simpelt.

Furthermore, you don’t need to understand the exact behind-the-scenes work going on in order to implement HTTPS on a website.

Er du bekymret for HTTP og HTTPS? Dette trin for trin snydeark vil lære dig, hvordan du kan implementere HTTPS på dit websted.

What’s the deal? Is HTTPS important or not?

Ideen om HTTPS har altid været en god, og de fleste førende virksomheder har implementeret det for længe siden.

Men for nylig meddelte Google det HTTPS er en placeringsfaktor.

Det er klart, at der er SEO'er, der snakker om og debatterer emnet.

At the time, it was a very small ranking factor, affecting less than 1% of global searches. Even now, it’s not a big factor.

However, security is something that Google takes very seriously, and it’s likely to become more important in the future.

Nogle SEO'er hoppede lige på det og lavede kontakten.

De fleste så lidt til ingen forbedring, men der var sikkert anekdotiske beviser for ranking forbedringer:

image05

der is en potentiel fordel ved at lave omskifteren.

På toppen af ​​søge rankings får du også en smuk lås symbol i Chrome og Firefox.

image00

If your site isn’t HTTPS, you don’t get this symbol, and sometimes visitors may get warnings about the security of your site on certain types of pages.

HTTPS: Explain it to me as if I’m five

I’m not going to pretend to know all the technical details behind HTTPS (Hypertext Transfer Protocol Secure), but I can certainly tell you the basics.

The main benefit of HTTPS is that it makes your site more secure for your users. More specifically, it’s more secure when a user is giving you any sort of information.

It’s essential on pages where users are required to give their credit card information and/or other personal details. However, it’s a good thing to have on all pages.

Den reelle ændring sker, når en bruger sender deres data. HTTPS er i stand til at levere flere lag af beskyttelse til disse data:

  • encryption – the data is worthless to anyone who somehow manages to intercept it because they don’t have the key to decrypt it (du gør).
  • data integrity – data can’t be corrupted, which is a good thing.
  • authentication – det forhindrer “man in the middle” attacks, which means that it’s not possible for anyone to trick your customers into thinking they’re providing you data when they’re really giving it to a scammer. This is what your SSL certificate (more on that soon) is for.

image07

Har du har brug for HTTPS?

Som SEO eller virksomhedsejer forstår du, at ved hjælp af HTTPS er det en god ting.

Men er det virkelig nødvendig?

Nå er der to fordele ved at have det:

  • et lille boost i rankings (muligvis større i fremtiden)
  • et mere sikkert websted til dine brugere

If you run a big site such as Quick Sprout, even a small boost in SEO results in tens of thousands of visitors per month. That’s one reason why HTTPS definitely made sense for Quick Sprout.

However, if you’re starting out, you’re not going to see a real difference in your search traffic.

In the future, it could make a bigger impact, but for now it won’t.

Alt i alt, if you’re expecting to get a significant amount of search traffic in the next few years, you should plan on switching to HTTPS.

Hvad med sikkerhed?

Hvis du bare har en blog, og alt hvad du behøver fra dine brugere, skal du indtaste deres e-mailadresser for at optage i dine e-mail lister, du probably don’t need HTTPS for security reasons.

Men hvis du accepterer betalinger eller vigtige personlige oplysninger af en eller anden grund, er du har brug for HTTPS på disse sider på et minimum.

Mellem disse to faktorer skal du vide, om du skal implementere HTTPS på dit websted overhovedet. En stor del af steder skal have det, men ikke alle gør det.

If you do need to implement HTTPS, I’m going to show you the steps you need to follow. I’ll provide as many specifics as I can, but there are many parts that will vary based on your site choices (I’ll lay it out for you).

Trin 1: Vælg en type SSL-certifikat

SSL? What’s that?

SSL er den protokol, som HTTPS bruger. I grund og grund skal du installere et SSL-certifikat på dit websted for at kunne bruge HTTPS.

Der er tre forskellige typer certifikater, du kan få:

  • Domain validation – the cheapest and most basic; it only really covers encryption (from the three things we went over earlier).
  • Organization validation – the middle choice in terms of price, which also includes authentication. If you’re collecting personal information, you probably want at least this option.
  • Extended validation – the top of the line option, which provides the best security you can get with HTTPS. This is mainly for big e-commerce sites and sites that collect really important private information.

Her er en flot lille resumé:

image01

Google anbefaler, at du bruger 2048-bit krypteringscertifikater, så husk det, hvis du går med et organisationsvalideringscertifikat (som tilbyder forskellige krypteringsniveauer).

Hvor kan man købe et SSL-certifikat: You can buy a certificate from a ton of different websites. They will offer different types at different prices, so you can shop around if you’d like.

Jeg anbefaler dog at købe en fra dit hostingfirma.

Hvorfor?

Fordi de fleste hosting virksomheder tilbyder dem i første omgang, og mange af dem vil også hjælpe dig med at installere dem. Så for nemheds skyld, start med at se på dem.

For eksempel sælger Hostgator en Få forskellige typer certifikater:

image02

You can see that the prices aren’t too steep.

Once you’ve bought one, you can then få dem til at installere det for dig på din hosting server (forudsat at du har en dedikeret IP):

image09

If that’s not possible…Ikke alle hostingudbydere vil installere certifikatet for dig.

På dette tidspunkt skal du se, om de har en installationsvejledning af Googling:

(hostingfirma) + SSL-certifikatinstallation

If that doesn’t bring up anything useful, contact their support.

The process of installing a certificate differs from host to host, which is why I can’t give you specific steps here.

Trin 2: Opret en URL-kort over dit websted og omdirigere

Tag et eksempel URL til:

http://www.example.com

Sammenlign det derefter med:

https://www.example.com

The only difference is one “s” in the URL, and it’s before the actual domain name.

Men det gør en forskel. Disse er to helt separate webadresser.

What that means is that you need to create copies of all your site’s pages and then redirect all of your old “http” pages to your new “https” pages.

Although a pain, it’s pretty simple.

Et URL-kort kan bare være et simpelt regneark, der indeholder en liste over gamle webadresser med en liste over de tilsvarende nye webadresser ud for det.

Hvis du ville foretage ændringer i din webstedsstruktur eller URL-format, ville det nu være en god tid at gøre det.

If you’re using WordPress, you can add all the 301 (permanent) redirects to your .htaccess file.

Hver linje skal se sådan ud:

Omdiriger 301 /oldpage.html https://www.yoursite.com/newpage.html

Du skal bare rette de modige dele.

If you’re planning to move to a brand new domain while you’re doing this, refer to min guide til at flytte et WordPress-websted for trinvise instruktioner.

3. Opdater dine interne links

You’re not quite done with linking yet.

You likely have many internal links throughout your site. These may point to your old “http” pages.

Ideelt set vil du have disse til at pege direkte på dine HTTPS sider.

Introduktion af relative webadresser: If you’re lucky, you’ve been using relative URLs all along.

These don’t specify an absolute (entire) URL; instead, they tell your browser to add something to the end of the domain.

For eksempel, hvis dette link:

<a href=“/page2”>Link</a>

blev placeret et eller andet sted på vores domæne example.com, ved at klikke på det ville tage dig til:

http://www.example.com/page2

When you switch to “HTTPS,” the same link would take you to:

https: //www.example.com/page2

som er perfekt.

If your site wasn’t built like that and instead uses absolute links:

<a href=“http://www.example.com/page2”>Link</a>

then you’ll need to find each link and add the correct ny URL til den.

4. Opdater billede og andre links

It’s not just links to pages on your site that you need to worry about.

It’s also any other link to resources such as images, stylesheets, and scripts.

If you right-click any of your site’s pages and click “view source,” you’ll see all kinds of tags like this:

<script src=”http://www.domain.com/js/file.js” />

Problemet er, at du skal sikre, at alle filer, der bruges og serveres på dit websted, også bruger HTTPS.

Hvis disse kilder og billedsteder findes på dit domæne, skal du pege på de korrekte HTTPS-placeringer.

Hvis du har både HTTP- og HTTPS-URL'er, kan du bruge protokollens relative webadresser, som ser sådan ud:

<script src=”//www.domain.com/js/file.js” />

Den dobbelte skråstreg foran fortæller din browser at bruge HTTPS foran den webadresse, når filen bliver anmodet om fra en HTTPS-side.

Don’t forget about your CDN: Hvis du bruger en CDN, skal du sørge for, at din CDN understøtter HTTPS.

De fleste CDN'er understøtter nu HTTPS, men ikke alle.

For eksempel, Cloudflare gør.

If they don’t have detailed instructions on how to implement HTTPS, so you’ll again have to contact their support.

Then, you’ll have to go back to your new HTTPS site and make sure that the source for all images is pointing to the HTTPS image location on your CDN.

To ensure that you don’t miss any links or images, I recommend using a site crawling tool like Screaming Frog SEO.

Du lægger dit domæne i spidtekassen øverst, og det vil udtrække et ton af information fra dit websted.

Then, click the “internal”, “external”, and “images” filtre langs toppen to see what’s on your site.

image06

If they’re all HTTPS, you’re good to go.

5. Tilføj dit websted igen i WMT

Nu hvor dit websted er grundlæggende helt igen, vil du få Google til at gennemgå det så hurtigt som muligt for at begrænse chancerne for, at din trafik bliver negativt påvirket.

Du er nødt til Tilføj dit websted igen til Googles webmasterværktøjer (Search Console), fordi HTTPS-webstedet betragtes som et helt andet websted.

image10

Derefter skal du indsende dit nye sitemap i din nye liste.

image08

Udover det, skal du indsende dit gamle sitemap (i din gamle WMT-ejendom), da Google derefter vil se omdirigeringer af 301 og opdatere dets fortegnelser.

6. Gør noget hurtig test for at sikre, at alt gik godt

Hvis alt går glat, bør du ikke se nogen ændring eller en lille positiv bump i søgerangeringer.

Hvis trafikken falder betydeligt i mere end en dag eller to, har du sandsynligvis et problem og bør gennemgå denne vejledning igen (og spørg din vært eller en SEO konsulent for at få hjælp).

Først skal du sørge for, at dit SSL-certifikat er installeret korrekt.

For at gøre det skal du bruge dette gratis SSL-servertest:

image04

Just put in your new homepage URL, and it’ll do a thorough test:

image03

Bortset fra dette, vil du se dine placeringer for at sikre, at du får øje på problemer.

Endelig skal du klikke rundt på forskellige sider på dit websted og sørge for, at HTTPS-låsen vises korrekt (grøn) i Chrome.

Konklusion

I know that you might not love technical SEO, but it’s important.

På nuværende tidspunkt skal du vide, om HTTPS er brug for dit websted, eller hvordan du implementerer det.

Although questions about the actual migration can be difficult to answer, if you leave me questions with as much detail as possible in a comment below, I’ll try to answer them.

Efterlad en kommentar

Dette websted bruger Akismet til at reducere spam. Lær, hvordan dine kommentardata behandles.