KEYWORDS
- 格式:pdf
- 大小:24.63 KB
- 文档页数:2
Keywords简介Keywords又叫关键词、关键字,其就是一个网站管理者给网站某个页面设定的以便用户通过搜索引擎能搜到本网页的词汇,关键词代表了网站的市场定位。
网站的首页关键词至关重要。
首页网站关键词代表了网站主题内容,内页和栏目页的关键词一般紧扣页面主题,代表的是当前页面或者栏目内容的主体。
什么是keywords密度keywords密度是指keywords出现的次数和keywords关联字词出现的次数与整个网页文本之比,keywords在文本中出现的次数越多,那么keywords密度越高,反之就越低。
运用keywords密度比例现在主流搜索引擎中,baidu、google、yahoo!、MSN、sogou、iask等都将keywords密度作为其排名算法考虑因素之一,每个搜索引擎都有不同的算法计算密度比例从而获得排名位置,当然,容忍的关键字词密度容量是不一样的,我的观察是容忍从大到小排列依次是baidu,MSN,然后是google,sogou ,iask,yahoo!最低。
公式比例来限定密度很遗憾的告诉你,没有一个准确的公式。
现在有SEO站点中提到的是2%~8%以内,但根据最新国外和我自己的研究表明:如果需要在各个搜索引擎中都有很好的表现,请控制keywords 密度在5%左右。
当然,并不能排除在一个页面中出现keywords密度很高的情况,这个如果是实际需要的,还是可以保留,毕竟网站是给客户看的,尽量提供最有价值的信息给访客才是最重要的考虑点之一,不过需要澄清的是,那样的页面有可能会被搜索引擎自动的过滤掉。
允许出现的位置由于keywords密度是相对于整个网页的文本之比,那么对于出现的位置来说,可以出现keyword的地方可以是title,元标签,文本正文或者其他地方。
有人使用网页中的alt属性来做为keywords密度加强,这个属性在搜索引擎中的权值已经被降低,但不是说没有用,点石小鹏给出的建议是:结合alt属性中的锚文本和主页中的其他元素告诉搜索引擎该网页的主题。
ABAQUS帮助里关键字(keywords)翻译(2013-03-06 10:42:48)转载▼分类:abaqus转自人人网总规则1、关键字必须以*号开头,且关键字前无空格2、**为注释行,它可以出现在中的任何地方3、当关键字后带有时,关键词后必须采用逗号隔开4、参数间都采用逗号隔开5、关键词可以采用简写的方式,只要程序能识别就可以了6、不需使用隔行符,如果参数比较多,一行放不下,可以另起一行,只要在上一行的末尾加逗号便可以-----------------------------------------------------------------------------------------------------------------------------------------*AMPLITUDE:幅值这个选项允许任意的载荷、和其它指定的数值在一个分析步中随时间的变化(或者在ABAQUS/Standard分析中随着的变化)。
必需的参数:NAME:幅值曲线的名字可选参数:DEFINITION:设置definition=Tabular(默认)给出表格形式的幅值-时间(或幅值-频率)定义。
设置DEFINITION=EQUALLY SPACED/PERIODIC/MODULATED/DECAY/SMOOTH STEP/SOLUTION DEPENDENT或BUBBLE来定义其他形式的幅值曲线。
INPUT:设置该参数等于替换输入文件名字。
TIME:设置TIME=STEP TIME(默认)则表示分析步时间或频率。
TIME=TOTAL TIME表示总时间。
VALUE:设置VALUE=RELATIVE(默认),定义相对幅值。
VALUE=ABSOLUTE表示绝对幅值,此时,行中载荷选项内的值将被省略,而且当温度是指定给已定义了温度TEMPERATURE=GRADIENTS(默认)梁上或壳上的,不能使用ABSOLUTE。
keywords与description还需要写吗keywords又叫关键词、关键字,其就是一个网站管理者给网站某个页面设定的以便用户通过搜索引擎能搜到本网页的词汇,关键词代表了网站的市场定位。
description是对网页内容的精练概。
最近一直看到有朋友在论坛,群里讨论网站是否还需要写keywords与description这两个META标签。
Description我觉得不需要太多的讨论,虽然description的内容和权重没有关系,但是他是给搜索用户看的,让用户更快速简单的知道你网站的内容,所以我觉得他依然是重要而且必须的。
而keywords的争论一直没有停过,支持取消keywords的理由主要是:1、 keywords初衷是帮助搜索引擎判断页面的关键词,但很多网站用大量堆积关键词可以获得好的排名,所以搜索引擎不得不改变算法,去掉了关于keywords算法因子。
2、搜索引擎已经更智能了,从搜索引擎可以根据网站的内容判断并修改搜索内容中网站title的展示,而不是你写什么title就显示什么了,这点可以看出现在的搜索算法已经智能到不需要keywords来获取网站的内容关键字了。
3、因为现在很多网站的内容比较复杂,如论坛或者带评论的网站,keywords 的内容反而并不能概况网站实际的内容,而遭到搜索惩罚。
4、某些知名SEO说搜索引擎还在读取keywords内容,是为了判断SEO行为。
支持继续写keywords的理由1、各大网站都有写keywords,说明keywords还是重要的。
2、搜索引擎并没有正式的说过keywords标签已经不需要了。
3、通过自己的一些操作再证明keywords还是有效的。
个人觉得不能否认keywords在搜索引擎的作用在降低,毕竟搜索引擎会越来越智能。
但至少在现在来说,keywords还是有一定作用的,只是这个作用大。
比如说首页写了keywords可以让搜索马上判断出网站主要的一个内容。
怎么写网站关键词Keywords?今天德恒网站管家要跟大家分享下对于SEO中网站关键字的心得和写法。
Kewords是用户不能直接在网页前台看得到,只有查看网页源代码才行,有很多人说百度已经降低了对Keywords的权重,不写关键词搜索引擎也能对网站做出正确的分析,写不写keywords不重要,要不要写关键词的问题对很多新手来说很纠结。
对于这个问题德恒网站管家还是建议大家不要去考验搜索引擎的分析能力,因为网站推广搜索引擎分析错误,损失的不是他而是你因此keywords正确书写非常的必要。
接下来我们来看看如何来写网站关键词。
Keywords的主要作用是把当前网页的内容用几个简明扼要的词语来概述一下。
首页keywords的写法:一般来说首页keywords的写法就是,“网站名称+ 主打几个栏目名+ 主打的几个关键词”。
栏目页keywords的写法:把当前栏目的名称和栏目的几个分类列表名称写上。
栏目页keywords的写法一般来说是这样:“栏目名称+ 栏目关键词+ 栏目下的几个分类”。
内容页keywords的写法:内容页面的关键词我们也一般来说的话,就提取我们当前网页主要内容的几个关键词,然后写上就可以了,其他的大可不必添加的,除非你是为了刻意的增加关键词密度而做。
最后还要提醒大家的是keywords的个数一般不要超过7个,最好是3到4个,因为太多的话会让搜索引擎认为过度优化。
网站keywords中的隔开符一般是用半角的逗号。
一旦写好,便不要进行随意更改,过度的修改会使得网站被降权,所以在选择keywords时一定要充分考虑整个网站。
今天关于SEO中keywords问题的分享就到这里,德恒网站管家将和大家一起成长,想了解更多SEO知识请到德恒文化传播有限公司官网.。
META标签的写法包括以下几种:META标签的Keywords:代表说明网站的关键词是什么,写法为:<meta name="Keywords" content="信息参数">。
META标签的Description:代表说明网站的主要内容,概况是什么,写法为:<meta name="Description" content="信息参数">。
META标签的author:代表说明网页版权作者信息,写法为:<meta name="author" content="信息参数">。
META标签的COPYRIGHT:代表说明网站版权信息,写法为:<META NAME="COPYRIGHT" CONTENT="信息参数">。
Content-Type和Content-Language:显示字符集的设定。
Refresh:刷新,用法为<meta http-equiv="Refresh" Content="秒数">。
Expires:期限,用法为<meta http-equiv="Expires" Content="日期时间">。
Pragma:cach模式,用法为<meta http-equiv="Pragma" Content="No-cach">。
Set-Cookie:cookie设定,用法为<meta http-equiv="Set-Cookie" Content="cookievalue=xxx; expires=Wednesday,21-Oct-98 16:14:21 GMT; path=/">。
title、keywords、description的写法及需注意的重点时至今日,还有很多人在纠结着到底网站的title、keywords、description要不要按照一定的标准去书写,因为这个标准的确没有官方的认可。
而现在很多人滥用之就常常导致被搜索引擎认为是在堆砌关键词进而最后发展为作弊。
所以,现在搜索引擎已经不怎么看重这三项内容了,但是从一些优秀的网站上还是可以看出这些东西的书写规则还是比较标准的,所以大家临摹一下也未尝不可不过要想了解这三个元素的一般书写规则的话,就首先应该知道他们三个东东到底是什么。
下面的解释仅供新手SEO入门学习,高手请绕道。
title、keywords、description是什么?title:即网站标题,也就是在浏览器上面显示的那些内容,这些内容不仅用户能看到,而对于搜索引擎来说也是能够检索的到的,而且要特别注意它还是判定你网页的主要依据之一。
Keywords:这也就是我们常说的关键词了。
Kewords用户是不能直接在网页前台看得到的。
只有查看网页源代码才行。
Keyword的主要作用是把当前网页的内容用几个简明扼要的词语来概述一下。
这里还牵扯到一个关键词密度问题,以后再细谈这个keywors密度。
description:这个和上面的keywords一样,同样是用户直接在当前网页上看不到的内容,而且也是对于一个网页的简要内容概况。
但是又和keywords不同,keywords是几个词语的组成的,而description 则是完整的一句话,就像本博客的首页描述一样。
title、keywords、description的一般写法Title的一般写法:首页title的写法,一般是“网站名称–主做的几个词语或简单描述”。
在这里讲一下个人感觉,本人在做优化有时候习惯把相对较难的几个关键词放在标题最前面,网站名称放在后面,因为搜索引擎给予标题最前面的词肯定要比后面的高的。
就譬如说我这个博客做“郑州SEO”这个词,就这样写“郑州SEO_武汉网站优化_SEO基础教程学习,而反观很多小网站都是这样去书写的,但是也不唯一。
北京大学出版社大学英语1Unit7Keywordsandphrases(DO C)Unit 7 The Man Who Married HimselfKey words and phrasestempt【释义】1.V-T Something that tempts you attracts you and makes you want it, even though it may be wrong or harmful. 引诱; 吸引2.V-T If you tempt someone, you offer them something they want in order to encourage them to do what you want them to do. 诱使,鼓动,怂恿tempt sb into sth/doing sth【例句】1.It is the fresh fruit that tempts me at this time of year.2.Don't let credit tempt you to buy something you can't afford.3.Nothing would tempt me to join the army.4.The warm weather tempted us into going for a swim.【派生】temptation n.(1) 劝诱,诱惑,引诱Will they be able to resist the temptation to buy?他们能抵抗得住购买的诱惑吗?Yield/give way to temptation 经不住诱惑(2) 有诱惑力或吸引力的东西The bag of sweets on the table was too strong a temptation for the children to resist. 桌上那包糖果对于孩子们而言是难以抗拒的诱惑。
KEYWORDSInteractive user interfaces, multiscale interfaces, multime-dia authoring, information navigation, hypertext, informa-tion visualization.ABSTRACTWe have implemented an infinite resolution multimedia sketchpad as a base for exploring a stream-of-consciousness model of computation where information creating, sharing and retrieval becomes so intuitive that the interface becomes invisible. Motivation to pursue this came from work on Pad [4], which can be thought of as a kind of tradi-tional sketchpad or windows environment in the sense that it is a general-purpose substrate for visualizing two dimen-sional graphics and text. But Pad also supports the radical notion of being infinite in extent and resolution.We implemented Pad++ to explore smooth zooming for navigation and to serve as a platform for multimedia author-ing and information visualization. The ability to work with very large datasets has been a primary design consideration in the development of Pad++.INTRODUCTIONThe motivation for our work on multiscale interfaces is to move beyond windows, icons, menus, and pointers to explore interfaces that more effectively support navigation through complex sets of multimedia information [1, 2, 5]. One premise of our work is the belief that navigation in information spaces is best supported by tapping into our natural spatial and geographic ways of thinking [3]. Information can be entered interactively by the user or dynamically by a program on Pad++. It can be placed at any location and at arbitrary scale. Navigation is performed by zooming in and out and moving around the surface. Our metaphor for searching for information is that all the infor-mation is there and to see more detail, you just have to take a closer look. Using Pad is meant to feel like you have a gigantic piece of paper that you can look at with a micro-scope with arbitrary resolving power and smooth zooming. RECENT ADVANCES Our focus in this implementation has been to provide smooth zooming in a system that works with very large datasets. The nature of the Pad++ interface requires consis-tent high frame-rate interactions, even as the dataspace becomes large and the scene gets complicated. In many applications, speed is important, but not critical to function-ality. In Pad++, however, the interface paradigm is inher-ently based on interaction. The searching strategy is to visually explore the dataspace, so it is essential that interac-tive frame rates be maintained.We implemented Pad++ in C++ on Silicon Graphics com-puters using SGI’s graphics language facilities (the GL) to provide smooth zooming. We wrote a standard set of draw-ing widgets to enter text, lines, squiggles, etc., to load files and images, and a standard set of operators such as group-ing, copying, deleting, etc. These give a multimedia author the basic tools for creating a dataspace.In order to keep the animation frame-rate up as the dataspace size and complexity increases, we implemented several standard efficiency methods, which taken together create a powerful system. We are able to load in over 600,000 objects and maintain interactive rates. Briefly, these methods are:•Spatial Indexing: Create a hierarchy of objects based on bounding boxes to quickly index to visible objects. •Spatial Level-Of-Detail: Render only the detail needed, do not spend time rendering what can not beseen.•Clipping: Only render the portions of objects that are actually visible.•Refinement: Render fast with low resolution while nav-igating and refine the image when still.•Adaptive Render Scheduling: Keep the zooming rate constant even as the frame rate changes.One challenge in navigating through any large dataspace is maintaining a sense of relationship between what you are looking at and where it is with respect to the rest of the data. The rough animation or jumpy zooming as implemented in the original Pad [4] can be disorienting and thus not provide the most effective support for the cognitive and perceptual processing required for interactive information visualization and navigation. We implemented smooth zooming wherePad++: A Zoomable Graphical InterfaceBenjamin B. Bederson Bell Communications Research 445 South StreetMorristown, NJ 07960(bederson@)James D. Hollan Computer Science Department University of New MexicoAlbuquerque, NM 87131(hollan@)Published in CHI ‘94: short paper categorypressing the middle button zooms in and pressing the right button zooms out (the left button is a context-dependentbutton). Pressing either of the zoom buttons once and hold-ing it initiates the zooming which starts slowly and acceler-ates according to a profile specified by the maximum zooming speed and how long it takes to reach that speed.Holding the middle and right buttons permit panning.An important interactive interface issue when accessing external information sources is how to give the user access to them without incurring substantial start-up costs while the database is parsed and loaded. In Pad++ this is accom-plished with parallel lazy loading : only load the portion of the database that is visible in the current view. As the user navigates through the database and looks at new areas,those portions of the database are loaded. This lazy loading is done in the background so the user can continue to inter-act with Pad++, and when the loading is complete, items appear in the appropriate place.SAMPLE APPLICATIONWe built a Pad++ directory browser to explore how smooth zooming and the various efficiency mechanisms help in viewing a large hierarchical database. The Pad++ directory browser provides a graphical interface for accessing the directory structure of a filesystem [Figure 1]. Each directory is represented by a square pink frame, and files are repre-sented by solid squares colored by file type (Figure 1 is B&W). Both directories and files show their filenames as labels when the user is sufficiently close to be able to read them. Each directory has all of its subdirectories and files organized alphabetically inside of it. Searching through the directory structure involves only zooming in and out of the directory tree. Zooming into a file automatically loads the text inside the colored square and it can then be edited and annotated.We are able to load in a directory tree with over 600,000objects, and maintain interactive animation rates of about 10frames per second. Spatial indexing allows us to maintain aFigure 1: Directory browser snapshotvery large database while keeping the search time fast, since we render only the visible portion. While navigating with Pad++, very small objects are not drawn and larger ones are drawn with reduced resolution. The reduced resolution objects are refined when the user stops changing the view.CONCLUSIONWe implemented Pad++, a multimedia multiscale hierarchi-cal sketchpad, focusing on efficiency and expandability. By implementing several efficiency mechanisms which act in concert, we are able to maintain high frame-rate interaction with very large databases.We are currently, in collaboration with NYU, beginning to design an end user language for application authoring. In addition, we also are exploring several application domains,such as history-enriched digital objects, as part of the con-tinued development of Pad++.ACKNOWLEDGEMENTSWe would like to acknowledge other members of the Com-puter Graphics and Interactive Media Research Group at Bellcore for many discussions shared during our search for the best cheeseburger. We also would like to thank Ken Per-lin and his students, David Fox and Matthew Fuchs, at NYU for enjoyable discussions and for seeding out interest in multiscale interfaces.REFERENCES[1]Benjamin B. Bederson, Larry Stead, and James D. Hollan,Pad++: Advances in MultiScale Interfaces,Proceedings of ACM Human Factors in Computing Systems Conference (CHI ‘94).[2]Stuart K. Card, George G. Robertson, and Jock D. Mackin-lay. The Information Visualizer, an Information Workspace,Proceedings of ACM Human Factors in Computing Systems Conference (CHI ‘91), 181-188.[3]William C. Donelson. Spatial Management of Information,Proceedings of 1978 ACM SIGGRAPH Conference , 203-209.[4]Kim M. Fairchild, Steven E. Poltrock, and George W. Furnas.SemNet: Three-Dimensional Graphic Representations of Large Knowledge Bases, in Cognitive Science and its Appli-cations for Human-Computer Interaction , Lawrence Erlbaum Associates, 1988.[5]George W. Furnas. The FISHEYE View: a New Look atStructured Files, Bell Laboratories Technical Report, 11221-22, 1982.[6]George Lakoff and Mark Johnson. Metaphors We Live By.University of Chicago Press, 1980.[7]Ken Perlin and David Fox. Pad: An Alternative Approach tothe Computer Interface,Proceedings of 1993 ACM SIG-GRAPH Conference , 57-64.[8]Ivan E. Sutherland. Sketchpad: A man-machine graphicalcommunications systems,Proceedings of the Spring Joint Computer Conference , 1963, 329-346, Baltimore, MD: Spar-tan Books.。