Introduction
The nutritionistpro.com WordPress marketing site, where it is hosted, and how the pieces fit together.
Hosting and deployment
The AWS Lightsail instance that runs nutritionistpro.com, its software stack, certificate, mail, backups, plugins, and the external services connected to it.
Domain and DNS
Where nutritionistpro.com is registered, where its nameservers point, every DNS record and who owns it, and what to check before changing any of them.
SSH access
Connecting to the Lightsail instance that runs the nutritionistpro.com WordPress site, and where the important files live.
WordPress configuration
The wp-config.php site URL constants, why the image defaults broke the sitemap and robots.txt, and how to verify the fix.
Outgoing email
Every email nutritionistpro.com sends through the WP Mail SMTP Pro plugin, what each one is for, when it is sent and to whom, and how the plugin is set up since the switch from Amazon SES to Microsoft 365 on 2026-10-27.
Content editing
How the nutritionistpro.com pages, menu, images, and page titles are managed in WordPress.
Cloudflare
The Cloudflare zone in front of nutritionistpro.com, its DNS, SSL, crawler, and caching settings, and the open hardening items.
Google Search Console
The Search Console property for nutritionistpro.com, which Google account can reach it, and how to interpret the page indexing report.
Changes in 2026
A dated list of every configuration change made to the nutritionistpro.com website, its domain, and its Cloudflare zone during 2026, and the items still open.
Moving to the new tenant
The procedure for moving the nutritionistpro.com WordPress site from the old Axxya AWS tenant to a fresh Lightsail-packaged WordPress instance in the nexgen_v3 tenant, including the PHP upgrade that the October 2026 security release made urgent.
PHP security stopgap
The temporary measures applied to the old nutritionistpro.com origin on 2026-10-21, between the PHP security release that morning and the cutover to a patched instance that evening. Its PHP 7.4 could not receive, and why the move to a new instance is the only real fix.