Website

nutritionistpro.com is the public marketing site for Nutritionist Pro. It is a WordPress site and is entirely separate from the Nexgen applications: different hosting, different AWS tenant, and a different technology stack. The public product documentation at nutritionistpro.com/docs is a separate Docusaurus site and is not part of this WordPress install. See Documentation for that.

Old Axxya AWS tenant, not the Nexgen V3 tenant

The website runs on AWS Lightsail in the old Axxya tenant. This is not the tenant that runs nexgen_v3. Signing in to the wrong AWS account is the most common reason someone cannot find the instance. Check which tenant you are in before concluding the server is missing.

The stack

• DNS and CDN: Cloudflare (zone nutritionistpro.com)
• Compute: AWS Lightsail instance, old Axxya tenant
• Server stack: Bitnami WordPress
• Web server: Apache with PHP-FPM
• PHP: 7.4.24
• Database: MariaDB 10.3.31, local to the instance
• SEO plugin: Yoast SEO

Other components worth knowing about: Gravity Forms (with GravityExport), the AIOVG video plugin (which owns the /player-embed/ and /video-tag/ URLs), and the Divi theme.

Where things live

• Server access and file paths: SSH access
• The wp-config.php URL constants and why they matter: WordPress configuration
• DNS, SSL, crawler controls, and caching: Cloudflare
• Search Console property, correct sign-in account, and how to read the index reports: Google Search Console

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.