我应该包含一个<元生成器>吗?标签?

发布于 2024-09-17 13:21:04 字数 166 浏览 9 评论 0原文

假设我有某种专有的网络框架。我应该在生成的文件中包含 标记吗?

我注意到 StackExchange 0.9 应用程序可以这样做,并且想知道这样做的优点/缺点是什么。它有什么作用,或者只是对查看源代码的人有用吗?

Suppose I have some sort of proprietary web framework. Should I include a <meta generator="My framework"> tag in the generated files?

I noticed that StackExchange 0.9 applications do that, and wondered what are the pros/cons of doing it. Does it have any effect, or is it just useful for people looking at the source to see?

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(4

绅刃 2024-09-24 13:22:13

自动生成(也称为“自动生成”内容)是通过编程方式生成的内容。如果 Google 旨在操纵搜索排名而不是帮助用户,则可能会对此类内容采取行动。一些示例情况包括但不限于:

对读者来说毫无意义但可能包含搜索关键字的文本。
文本由自动化工具翻译,在发布前无需人工审核或管理。
通过自动化流程(例如马尔可夫链)生成的文本。
使用自动同义词或混淆技术生成的文本。
通过抓取 Atom/RSS 提要或搜索结果生成的文本。
拼接或组合来自不同网页的内容而没有增加足够的价值。
形成谷歌...

Automatically generated (also called "auto-generated"—content) is content that's been generated programmatically. In cases where it's intended to manipulate search rankings and not help users, Google may take actions on such content. Some example cases include, but are not limited to:

Text that makes no sense to the reader but which may contain search keywords.
Text translated by an automated tool without human review or curation before publishing.
Text generated through automated processes, such as Markov chains.
Text generated using automated synonymizing or obfuscation techniques.
Text generated from scraping Atom/RSS feeds or search results.
Stitching or combining content from different web pages without adding sufficient value.
form google...

静赏你的温柔 2024-09-24 13:22:03

这可以使黑客的工作变得更容易,因此明智的做法是保留选择性生成器。

This can make a hacker's job bit easier, therefore it would be wise to just keep selective generators instead.

他夏了夏天 2024-09-24 13:21:53

好处(或坏处?)是您可以出现在 搜索 已完成生成器。

A benefit (or a con?) is that you can show up in searches done for generator.

泛滥成性 2024-09-24 13:21:42

我以前从未见过这样格式化的标签,其中包含名为 generator 的属性和生成软件作为其值。通常你会看到它呈现为 name="generator" 以及生成软件作为其相应的内容,例如:

<meta name="generator" content="WordPress 3.0.1" /> <!-- leave this for stats -->

以前我不知道这方面的任何标准,但它看起来像 HTML5 已经将“生成器”的使用标准化为元数据名称。它是这样描述的:

该值必须是自由格式字符串,用于标识用于生成文档的软件包之一。该值不得用在标记不是由软件生成的页面上,例如标记是由用户在文本编辑器中编写的页面。

在过去,当动态 Web 应用程序还没有那么流行时,某些网站编辑器,例如 FrontPage(我说过),会在您创建新的 HTML 文档或使用它们发布网站时自动插入生成器标记。这意味着“此页面是使用 FrontPage 创建的”。我认为任何现代编辑器或 IDE 都不会再这样做了,但我可能是错的。然而,它现在在动态网络应用程序中肯定很常用。

I've never seen a tag formatted like that before, with an attribute called generator and the generating software as its value. Usually you'll see it presented as name="generator" and the generating software as its corresponding content, for example:

<meta name="generator" content="WordPress 3.0.1" /> <!-- leave this for stats -->

Previously I was unaware of any standard for this, however it looks like HTML5 has gone ahead and standardized the use of "generator" as a metadata name. It describes it thus:

The value must be a free-form string that identifies one of the software packages used to generate the document. This value must not be used on pages whose markup is not generated by software, e.g. pages whose markup was written by a user in a text editor.

In the past when dynamic web apps weren't that prevalent, certain web site editors, like FrontPage (there, I said it), would automatically insert generator tags when you create new HTML documents or publish sites using them. This was taken to mean "This page was created using FrontPage". I don't think any modern editors or IDEs do this anymore, but I could be wrong. It's definitely commonly used in dynamic web apps today, however.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文