In order to better understand the potential impact of sampling changes on Google users
\n and publishers’ subscription models, we developed a series of experiments in cooperation with
\n our publishing partners. From these experiments we learned that even minor changes to the
\n current sampling levels could degrade user experience and, as user access is restricted,
\n unintentionally impact article ranking in Google Search. <\/p>\n
There are two types of sampling we advise: metering<\/b>, which provides users
\n with a quota of articles to consume before requiring users to subscribe or log in, after
\n which paywalls will start appearing; and lead-in<\/b>, which offers a portion of
\n an article’s content without it being shown in full. <\/p>\n
We encourage publishers to experiment cautiously with different amounts of sampling.
\n Here is some general guidance for implementing flexible sampling. <\/p>\n
In general, we think that monthly, rather than daily metering provides more flexibility and
\n a safer environment for testing. The user impact of changing from one integer value to the
\n next is less significant at, say, 10 monthly samples than at 3 daily samples. Monthly
\n metering also has the advantage of focusing paywall views on your most engaged users, who are
\n those most likely to subscribe, while allowing your newer and less engaged users to become
\n acquainted with the value of your content before experiencing a paywall. (“Paywall,” in this
\n context, applies equally to barriers that require either subscription or merely registration
\n for content access.)<\/p>\n
There is no single value for optimal sampling across different businesses. However,
\n for most daily news publishers, we expect the value to fall between 6 and 10 articles per
\n user per month. We think most publishers will find a number in that range that preserves a
\n good user experience for new potential subscribers while driving conversion opportunities
\n among the most engaged users. <\/p>\n
As a starting point for your explorations, we encourage you to provide 10 articles per month
\n to Google search users and iterate from there. We leave the exact number to the discretion of
\n individual publishers, who are best positioned to understand the particular demands of their
\n businesses. We encourage publishers to analyze the current percentage of search users who land
\n on their paywalls, and select a monthly number that achieves a similar result. You can always
\n lower the value later, after you have some confidence that you are on a stable footing. <\/p>\n
In addition to metering, some publishers show the first few sentences of an article “above
\n the fold” of their paywall after the meter has run out. We think this is a good practice. By
\n exposing the article lead, publishers can let users experience
\n the value of the content and so provide more value to the user than a page with completely
\n blocked content. Lead-in also generates user curiosity about how article continues, which
\n may assist in conversion.<\/p>\n
Publishers will want to experiment with different sampling values to determine their
\n effect on referral traffic and conversion. <\/p>\n
Bear in mind that our user studies have shown that when users who have experienced only a
\n small amount of content are required to subscribe, their interest in the product diminishes
\n greatly. Our analysis shows that general user satisfaction starts to degrade significantly
\n when paywalls are shown more than 10% of the time (which generally means that about 3% of
\n the audience has been exposed to the paywall). We recommend caution in approaching that limit,
\n because you may start to alienate users who have not yet become convinced of the value of your
\n content. <\/p>\n
Publishers with more advanced technical resources may want to focus their efforts more
\n narrowly on those specific users in the engaged segment. By identifying users who
\n consistently use up the monthly allotment, publishers could then target them by reducing the
\n sample allowance for that audience specifically, and, by allowing more liberal
\n consumption for other users, reduce the risk that overall user behavior and satisfaction is
\n degraded. <\/p>\n
Enclose paywalled content with structured data in order to help Google Learn more about how to indicate paywalled We recommend two types of flexible sampling: metering and lead-in. Explore general guidance for flexible sampling including metering and paywalls.<\/p>\n","protected":false},"menu_order":60,"template":"","meta":{"footnotes":""},"ar_kb_kategori":[670],"ar_kb_etiket":[],"class_list":["post-25488","ar_kb","type-ar_kb","status-publish","has-post-thumbnail","hentry","ar_kb_kategori-ranking-and-search-appearance"],"_links":{"self":[{"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb\/25488","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb"}],"about":[{"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/types\/ar_kb"}],"version-history":[{"count":0,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb\/25488\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/media\/27527"}],"wp:attachment":[{"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/media?parent=25488"}],"wp:term":[{"taxonomy":"ar_kb_kategori","embeddable":true,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb_kategori?post=25488"},{"taxonomy":"ar_kb_etiket","embeddable":true,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb_etiket?post=25488"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\n differentiate paywalled content from the practice of cloaking<\/a>,
\n where the content served to Googlebot is different from the content served to users.
\n If you don’t want the content to be accessible to the browser at the time of serving, choose a
\n paywall implementation that doesn’t supply the paywalled content to the browser.<\/p>\n
\n content with structured data<\/a> and refer to our guidance on using JavaScript to implement paywalled content<\/a>. <\/p>\n","protected":false},"excerpt":{"rendered":"