Hi guys,

The tech department implemented rel="prev"  and rel="next" on this website a long time ago.
We also added a canonical tag to the 'own' page.

We're talking about the following situation:

https://bit.ly/2H3HpRD

However we still see a situation where a lot of paginated pages are visible in the SERP.
Is this just a case of rel="prev" and "next" being directives to Google?
And in this specific case, Google deciding to not only show the 1st page in the SERP, but still show most of the paginated pages in the SERP?

Please let me know, what you think.

Regards,
Tom

Hi,

A website is not fully secured with a SSL certificate.
Approx 97% of the pages on the website are secured.

A few pages are unfortunately not secured with a SSL certificate, because otherwise some functions on those pages do not work.

It's a website where you can play online games. These games do not work with an SSL connection.

Is there anything we have to consider or optimize?
Because, for example when we click on the secure lock icon in the browser, the following notice.
Your connection to this site is not fully secured Can this harm the Google ranking?

Regards,
Tom

Hi Oleg,

Thanks for your reply.

I am also curious about our customers who are currently hosting their website on our servers.
We are their online marketing agency.

We want them to get more converting visitors.
Therefore we develop optimized websites and make sure the websites are hosted on a fast and reliable servers.
However, if this server is upgraded from IPv:4 to IPv:6, will there be any things we have to consider with this transition regarding SEO?

And with SEO, I mean, possible positiondrop of keywords and visitors.
Is there any chance search engines will have to 'reindex the websites' because of the IP transition?

And are there any possible technical setbacks, that can make the rating of the server worse (GTMetrix, Google Lighthouse, etc)

I hope any of you can clearify a bit more on this and if this is anything to keep in mind.
If you need more information please let me know.

Regards,
Tom

Hi all,

I read the article from 2014 on MOZ regarding ipv6.
https://moz.com/blog/ipv6-cblocks-and-seo

Our technical department is about to change our server from ipv4 to ipv6.
Are there any things we have to consider regarding SEO / rankings / duplicate content etc.. with this transition?

I hope you have a little spare time to answer this question.

Regards,
Tom

Hi Lesley,

Thx. But I'm still confused, Chris says 'use pagination' , you say 'use canonical'.
I don't really know what the best practice is tbh.

Can you explain why you wouldn't use the rel next/prev with this?

Regards,

Tom

Hi Chris, Thx for your quick reply. We have a similar situation as the one I described earlier. Currently the code below is on the page. What are your thoughts on this contruction? Because, we use the prev and next AS WELL AS the canonical tag. The canonical to prevent duplicate content. The link prev and next to prevent Google indexing all the seperate /?tab=.. as inidivual pages. I'm looking forward to your response. Regards, Tom

Hi guys,

When you have several tabs on your website with products, you can most likely navigate to page 2, 3, 4 etc...
You can add the link rel="prev" and link rel="next" tags to make sure that 1 page get's indexed / ranked by Google. am I correct?

However this still means that all the pages can get indexed, right?

For example a webshop makes use of the link rel="prev" and ="next" tags.

In the Google results page though, all the seperate tabs pages are still visible/indexed..
http://www.domain.nl/watches/?tab=1
http://www.domain.nl/watches/?tab=24
http://www.domain.nl/watches/?tab=19
etc.....

Can we prevent this, and make sure only the main page get's indexed and ranked,  by adding a canonical link on every 'tab page' to the main page --> www.domain.nl/watches/

I hope I explained it well and I'm looking forward to hearing from you.

Regards,

Tom