Back
Question
Security issue google search console
Captura de pantalla 2024-10-01 155619.png
54.7 KB
I have just added my domain to the Google search console and I am getting this error. Can anyone help me?
We're a group of makers shipping together. We help each other stay accountable and reach our goals.
Apply for accessGo to Homepage | g h |
Go to Done Todos | g d |
Go to Questions | g q |
Compose a New Todo | n |
Go to Search | / |
Show this dialog | ? |
👋 Join WIP to participate
What's the link to your site? What does it say when you click on Misleading pages?
stripeautomail.com and this is what is says:
Thank you for your help, it's all solved now. It was just a bug
I don't know if it's related, but maybe use your own domain instead of stripe-app-production-5848.up.railway.app for your API?
It's all solved now, thank you for your help!
Sure.
When you sign into GSC, go to Security & Manual Actions then Security Issues.
Which pages specifically are showing up?
Have you already used a security scanner on your site? If not, use one that's compatible with where you're hosting. (I can help if you're using WP or Squarespace.)
Actually go into your site's file system, if possible, and go through every single file to look for any weird redirects or suspicious files.
(You can run an Ahref's site audit (free) and it'll tell you if there are any redirects.)
Make sure every part of your site (all components) are updated to the latest versions because they're the most secure. This includes website themes if you didn't build it from scratch.
Actually, now that I think about it, go and run an Ahref's audit anyway, and show us what that looks like. Some stuff could still be loading with HTTP instead of HTTPS, and that could cause an issue.
Does your site link out to software, like installers? If so, double-check those for PUPs. That'd definitely trigger that warning if any exist.
After you do all that and it still doesn't change, let me know. I've got more suggestions you can try to troubleshoot, but they'd be on a server level, and I'm not as confident doing that as the above (but I can tag a local friend who is a genius with that stuff).
Thank you so much for your help, you really are a genius. It seems that this has been resolved, I emailed them and apparently everything was correct, it was just a bug. However, I will keep these processes in mind in case it happens again
I'm glad everything was fixed!
Not a genius, just someone who has had to deal with brain-melting situations and figure them out for clients 😹 I've learned to keep a little reference doc so I don't have to reinvent the wheel every time.