Webmaster Central Blog
Official news on crawling and indexing sites for the Google index
Will the Real <Your Site Here> Please Stand Up?
marți, martie 30, 2010
Webmaster Level: Intermediate
In our recent post
on the Google Online Security Blog
, we described our system for identifying phishing pages. Of the millions of webpages that our scanners analyze for phishing, we successfully identify 9 out of 10 phishing pages. Our classification system only incorrectly flags a non-phishing site as a phishing site about 1 in 10,000 times, which is significantly better than similar systems. In our experience, these “false positive” sites are usually built to distribute spam or may be involved with other suspicious activity. If you find that your site has been added to our phishing page list (”Reported Web Forgery!”) by mistake, please
report
the error to us. On the other hand, if your site has been added to our malware list (”This site may harm your computer”), you should follow the instructions
here
. Our team tries to address all complaints within one day, and we usually respond within a few hours.
Unfortunately, sometimes when we try to follow up on your reports, we find that we are just as confused as our automated system. If you run a website, here are some simple guidelines that will allow us to quickly fix any mistakes and help keep your site off our phishing page list in the first place.
-
Don’t ask for usernames and passwords that do not belong to your site.
We consider this behavior phishing by definition, so don’t do it! If you want to provide an add-on service to another site, consider using a public API or
OAuth
instead.
-
Avoid displaying logos that are not yours near login fields.
Someone surfing the web might mistakenly believe that the logo represents your website, and they might be misled into entering personal information into your site that they intended for the other site. Furthermore, we can’t always be sure that you aren’t doing this intentionally, so we might block your site just to be safe. To prevent misunderstandings, we recommend exercising caution when displaying these logos.
-
Minimize the number of domains used by your site, especially for logins.
Asking for a username and password for Site X looks very suspicious on Site Y. Besides making it harder for us to evaluate your website, you may be inadvertently teaching your visitors to ignore suspicious URLs, making them more vulnerable to actual phishing attempts. If you must have your login page on a different domain from your main site, consider using a
transparent proxy
to enable users to access this page from your primary domain. If all else fails...
-
Make it easy to find links to your pages.
It is difficult for us (and for your users) to determine who controls an off-domain page in your site if the links to that page from your main site are hard to find. All it takes to clear this problem up is to have each off-domain page link back to an on-domain page which links to it. If you have not done this, and one of your pages ends up on our list by mistake, please mention in your error report how we can find the link from your main site to the wrongly blocked page. However, if you do nothing else...
-
Don’t send strange links via email or IM.
It’s all but impossible for us to verify unusual links that only appeared in your emails or instant messages. Worse, using these kinds of links conditions your users/customers/friends to click on strange links they receive through email or IM, which can put them at risk for other
Internet crimes
besides phishing.
While we hope you consider these recommendations to be common sense, we’ve seen major e-commerce and financial companies break these guidelines from time to time. Following them will not only improve your experience with our anti-phishing systems, but will also help provide your visitors with a better online experience.
Written by Colin Whittaker, Anti-Phishing Team
Hey!
Check here if your site is mobile-friendly.
Etichete
accessibility
10
advanced
195
AMP
13
Android
2
API
7
apps
7
autocomplete
2
beginner
173
CAPTCHA
1
Chrome
2
cms
1
crawling and indexing
158
encryption
3
events
51
feedback and communication
83
forums
5
general tips
90
geotargeting
1
Google Assistant
3
Google I/O
3
Google Images
3
Google News
2
hacked sites
12
hangout
2
hreflang
3
https
5
images
12
intermediate
205
interstitials
1
javascript
8
job search
2
localization
21
malware
6
mobile
63
mobile-friendly
14
nohacked
1
performance
17
product expert
1
product experts
2
products and services
63
questions
3
ranking
1
recipes
1
rendering
2
Responsive Web Design
3
rich cards
7
rich results
10
search console
35
search for beginners
1
search queries
7
search results
140
security
12
seo
3
sitemaps
46
speed
6
structured data
33
summit
1
TLDs
1
url removals
1
UX
3
verification
8
video
6
webmaster community
24
webmaster forum
1
webmaster guidelines
57
webmaster tools
177
webmasters
3
youtube channel
6
Archive
2020
nov.
oct.
sept.
aug.
iul.
iun.
mai
apr.
mar.
feb.
ian.
2019
dec.
nov.
oct.
sept.
aug.
iul.
iun.
mai
apr.
mar.
feb.
ian.
2018
dec.
nov.
oct.
sept.
aug.
iul.
iun.
mai
apr.
mar.
feb.
ian.
2017
dec.
nov.
oct.
sept.
aug.
iun.
mai
apr.
mar.
feb.
ian.
2016
dec.
nov.
oct.
sept.
aug.
iun.
mai
apr.
mar.
ian.
2015
dec.
nov.
oct.
sept.
aug.
iul.
mai
apr.
mar.
feb.
ian.
2014
dec.
nov.
oct.
sept.
aug.
iul.
iun.
mai
apr.
mar.
feb.
ian.
2013
dec.
nov.
oct.
sept.
aug.
iul.
iun.
mai
apr.
mar.
feb.
ian.
2012
dec.
nov.
oct.
sept.
aug.
iul.
iun.
mai
apr.
mar.
feb.
ian.
2011
dec.
nov.
oct.
sept.
aug.
iul.
iun.
mai
apr.
mar.
feb.
ian.
2010
dec.
nov.
oct.
sept.
aug.
iul.
iun.
mai
apr.
mar.
feb.
ian.
2009
dec.
nov.
oct.
sept.
aug.
iul.
iun.
mai
apr.
mar.
feb.
ian.
2008
dec.
nov.
oct.
sept.
aug.
iul.
iun.
mai
apr.
mar.
feb.
ian.
2007
dec.
nov.
oct.
sept.
aug.
iul.
iun.
mai
apr.
mar.
feb.
ian.
2006
dec.
nov.
oct.
sept.
aug.
Feed
Follow @googlewmc
Give us feedback in our
Product Forums
.
Subscribe via email
Enter your email address:
Delivered by
FeedBurner
