320px knowledge base

What to do with a WordPress site

Concrete guides to WordPress maintenance, updates, backups, PHP, migration, performance, indexing, and incident recovery.

Direct answer

Choose the problem you need to solve now.

Choose a task below. Each guide covers the steps, common mistakes, and situations that call for a specialist.

Eight tasks

From regular maintenance to an incident.

01

What WordPress maintenance includes

A practical scope for ongoing WordPress maintenance: updates, backups, failures, performance, technical SEO, small releases, and documentation.

02

A safe WordPress update sequence

A WordPress update workflow built around a checkpoint, compatibility review, stage, critical journeys, release, and postflight.

03

WordPress backup and restore verification

What a WordPress backup must contain and why only an isolated restore test proves that an archive is usable.

04

Updating PHP for WordPress

A safe move to a supported PHP version: code inventory, stage, error logs, critical journeys, production switch, and rollback.

05

Migrating WordPress to another host

A WordPress migration plan covering inventory, copy, DNS, mail, redirects, search signals, freeze/delta, verification, and rollback.

06

Why a WordPress site is slow

A diagnosis order for slow WordPress: reproduction, network, server, database, plugins, cron, caches, assets, and result verification.

07

Why a WordPress site is not indexed

What to check when WordPress pages do not appear in search: HTTP, robots, noindex, canonical, sitemap, links, duplicates, and webmaster data.

08

What to do when a WordPress site is hacked

First actions after suspected WordPress compromise: contain damage, preserve state, rotate secrets, restore trusted code, and verify again.

Start with evidence

The free check changes nothing on the site.

320px Site Audit builds a local report across WordPress, technical SEO, frontend, privacy, and security. No account or report transfer is required; an unknown area remains not tested.

Tell us what the site needs.

A goal, the current difficulty, and an optional website address are enough. Do not send passwords, keys, or private exports.