Streaming live at 10am (PST)

IP Canonicalization (duplicate content)


#1

Hey WF community! :slight_smile:

I ran a test on my WF-site http://dansbrudevals.dk at http://seositecheckup.com/ and got positive results. The only negative result is that the website fails at IP canonicalization with the following message:

"Your site's IP 23.235.33.229 does not redirect to your site's domain name. This could cause duplicate content problems if a search engine indexes your site under both its IP and domain name. "

How do I fix this? :blush:

I hope you can help me.
Thanks a lot!

Cheers,
Oliver


#2

I've received the same thing...not sure if this is important or not either!


#3

@Curting
@DylanUrquhart

Duplicate content will ding you with Google.

Typically, this can be fixed by adding a rewrite rule in an .htaccess file...

RewriteCond %{HTTP_HOST} ^111.111.111.111
RewriteRule (.*) http://dansbrudevals.dk/$1 [R=301,L]

You will need to change the IP address to your own. If your site doesn't use a dedicated IP (not sure if Webflow does or not.) If not, that could cause this to not work. I have only done this in WP on dedicated servers and VPSs, not Webflow, so if someone else could weigh in, that would be great!

Take care,
~B.


#4

Thanks @itbrian40 :slight_smile:

Might need to brush up on my web skills before I can take that on one.


#5

@DylanUrquhart

  • open a text editor and create the file: htaccess.txt
  • OR, if already present in your site's root folder (or elsewhere, nose around a bit), download it to your local machine.
  • Change the one on the site to htaccess.old so you have a backup of it.
  • Add the edits to the existing file or the new file and upload it back up your site or to where you found the existing one on your site.

Note: Some FTP software may pitch an error when trying to upload the actual .htaccess file due to the filename format, so use the .txt extension (example above) to get it uploaded and then change it to .htaccess once it's in the site's root folder or the folder you found the existing one in.

Take care,
~B.


#6

@Curting
@DylanUrquhart

I spoke to Webflow yesterday and it turns out that it's a more modern version of a shared IP address, so I would not try to implement the .htaccess strategy outlined above based on this new information.

This is the answer I was given, for your reference:

Yes, they are all shared. However it’s important to note that the IP is pointed to hundreds of servers worldwide and not a single server like “shared” hosting would be.

Traditionally with web hosting, “shared hosting” was where a provider had a single server and a single IP that you would be assigned. They would assign hundreds of sites to the same server. With the anycast IPs Webflow uses, the IPs we provide are mapped to hundreds of globally distributed servers and cannot directly be compared to shared hosting as it historically exists.

I hope this makes it clearer.

Take care,
~B.


#7

Thank you very much for your answer, @itbrian40 ! :slight_smile:
So I shouldn't take this issue too seriously?


#8

Yes, you should take it semi-seriously because Google does. They may ding you in the SERPs for duplicate content, even though you may not have any, just a domain/IP mismatch you've stated above. I would use a rel="canonical" strategy here since a 301 redirect isn't going to work in this situation, but even that isn't going to work the best for this situation (since it's an IP based issue).

~B.


#9

I see the same issue using the same SEO site check tool. Is there any update on this?

RewriteCond %{HTTP_HOST} ^XXX.XXX.XXX.XXX
RewriteRule (.*) http://www.yourdomain.com/$1 [R=301,L]

Is the only suggestion in SEO site check, and per @itbrian40 suggested not to do this.

Thank you for your help!


#10

That was as per Webflow staff member via Slack. Just to clarify where the info came from.

~B.


#11

Sorry - yes - didn't quote that right. Indeed, you said Webflow said not to try it.


#12