品真cpa广告联盟
http://ask.seowhy.com/favicon.ico
看看搜问的ico小图标 一般存放在根目录 是网站的标志，有利于识别当前窗口是在哪个网站。
对于seo的作用可以忽略了。如果你是知名品牌站的话ico小图标会出现在搜索结果的标题前面。
这个图标可以换，你可以用百度在线美图秀秀简单写个字来制作，或是百度ico小图标制作有很多在线制作的，百度搜索：制作ico图标，当然还可以淘宝找人做下。这个ico小图标一般存放在网站根目录。
ico小图标大小：32x32 或 16x16 做好原始图像（可以是: .jpg .jpeg .gif .png等图像格式 原图大小可以是等比例的如：400x400），然后在可以生成ico图标的网站生成.ico后缀的图片格式就可以了。
其他讨论这个ico小图标的帖子：
http://ask.seowhy.com/question/1393 (百度搜索前面出现了小标志)
http://ask.seowhy.com/question/5059 (如何在百度搜索结果中出现小logo和官网图标)
http://ask.seowhy.com/question/8365 （想问下有的站点在网页展示的时候有logo，而有的网站却没有？这个如何才能加上呢？ ）
ps：回答过后，感觉我的回答关键词密度应该够了，哈哈
这个是ico图标，百度一下ico图标如何设置。网上很多教程！
###
把代码插在
图标有什么用呢？
它的意义不在于本身有何用，在于你要赋予它的作用！用户通过图标就能知道是代表你的网站，同时还了解网站是干什么的（更有甚者还能传递某种意义，类似奥运会吉祥物）：图标有没有用？它的作用大不大呢？###
另外一个问cpa联盟的也是你吧？刚要提交，问题没了。答案如下。
先不说流量了。网站整体设计的一塌糊涂，嗯，当然，可以说我们是cpa联盟，不用管界面。这个问题上面评论说过了。补充下。
那就说网站主要怎么相信你？没有一丝可以让我有足够投放广告的信心。
哎，不说了，自己揣摩下吧。联盟不是那么好做的，需要不停的找站长找站长找站长。。。。
做seo点能够唔会用百度呢，自己去搜寻下用下唔就会咗啦，简单快捷。###
那个是网站的图标，可以是你网站的标识之类的。
可以换的，一般会在网站程序的图片文件或者根目录下，会有一个 文件，那个就是所显示的图标，替换就可以了。
这个图标有两个地方展示，一个是百度搜索结果tilte 标题前面。一个是浏览器上显示，设置方法是在网站根目录有个 favicon 文件 ，网上有教程很好做。生成一个图标就成了。在百度搜索结果里的图标。目前不能自由控制，是有百度自己来控制是否显示，一般是知名品牌网站会显示
###不是优化的问题，这个问题可以找美工，想要什么样的让他给你做，让程序给你替换，没什么作用的。
###你还没入门
###这个主要起到一个醒目的作用，可以提高用户的点击率，对老用户也有一个很好的导向作用。
###在首页模板中meta属性下面行代码插入
网站根目录 放好这个文件，当然前缀名字favicon可以自己改动，
如果你只是想要换的话就只要改ICO这文件，这种起得的是企业形象问题，谈不上什么SEO优化，一般的网站用公司logo做，如果是B2B类的网站可以让美工设计下。
想要快照的中小有图标，这个很难，一般hao123中你的网站基本就有小图标了，或者权重在6以上（目测分析）
对于这个的优化还没有一个具体的案例指向，一般的只是百度抓取的一个图标，这个就相当于你网站的商标这个性质
###在本页，点击右键，查看源文件，如下的代码。
模仿搜外问答即可。
A favicon is a graphic image (icon) associated with a particular Web page and/or Web Site. Many recent user agents (such as graphical browsers and newsreaders) display them as a visual reminder of the Web site identity in the address bar or in tabs. The wikipedia includes an article about favicons
To add a favicon to your Web site, you'll need both an image and a method for specifying that the image is to be used as a favicon. This document explains the method preferred by W3C for specifying the favicon. There is another common method that is illustrated below, with an explanation of why that method is inconsistent with some principles of Web architecture. Both methods only APPly to HTML and XHTML, one of the limitations discussed below.
This document does not discuss in detail how to create a favicon image. However, the format for the image you have chosen must be 16x16 pixels or 32x32 pixels, using either 8-bit or 24-bit colors. The format of the image must be one of PNG (a W3C standard), GIF, or ICO.
Method 1 (Preferred): Use of a rel attribute value defined in a profile
The first approach for specifying a favicon is to use the rel attribute value "icon" and to define what the value means via a profile; profiles are discussed in more detail below. In this HTML example, the favicon identified via the URI example。com/myicon.png as being a favicon:
<!DOCTYPE html
PUBLIC "-//W3C//DTD HTML "
"">
<html lang="en-US">
<head profile="">
<link rel="icon"
type="image/png"
href="">
[…]
</head>
[…]
</html>
The XHTML version looks very similar:
<!DOCTYPE html
PUBLIC "-//W3C//DTD XHTML "
"">
<html
xmlns=""
xml:lang="en-US"
lang="en-US">
<head profile="">
<link rel="icon"
type="image/png"
href="/somewhere/myicon.png" />
[…]
</head>
[…]
</html>
Method 2 (Discouraged): Putting the favicon at a predefined URI
A second method for specifying a favicon relies on using a predefined URI to identify the image: "/favicon", which is relative to the server root. This method works because some browsers have been programmed to look for favicons using that URI. This approach is inconsistent with some principles of Web architecture and is being discussed by W3C's Technical Architecture Group (TAG) as their issue siteData-36. To summarize the issue: The Web architecture authorizes site managers to manage their URI space (for a given domain name) as they see fit. Conventions that do not represent community agreement and that reduce the options available to a site manager do not scale and may lead to conflict (since there is no well-known list of these predefined URIs). One practical consideration illustrates the problem: many users have Web sites even though they do not have their own domain name. These users cannot specify favicons using the second method if they cannot write to the server root. However, they can use method one to specify a favicon since it is more flexible and does not constrain the site manager to use a single favicon at a single place on the site.
There are a few other well-known encroachments on URI space, including the "Robots.txt" file and the location of a P3P privacy policy. The Technical Architecture Group is exploring alternatives that do not impinge on URI space without license.
Use of Profiles to Define Terms Such as "icon"
Loosely speaking, a profile is a definition of set of terms. Ideally, a profile includes both machine-readable information and human-readable information. In HTML and XHTML , a few attributes such as the rel attribute do not have a predefined set of values. Instead, the author can provide values according to need, and then use a profile to explain what the values mean. In our case, we have recommend that authors use the value "icon" and a profile that explains that "when we say icon, we mean 'this is a favicon.'"
In Method 1 above, we use the rel attribute with the LINK element and choose a profile with the profile attribute on the HEAD element.
We defined a profile which you can freely use for your own sites.
Limitations
There are several limitations to the approaches described above, including the preferred method (which is why the TAG continues to work on the question):
- The approaches only work in HTML or XHTML
- The preferred approach associates a favicon with an HTML document, not a collection of documents (, a site)
- The proposed profile for defining the "icon" value is not a recognized standard, which means there may be interoperability issues in practice.
- There is no standard (at least defined by HTML ) for machine-readable profiles that would allow a browser to know "this means an image is a favicon." Thus, a browser has to be programmed in advance to recognize this particular value of rel. For more information on the use of profiles in HTML and XHTML, see GRDDL
The following QA Interest Group participants and W3C staff have contributed significantly to the content of this document: Dominique Hazaël-Massieux (W3C), Chris Lilley (W3C), and Olivier Théreaux (W3C).
本文来自投稿，不代表微盟圈立场，如若转载，请注明出处：https://www.vm7.com/a/ask/26816.html
