Attacks were recorded from October 17. WordPress.org told some owners to take servers offline. Google said how to do it without hurting search.
Read Article →A prospective member lands on your Ohio chapter and finds a retired logo, a 2023 conference, and a donate button pointing at a personal payment account. Every federated association hits...
Read Article →PHP shipped emergency fixes for two flaws rated 9.2. This sits under WordPress and Drupal, so a CMS update does nothing. Your host patches it, and you need to ask.
Read Article →Patching would not have helped. The sites were current. The exposure was a remote-management channel an administrator switched on, running at that administrator's permission level.
Read Article →Your site went live in 2018 and nothing has been removed since. Search traffic has been sliding for three years. Here is what Google actually documents about fixing it, and...
Read Article →Your AMS has an AI feature on the roadmap and your CMS has one in the release notes. Nobody has asked which model any of them run. Here is why...
Read Article →Somebody asked whether anything could be done about AI companies training on your content, and a switch got flipped. Here is how to tell whether that switch is also blocking...
Read Article →Your job board runs on a vendor's platform but lives on your domain and carries your logo. Google has now published how it judges content like that. Here is what...
Read Article →Your association added a second language years ago and a translation plugin has been running quietly ever since. Here is how one ends up keeping a copy of a password...
Read Article →The Click2Shell flaw needed an administrator to click a link. This one needs nobody. Two WordPress security releases in five days, and what that cadence means for a monthly patch...
Read Article →