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. "
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!
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.
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.
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).
