Welcome to the Q&A Forum

Hi Becky,

I am also faced with the same issue as you and after intensive research, I found that the best solution would be to make the server to an automatic 301 redirection for all HTTP pages to the their respective HTTPS pages.

This would enable you to preserve all SEO value of the pages and at the same time, avoid having duplicates.

However, since you have not yet moved all the pages in HTTPS, then a canonical would work the best, but this needs to be manually defined for each page, unless you have a CRM that can pull the respective absolute URL accordingly.

Hope this helps.

Tej Luchmun

Hi,

Thanks a lot for your reponse, it is very useful.

We will try to push forward a virtual pageview, however, through some in-depth investigation, I noticed that Google does not crawl AJAX content.

We tried to follow the instructions of HIJAX from the following page, but unfortunately, could not find any evidence that it is working.

https://developers.google.com/webmasters/ajax-crawling/docs/learn-more

Do you know a way around to test if Google is able to crawl the content?

Thanks so much for your help.

Tej Luchmun

Hi,

Our current website http://www.luxresorts.com has sections that pull content through AJAX which is accessible through a URL.

For example, on our homepage, we have a section called "LUX* Magazine THE TASTEMAKER", if you click on "Read More" it would open on the same page while pulling content from this URL: http://www.luxresorts.com/en/posts/lux-magazine.

There are two concerns here:

a. the above url does not contain any google analytics code, does pulling content from a url through ajax cause a bounce rate?

b. since the url is indepenedent, the is no meta tags including title, description or even robot attributes. Should we treat this page as all other pages?

Thank you for your help.

Tej Luchmun

Hi Sean,

Thanks a lot for your reply.

Indeed having the rel=canonical pointing to the wrong page would be another issue. What David Lee suggested me is using the rel=canonical on both the original post and the duplicate post. This can be set programmatically instead of the ignore button.

But surely, the ignore button would be much more easier, in some situations. Please keep us update once this ignore feature has been implement.

Thanks again for your help.

Tej Luchmun

Hi Sheena,

Yes, Moz Crawl Diagnostics Report is showing duplicate title tag for the content that already have a rel=canonical tag.

I contacted them, and they suggested that i should include the canonical tag on the duplicate and original post, where both tags are pointing to the original post.

I have not yet tested it out, but hopefully, this should solve the issue.

Thanks again for your help.

Tej Luchmun

Thanks a lot Karl, indeed with the canonical tag, neither the title nor the content becomes a duplicate.

It's just the MOZ crawl issue that raised the alarm.

Thanks again.

Tej Luchmun

Thanks.

Done since a while and already live

Tej Luchmun

Hello,

We were having duplicate content in our blog (a replica of each post automatically was done by the CMS), until we recently implemented a rel=canonical tag to all the duplicate posts (some 5 weeks ago).

So far, no duplicate content were been found, but we are still getting duplicate title tags, though the rel=canonical is present.

Any idea why is this the case and what can we do to solve it?

Thanks in advance for your help.

Tej Luchmun

Thanks a lot for your reply gfiorelli1.

We currently have no redirection based on IP detection nor user agent.

Taking into account the two options you mentioned, the best option would definitely be to make luxresorts.com the main page for the targeted country (while we would make the current default page http://www.luxresorts.com/en 301 to http://www.luxresorts.com) and then having a browser language detection then serve the language accordingly.

Do you think this would be the best thing to do?

Thanks again.

-Tej Luchmun

Thanks a lot Andy, we definitely want to preserve the Link Juice, since http://www.luxresorts.com has a higher SEO value, but currently having a 302 to /en.

I guess we would go for the 301 soon.

Thanks a lot Andy, we definitely want to preserve the Link Juice, since http://www.luxresorts.com has a higher SEO value, but currently having a 302 to /en.

I guess we would go for the 301 soon.

Hi Sean,

Thanks a lot for your reply.

Indeed having the rel=canonical pointing to the wrong page would be another issue. What David Lee suggested me is using the rel=canonical on both the original post and the duplicate post. This can be set programmatically instead of the ignore button.

But surely, the ignore button would be much more easier, in some situations. Please keep us update once this ignore feature has been implement.

Thanks again for your help.

Tej Luchmun