What the warning means, how to keep working in the meantime, and how to get a legitimate storefront reviewed and cleared.
Summary
A browser is showing visitors a red “Dangerous site” or “Deceptive site” warning on one of your storefronts. For branded print storefronts this is nearly always a false positive: an automated system has mistaken a legitimate portal for a phishing page. This guide covers what to do now and how to stop it recurring. For the background on why it happens, see Why search engines flag branded storefronts.
Most important thing to know
This usually is not an SSL or certificate fault, and usually nothing is broken on your store. The warning comes from a search engine’s phishing detection reacting to how the page looks (brand, login, little context), not from an error in Infigo. So the fix is a review request plus adding context, not a rebuild.
Environment
- A branded storefront showing a browser security warning (commonly in Chrome and Firefox; Edge may differ).
- Access to the organisation’s Google Search Console for the affected domain (for the review request).
- Your Infigo Customer Success Manager or the Support team.
Step 1 · Confirm what’s happening
Note the exact wording of the warning and which browsers show it. You can check how Google currently classifies a domain on its public Safe Browsing site-status page. If several of your storefronts went dark at once, note them all. That pattern points to storefronts sharing a certificate, which the Support team can help separate.
Step 2 · Keep working in the meantime
Your storefront usually stays reachable on its underlying Infigo domain (for example https://<yourstore>.infigosoftware.com/) even while a custom domain is being warned on. Ask Support for the correct interim address if you need one, so your users can keep ordering while the review is in progress.
Step 3 · Raise a Support ticket
Contact your Customer Success Manager or raise a Support ticket straight away. Infigo can:
- confirm whether it’s an SSL issue or a search-engine flag (usually the latter);
- separate storefronts that share a certificate, so one flagged store stops affecting the others; and
- advise on the review request and the context changes below.
Step 4 · Request a review from the search engine
For a Google “Deceptive site” flag, the owner of the affected domain requests a review in Google Search Console:
- Sign in to Google Search Console and select the affected property.
- Open Security & Manual Actions › Security issues.
- Review the flagged pages and make any changes Google requests.
- Choose Request review, confirm the issues are addressed, and in the description explain that the domain is a legitimate print-ordering store. For example:
Suggested review wordingThis is a legitimate online print-ordering store, operated by <Your Company> on behalf of <Company>, hosted on Infigo’s web-to-print platform (https://infigo.net). It provides authorised <Company> users a place to order branded printed goods. The page has been updated to clearly describe its purpose and operator.
If Microsoft Edge shows the warning, you can report the site through Microsoft’s SmartScreen report form too. You can also report a specific incorrect Google warning with Google’s Report incorrect phishing warning form. Reviews can take some time, and a browser or firewall may cache the old warning after it clears, so re-test in a fresh incognito session.
Step 5 · Remove the cause so it doesn’t recur
Adding context is what actually clears the underlying signal, so make these changes before or right after the review:
- Add descriptive text to the login page saying what the store is, who it’s for and who operates it. In brief: put your wording into an HTML Content Block, then place it on the login page with the Layout Manager. The step-by-step how-to shows this with screenshots.
- Show the brand’s logo with print or ordering context, not identical to their public site.
- Use a descriptive domain or subdomain.
- Move any pre-login downloadable files behind the login.
Verification
- Google Search Console shows the security issue cleared or the review approved for the domain.
- The storefront loads without a warning in a fresh incognito window (clear the cache or try another network if it persists locally).
- The login page now clearly states the store’s purpose and operator.
Good to know
- Being flagged does not mean your site was hacked or your certificate is invalid. It’s an automated impersonation judgement about how the page looks.
- When several storefronts are flagged together, it’s usually because they share one certificate. Separating them (Support can do this) stops the spread.
- Asking a few users to submit the “incorrect warning” report can help, but the Search Console review by the domain owner is the primary route.
Related
Search Terms
dangerous site warning, deceptive site, storefront blocked, phishing false positive, Google Search Console review, request review security issues, safe browsing report, storefront flagged, remove dangerous site warning, storefronts down after SSL change, shared certificate flagged