I am Mariusz Szatkowski, a WordPress developer since 2006, and I rebuild WordPress sites whose technical base no longer holds: PHP stuck on 7.x, a page builder nobody can remove, load times that caching does not fix. You bring the design, I build it as a responsive theme, move the content and keep the URLs working.
I work alone from Gdynia, Poland. The code you get is code I wrote, and your access details stay with me. I talk by email, in written documents and in the repository.
Good and bad reasons to rebuild a WordPress site
There are two honest reasons.
The business has changed. A new audience, a new product line or a rebrand leaves the old site structurally wrong for what the company sells now, and swapping the header does not fix that. In that case the rebuild follows the positioning work you have already done.
The stack has rotted. WordPress core that nobody dared to upgrade, PHP 7.x on a host that stopped patching it, a page builder whose shortcodes sit in every page, jQuery plugins glued to a 2015 theme. At that point every update costs a half-day risk check and every month adds to the debt.
“The design feels dated” does not survive the question of which number should move. If the answer is “it will look better”, plan a refresh of the theme styles and keep the structure, URLs and content that already rank.
Redesign, modernization or a new site
Three projects share one word, and the choice changes budget and risk.
| Redesign (refresh) | Technical modernization | New site | |
|---|---|---|---|
| When it fits | The site sells, the look no longer matches the brand | Slow, hard to update, PHP or plugins blocked | Business model, audience or brand changed |
| Design | New design from you or your designer | Existing design kept, rebuilt cleanly | New design from you or your designer |
| What I change | Theme templates and styles | Theme, plugins, PHP version, hosting setup, database cleanup | Theme, content structure, integrations |
| Content | Stays | Stays, audited and migrated | New structure, content from you |
| URLs | Unchanged | Kept, changed ones get a 301 | New structure, full 301 map |
| SEO risk | Low | Moderate, controlled by the map | Higher, needs a migration plan |
| Duration | Follows scope | Follows scope | Follows scope |
Most projects mix the first two. If the diagnosis points to a new site, see creating WordPress websites and shops. To check your own site first, the redesign readiness checklist has ten questions you can answer yourself.
What you bring and what I build
You supply the graphic design or wireframe, the copy and any brand assets. If you have no designer, I send a spreadsheet template where you mark which elements go on each view; a Figma file works too. I do not do graphic design, UX research, branding or copywriting.
I build and deliver:
- a responsive WordPress theme from your design, block-based with theme.json where it fits, so editors can publish without a developer;
- content migration: posts, pages, products, media, dates, authors, custom fields and SEO metadata, with a row-by-row check after the move;
- the 301 redirect map for every changed URL, crawl-tested on staging;
- performance work measured on LCP, INP and CLS, using field data where the site has enough traffic;
- accessibility in code: semantic HTML, heading order, form labels, keyboard operation, focus states, alt text fields; if the supplied design has contrast problems, I point them out before building;
- staging for your acceptance, then launch, and optional care afterwards.
How a rebuild runs
- Written brief. Current URL, known problems, the design you have, integrations, deadlines.
- Inventory. I crawl the current site, export URLs with traffic and inbound links from your Search Console and analytics, and list every integration: CRM webhooks, analytics events, payment and shipping plugins.
- Quote. Scope, assumptions and a schedule in writing.
- Build. Theme from your design in a Git repository, deployed to staging.
- Migration. Content moved and reconciled, redirect map loaded and crawled on staging.
- Acceptance. You review on staging; every change is described in writing.
- Launch. DNS or server switch, redirect file live, Search Console checked for crawl errors in the following weeks.
What breaks during a WordPress redesign
The redirect map. A site with a thousand URLs needs a thousand rows matching old slug to new slug. Every miss is a 404 on a page that used to rank, so I build the map before the templates.
Internal links. Old posts keep linking to the old URL after it changes. The redirect catches the request, but every internal link then costs an extra hop, so I also rewrite the links in the database.
Integrations. A CRM webhook expecting a specific form field name, a marketing script tied to an old form ID, analytics events firing on selectors that no longer exist. Each one gets re-tested on staging before launch.
Content fields. ACF fields that did not map cleanly, custom post types left out of an export, featured images that lost their alt text. A content audit before the move and reconciliation after it catch these.
Editors. People who knew Elementor now face the block editor. I write a short runbook for the common tasks: adding a post, updating a service page, changing the homepage hero.
Full rebuild or gradual modernization
If the calendar allows, gradual is the lower-risk path. Header and navigation first, then service or product pages, then the blog, checkout last because that is where revenue lives. Each phase goes live, gets real traffic and earns its own decision before the next one starts.
A full rebuild wins in two cases: a rebrand where every page has to change on the same day, and a stack so tangled (builder shortcodes everywhere, no child theme, a database schema improvised years ago) that refactoring costs more than starting the theme again.
Accessibility law in the UK, Ireland and the EU
European Union. The European Accessibility Act, Directive (EU) 2019/882, applies to e-commerce services and several other consumer services provided after 28 June 2025. Microenterprises providing services (fewer than 10 staff and annual turnover or balance sheet total up to 2 million EUR) are exempt from the service accessibility requirements; the exemption does not cover products.
Ireland. The Directive is transposed by S.I. No. 636/2023, the European Union (Accessibility Requirements of Products and Services) Regulations 2023, in operation since 28 June 2025. For e-commerce services the compliance authority is the Competition and Consumer Protection Commission.
United Kingdom. The UK left the EU, so the EAA does not apply there. In England, Wales and Scotland, service providers have a duty to make reasonable adjustments for disabled people under section 29 of the Equality Act 2010.
A rebuild is the cheapest moment to fix accessibility, because the templates are written anyway. My target in code is WCAG 2.1 AA. Contrast, wording and media captions depend on the design and content you supply, so I flag what I find there.
Measuring the result
Before launch I record a baseline: Core Web Vitals, indexed pages, clicks and impressions per landing page, form submissions or orders. After launch the same numbers are compared, so the rebuild is judged on data you already track.
Get started
Send the current URL, the known problems, the design or wireframe you have, the integrations and any deadline through the contact form. I reply in writing with the open questions, then a quote with assumptions.
For care after launch, see WordPress website maintenance.







