Your site says “Not secure.” We'll make it go away, and set the certificate to renew on its own.
Every visitor sees that warning next to your web address, and when the certificate is the problem, the browser stops them before your page loads. It usually means a certificate lapsed or a setting is off, not that you've been hacked, and those are quick to fix. We find the cause, fix it, turn on automatic renewal, and check it on phones and desktops.
$149 flat · Fixed in 2 business days of access or no charge · No passwords by email
What your customers see
Two warnings, in plain words.
“Not secure” in the address bar
The page loaded over plain HTTP, without the certificate that encrypts it. Either there isn't one, or there is and nothing sends visitors to it. The page still shows, with the warning right beside your address, and anything typed into your forms travels unencrypted.
Your connection is not private
NET::ERR_CERT_DATE_INVALID
A full page: “Your connection is not private”
The certificate expired, or it names a different address, often the www version or your host's own name. Your page doesn't load at all. To reach you, a visitor has to click past a warning that tells them not to.
Chrome got stricter. Since Chrome 154, released September 22, 2026, Chrome asks by default before it opens a site over plain HTTP (Chrome's release notes). Google says it asks when the visitor hasn't been to that site recently (Google), and someone who hasn't been to your site recently is usually a new customer.
Certificates run out sooner. Since March 2026, a new certificate can last at most 200 days, down from 398, and the limit keeps falling to 47 days by March 2029 (CA/Browser Forum). One renewed by hand will lapse more and more often. Automatic renewal is what keeps the fix fixed.
Free · Check it yourself
How to tell which warning you have. A few minutes, on your own phone and computer.
Open your site the way a customer would, on cell data and on a computer, then match what you see. Every one of these has a known fix, and none of them means rebuilding the site.
- “Not secure” in the address bar, and the page loads
- The page came over plain HTTP. Type https:// in front of your address. If that loads with no warning, the certificate is fine and nothing sends visitors to it: a missing redirect. If that shows a full-page warning, the certificate is part of the problem too.
- “Your connection is not private” before the page loads
- The certificate is the problem. In Chrome, tap Advanced to see the code: NET::ERR_CERT_DATE_INVALID means it expired, and NET::ERR_CERT_COMMON_NAME_INVALID means it was issued for a different address. Safari says “This Connection Is Not Private,” and Firefox says “Warning: Potential Security Risk Ahead.”
- One address works and the other warns
- Try both yourbusiness.com and www.yourbusiness.com. A certificate often covers one and not the other, and customers type both.
- No warning, but images are missing or a form won’t send
- Mixed content: the page itself is secure, but it loads a picture or a script over plain HTTP, and the browser blocks it or drops the secure label.
- No warning yet, and you want to know when one is due
- Click the icon at the left end of the address bar, open the connection details, and look for the certificate's expiry date.
Free, no email needed. Yours whether we ever talk or not. If you book, bring what you saw: it's where the fix starts.
What's included
Found, fixed, checked, and written down.
Find what's causing it
An expired, missing or wrong-name certificate, no redirect to HTTPS, or mixed content: images or scripts still loading over plain HTTP.
Fix it
Install or renew a valid certificate, send every visitor to the HTTPS address, fix the mixed content, and turn on automatic renewal.
Check it where your customers are
On an iPhone, an Android phone and desktop browsers, on both the www and the bare address.
A short note in plain words
What was wrong, what we did, and when the certificate renews from now on.
The price and the guarantee
$149, once. Fixed within 2 business days of access, or you don't pay.
$149
One flat price, paid once the warning is gone
The terms, in one sentence: $149, paid only once the warning is gone, to find and fix what's behind your site's browser warning (an expired or wrong-name certificate, a missing HTTPS redirect, or mixed content) and turn on automatic renewal: fixed within 2 business days of getting access, not counting your platform's own certificate queue, or you don't pay, and we never ask for a password by email.
What doesn't count against the 2 business days: your platform's own certificate queue (Shopify, for one, says a new certificate can take up to 48 hours), and anything that waits on your decision, like buying a certificate your host charges for or moving your domain. We name either one on the first day.
If your host won't allow it: some hosts and site builders don't let anyone change how the certificate works. If yours won't allow a fix, you don't pay, and we tell you what your options are.
Covers: one site, its domain and its www address. Most hosts include a free certificate, though some cheaper plans charge after the first year. If yours does, that charge is the host's, and we tell you before anything is bought.
How we get in
We never ask for your password by email.
Many hosts and domain registrars let you invite someone in as a collaborator or delegate, with their own login, and switch them off when the work is done. We use that. If yours doesn't have it, we fix it on a screen share while you drive, and you keep the keys the whole time.
The 2 business days start when we're in. If you're not sure who hosts the site, say so on the call: finding out is part of the job.
Straight answers
What owners ask about the warning.
Is my site hacked?
Usually not. These warnings come from the certificate, one that lapsed or never covered that address, or from a setting that doesn't send visitors to it, and neither means anyone got in. Different signs point to a hack: pages or links you didn't write, your site sending visitors somewhere else, or a red “Dangerous site” or “Deceptive site ahead” screen from the browser. If we see any of those while we're in, we'll tell you plainly.
I'm on Wix, Squarespace or GoDaddy. Can you still fix it?
Yes, in most cases. Wix and Squarespace issue and renew the certificate themselves, so a warning there usually comes from how the domain is connected, and the fix is in the domain's settings. Squarespace makes the certificate once the domain is fully connected, and says a change to its SSL settings can take up to 48 hours. On GoDaddy it depends on the product: the website builder and Managed WordPress look after the certificate, while the cheapest hosting plan includes one for the first year only. Each of them lets you invite someone in without sharing your password, and if the platform won't allow the fix, you don't pay.
Will it come back?
Not from a lapsed certificate, once renewal is automatic and the domain and hosting stay paid. A certificate can now last 200 days at most, so one renewed by hand lapses again within the year. We switch renewal to automatic and check that it works. The other common way it comes back is the domain itself lapsing, so the note tells you when the domain renews and whether auto-renew is on.
Do you need my password?
No, and we never ask for one by email. We use your host's or registrar's collaborator or delegate access, which gives us our own login that you switch off when we're done. If your host doesn't offer that, we do the fix on a screen share while you drive.
What if it isn't fixed in 2 business days?
Then you don't pay. The 2 business days start when we have access. Your platform's own certificate queue doesn't count against them, and neither does anything that waits on your decision, like buying a certificate your host charges for; we name either one on the first day. If your host or site builder won't allow a fix at all, you don't pay either, and we tell you what your options are. Either way, you pay only once the warning is gone.
Site past fixing, or never quite right? Websites, hosted and managed for you →
A note from Nick
Owner to owner.
Customers already find you and look you up. No software builds that part. You did.
Before I wrote a line of code, I spent five years selling door to door and built a sales company to $1.2M+ in a single year at 24. My income depended on the next conversation, the same way yours depends on the next customer. Today I run a small business of my own, here in Charlotte.
On the call, I'll ask what customers have said to you about the site, because you hear from them and I don't. If the fix is a setting you can switch on yourself, I'll tell you where it is.
Nick George · Charlotte, NC
What a client said
“I hired [Nick George AI] to help me make my website (and my company) more visible to potential customers. … Nick did an absolutely fabulous job at SEO’ing my website, and even took it upon himself to fix everything else that was wrong with it. … I could already tell the difference after a week!”
AI training from
NVIDIA · Google · Microsoft · AWS
5 credentials, each with a public verify link. Check them →
Until it's fixed, the warning greets every visitor, new customers included.
Fifteen minutes, and you'll know what it is.
Book a call or send a message with your site's address and what the warning says, from the check above if you ran it. You'll hear back within one business day.
The fix is the whole job. If the site needs more than a fix, we'll say so in the note, and what you do with that is up to you.