[et_pb_section fb_built=”1″ admin_label=”section” _builder_version=”4.16″ global_colors_info=”{}”][et_pb_row admin_label=”row” _builder_version=”4.16″ background_size=”initial” background_position=”top_left” background_repeat=”repeat” global_colors_info=”{}”][et_pb_column type=”4_4″ _builder_version=”4.16″ custom_padding=”|||” global_colors_info=”{}” custom_padding__hover=”|||”][et_pb_text _builder_version=”4.27.4″ _module_preset=”default” hover_enabled=”0″ sticky_enabled=”0″]<\/p>\n
He wrote to me late in the afternoon. I still had a mug of cold coffee on my desk and a to-do list full of things that should have been done \u201cyesterday.\u201d But I read his email and immediately knew this wasn\u2019t one of those cases I could postpone. There was something in it that triggered empathy. The client didn\u2019t sound like just another complainer \u2014 more like someone who was genuinely lost and didn’t know how to get out of trouble.<\/p>\n
\n\u2013 Mr. Pawel, I don’t know if you can help me, but I have a website… or rather, I had one. Because something seems to have eaten it.\n<\/p><\/blockquote>\n
Word for word \u2014 eaten<\/em>.<\/p>\n
The guy\u2019s name was Marcin. He ran a renovation company somewhere near Birmingham. His website had been built by a friend of his sister\u2019s boyfriend\u2019s cousin. For free. A kind gesture, sure \u2014 but two years later, customers were calling, saying they couldn\u2019t access the site. One even took a screenshot and sent it: a bright red warning screen saying the site could harm your computer.<\/p>\n
I asked for the link. I clicked. And immediately got hit in the face: threat alert, warning, red background, an airport-level alarm sound. Great \u2014 not only was the site not working, but it looked like it was about to empty someone\u2019s bank account.<\/p>\n
I asked for login credentials \u2014 nothing. Hosting? \u201cI don’t remember, I once got something by email, but I\u2019m not sure if it\u2019s still active.\u201d<\/em><\/p>\n
I asked about email addresses, invoices, company name \u2014 anything. Fortunately, the domain was registered to his personal data, so it was possible to trace where everything was hosted.<\/p>\n
And that’s when it all started.<\/p>\n
I logged into the hosting panel. The files looked like a basement where someone had been dumping junk for two years without ever cleaning up. I opened the main directory \u2014 good, there was WordPress. I checked \u2014 a two-year-old version. Fine, it happens.<\/p>\n
Then I looked into the themes folder \u2014 five different templates, some unused, some with suspicious modification dates. Plugins \u2014 now that was a festival: one had a name using characters my keyboard doesn\u2019t even have. Another looked like an installer, and another like some kind of chat tool.<\/p>\n
I kept digging \u2014 unpacked some files \u2014 and suddenly felt like someone was watching over my shoulder. As if I was opening lockers I shouldn\u2019t. The code was riddled with suspicious fragments, random links, redirects, and in one file, I found a panel that looked like a hacker control center. Seriously \u2014 login screen (very weak password, by the way), and then a dashboard: where to redirect users, which files to add, what to delete.<\/p>\n
They had left themselves a backdoor. And they could enter whenever they wanted. Like it was their own kitchen. And because they had full access \u2014 they dumped in a few \u201cgems\u201d: a page advertising “miracle” pills, a Russian online casino, and \u2014 I felt genuinely awkward browsing this \u2014 an adult website automatically redirecting from Marcin\u2019s domain.<\/p>\n
I closed the panel, leaned back in my chair, and just stared at the screen for a moment. I knew one thing: there was no saving this site. No cleaning, no refreshing. It was like trying to disinfect an apartment after a wild party where someone handed out spare keys to everyone they knew.<\/p>\n
I sighed, drafted a quick email, and moved on to the rescue plan.<\/p>\n
I wrote him an email. No drama, no technical jargon that would have meant nothing to him. Straightforward:<\/p>\n
\n“The site has been severely infected. From my perspective, it cannot be safely salvaged. The most reasonable option would be to rebuild everything from scratch \u2014 but that\u2019s just my opinion. I\u2019m not the only expert out there. If you find someone who can fix it \u2014 great. But if you need help \u2014 I\u2019m here.”\n<\/p><\/blockquote>\n
I always write it this way. Because I know how it works \u2014 especially in our culture. As soon as you say \u201cit needs to be rebuilt from scratch\u201d<\/em>, a little warning light goes off in the client’s head: \u201cAh, he\u2019s trying to rip me off. Classic.\u201d<\/em><\/p>\n
Some don’t even read further \u2014 already wondering who else they could ask or how to cut corners.<\/p>\n
But I’m not about pushing services. I described what I would do, how I would do it, and what it would involve. I also suggested that since we were starting fresh, it might be a good opportunity to refresh his branding \u2014 a new layout, better photos, clearer content. No pressure. More a suggestion for a facelift rather than a revolution.<\/p>\n
And I clearly stated:<\/p>\n
\n“If you don’t plan to handle website updates and security yourself, I can take care of it under a monthly maintenance plan. It’s an option \u2014 not an obligation.”\n<\/p><\/blockquote>\n
I sent it. And waited.<\/p>\n
Not even five minutes later \u2014 seriously, I checked \u2014 I got a reply:<\/p>\n
\n“Pawel, do everything. Website, refresh, maintenance. I don\u2019t want to deal with this anymore. I want someone to handle it properly.”\n<\/p><\/blockquote>\n
That kind of moment always gets me. Because it\u2019s not about technicalities. It\u2019s about trust. About not having to convince anyone \u2014 the way you communicate speaks for itself.<\/p>\n
Before I designed anything, we had to figure out what exactly needed to go on the site. Marcin, like most of my clients, didn\u2019t need a \u201cpretty website\u201d<\/em>. He needed a tool that would work with him \u2014 attract clients, answer questions, build trust. He just didn\u2019t know how to put it into words yet.<\/p>\n
I called him, a relaxed chat \u2014 no buzzwords like \u201cconversion\u201d<\/strong> or \u201cCTA\u201d<\/strong>.<\/p>\n
\n\u2013 Tell me how you work. What does a typical day look like? Where do your clients come from? What do they ask? What do you usually show them when they ask for examples?\n<\/p><\/blockquote>\n
He talked, I listened and organized it in my head. From that conversation, I built a plan:<\/p>\n
\n
- Homepage<\/strong> with a quick overview of his services and a big \u201cCall Now\u201d<\/em> button \u2014 because most clients want immediate action.<\/li>\n
- Portfolio gallery<\/strong> \u2014 not for show, but real “before and after” photos, because that’s what builds trust in the construction industry.<\/li>\n
- Simple service descriptions<\/strong> \u2014 in the client\u2019s language. No \u201ccomprehensive renovation solutions\u201d<\/em>. More like: \u201cpainting, tiling, bathrooms, kitchens, fixes after previous crews\u201d<\/em>.<\/li>\n
- Testimonials section<\/strong> \u2014 we pulled them from Messenger, Facebook, and even a few SMS messages. It all could be organized.<\/li>\n
- Minimalist contact form<\/strong> \u2014 not discouraging with too many questions.<\/li>\n<\/ul>\n
Meanwhile, the question of photos came up. Marcin shrugged \u2014 he had no professional shots. But he remembered his daughter sometimes took pictures with her phone. He sent a few \u2014 and surprisingly, they were pretty good. Natural, candid, exactly the kind that works best: Marcin at work, holding a spirit level, dirty hands, real craftsmanship.<\/p>\n
Turns out, Generation Z comes in handy \u2014 so many selfies that they know how to catch a good angle and lighting without even trying.<\/p>\n
I also suggested something I now consider standard for such websites: a separate portfolio page. A place to show concrete projects \u2014 before, after, with a short description of what was done. Clients who see the results don\u2019t even need to read a line of text to understand what Marcin can do.<\/p>\n
And so, from a conversation and a few sent photos, we created the skeleton of a website that would truly be his \u2014 not a copy, not a \u201ctemplate\u201d<\/em>, but a real showcase of a skilled craftsman who knows his job.<\/p>\n
Ultimately, the site was built on WordPress<\/strong> \u2014 not because it\u2019s trendy, but because it was simply the most reasonable choice in his case. Clear layout, fast loading, easy editing if he ever wants to add or change something. Everything according to plan \u2014 no chaos, no accidents.<\/p>\n
Visually, we focused on simplicity and clarity: large project photos, clear headlines, visible contact details. A website you visit and immediately know who you\u2019re dealing with.<\/p>\n
This time, I especially made sure of security: solid hosting with backups, additional security plugins, automatic updates, and regular backups. Everything under constant care \u2014 Marcin immediately decided on monthly administration<\/strong>, so he knows someone\u2019s watching over everything. He doesn\u2019t have to worry about updates, dashboard alerts, or security warnings. It\u2019s all on me.<\/p>\n
Previously, he had a free website. Now, he has peace of mind. And the knowledge that his online presence isn\u2019t abandoned in some random folder but is actually working \u2014 for him, on his terms, without surprises.<\/p>\n
The project for Marcin was different from the usual ones. Normally, everything is agreed: contract, project details, scope. Here, it was different. Marcin didn\u2019t know what to do or how to approach the problem. He admitted his mistake, didn\u2019t pretend \u201cit could be fixed\u201d<\/em>.<\/p>\n
He knew he needed help.<\/p>\n
What happened was a quick decision on my part. Not because it was easy, but because we didn\u2019t have to stop at endless details. Marcin let me work, trusted me to do it right.<\/p>\n
It was a decisive reaction to a situation \u2014 no unnecessary questions, no \u201cwhat ifs.\u201d I knew quick action was crucial. His understanding of his situation met my understanding of my role: he knew I had to act quickly to give him what he needed.<\/p>\n
The website was created quickly and efficiently, and the final result satisfied him completely. Marcin not only appreciated the final product but also decided to continue our cooperation for years. I managed the site\u2019s administration, security, updates \u2014 everything that made his business online work smoothly while he focused on what he does best \u2014 his craft.<\/p>\n
When Marcin returned to Poland, the project came to an end, but those few years of cooperation were a valuable experience for me. Thanks to the trust, freedom, and mutual understanding, we achieved something truly beneficial for both sides.<\/p>\n
[\/et_pb_text][\/et_pb_column][\/et_pb_row][\/et_pb_section]<\/p>\n","protected":false},"excerpt":{"rendered":"
When a website gets hacked, it’s more than a technical problem \u2014 it’s a blow to your brand\u2019s reputation. See how rebuilding from scratch turned a crisis into a success story.<\/p>\n","protected":false},"author":2,"featured_media":1134,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_et_pb_use_builder":"on","_et_pb_old_content":"","_et_gb_content_width":"","footnotes":""},"categories":[5],"tags":[72,71],"class_list":["post-1379","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-media-en","tag-website-recovery","tag-website-security"],"_links":{"self":[{"href":"https:\/\/pawelopitek.com\/en\/wp-json\/wp\/v2\/posts\/1379","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/pawelopitek.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/pawelopitek.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/pawelopitek.com\/en\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/pawelopitek.com\/en\/wp-json\/wp\/v2\/comments?post=1379"}],"version-history":[{"count":0,"href":"https:\/\/pawelopitek.com\/en\/wp-json\/wp\/v2\/posts\/1379\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/pawelopitek.com\/en\/wp-json\/wp\/v2\/media\/1134"}],"wp:attachment":[{"href":"https:\/\/pawelopitek.com\/en\/wp-json\/wp\/v2\/media?parent=1379"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/pawelopitek.com\/en\/wp-json\/wp\/v2\/categories?post=1379"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/pawelopitek.com\/en\/wp-json\/wp\/v2\/tags?post=1379"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}