A REAL OBSERVATION · OUR OWN DOMAIN
A homepage that
returns an error.
This is a single finding from our own website, not a complete client audit or a testimonial. It shows how we separate evidence from assumptions.
At 09:13 UTC on 4 October 2026, direct GET requests to https://proudnations.com/ and https://www.proudnations.com/ returned HTTP 404. The www request ended at the apex address. The separate audit subdomain hosts this service.
How to reproduce
Request each exact URL and record the final document response, redirect chain and time. Check another device or network to distinguish a repeatable public failure from a local issue.
Why it matters
A visitor opening the homepage cannot reach the intended offer through that address while it returns an error. We have no analytics evidence of how many visitors were affected and do not attach an invented sales-loss figure.
Recommended action
- Review the existing storefront's domain assignment and publication state through authorised owner access.
- Identify the actual cause before changing configuration or enabling a paid plan.
- After correcting it, verify the public homepage, redirect behaviour and intended contact or product path on desktop and phone.
Acceptance check
The intended public homepage loads successfully, without an error response, and its intended next step is usable on both screen sizes.
Scope limit: this observation did not test payment, customer accounts or the storefront admin. The cause remains unverified. This example is dated evidence; later changes may produce a different response.
Request your €149 audit ↗