Dennis Hüttner

A waterproof web wizard fights the dark side of agencies selling hot air. He doesn't like ugly websites. #TYPO3 #Wordpress #SEO #OnlineMarketing #AI

[Dennis Hüttner @proofwebwizard]

@westonruter Thanks, that settles it. Five plugins, all closed or abandoned, is a much smaller blast radius than I expected. We will still run client sites against the 7.2 beta before rollout.

[Dennis Hüttner @proofwebwizard]

@rustybrick Weekend volatility always lands in Monday client calls. Our rule: wait a few days, compare Search Console clicks and impressions, then decide. Reacting on day one usually does more harm than the update itself. Anyone seeing it hit the local pack too?

[Dennis Hüttner @proofwebwizard]

@glenngabe If this holds, every rank tracker trend since early 2026 needs a second source. For local clients, comparing tracker data with Search Console queries and manual checks from the target city is the safer baseline before reporting any change.

[Dennis Hüttner @proofwebwizard]

@aleyda The new Business Profiles home matters for B2B too. We run several location profiles for our web agency, and keeping services and posts in sync with the website is where most of the work goes. Anyone seeing AI Mode cite GBP service entries yet?

[Dennis Hüttner @proofwebwizard]

@mmaunder Agree. We look after TYPO3 and WordPress sites for mid-sized manufacturers, and the hype made clients worry about the wrong things. What helps: confirm the patched PHP build is live after the restart, then move on. Calm, verified facts get patches deployed faster.

[Dennis Hüttner @proofwebwizard]

@Dhanush_Nehru Good breakdown. One thing we add for clients after patching: restart PHP-FPM and workers, then check for new admin users and unknown files in uploads. A patched binary doesn't help if the old process is still running or someone got in earlier.

[Dennis Hüttner @proofwebwizard]

@Majestic Agree, for near me searches the map pack still decides. But consistent NAP data is only the baseline. Precise categories, real service descriptions and regular posts are what move a profile from listed to chosen.

[Dennis Hüttner @proofwebwizard]

@itsMikeKipruto Most SMEs can't answer that question. It belongs in writing: who patches PHP, who updates the CMS, who gets called when something breaks at 6pm. If nobody can name that person today, that's the real vulnerability.

[Dennis Hüttner @proofwebwizard]

@BalaiBB The PHP part is the one site owners underestimate. Updating WordPress or TYPO3 does nothing here, the fix lives in the PHP runtime on the server. First question to ask your host today: which PHP build am I running, and when was it patched?

[Dennis Hüttner @proofwebwizard]

@alexgroberman This is the part local businesses miss: AI answers pull from your own service pages, not just directories. A clear page per service and location, plus a maintained Google Business Profile, gives the models something concrete to cite.

[Dennis Hüttner @proofwebwizard]

Polizei, Ministerien und Kliniken in Bayern haben ihre Websites vorsorglich vom Netz genommen. Grund ist eine PHP-Lücke, das BSI hält großflächige Angriffe binnen Stunden für wahrscheinlich. Lass dir vom Hoster bestätigen, dass das Update läuft. Vorlage:
https://t.co/xCq1OqwyfZ

[Dennis Hüttner @proofwebwizard]

@boringlocalseo Agree on citations first. One step we'd add: make the website's location page match the profile exactly before verification. Same name, same phone format, same service names. In our view small mismatches slow things down more than a missing link.

[Dennis Hüttner @proofwebwizard]

@irentdumpsters Worth adding: the new generative AI report in Search Console shows impressions only, no clicks. So a swing there says nothing about lost traffic. Compare against your own enquiry log before you rewrite pages for an update Google never announced.

[Dennis Hüttner @proofwebwizard]

@codyschneider Same holds for local. For "agency near me" style questions, AI Mode tends to lean on Google Business Profiles. Clean categories, real services and consistent contact data on site and profile still decide who gets named. Boring SEO work, new surface.

[Dennis Hüttner @proofwebwizard]

@jeffr0 For EU agencies this is not abstract. The European Accessibility Act has applied since June 2025 and clients ask whether core will keep up. Reverting a six-year-old a11y fix within a day makes that answer much harder. Clear process matters as much as code.

[Dennis Hüttner @proofwebwizard]

@AurelioVolle @patchstackapp Important detail for anyone patching today: per Nethemba, 1.26.12 deleted no keys at all because of a bug. Only 1.26.13 / 2.26.13 revokes the old ones, and keys created later on Oct 18 still need manual deletion. Check every site by hand.

[Dennis Hüttner @proofwebwizard]

@SybreWaaijer The weak point isn't the plugin code, it's the vendor's cloud. UpdraftCentral keys don't expire, and the box is pre-ticked when you connect an account. Every remote management link is standing trust. Audit and revoke the ones you don't actively use.

[Dennis Hüttner @proofwebwizard]

@DarkWebInformer The part many site owners miss: updating to 3.0.124 does not clean a site that ever activated the bad 3.0.123 build. Restore a clean backup, rotate salts, passwords and API keys. And stage premium plugin updates before they hit production.

[Dennis Hüttner @proofwebwizard]

@boringlocalseo Good order. One thing to add: lock the exact name, address and phone format before the first citation goes live. Fixing ten directories later because one says "St." and another "Street" takes longer than the whole setup.