Dennis Hüttner (@proofwebwizard) header
Dennis Hüttner (@proofwebwizard) profile picture

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

Baienfurt
Joined March 2009
Photo by Dennis Hüttner (@proofwebwizard)Photo by Dennis Hüttner (@proofwebwizard)Photo by Dennis Hüttner (@proofwebwizard)Photo by Dennis Hüttner (@proofwebwizard)Photo by Dennis Hüttner (@proofwebwizard)Photo by Dennis Hüttner (@proofwebwizard)Photo by Dennis Hüttner (@proofwebwizard)Photo by Dennis Hüttner (@proofwebwizard)Photo by Dennis Hüttner (@proofwebwizard)Photo by Dennis Hüttner (@proofwebwizard)
Replying to @wordfence
Good timing after PHP2Shell. Plenty of site owners patched and stopped there. A fast channel for reporting active compromises helps, because a backdoor planted before the patch survives the update.
1
39
Replying to @BowTiedBills
Solid map. For B2B I'd add one thing under Town Pages: real project references from that region. For industrial clients the profile gets the click, but the page behind it closes the lead.
22
Replying to @irentdumpsters
True, and it's why keyword-stuffed names keep showing up. The clean way to compete: real location pages, categories that match the service, and reporting competitors who fake their name. Renaming your actual company is a branding decision, not an SEO hack.
1
18
Replying to @lilyraynyc
Agreed. In B2B the signals sit in both columns: a named author who actually did the work, verifiable company details, real project specifics. AI answers pull from the same trust signals classic search has always rewarded.
40
Replying to @aleyda @semrush
This matters a lot for DACH. Germany, Austria and Switzerland share a language but not the same trusted directories, media or brands. If you target all three, you need local citations and sources per market, not one translated set.
21
Replying to @rustybrick
The practical takeaway for agencies: audit client sites for indexable utility URLs. Internal search results, filter combinations, preview links and form confirmations often sit in the index unnoticed. Noindex them before they dilute how Google sees the site.
100
Replying to @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.
1
13
Replying to @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?
15
Replying to @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.
9
Replying to @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?
1
24
Replying to @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.
66
Replying to @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.
16
Replying to @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.
8
Replying to @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.
1
23
Replying to @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?
1
112
Replying to @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.
8
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: waterproof-web-wizard.de/blo…
62
Replying to @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.
6
Replying to @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.
18
Replying to @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.
24