个人中心
gpt4 book ai didi

AMP-html 页面未按预期在 Google 搜索中显示

转载 作者：行者123 更新时间：2023-12-02 19:31:40 25 4
gpt4 key购买 nike

我一直在阅读 AMP 的可能性，但我似乎无法理解为什么我的页面没有像 Google 在他们的演示中显示的那样显示(请参阅 http://g.co/amp )。我的常规页面是这样的:

<!DOCTYPE html>
<html>
    <head>
        <meta charset="utf-8">
        <title>An example of an AMP Project; a part of a self-writen paper about maintainability</title>
        <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
        <meta name="language" content="NL"/>
        <meta name="description" content="Every software engineering project has a certain degree of maintainability. Period.">
        <meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1"/>
        <link rel="amphtml" href="http://amptest.millerpreview.nl/indexamp.html">
        <link rel="canonical" href="http://amptest.millerpreview.nl/index.html">
    </head>

    <body>
        <header>
            <nav>
                <ul>
                    <li><a href="/">Home</a></li>
                    <li><a href="/">Another page</a></li>
                    <li><a href="/">Another other page</a></li>
                </ul>
            </nav>
            <h1>Welcome!</h1>
            <img src='http://portal.tugraz.at/portal/page/portal/Files/internationales/Welcome_Center/Welcome_Fotolia_62393747_XXL.jpg' />
        </header>

        <h2>Maintainability of an Open Source Software Engineering Project</h2>
        <p>
            <b>Every software engineering project has a certain degree of maintainability which is directly derivable to the quality of the software, the complexity of the code, the amount and quality of the documentation and the understandability. In this paper, the maintainability of a randomly chosen open source Android application called TeamTalk is measured with the SIG Maintainability Model, created by the Software Improvement Group. The conclusion of the paper is an advice on improving maintainability towards the creators of this application.</b>
        </p>
        <h3>Introduction</h3>
        <p>
            Every software engineering project has a certain degree of maintainability which is directly derivable to the quality of the software, the complexity of the code, the amount and quality of the documentation and the understandability \cite{Heitlager07}. Maintainability is an often forgotten software quality attribute \cite{Radatz90, Swanson76} but a rather important one. Approximately 40 - 80\% of software`s life cycle is spent on maintainability \cite{Coleman94, Dubey11, Kiewkanya05}. Maintaining an application will cost less time and thus less money if the maintainability is given proper attention.<br />
            <br />
            The goal of this paper is to gain insight into the maintainability of a randomly chosen open source application; in this case, it is the Android \cite{Android} app TeamTalk \cite{TeamTalk}. For this, we will measure the software quality attributes \cite{ISO} of maintainability; the analyzability, changeability, stability and testability.<br />
            <br />
            In section 2 we will give more insights about the background of the app TeamTalk and about what the SIG Maintainability Model is. In section 3 the used tools and the approach, based on the SIG Maintainability Model, will be discussed. Section 4 shows and discusses the results, on which an overall adice is given in section 5. The paper will be concluded with a summary of the results and what our advice is for the TeamTalk developers.<br />
        </p>

        <footer>
            <img src='http://www.greetingsfromheart.com/images/bye_bye/bye_bye.gif' />
        </footer>
    </body>
</html>

我的 AMP html 页面是这样的:

<!doctype html>
<html amp lang="en">
  <head>
    <meta charset="utf-8">
    <title>Hello, AMPs</title>
    <link rel="canonical" href="http://amptest.millerpreview.nl/index.html" />
    <meta name="viewport" content="width=device-width,minimum-scale=1,initial-scale=1">
    <meta name="description" content="Every software engineering project has a certain degree of maintainability. Periods.">
    <script type="application/ld+json">
  {
    "@context": "http://schema.org",
    "@type": "ScholarlyArticle",
    "headline": "Maintainability of an Open Source Software Engineering Project",
    "datePublished": "2015-10-07T12:02:41Z",
    "image": [
      "logo.jpg"
    ]
  }
</script>
    <style amp-boilerplate>body{-webkit-animation:-amp-start 8s steps(1,end) 0s 1 normal both;-moz-animation:-amp-start 8s steps(1,end) 0s 1 normal both;-ms-animation:-amp-start 8s steps(1,end) 0s 1 normal both;animation:-amp-start 8s steps(1,end) 0s 1 normal both}@-webkit-keyframes -amp-start{from{visibility:hidden}to{visibility:visible}}@-moz-keyframes -amp-start{from{visibility:hidden}to{visibility:visible}}@-ms-keyframes -amp-start{from{visibility:hidden}to{visibility:visible}}@-o-keyframes -amp-start{from{visibility:hidden}to{visibility:visible}}@keyframes -amp-start{from{visibility:hidden}to{visibility:visible}}</style><noscript><style amp-boilerplate>body{-webkit-animation:none;-moz-animation:none;-ms-animation:none;animation:none}</style></noscript>
    <style amp-custom>
        main {
            margin: 0 auto;
            max-width: 620px;
        }
    </style>
    <script async src="https://cdn.ampproject.org/v0.js"></script>
  </head>
    <body>
        <main>
            <header>
                <nav>
                    <ul>
                        <li><a href="/">Home</a></li>
                        <li><a href="/">Another page</a></li>
                        <li><a href="/">Another other page</a></li>
                    </ul>
                </nav>
                <h1>Welcome!</h1>
                <amp-img src='http://portal.tugraz.at/portal/page/portal/Files/internationales/Welcome_Center/Welcome_Fotolia_62393747_XXL.jpg' width="325" height="200"/>
            </header>
            <h1>Maintainability of an Open Source Software Engineering Project</h1>
            <p>
                <b>Every software engineering project has a certain degree of maintainability which is directly derivable to the quality of the software, the complexity of the code, the amount and quality of the documentation and the understandability. In this paper, the maintainability of a randomly chosen open source Android application called TeamTalk is measured with the SIG Maintainability Model, created by the Software Improvement Group. The conclusion of the paper is an advice on improving maintainability towards the creators of this application.</b>
            </p>
            <h3>Introduction</h3>
            <p>
                Every software engineering project has a certain degree of maintainability which is directly derivable to the quality of the software, the complexity of the code, the amount and quality of the documentation and the understandability \cite{Heitlager07}. Maintainability is an often forgotten software quality attribute \cite{Radatz90, Swanson76} but a rather important one. Approximately 40 - 80\% of software`s life cycle is spent on maintainability \cite{Coleman94, Dubey11, Kiewkanya05}. Maintaining an application will cost less time and thus less money if the maintainability is given proper attention.<br />
                <br />
                The goal of this paper is to gain insight into the maintainability of a randomly chosen open source application; in this case, it is the Android \cite{Android} app TeamTalk \cite{TeamTalk}. For this, we will measure the software quality attributes \cite{ISO} of maintainability; the analyzability, changeability, stability and testability.<br />
                <br />
                In section 2 we will give more insights about the background of the app TeamTalk and about what the SIG Maintainability Model is. In section 3 the used tools and the approach, based on the SIG Maintainability Model, will be discussed. Section 4 shows and discusses the results, on which an overall adice is given in section 5. The paper will be concluded with a summary of the results and what our advice is for the TeamTalk developers.<br />
            </p>
        </main>
    </body>
</html>

它在 Google 搜索和 AMP 演示中显示如下。我知道我的页面被 Google 缓存:https://cdn.ampproject.org/c/amptest.millerpreview.nl/indexamp.html 。在本地，我的 AMP 已通过验证，但在缓存版本中，它表示脚本标记无效，即使这是 AMP 引擎 JavaScript，这应该被视为有效。

我的问题； Google 搜索中尚未实现此功能，还是我做错了什么？

我的 Google 搜索结果如下所示:

Google search result

最佳答案

目前 AMP 页面的使用受到限制。例如，Google 搜索结果不会显示 AMP 等效项，而是显示您的网页。

它们实现的一个地方是“热门故事”的轮播。此轮播将链接到 AMP 页面，并将附加显示到常规搜索结果中(将继续链接到非 AMP 版本 - 编辑:如上所述不再正确)。这只会显示 NewsArticle 发布的页面，并且仅当 Google 认为搜索可能需要最新新闻列表时(因此搜索您的公司不太可能显示此内容)。最近搜索新闻中的某些内容，您应该会看到热门故事轮播和文章中某些文章旁边的闪电。请注意，此功能尚未在所有地方推出，因此如果您没有看到此功能，请尝试使用 Google.com 而不是 Google.nl。

因此，目前实现 AMP 的主要好处是对新闻机构而言。

这会改变吗？很可能。 Twitter have stated they will start to use the AMP versions ，谷歌可能会更多地使用它(尽管不确定他们是否会取代主要搜索列表)，其他人可能会效仿。

至于缓存版本中脚本标记的问题，我没有看到这个问题。请注意，缓存版本不会经常更新，因此它不是“实时”版本。因此，如果出现错误，请访问缓存的 URL，它将加载它并显示错误。但是，如果您随后修复了错误并刷新了缓存的 URL，它仍然会显示该错误。您只需等待一两天，直到它从缓存中消失，然后重试。他们正在研究一种更好的方法来控制这个问题(尽管似乎有 closed the issue tracking this )。

编辑:自撰写此答案以来发生了很多变化。 Now amp pages DO show in main search results - 至少对于移动设备而言。因此，现在除了新闻机构之外还有其他好处。但是，将保留答案原样，因为它确实回答了用户当时的问题。

关于AMP-html 页面未按预期在 Google 搜索中显示，我们在Stack Overflow上找到一个类似的问题： https://stackoverflow.com/questions/36218539/

25 4 0
文章推荐： shell - Excel VBA : Running a shell script to both change directory and then run a custom script
文章推荐： c# - 如何处理具有相同父级的不同事件处理程序？
文章推荐： debugging - 有没有办法链接 iPython 笔记本和 PyCharm，特别是在调试方面？
文章推荐： .net - ParameterInfo.DefaultValue 和 ParameterInfo.RawDefaultValue 之间的区别
行者123
个人简介

我是一名优秀的程序员,十分优秀！

滴滴打车优惠券免费领取
滴滴打车优惠券
全站热门文章
Copyright 2021 - 2024 cfsdn All Rights Reserved 蜀ICP备2022000587号
广告合作:1813099741@qq.com 6ren.com