4 ms·

My main website has a domain authority of 53; a subdomain with the same IP would be seen as the same site (I used to use subdomains and have seen this firsthand

by byuu 7y ago

My main website has a domain authority of 53; a subdomain with the same IP would be seen as the same site (I used to use subdomains and have seen this firsthand); a subdomain with a different IP would start me over which is a very bad thing (I've been struggling with byuu.net in this regard.) The URL scheme is the convention I follow, but I also include the version# in the file name. I did put the executable inside of a ZIP archive, along with a text database and a few video pixel shaders. One change I made recently was moving from .7z to .zip since some users don't have 7-zip installed, but I presume Google is smart enough to scan inside 7-zip archives even if Windows isn't (out of the box at least.) I've been providing these releases for fourteen years now. I have no idea what suddenly changed other than it took about two years to release a new version due to a lot of massive changes. I appreciate the reply all the same, thank you for taking the time.

gdm85 7y ago
They probably calculate different scores depending on the purpose (SEO, safe browsing etc). If you want to stand your ground you could simply add a password to your archive (works best with 7zip as you can avoid exposing the filename with extension); just mentioning it for the records.
garganzol 7y ago
>a subdomain with a different IP would start me over which is a very bad thing Cannot confirm that. IP is virtual thing in terms of HTTP web hosting. I have experience with attaching fresh IPs to existing domains and attaching fresh domains to old IPs: the only thing that matters for HTTP reputation is DNS. IPs do not really matter unless they are seriously blacklisted by a manual action (which is not your situation I presume). >Google is smart enough to scan inside 7-zip archives Google sees raw EXE files as a risk factor. Once domain serves a naked EXE, Google gives it a higher risk score. Publishing an EXE file inside archive (of any format) significantly lowers that risk because an archive cannot be directly executed by OS. (Please note that a lot of corporate internet gateways do not allow naked EXE files via HTTP for the very same reason)
- byuu 7y ago
  Well it would be both, right? A new IP and a new subdomain. When I did that for a wordpress install it had very low (<10) DA. I trust your experience more than my one attempt though. Also my program was inside a ZIP archive. It did not help me.

by byuu 7y ago

gdm85 7y ago

They probably calculate different scores depending on the purpose (SEO, safe browsing etc). If you want to stand your ground you could simply add a password to your archive (works best with 7zip as you can avoid exposing the filename with extension); just mentioning it for the records.

garganzol 7y ago

>a subdomain with a different IP would start me over which is a very bad thing Cannot confirm that. IP is virtual thing in terms of HTTP web hosting. I have experience with attaching fresh IPs to existing domains and attaching fresh domains to old IPs: the only thing that matters for HTTP reputation is DNS. IPs do not really matter unless they are seriously blacklisted by a manual action (which is not your situation I presume). >Google is smart enough to scan inside 7-zip archives Google sees raw EXE files as a risk factor. Once domain serves a naked EXE, Google gives it a higher risk score. Publishing an EXE file inside archive (of any format) significantly lowers that risk because an archive cannot be directly executed by OS. (Please note that a lot of corporate internet gateways do not allow naked EXE files via HTTP for the very same reason)

byuu 7y ago
Well it would be both, right? A new IP and a new subdomain. When I did that for a wordpress install it had very low (<10) DA. I trust your experience more than my one attempt though. Also my program was inside a ZIP archive. It did not help me.