Website security
for WordPress and Next.js

Security audits, hardening and recovery for business websites. Get a clear assessment of the risks, recommended fixes and a practical plan for ongoing protection.

We review what you send and agree the scope before any quote.

IDEAS INTO EXPERIENCES

Clarity.
Character.
Craft.

STUDIO IDD / WEBSITE SECURITY
Concept study · Audit · Harden · Monitor · Recover

A GOOD PLACE TO START

Three ways to start

01

Security audit

For a site that seems fine but has not been reviewed in a while. Most websites are not attacked because someone chose the business: automated scans look for an outdated plugin, a reused password or an open admin login. The audit delivers a written report with every finding ranked by risk and a recommended fix. Carrying out the fixes is scoped and quoted separately.

02

Recovery after a suspected hack

For a site that shows signs of compromise: unknown admin users, strange redirects, spam pages, a warning from your host or a browser alert. Choose the suspected hack option in the form and describe what you have seen and when it started. Containment comes first, then the cleanup and the investigation of how the attacker got in.

03

Ongoing protection

For a site that needs someone to keep watching it. Updates, backups, monitoring and access reviews run on a schedule set in a support agreement, which also defines who is responsible for what and how quickly we respond to an alert.

01OUR EXPERTISE

What we check and fix

A considered approach, from the first question to the details that make it work.

01

WordPress security

Core, plugin and theme versions are checked against known vulnerabilities, and abandoned or unused plugins are removed. We lock down file permissions, file editing from the admin, XML-RPC and user enumeration, and review wp-config and the hosting setup. WooCommerce stores get the same review for checkout, orders and payment integrations.

02

Next.js security

We check that every API route and server action verifies who is calling it, instead of relying on middleware alone. We look for secrets exposed to the browser through public environment variables, review dependencies against published advisories and test the image, redirect and revalidation endpoints that can be abused.

03

Accounts and access

Two-factor authentication for every administrator, roles with only the permissions each person needs, and no shared or forgotten logins across the hosting, DNS, admin and code repository. Repeated login attempts are limited before they become a problem.

04

Firewall, headers and bot protection

A web application firewall and CDN in front of the site, HTTPS enforced with HSTS, a Content Security Policy and the other security headers browsers expect. Every public form gets protection against spam and automated abuse.

05

Updates, backups and monitoring

Core, plugin and dependency updates are tested on staging before release. We check that backups exist, are kept off the server and can actually be restored, by restoring one in a test. Uptime, file changes and errors are monitored so problems surface early.

06

Recovery after a hack

We contain the damage, find how the attacker got in, remove malicious code and backdoors and rotate every credential. If a clean, usable backup exists we restore from it; otherwise we rebuild the affected parts from verified sources. We then submit review requests to Google and blocklist services and follow them up, although the decision and its timing are theirs.

02HOW WE WORK

From the first review to a site that stays protected

Each stage moves the work forward. You see the decisions, review the progress and know what comes next.

  1. 01

    Assess

    Agree the scope, receive access through a secure channel, then audit the site and rank every finding by risk.

  2. 02

    Fix

    Once the remediation is scoped and agreed, apply the fixes on staging first, then release them with a rollback plan and document what changed.

  3. 03

    Protect

    Set up the firewall, backups and monitoring, with a named owner for each, on your side or ours.

  4. 04

    Maintain

    Under a support agreement, review updates, alerts and access on an agreed schedule and report what changed.

03BUILT TO HAND OVER

What each engagement delivers

  • Audit: a written report in which every finding has its risk, a recommended fix and a way to verify the fix.
  • Fixes, scoped and quoted after the audit: the agreed changes applied on staging first, released with a rollback plan and documented.
  • Recovery: containment, cleanup and new credentials, a summary of how the attacker got in and the review requests submitted on your behalf.
  • Ongoing protection: updates, tested backups, monitoring and access reviews on the schedule and response times set in the support agreement.

Website security questions

Ema, Studio IDD manager

You didn’t find your answer?

This is Ema, Studio IDD manager. Feel free to text her and get all the answers you need.

Ask a Question
Yes. Choose the suspected hack option in the form on this page, send the site address and describe what you have noticed and when it started. We start with containment: a copy of the site for analysis, steps to stop further damage and an investigation of how the attacker got in. Cleaning a site without closing that entry point usually leads to a repeat infection, so both are part of the work.
The audit delivers a written report and recommended fixes, and ends there. If you want us to carry out the fixes, that work is scoped and quoted separately once you have the report. Ongoing protection is a separate support agreement for sites that change often, run many plugins or would be costly to lose. You can start with the audit and decide on the rest once you know where the site stands.
Yes. We begin with a review of the code, the hosting and the access we need, then agree the scope. Our main focus is WordPress, WooCommerce, Next.js and headless setups that combine them.
A security plugin helps, but it runs inside the application it protects. It cannot fix outdated code, weak hosting configuration or too many people with administrator access. We use plugins where they add value, together with a firewall at the network edge, hardening and a tested update and backup routine.
No one can honestly promise that. What we can do is remove the common ways in, limit what an attacker could reach and make sure an incident is noticed quickly. Part of the work is checking that a clean, working backup exists, so the site can be restored if something does happen.
It depends on the size of the site, the number of plugins and integrations, and the condition of the code and hosting. The audit, the fixes that follow it, recovery after an incident and ongoing protection are each quoted separately. A plan with timeline and price follows once we have seen the site.
Nothing in advance. Once the scope is agreed, we tell you exactly which access we need, usually the hosting, the admin, the code repository and the DNS or CDN accounts, and you share it through a password manager or another secure channel, never in plain email. A list of who currently has access, and of anything unusual you have noticed, helps us focus the review.

Security review request

Find out how exposed your website is

Send the address and choose what you need. We review it, ask what we need to know and agree the scope before we send a quote. No access or passwords at this stage.

What do you need?
Platform, if you know it