How to migrate WordPress to a new domain without breaking page builders
Move a WordPress site to a new domain with a serialization-safe search and replace, so Elementor, widgets and plugin settings survive the change.
Problem-first guides written by the people who build and run the Dragon Core plugins. Each one is a reference we keep current, not a dated post.
Moving WordPress between domains, hosts and environments without losing anything.
Move a WordPress site to a new domain with a serialization-safe search and replace, so Elementor, widgets and plugin settings survive the change.
A step-by-step plan for moving a WordPress site to a new hosting provider: staging on the new server, a clean database transfer, DNS cutover and rollback.
Broken links, redirects and the upkeep that stops a site quietly rotting.
Find broken internal, external and image links across a WordPress site, triage them without false alarms, fix them safely in the block editor, and stop new ones appearing.
Why people leave the cloud-based Broken Link Checker, what actually matters in a link checker (local engine, no credits, no false positives, safe fixing), and where Dragon Broken Links fits.
How an agency keeps dozens of sites free of dead links without opening each one: a scheduled full re-scan, one email when links newly break, bulk domain fixes and a CSV for the client report.
A redesign changes URLs. This is how to map old to new before launch, build exact, prefix and regex redirects, triage real 404s after launch, and stop new dead ends appearing.
How to tell server time from front-end weight, measure what each plugin actually costs with leave-one-out profiling, read the results honestly, and prove the fix with a before-and-after scan.
Why sites get slower one update at a time, how to keep a measured baseline, scan after every update, and get an email that names the change responsible, only once a second scan confirms it.
How WP-Cron actually works, the four reasons scheduled tasks stop running, how to diagnose which one you have in a click, and how to replace the built-in scheduler with a real system cron.
Logins, second factors and an audit trail you can trust when something goes wrong.
Why every multi-user WordPress site needs an audit trail, what a good one records, how a hash-chained log proves it has not been edited, and how to use it in an incident.
Keeping what you have published working for you: decaying posts, internal links, alt text.
Old posts lose traffic quietly. How to spot decay early with GA4 and Search Console data, decide which posts are worth refreshing, and what a refresh that recovers rankings actually involves.
Why orphan content and thin internal linking hold a site back, how to find the pages nothing links to, how to rank link opportunities by real relevance, and how to add links without wrecking the copy.
What alt text is for, what good alt text looks like, why most libraries are missing it, and how to generate it for existing images and new uploads with your own AI key at a fraction of a cent each.
Store-specific workflows: who sees what, and what happens when an order lands.
How to run trade-only ranges, client-specific products and members-only collections in one WooCommerce store, with visibility rules by role, category and individual customer.
CRA, NIS2, PCI DSS and the paperwork that clients and auditors now ask WordPress teams for.
What the EU Cyber Resilience Act and NIS2 actually ask of a WordPress site, the dates that matter, and a checklist you can evidence rather than just tick.
What a Software Bill of Materials is, why clients now ask WordPress teams for one, what it should contain, CycloneDX versus SPDX, and how to export one in CycloneDX.
Since 31 March 2025 card-taking stores have to show which scripts run on their payment pages and that changes get noticed. What that means for WooCommerce and how to keep the record.