In accordance with an example, syndication data regarding the published content of a web page is used to determine supplemental content to display on that web page, in association with the published content. The act of publishing content to a webpage or blog may cause syndication data to be created providing an event indication that the web page content has been updated. This event in turn prompts a process of using the updated web page content to possibly determine different supplemental content to display on the web page in association with the updated published content.
In general, syndication data for a web page is data that represents the content of the web page and may even be identical in content to the content of the web page, but is not itself the content of the web page. The syndication data is available to syndication-aware programs that subscribe to a “feed” of the syndication data. The syndication data is typically designed to be machine-readable for efficient processing (e.g., into human-readable form). For example, the syndication data is typically XML-based or otherwise structured to ensure or enhance the machine-readability. A typical use of syndication data is by an aggregation program, which combines the contents of multiple feeds for display on a single screen or series of screens. Examples of syndication data include data formatted according to standards such as past, current and to-be promulgated versions of RSS and Atom. While RSS and Atom are popular syndication data formatting standards, there are (and, in high probability, will be) other standards for syndication data formatting.
In at least some examples, the syndication data 106 is determined and/or generated based on what the author and/or publisher of the web page content considers to be important. This may be done, for example, by an option of the same content management system that may be used to manually or automatically generate the web page content.
In accordance with one example, a “self-scraping” method is utilized to generate the syndication data. Thus, for example, scraping tools may process the web page content and extract what the tool deems to be the relevant parts, to include in the syndication data. Some scraping tools use regular expressions or XPath expressions. Other scraping tools process “hints” provided within the web page content, such as <div> or <span> tags, that help the scraping tool to decide what should be included in the syndication data. Alternately, some third parties may “scrape” the web page content and make the resulting syndication data generally available.
We now turn to
More particularly, the associated advertisement content caused to be displayed in the advertisement content portion 104 is determined based on syndication data 106 that corresponds to the publisher web page content. As shown in
In addition to the syndication data 106 being provided via the syndication data feed 107 for access by syndication-aware programs, a content analyzer 108 analyzes the syndication data 106 by accessing the syndication data feed 107. The analysis by the content analyzer 108 may be, for example, similar to the analysis that would otherwise be carried out on the published content during a crawling operation. The syndication data 106, typically structured, would generally be more easily processed than the web page content itself. In general, the syndication data is a cleaner representation of the web page content. For example, the syndication data typically does not include the navigation links of the web page.
In the discussion thus far, the supplemental content, caused to be displayed in association with the web page content, has been advertisement content. In accordance with other examples, the content caused to be displayed in association with the web page content is not advertisement content but, rather, is other content (such as, for example, a web badge, map, text ad, musical playlist, links, syndicated feed items, calendar with events, or other content) that has been determined based at least on the syndication data and that is available in association with the web page content.
Having discussed the architecture illustrated in
At step 204, syndication data is received regarding web page content. At step 206, the syndication data is processed to determine an indication of the web page content, such as a general or specific category of subject matter to which the web page content pertains. At step 208, the determined indication of the web page content is processed relative to an advertisement inventory, to determine an indication of advertising (which may even indicate no advertising). The advertisement service may have been configured, for example, as to how many advertisements to cause to indicate for the web page content and what types of advertisements to cause to display. The processing of step 208 may be informed by this configuration of the advertisement service.
The processing in step 208 indicated advertising to be displayed in association with the web page content. In some examples, the indication is a pointer that will point to a particular advertisement or particular advertisements that will be displayed, although it may not have been determined at the time of step 208 what is the particular advertisement or particular advertisements that will be displayed.
At step 210, the advertisement service (or, in the case of the supplemental content not being an advertisement, some other similar service) is configured relative to the web page content and to the indication of the advertising. For example, the advertisement service may be configured such that, when the web page content is caused to be displayed, the particular indicated advertisement is also caused to be displayed.
At step 212, the advertisement service serves the advertisements that the advertisement service has been configured to serve relative to the published content. Upon an indication 202 that new and/or updated syndication data is available, processing returns to step 204.
Arrow 214a indicates a request to display the published content. In accordance with the arrow 214 example, step 212 is repeated each time there is a request to display the published content. Arrow 214b illustrates another example, in which much of the
We have described syndication data regarding the published content of a web page being used to determine supplemental content to display on that web page, in association with the published content. In general, the form of the syndication data is such that the supplemental content, including advertising, have increased relevance to a viewer of the web page.