Cybersecurity + Data Migration Support

Objective

Support the transition of publishing content toward Substack while improving the security and operational stability of the existing WordPress ecosystem. The work included content review, subscriber preparation, abuse reduction, admin hardening, and practical cleanup around automation and site presentation.

What I completed

• Reviewed what content could move safely and what needed to remain on WordPress.
• Prepared subscriber data for migration review, but intentionally did not trigger a bulk Substack import once it was clear that it would auto-email the audience.
• Identified suspicious checkout and account patterns consistent with card-testing and bot activity.
• Cleaned suspicious Mailchimp subscribers and supported API key rotation after audience pollution concerns.
• Enabled reCAPTCHA and MFA on admin access and changed the default WordPress login path to reduce automated attacks.
• Completed front-end SEO work and cleaned the visible Substack integration and spacing on the live site.
• Updated the post-class follow-up email on earthstudiosonline.com so customers receive a delayed review and pottery pickup reminder.
• Escalated Redis and database instability to the hosting contact when the issue pointed beyond normal WordPress admin work.

Why this mattered

The strongest value here was judgment. Some work was worth implementing immediately, like hardening login access and cleaning suspicious records. Other work needed restraint. Holding back the direct subscriber import avoided spamming the audience, and escalating server instability prevented wasted time chasing a problem that belonged to the hosting layer.