23:52 给免费空间的建议:对站长更友好 » 谷歌中文网站管理员博客

原文:Recommendations for webmaster friendly freehosts


发表于: 2009 914日星期一,下午4:17


一直以来我们大都是针对单独的网站管理员管理个人的网站提出建议。现在,有很多像是 Blogger, Google Sites 这样的网站,它们提供免费平台让用户创建自己的网站、管理用户上传的内容。现在我们觉得有必要给它们一些最好的、和实用的建议。这样的网站大多被大家叫做 “免费空间站”,当然我们的建议同样适用于那些 “不免费” 的空间提供商。

  • 确保你的用户可以在像是 “Google 网站管理员工具” 这样的网站管理套件中验证他们的网站。
网站管理员工具可以让站长得到他们网站在 Google 上面表现如何的详细数据。在您的用户可以接触到这些数据之前,我们必须要验证他们的确拥有那个网站。在网站管理员工具里面验证网站可以通过 HTML 文件,和元标记的方法,国外用户还可以通过 Google Services for Websites 与您的系统的整合来达到。其他的网站管理工具例如 Yahoo! Site Explorer,和 Bing 网站管理员工具可能使用类似的验证方法;我们建议您能确保您的用户可以使用以上的网站管理工具。

  • 为每个用户选择一个独特的子目录名或主机名。
网站管理员工具是在单个 URL 的基础上来验证网站的,但是我们期望用户可以在site:URL 层面看到所有在这个URL 以下的 URL。您可以阅读《验证子域名和子目录》这篇文章来了解更多信息。除了网站管理员工具之外,网络上其他一些自动系统,比如搜索引擎或其他聚合系统,都期望网站能更好地结构化,这样的结构化将会为这些系统发现和组织您的内容带来很多便利。

  • 为网页设置更具有描述性的,有用的标题。
让用户自己设置他们的标题,或者自动实现让您的用户们的网页标题更具描述性,而不是让它们千篇一律地设置为"博客:建立您的免费博客"。类似地,如果一个用户的网站有很多不同内容的网页,他们也不应该有像"用户XYZ的主页"这样完全一样的标题

  • 允许对网页添加标签。
特定的meta标签对于搜索引擎来说是非常有用的,用户可能想自己来控制他们。这里所指的meta标签包括"robots","description", "googlebot", "slurp", or "msnbot"。通过点击相关链接,你可以更多的了解这些标签。

  • 允许你的用户使用类似 Google Analytics (分析)这样的第三方的分析工具包。
Google Analytics 是一个免费的企业级的分析软件。你只需要加载一段 JavaScript的代码就可以让这个软件运行在你的网站上。如果你担心安全问题而不想让用户自己加载JavaScript的代码的,也有办法解决。Google Analytics 软件的代码其实只改变了一个简单的ID。 你只需要让你的用户告诉你他们的 Google Analytics 的ID,你就可以帮助他们做余下的工作了。如果用户能够理解他们的流量来源,那么他们就可以从你的服务中取得更大的价值了。我们建议考虑你在向用户开放使用权限的时候,使用类似的方法。

  • 帮助你的用户工作更加灵活。
人们的喜好总是在变化的。一些使用你的网站服务的人可能会想改变他们的账户名称,甚至可能想将他的网站重定向到另一个网站。您应该允许您的用户访问他们自己的数据。当他们使用301重定向将网站的全部或者部分重定向到另一个网站时,您也应该帮助他们通知搜索引擎。同样的道理,当用户想要删除某一页或者某个网站的时候,应当返回404代码,这样搜索引擎就会知道这一页或者这个网站已经不在了。这样也可以允许用户(在必要的时候)使用 URL紧急删除工具,从而确保那些用户不想要的网页尽快的从搜索引擎的结果中去除。

  • 帮助搜索引擎从您的用户那里找到好的内容。
搜索引擎一直在互联网上抓取更多的内容。帮助我们的抓取爬虫找到你网站上最好的内容。允许我们抓取用户的内容,包括用户上传的图像文件这样多媒体的。通过XML网站地图帮助我们找到用户内容。帮助我们清除重复的内容,这样我们可以找到你用户更好的内容信息,同时尽量为每个信息创建一个唯一的URL,或者在上述情况不可行的情况下制定你的主域名。如果你是博客服务的提供者,可以创建 RSS feeds 以便我们在谷歌博客搜索中发现。如果你的网站宕机或者出现错误,请返回5XX的响应代码。这会帮助我们通过让抓取爬虫知道那些内容是暂时无法访问的,从而避免我们收录大量的 “服务暂时不能使用” 的页面。

对这类管理用户内容和页面的网站您还能想到其他好的建议吗?

国庆北京交通限行地图上线!Google 黑板报 -- Google 中国的博客网志 » 车东's shared items in Google Reader
发表者:谷歌公关部

9月30日,国庆前夕,谷歌中国正式上线“国庆北京交通限行地图”,图示北京市在国庆期间,即10月1日至8日国庆长假期间的交通限行区域和路线,用户登录谷歌地图(ditu.g.cn)点击国庆北京交通限行地图就可以方便帮助自己科学的规划出行,此外,用户还可以获取“国庆北京交通限行地图”链接与亲朋好友共享。

    


谷歌“国庆北京交通限行地图”包括机动车限行、载货汽车和载客汽车限行、机动车绕行路线,针对不同车型的限行道路可以根据道路的颜色明显地区分,在地图上分别标志为红色线路、蓝色线路和绿色线路。地图页面同时提供了一份北京国庆交通限行的日历表,默认显示“今日交通管制”,点击日期,就可以看到其他日期的详细交通限行信息,其中包括了限行的路段和时间段,以及限行车辆的类型。

    


    


根据“国庆北京交通限行地图”提示,国庆期间的禁行地区是奥林匹克公园、香山、颐和园和八达岭地区,点击禁行地区链接,可以快速地放大对应区域地图, 限行道路看得更清楚更详细。如下图为奥运公园附近10月1日道路通行信息。

    


在地图上标志蓝色气泡的路线是国庆期间采取临时交通限行措施的路段,点击蓝色气泡,可以看到在北京二环至四环的各条道路的交通限行路段、限行时间、禁止通行的车辆类型、限行方向等等。

谷歌地图是一张可以与亲朋好友分享的在线地图,谷歌地图页面右上角有“电子邮件”、“链接”等,点击“链接”,可以获取谷歌“国庆北京交通限行地图”链接,或者点击“电子邮件”,可以直接发送给朋友。

    


谷歌“国庆北京交通限行地图”是你的一份国庆出行指南,60周年国庆大典即将来临,让我们穿行北京城,一起见证世纪性的时刻!
23:26 感谢大家对谷歌网站管理员支持论坛征文活动的支持! » 谷歌中文网站管理员博客


为了鼓励更多的站长和朋友们参与谷歌网站管理员支持论坛的交流与互动,分享自己在改善网站抓取索引、使用网站管理员工具等方面的心得和经验,增进站长之间的信息共享,谷歌网站管理员支持论坛在8月份举办了一次面向网站管理员朋友的征文活动

在大家的参与和支持下,从8月3日到8月31日,论坛收到了13 篇符合主题要求的站长来稿,这些精彩的来稿来自于祖国的四面八方,他们有的侧重分享自己在改善搜索引擎抓取和索引的经验与心得,有的以切身体验介绍了如何更好地应用网站管理员工具,有的为避免网站安全漏洞、清除恶意软件提出了切实的建议,还有的则讲述了在改善自己网站与搜索引擎关系中的苦辣酸甜,并对谷歌提出了殷切的期望和中肯的建议。

除了提交投稿之外,很多论坛用户还通过跟贴和留言的方式与投稿的站长交流,很多朋友在回帖中表达了对投稿文章的欣赏,还表示会把这些心得经验应用到自己的网站中。例如,其中一篇来稿吸引了多达二十多个讨论回帖。

或许您会发现这些"讲述咱站长自己的故事" 的精彩文章,也会对您的网站建设有一些参考作用,如使用rel="canonical",轻松解决“重复”问题》,《让谷歌为您的网站把脉》,《通过网站管理员工具 增加Google爬虫对网站的访问量》等等。

除了向获奖作者寄去谷歌小礼物之外,我们想再次向所有参加和支持这次征文活动的站长和朋友们表示感谢。由于站长们的精彩来稿无法在此一一列举,如果您希望阅读更多站长来稿或者您也有与网站管理员相关的问题,欢迎您访问谷歌网站管理员支持论坛

14:22 Movable Type 4.32 Bug-fix Release + Zemanta plugin » MovableType.org - Home for the MT Community

Many of you are looking forward to using MT5 exclusively, but truthfully you may be content with MT4 or maybe you’re unable to upgrade because a plugin you rely upon may not yet be ported to MT5.

So until MT5 is solid and there is little demand for MT4, Six Apart will continue to release new versions of MT4.x as necessary to provide fixes for various security issues and bugs which are major pain points. Small features may be potentially included as well.

MT4.32 fixes a handful of minor bugs which are detailed in the Movable Type 4.32 release notes.

One of the commits in MT4.32 was to bundle the Zemanta plugin. Zemanta has committed to supporting the development of Movable Type; what better partnership than that of a content management system and a service to recommend quality related-content?

While it may not be useful for every blogger, it can be very helpful in the case where you need an image, links to related articles, help with tags for an entry, etc to have a more compelling blog entry. Check out the Zemanta FAQ for more info on how Zemanta’s services may be useful for you or your bloggers. All support or technical questions regarding Zemanta or the Zemanta Plug-in for MovableType should be forwarded to support@zemanta.com.

Zemanta not for you? There are many ways to disable the Zemanta plugin additionally anyone with file-system access can remove the Zemanta plugin from the plugins directory within the MT install.

Also, you don’t need MT4.32 to use the Zemanta plugin, you can also download Zemanta from the plugin directory.

One known issue which wasn’t in the Zemanta FAQ:

For internal Movable Type deployments behind the firewall the Zemanta functionality will not be available. This will not have impact the operation of Movable Type. However, administrators may see the error message “Can’t connect to Zemanta API service” in the Movable Type system log. To avoid seeing this error, the plug-in should be disabled by the administrator as described above.

Hope the fixes in MT4.32 are useful. If there is a bug or patch that you want committed in a future version of MT4.x

MT5 Beta 3 should be available tomorrow.

11:58 Advanced: Structure Your Account With Roll Up Reporting And More » Google Analytics Blog
Guest post by the team at E-Nor, a Google Analytics Authorized Consultant

For the analytics ninjas out there, you know that data accuracy is probably one of the most challenging aspects of analytics across all solutions and platforms, and you learn to apply best practices and establish processes to improve data collection and reporting.

But for the rest of us, how do we help marketers, business owners, and webmasters have confidence in their data? Analytics is all about clarity. It should help you see actionable statistics clearly and quickly. However, when you have a website structure with multiple domains and subdomains - which is often the case - sometimes things can get jumbled.

For instance, you are a CMO or a Director of Marketing at the enterprise and you are responsible for the performance and ROI of a large number of web proprieties. You look at your analytics reports and you can't find your ecommerce data from site A, site B is referring traffic to itself (definitely not a good thing!), and conversion data from your marketing campaign microsite is no where to be found.

This image sums up the feeling.

No need to panic. This post aims to offer an approach to help you plan your Google Analytics accounts setup in a structured fashion to help with clarity. I hope that by following the approach and the technical steps, you will be able to collect and manage all your data, make more sense of it, and most importantly, ensure what you are reporting on, trending, dashboarding and analyzing is based on accurate data.

There are two distinct sections of this post:

  • The Strategy (non-technical)
  • The How (technical)

The Strategy

There are many ways to structure your Google Analytics profiles when you have multiple domains and subdomains. But in this post I will limit myself to the one that I like the most and I believe is the least confusing.

Before I go into details of the solution, and for simplification, let us assume we are dealing with a pr
oject that has the following requirements:
  • A business with 3 domains (www.a.com, www.b.com, and www.c.com)

  • 1 domain (a.com) links to a 3rd party shopping cart (www.mystore.com)

  • 2 domains (a.com and b.com) have multiple sub-domains

Here is a graphical representation of the structure:

Measurement Requirements
  • Track each domain and sub-domain separately (e.g. www.a.com, news.a.com, and blog.b.com)

  • Track the rollup/overall traffic for all domains and sub-domains

  • Track full e-commerce transactions

Solution
  • Create a Google Analytics account for each domain (www.a.com, www.b.com, and www.c.com)

  • Customize the tracking code to link the multiple sub-domains with their main domains

  • Link the third party shopping cart with the main domain and install Google Analytics tracking code in all shopping pages

  • Create a rollup Google Analytics account and add its code to all domains and sub-domains
Graphical example of a well-planned Analytics Account Structure:

Now on to the technical stuff. If you don't enjoy javascript and regular expressions, you may stop here and ask your webmaster or technical analyst to read further :-)


The How:

I will try to illustrate the technical implementation in 10 simple steps:

1- Create a unique Google Analytics account for each domain www.a.com, www.b.com, and www.c.com and then use the account number UA-AAAAAAAA-1 in the code in step 3 and use the accounts UA-BBBBBBBB-1 for www.b.com and UA-CCCCCCCC-1 for www.c.com in the code in step 8.

2- Create a Google Analytics account for the a rollup account that will oversee all domains and sub-domains (use the GA account number UA-XXXXXXXX-1 in the code used in step 3 and 8)

3- Add the following Google Analytics tracking code to the main site (www.a.com) and its sub-domains (blog.a.com, news.a.com, images.a.com, and media.a.com)

About the following code: We have a regular pageTracker object to track activity on each particular subdomain and a rollupTracker to track activity across all subdomains and the third party checkout site. (Click here to learn more about the customizations we made to the standard Google Analytics tracking code)

<script type="text/javascript">
var gaJsHost = (("https:" == document.location.protocol) ? "https://ssl." : "http://www.");
document.write(unescape("%3Cscript src='" + gaJsHost + "google-analytics.com/ga.js' type='text/javascript'%3E%3C/script%3E"));
</script>
<script type="text/javascript">
try {
var pageTracker = _gat._getTracker("UA-AAAAAAAA-1");
pageTracker._setAllowHash(false);
pageTracker._setDomainName(".a.com");
pageTracker._setAllowLinker(true);
pageTracker._trackPageview();
var rollupTracker = _gat._getTracker("UA-XXXXXXXX-1");
rollupTracker._setAllowHash(false);
rollupTracker._setDomainName(".a.com");
rollupTracker._setAllowLinker(true);
rollupTracker._trackPageview();
}
catch(err) {}

</script>

4- Enable E-Commerce Reporting

Analytics Settings > Profile Settings > Edit Profile Information

5- Add the following code* to all shopping cart pages on the store site (www.mystore.com)

*Make sure to add this code to the top of the pages.

<script type="text/javascript">
var gaJsHost = (("https:" == document.location.protocol) ? "https://ssl." : "http://www.");
document.write(unescape("%3Cscript src='" + gaJsHost + "google-analytics.com/ga.js' type='text/javascript'%3E%3C/script%3E"));
</script>
<script type="text/javascript">
try {
var pageTracker = _gat._getTracker("UA-AAAAAAAA-1");
pageTracker._setDomainName("none");
pageTracker._setAllowLinker(true);
pageTracker._trackPageview();
var rollupTracker = _gat._getTracker("UA-XXXXXXXX-1");
rollupTracker._setDomainName("none");
rollupTracker._setAllowLinker(true);
rollupTracker._trackPageview();
}
catch(err) {}

</script>

6- Add the e-commerce tracking code to the confirmation page after the GATC.

Read more about "How to track e-commerce transactions?"

7- Change the links to the store site (www.mystore.com) on the main site (www.a.com) to use _link as following:

If the current link looks like:

<a href="https://www.mystore.com">Buy Now</a>

Change it to:

<a href="https://www.mystore.com" onclick="pageTracker._link(this.href); return false;">Buy Now</a>

8- Repeat step number 3 for domains www.b.com and www.c.com after updating the Google Analytics account number UA-AAAAAAAA-1 and the setDomainName value.

  • To view the entire code for www.b.com and its sub-domains (click here)

  • To view the entire code for www.c.com (click here)

9- Create a profile for each sub-domain (only if needed)

In order to track a sub-domain (ex. blog.b.com) in its own profile, follow the following three steps:

a- Create a filter that include only traffic from Hostname=blog.b.com


b- Create a profile and name it "Blog"

c- Apply the sub-domain filter to the new profile

10-
As you might have noticed from the codes that we added so far to all pages, we added an extra Google Analytics account to track all pageviews across domains and sub-domains to one Google Analytics account. We call this account “rollup account”.

var rollupTracker = _gat._getTracker("UA-XXXXXXXX-1");
rollupTracker._trackPageview();

Since in the rollup account, we will track pages from different sites and many of these pages might share the same naming convention, I suggest that you create an advanced filter that adds the hostname to the page name to differentiate between pages with same URI.

Once you apply the filter, the upcoming data will appear as following:


Note, in the example above if we didn’t apply the “Add Hostnames” filter, all home.aspx pages will appear as one page with 2685 pageviews.

If you have been with us so far, you are now ready to conduct your analysis based on clean and much more accurate data :)
  • To review each domain by itself and for deep-dive analysis, use the domain profiles

  • To get an overview and to see how the business is doing across all sites, use the “Rollup Account”

Related Posts



^==Back Home: www.chedong.com

^==Back Digest Home: www.chedong.com/digest/

<== 2009-09-28
  九月 2009  
  1 2 3 4 5 6
7 8 9 10 11 12 13
14 15 16 17 18 19 20
21 22 23 24 25 26 27
28 29 30        
==> 2009-09-30