Typing inveterate.com, or following any link, email signature or old backlink that omits "www", lands on Cloudflare's "Error code: 525" page because the origin fails the secure handshake. Even http://inveterate.com redirects into the broken address. Google's own test of the bare domain saw the error page, scored SEO 36/100 and flagged it as blocked from indexing. Only www.inveterate.com works.
First action
Open https://inveterate.com/ in a private window and confirm the 525.
How to measure it
Apex requests answered with a 301 to www
- Now
- –
- Target
- 100%
- By
- 1 week
Steps
Confirm the error
https and http on the apex and two deep links.
Web and Growth Marketer 15 minutes
Add the redirect rule
Apex to www, path preserved, 301, at the Cloudflare edge.
Web and Growth Marketer 30 minutes
Fix the origin
Valid origin certificate or the right SSL mode for the apex.
Web and Growth Marketer 2 hours
Test every variant
http, https, deep links, query strings.
Web and Growth Marketer 30 minutes
Monitor
Uptime check on the apex and www.
Web and Growth Marketer 15 minutes
Recheck search
Search Console coverage and PageSpeed on the apex.
Web and Growth Marketer 1 week
Why it works
In Cloudflare, add a redirect rule that sends every request to inveterate.com (http and https, any path) to the same path on https://www.inveterate.com with a 301, answered at the edge so the origin is never asked. Then fix the origin certificate or SSL mode so the apex works even if the rule is removed. Test the bare domain, a deep link (/pricing, /case-study/true-classic) and http, and add an uptime check on the apex.
Prospects who type the brand name are the warmest traffic a B2B site gets, and right now some of them see an error and leave. A 301 also passes the value of 17 years of links to the bare domain to the pages that work.
Ready to use
ChecklistBare-domain fix list
[ ] https://inveterate.com/ -> 301 to https://www.inveterate.com/ [ ] http://inveterate.com/ -> 301 straight to https://www. [ ] Deep links keep their path (/pricing, /case-study/...) [ ] Origin certificate valid for the apex [ ] Cloudflare cache purged [ ] Uptime monitor on apex and www [ ] PageSpeed rerun on the apex shows the real site
Risks and how to handle them
Redirect loops with existing rules
Test in a staging zone or with one path first.
Cached error responses
Purge the Cloudflare cache after the change.
Evidence
- Your websiteThe bare domain https://inveterate.com/ (no "www") returns Cloudflare "Error code: 525" (SSL handshake failed between Cloudflare and the origin server), checked October 20, 2026. http://inveterate.com/ answers with a 301 to the same broken https address. Only https://www.inveterate.com/ loads.Source
- Google PageSpeedPageSpeed's mobile test of https://inveterate.com/ (October 20, 2026) loaded the error page instead of the site: its largest element is the text "SSL handshake failed", SEO scores 36/100 ("Page has unsuccessful HTTP status code", "Page is blocked from indexing", "robots.txt is not valid", no meta description) and the page weighs 13 KB. Real-visitor data for the origin is good (LCP 1.0s at the 75th percentile, CLS 0.03).Source
- Your websiteHomepage (www): H1 "Loyalty Without Limits", "NEXT-GENERATION LOYALTY PLATFORM"; programs: Free-To-Join, Paid Memberships, Spend-Based Tiers, VIP & Hidden Tiers, "all powered by store credit instead of margin-killing discounts"; a points vs store credit table; integrations with Shopify POS, Attentive, Klaviyo, Postscript. The site never mentions Onward, and a footer link labelled "Better Options" opens a YouTube video.Source