tag management 的设计

用途:一般市面上都是管理第三方代码的

作为刺入页面的针,实现第三方代码的管理太过简单,所有的营销需求都可以与之发生关联

QQ截图20150423104541

如图是Google GTM的基本结构

container:容器,代码仓库,物料基地,容纳了形形色色与业务有关所有的代码

tags:容器中取出的代码,谓之tag

rules:如何从容器中取出tag

marcos:宏,这玩儿吧,如果你早年玩过一些自动SEO工具,一眼就可以看懂

容器是你的仓库,tag是你要喷出的代码,rules 决定你喷代码的范围,当没有变量时候可以作为trigger,宏来产生变量,变量可以做出rules,也可以捕获营销所需的值向后传递。

tag management像一支锋利尖韧的针,将营销需求刺入 页面

遵循这个思想,我准备开工做一个

 

移动网站checklist…..没空

百度站长平台的供稿之一
前言

随着移动流量的与日俱增,搜索引擎的移动版本功能越来越丰富,丰富意味着更多移动特性可以施展,同时也意味着对HTML5网站的要求更趋规范和严格。

tumblr_me5wab5c811rynl5e

我一般将站内优化的生命周期概括为三个词,实验、评估、调整,因此我的checklist也贯穿了这一过程。

技术方案方面——融合站内优化需求,保障网站稳定

数据埋点方面——收集和跟踪数据,进行后期调整

适配——作为识别移动网站的重要手段,单独列出关注 Continue reading 移动网站checklist…..没空

Categories SEO

单页应用Single Page Application的SEO(为百度站长平台供稿)

1.单页应用?此SPA不是彼SPA…

我们所说的“单页应用”都为Single Page Application的直译,基本市面上“单页面应用”、“One Page Application”、“SPA”及某些语境下的“webapp ” 都是指这一类移动站点

那么典型的SPA是什么样子?我们用手机看看这条URL,http://cc-ng-z.azurewebsites.net/,可以衍生想象一下乘以N倍的:切换页面无需加载的效果,HTML和JS无法比拟的动画,以及对原生APP的追求…..

07575ECA-35EF-4BBA-81A9-2A5F58D82F82
案例采用了angularJS这个鼎鼎大名的框架

 

关于HTML5及单页应用的处境,推荐以下两篇文章,第二篇实际上是百度UMX写的,但是现在原文删掉了,可以对自己的移动站点在技术架构上有个抉择和处理。

HTML5移动应用开发的生态环境简介

论Web App、Hybrid App以及Native App的设计差异

Continue reading 单页应用Single Page Application的SEO(为百度站长平台供稿)

Categories SEO

Recommendations for building smartphone-optimized websites

日他先人斯巴达

Matt Cutts PubCon 2012 slides

Webmaster level: All

Every day more and more smartphones get activated and more websites are producing smartphone-optimized content. Since we last talked about how to build mobile-friendly websites, we’ve been working hard on improving Google’s support for smartphone-optimized content. As part of this effort, we launched Googlebot-Mobile for smartphones back in December 2011, which is specifically tasked with identifying such content.

Today we’d like to give you Google’s recommendations for building smartphone-optimized websites and explain how to do so in a way that gives both your desktop- and smartphone-optimized sites the best chance of performing well in Google’s search results.

Recommendations for smartphone-optimized sites

The full details of our recommendation can be found in our new help site, which we now summarize.

When building a website that targets smartphones, Google supports three different configurations:

  1. Sites that use responsive web design, i.e. sites that serve all devices on the same set of URLs, with each URL serving the same HTML to all devices and using just CSS to change how the page is rendered on the device. This is Google’s recommended configuration.
  2. Sites that dynamically serve all devices on the same set of URLs, but each URL serves different HTML (and CSS) depending on whether the user agent is a desktop or a mobile device.
  3. Sites that have a separate mobile and desktop sites.

Responsive web design

Responsive web design is a technique to build web pages that alter how they look using CSS3 media queries. That is, there is one HTML code for the page regardless of the device accessing it, but its presentation changes using CSS media queries to specify which CSS rules apply for the browser displaying the page. You can learn more about responsive web design from this blog postby Google’s webmasters and in our recommendations.

Using responsive web design has multiple advantages, including:

  • It keeps your desktop and mobile content on a single URL, which is easier for your users to interact with, share, and link to and for Google’s algorithms to assign the indexing properties to your content.
  • Google can discover your content more efficiently as we wouldn’t need to crawl a page with the different Googlebot user agents to retrieve and index all the content.

Device-specific HTML

However, we appreciate that for many situations it may not be possible or appropriate to use responsive web design. That’s why we support having websites serve equivalent content using different, device-specific, HTML. The device-specific HTML can be served on the same URL (a configuration called dynamic serving) or different URLs (such as www.example.com and m.example.com).

If your website uses a dynamic serving configuration, we strongly recommend using the Vary HTTP header to communicate to caching servers and our algorithms that the content may change for different user agents requesting the page. We also use this as a crawling signal for Googlebot-Mobile. More details are here.

As for the separate mobile site configuration, since there are many ways to do this, our recommendation introduces annotations that communicate to our algorithms that your desktop and mobile pages are equivalent in purpose; that is, the new annotations describe the relationship between the desktop and mobile content as alternatives of each other and should be treated as a single entity with each alternative targeting a specific class of device.

These annotations will help us discover your smartphone-optimized content and help our algorithms understand the structure of your content, giving it the best chance of performing well in our search results.

Conclusion

This blog post is only a brief summary of our recommendation for building smartphone-optimized websites. Please read the full recommendation and see which supported implementation is most suitable for your site and users. And, as always, please ask on our Webmaster Help forums if you have more questions.

Categories SEO

笔记:excel结合datanitro

data_nitro关于datanitro

安装

先保证安装了office,它是一个office的插件

python必须2.7版本以上,要不然print用不了,西特。

datanitro下载地址

安装完成,打开excel后看到操作界面

editor:启动一个自带IDE,用于编写python代码

python shell:启动一个shell界面

import:导入脚本,py文件

remove:移除脚本

run:运行脚本

stop:停止脚本运行

docs:打开在线文档

live help:联系客服

Continue reading 笔记:excel结合datanitro