I don’t understand, a mail server sends an email and it has an ip address. There’s no website associated with that. Sure, there’s an email address, and a load of rules about how to help avoid spam by setting up SPF and DKIM and DMARC to prove that the mail server is allowed to send on behalf of the ___domain. And if the specific IP address of the mail server ends up on a spam list, you can try to get it removed or start sending from another ip.
I don’t get what it means for the entire website to be blocked from an SEO perspective. Google don’t remove you from the index because an IP address ends up on a spam list and that’s also where you website is hosted, right?
Also, you’re only hosting on s3 if you’re hosting a totally static website, which very few people do.
You could potentially host an spa on s3 which hits an api. In that situation the spa would still be indexable. And I dont think google removes you from the index, but spam coming from the same ip seems to be a negative criteria.
Is it negative criteria though? It seems to me that with shared hosting the situation would be so common that it would seem to be big false positive metric. Granted, it’s a couple of years ago and things maybe have changed, but here’s Matt Cutts saying that it doesn’t (for that reason) https://youtu.be/4peSUa2FKvk
I think this is the danger of the SEO industry. On the one hand you have bad actors trying to game the system, but on the other, people selling you legitimate SEO are often claiming rules as fact with little or no evidence - because it’s different to verify.
I don’t get what it means for the entire website to be blocked from an SEO perspective. Google don’t remove you from the index because an IP address ends up on a spam list and that’s also where you website is hosted, right?
Also, you’re only hosting on s3 if you’re hosting a totally static website, which very few people do.