网站开发人员非常伟大：没有他们，我们将不会有网站！但不幸的是许多开发人员在SEO方面有一些盲点。尽管一些SEO功能在当今几乎成为标准的网站配置（编辑tags标签，alt属性，等等），但是还是有些被经常遗忘。让我们看看……

分析工具（Google Analytics或其他的分析工具）

一个不错的分析工具对于任何网络营销活动都是至关重要的，既可以测量结果又可以获得网站上如何被发现及时用的数据。另外，所有营销人员都知道，拿到网站的历史数据对于开启一个新的广告计划几乎是无价的。然而，很惊奇地发现有很多网站不装分析工具就上线的，大小网站都有这种情况。即可申请一个并配置好吧！

有语义的URL

有语义的URL简言之就是易读且可转化游泳信息的网页地址。以“blue wigets”这个网页为例，将会是这样：

www.example.com/blue-widgets/

然而，我们通常看到如下的地址：

www.example.com/index.php?page_id=46

我们看到后一个版本的原因通常是这更容易采用。麻烦是，那是SEO的灾难！尽管网页层次的因素相对链接建设来说并不那么重要，大体而言，URL中嵌入关键词是唯一最重要的网页层次优化的部分。

确保你的开发人员采用有语义的URL并且给你控制每个页面URL的权限—-没有任何借口！尽管你不会因为用一个无语义的URL结构而被惩罚，但是你将失去一个很大的机会 —而且在网站上线后切换URL将是一个大麻烦。

XML格式的网站地图

网站地图在你网站变得庞大之后将会 有重要影响，但是他们很容易设置并且不需额外支出，因为，这总是值得使用的。人工生成这些网站地图并不是问题（有很多免费工具可以办到），但是如果你的网站上动态的并且经常更新，这将很快变得十分头痛。

让网站的CMS（内容管理系统）在每次网站更改时自动更新网站地图会更好些。很多软件包自带这个功能或者可以通过插件来实现，但是如果你们使用定制的CMS，确保开发员保护这个功能。

控制索引

If you have a large site, Google will almost never index your entire site: they have a percentage cap of the number of your pages that they will keep in the index. Now, discussing how much of the site they decide to index and upon which pages they bestow the honor of indexation is a post for another time, but suffice to say for now that although you definitely can’t tell Google which pages to index, you cantell them which pages you definitely don’t want indexed. You do this with this meta tag in the head of the page:

[meta name="robots" content="noindex,follow" /]

Again, if you’ve got a small or static site, this isn’t a problem to set up manually, but for larger sites you’ll need to be able to control this through the CMS. You may even want to develop a strategy for noindexing pages automatically – if they’re not getting search traffic anyway, for example. Ideally, yes, we’d like never to have to do this kind of thing, but if Google are only going to index a part of your site anyway, you’d better make sure it’s the part that counts.

301重定向

Honestly, could this be more important? Unfortunately, a lot of developers don’t think so.

If you’re migrating from an old site, making sure that pages from the old version are redirected to the new is vital (assuming that the page names or URL structure has changed), but it’s also important that your new CMS creates 301s automatically if you remove or change the URL of any page – something that you’ll inevitably end up doing if you work actively on your site.

Again, some CMSs do this natively or through plugins, but many don’t. If you’re having something custom written or your developer is using something off the shelf, make sure it handles 301s for changed pages properly.

规范化网页

Sorting out canonicalization of URLs from the start is another must – you don’t want Google to see duplicate content on your site even for an instant, or it’ll be reminding you of it through Webmaster Tools for evermore.

The first step is www versus non-www canonicalization. From an SEO perspective, it doesn’t matter which you choose, but you have to choose one and stick to it. Implementing it involves just a simple 301 redirect rule and is easy for your developer to do.

The second step is making sure that your CMS, e-commerce package or other platform isn’t generating multiple URLs for each page, and isn’t adding a lot of extraneous data to URLs. This might sound like a no-brainer, but Magento, for example, makes each page available by three different URLs by default. Checking to see if you have this problem is relatively straightforward – use a tool such as Xenu’s Link Sleuth(yes, it’s a crazy site) to check the number of pages on your site. If it’s way higher than you were expecting, you’ve got a problem. If you’ve not fixed this problem before the site goes live, that means a lot of 301 redirects to set up as you rationalise the URL structure.

Lastly, implement the canonical tag itself. At it’s most basic level, this tag tells Google what the definitive URL of a page should be. If your CMS definitely isn’t generating multiple URLs per page, it is still worth implementing, as it will help prevent potential problems caused by incoming links with extra URL data in them (e.g., tracking tags from mailing list software, etc.). The canonical tag is dead easy to implement and should appear on every page. It looks like this:

[link rel="canonical" href="http://www.example.com/page.html" /]

Google is expanding the remit of this humble tag over time as well, so it’s worth keeping an eye on what you can and should be doing with it – it all helps with Google’s indexation of your site.

网站速度

Hardcore coders are often obsessed with speed. This is a good thing, as site speed is now a part of Google’s ranking algorithm (although perhaps not a large part… yet). The problem is that the main issues to do with a site’s performance are not to do with the code itself (at least not for most smaller sites), but rather to do with things such as HTTP request optimization, combining and compressing external files, loading JavaScript asynchronously, using cookie-less domains, etc.

If all that sounds pretty technical… well, it is. Luckily, you don’t need to understand how to do it – you just need to ask your developer to look after it for you. If they’re not already on the ball with site speed, a number of free tools will audit a site’s performance and make recommendations for improvement, such as the Google’s Page Speed suite. You may also want to ask your developer about using a content delivery network such as CloudFlare. Going to town on your site’s speed really can make a surprisingly big difference!

总结

确保你的网站开发员从开始就实现这些基本功能会使你的站内SEO顺其自然地运行，让你可以集中精力进行链接建设及内容维护。上述所有功能都是必须的！

译者肖庆原创翻译，原文：http://searchenginewatch.com/article/2120878/7-SEO-Friendly-Site-Features-that-Developers-Often-Miss