Add, edit, or delete roles and configure exactly what each one can do. A role with users assigned, or the built-in Super Admin role, can't be deleted.

A Client groups one or more websites under the same name, picked on the Add/Edit Website form or added directly here. Renaming one here updates it everywhere it's used, immediately. Deleting one unassigns it from every website using it — they go back to "— No Client —" — rather than deleting or hiding the websites themselves.

Scoring & Status Reference

The exact thresholds used wherever this app shows a website's status — Websites, Speed Performance, and the Dashboard. Not editable here; these are fixed scoring rules, not per-site preferences.

A separate status is also computed and stored right after each scan for internal bookkeeping, using lab-measured Core Web Vitals instead of real-user field data and without the page-weight rule — it can occasionally differ from what's shown throughout the app, which always reflects the logic above.

PageSpeed Insights and GTmetrix results come from Google's / GTmetrix's own servers, not this system, so they're never affected by a client's firewall. The real-time SSL certificate check and the Audit & Maintenance checks (homepage fetch, robots.txt, sitemap, llms.txt, and a couple of fixed CMS-detection paths) run directly from this backend as the identity below — they're the ones that can get blocked, and the ones worth allowlisting on a new client website.

This is the exact identity string this backend sends with every SSL-certificate check and Audit & Maintenance request — never for PageSpeed Insights or GTmetrix, which never touch the client's server at all. A client's WAF or security plugin has no way to tell this apart from a malicious scraper unless it's told to allow it, which is exactly what the 6 setups below walk through. If a website's SSL check or Audit checks suddenly start failing/timing out right after a client installs or updates a security plugin, this is almost always why — allowlisting the IP and this exact User-Agent string resolves it.

The thedigitalintellect.com/bot-info URL identifies TDI as the operator, not the deployment — it stays the same no matter which server, environment, or client website is being scanned. It only needs to change if TDI's own domain changes, or if this system is ever white-labeled for another agency. The egress IP above should be re-confirmed if the backend is ever redeployed to a different server.