Website

nutritionistpro.com is the public marketing site for Nutritionist Pro. It is a WordPress site running on an AWS Lightsail instance in the nexgen_v3 AWS tenant (since 2026-10-21; before that, a 2021 Bitnami instance in the old Axxya tenant). The admin is at nutritionistpro.com/wp-admin, which redirects to the login page at wp-login.php.

It is entirely separate from the Nexgen applications: different hosting (Lightsail rather than Copilot services) and a different technology stack, in the same AWS account. The public product documentation at nutritionistpro.com/docs is a separate Docusaurus site and is not part of this WordPress install. See Documentation for more details on the docs.

Overview of website changes

The short version of changing a page. Each step is expanded in Publishing a change.

1. Make the change in wp-admin, in the editor the page was built with (the Divi Builder or the default editor), and select Update or Publish.
2. Check the sitemap. Yoast SEO rebuilds it when a page is saved, so there is nothing to regenerate. Confirm the page's lastmod date moved.
3. Check llms.txt. The Website LLMs.txt plugin rebuilds it when a page is saved. Confirm its Last-Modified date moved. If it did not, go to Tools > Llms.txt in wp-admin and select Generate Now.
4. In Google Search Console, open URL Inspection for the changed page and select Request Indexing.

If the change causes a problem, restore the previous version of the page from Revisions on its edit screen.

The stack

Lightsail in the nexgen_v3 tenant

The website runs on the Lightsail instance nutritionistpro-web in the nexgen_v3 AWS tenant, the same account as the Nexgen apps, under Lightsail rather than the Copilot services. Until 2026-10-21 it ran in the old Axxya tenant; that instance is kept only for rollback and is described at the end of Hosting and deployment.

• DNS and CDN: Cloudflare (zone nutritionistpro.com)
• Compute: AWS Lightsail instance nutritionistpro-web, nexgen_v3 tenant, static IP 35.174.58.107
• Server stack: the Lightsail-packaged WordPress blueprint on Debian 12
• Web server: Apache 2.4.68 with PHP as an Apache module
• PHP: 8.2.35, the 2026-10-21 release that fixes CVE-2026-109618 and CVE-2026-109619; upstream support for 8.2 ends on 2026-12-31 and Debian patches it after that
• Database: MariaDB 10.11, local to the instance
• WordPress 7.1.3 with the Divi theme
• SEO plugin: Yoast SEO
• llms.txt plugin: Website LLMs.txt

Other components worth knowing about: Gravity Forms (with GravityExport), WPCode, WP Rocket, and the AIOVG video plugin (which owns the /player-embed/ and /video-tag/ URLs). The full inventory, including the Lightsail instance, certificate, mail, backups, and every plugin, is on Hosting and deployment. How the site got onto this instance, and what the old one looked like, is on Moving the site to the new AWS tenant.

Where things live

• The instance, software versions, certificate, mail, backups, plugins, and connected services: Hosting and deployment
• Registrar, nameservers, and every DNS record: Domain and DNS
• Server access and file paths: SSH access
• The wp-config.php URL constants and why they matter: WordPress configuration
• The main menu, page editors, images, and Yoast page titles: Content editing
• The desktop trial forms and the snippet that sends them to Freshsales: Trial sources
• DNS, SSL, crawler controls, and caching: Cloudflare
• Search Console property, correct sign-in account, and how to read the index reports: Google Search Console
• Adding a release to the Release Notes page after a dev milestone closes: Milestones and release notes
• What changed this year and what is still open: Changes made in 2026
• How the site was moved to the nexgen_v3 tenant on 2026-10-21, and how to rebuild it: Moving the site to the new AWS tenant
• The temporary measures applied to the old instance after the October 2026 PHP release: PHP security stopgap (October 2026)

robots.txt is virtual

There is no robots.txt file on disk. WordPress generates it per request and Yoast filters extra lines into it, which is why the response returns content-type: text/html with PHP headers rather than text/plain. Editing it means either using Yoast SEO > Tools > File editor (which writes a real file), or changing what feeds it. The Sitemap: line is derived from the site URL, so it is fixed by correcting the URL constants rather than by editing robots.txt. See WordPress configuration.