JP7314247B2 - Management device, proposed method, and program - Google Patents

Description

The present invention relates to a management device, a proposal method, and a program.

In recent years, sales sites that conduct electronic commerce have gained popularity on the Internet. For example, a large-scale sales site (shopping mall site) consisting of many shops (virtual shops) not only handles products in a wide range of categories (genres), but also attracts many users due to price competition between shops.

A huge number of product pages are uploaded to such sales sites, and a desired product page can be browsed from a user terminal. For example, a user using a sales site performs a search within the sales site from the top page of the sales site or the like, and browses a desired product page.
In addition, there are many users who search the web with a predetermined search engine from outside the sales site, and transition to the product page of the sales site from the searched search list.
Therefore, it is desirable to make the product page easier to search from search engines (for example, to display it higher in the search list).

For example, Patent Literature 1 discloses a technique for performing search engine optimization (SEO).
The technology disclosed in Patent Document 1 collects pages of a large number of business owners who run "the same type of business", and sets keywords related to common businesses in a common industry to each page, thereby making it easier to be ranked high in the search list when searched by a search engine.

Japanese Patent No. 6600425

As one of the SEO measures in the sales site described above, metadata (metatag) including effective keywords is registered in the product page. For example, in the case of a product page for selling a game machine, by registering metadata containing a plurality of keywords (keyword group) such as the name, model number, abbreviation, characteristics, and related terms of the game machine on the product page, the crawler of the search engine (a program that crawls each web page and collects necessary data) can collect more appropriate data on the product page. As a result, it is expected that the product page will be effectively analyzed and the product page will be highly evaluated, and that the product page will be displayed at the top of the search list when the web is searched by a search engine.

However, in reality, when a shop registers metadata on a product page, there are many cases where the metadata includes an invalid keyword, or conversely, does not include an effective keyword. Furthermore, there are cases where the metadata itself is not registered in the product page.
In those cases, even if the crawler of the search engine collects data on the product page, the evaluation of the product page does not increase sufficiently. As a result, it has become extremely difficult to navigate to the product page from outside the sales site through a search using a search engine.

Therefore, there has been a demand for a technology capable of appropriately managing product pages for which metadata registration is recommended.

SUMMARY OF THE INVENTION It is an object of the present invention to provide a management device, a proposal method, and a program capable of appropriately managing product pages for which metadata registration is recommended.

The management device according to the first aspect of the present invention includes:
A management device for managing product pages for which it is recommended to register metadata including keyword groups about products,
a generating unit that generates a search query for searching the product page using a predetermined search engine;
a collection unit that collects a search list obtained by searching using the search query generated by the generation unit in the search engine;
an extracting unit that extracts a candidate keyword group that is a candidate for the keyword group from summary information describing an outline of each web page included in the search list collected by the collecting unit;
a proposal unit that proposes the keyword group to be included in the metadata based on the candidate keyword group extracted by the extraction unit;
characterized by comprising

Further, in the management device according to the above aspect,
The proposal unit may propose registration of the metadata including the candidate keyword group when the metadata is not registered in the product page.

In addition, the management device according to the above aspect,
A registration unit may be further provided for registering the metadata including the candidate keyword group in the product page when the metadata is not registered in the product page even after a certain period of time has passed since the proposal unit proposed the registration of the metadata.

In addition, the management device according to the above aspect,
further comprising a comparison unit that compares the keyword group in the metadata registered in the product page with the candidate keyword group extracted from the summary information,
The proposing unit may propose correction of the keyword group in the metadata based on a comparison result by the comparing unit.

Further, in the management device according to the above aspect,
The proposing unit may propose deletion of the first keyword from the keyword group in the metadata when the first keyword included in the keyword group in the metadata is not included in the candidate keyword group in the comparison result by the comparing unit.

Further, in the management device according to the above aspect,
The proposing unit may propose addition of the second keyword to the keyword group in the metadata when the second keyword included in the candidate keyword group is not included in the keyword group in the metadata in the comparison result by the comparison unit.

Further, in the management device according to the above aspect,
The generating unit may generate the search query used by the search engine, based on transition source information indicating a transition source of the access when the access to the product page transitions from the search list searched by the search engine.

Further, in the management device according to the above aspect,
The generating unit may generate the search query based on the metadata registered in the product page or the description content of the product page when the access to the product page has not transitioned from the search list, or when the access to the product page has not occurred for a predetermined period of time.

In addition, the management device according to the above aspect,
After the proposal is made by the proposal unit, if the metadata is registered in the product page, or if the keyword group in the metadata that has been registered in the product page is corrected, a verification unit that verifies the search ranking of the product page in the search list searched by the search engine using the keyword group after the registration or after the correction as the search query.

The proposed method according to the second aspect of the present invention includes:
A proposal method executed by a management device that manages product pages in which it is recommended to register metadata including keyword groups about products,
a generation step of generating a search query for searching the product page with a predetermined search engine;
a collecting step of collecting a search list obtained by searching using the search query generated in the generating step in the search engine;
an extracting step of extracting a candidate keyword group, which is a candidate for the keyword group, from summary information describing an outline of each web page included in the search list collected in the collecting step;
a proposing step of proposing the keyword group to be included in the metadata based on the candidate keyword group extracted in the extracting step;
characterized by comprising

A program according to a third aspect of the present invention comprises
The computer that manages the product page where it is recommended to register metadata that includes a group of keywords about the product,
A generation procedure for generating a search query for searching the product page with a predetermined search engine;
A collection procedure for collecting a search list obtained by searching using the search query generated in the generation procedure in the search engine;
An extraction step of extracting a candidate keyword group that is a candidate for the keyword group from summary information describing an overview of each web page included in the search list collected in the collection step;
a proposal procedure for proposing the keyword group to be included in the metadata based on the candidate keyword group extracted by the extraction procedure;
is characterized by executing

The above program can be distributed and sold through a computer communication network independently of the computer on which the program is executed.
Furthermore, the information recording medium for recording the above program is a non-transitory recording medium, and can be distributed and sold independently of the computer. Here, a non-temporary recording medium refers to a tangible recording medium. Examples of non-temporary recording media include compact discs, flexible discs, hard discs, magneto-optical discs, digital video discs, magnetic tapes, and semiconductor memories. Also, a transitory recording medium indicates a transmission medium (propagating signal) itself. Temporary recording media are, for example, electrical signals, optical signals, electromagnetic waves, and the like. A temporary storage area is an area for temporarily storing data and programs, and is, for example, a volatile memory such as a RAM (Random Access Memory).

According to the present invention, it is possible to appropriately manage product pages for which registration of metadata is recommended.

1 is a block diagram showing an example of the overall configuration of an information processing system according to this embodiment; FIG. 1 is a block diagram showing an example of a schematic configuration of a typical information processing device that implements a management device; FIG. It is a block diagram showing an example of functional composition of a controlling device concerning this embodiment. It is a schematic diagram which shows an example of the metadata registered into the goods page. FIG. 10 is a schematic diagram for explaining how a search query is acquired from transition source information; FIG. 4 is a schematic diagram showing an example of a search list obtained by searching with a search engine using a search query; FIG. 4 is a schematic diagram for explaining how a keyword group extracted from summary information and a keyword group registered in a product page are compared; FIG. 11 is a schematic diagram showing an example of a proposal email when metadata is not registered; 10A and 10B are schematic diagrams showing an example of a proposal email when metadata has already been registered; FIG. 6 is a flowchart for explaining proposal processing according to the embodiment; It is a block diagram showing an example of functional composition of a controlling device concerning other embodiments.

Embodiments of the present invention are described below. In the embodiments of the present invention, a management device that manages product pages for which it is recommended to register metadata containing keywords about products will be described as an example. However, as will be described later, in addition to product pages, it is also applicable to managing web pages that publish news, blogs, etc., for which it is recommended to register metadata containing keywords for the same reason.
That is, the following embodiments are for explanation and do not limit the scope of the present invention. Therefore, those skilled in the art can adopt embodiments in which each or all of these elements are replaced with equivalents, and these embodiments are also included in the scope of the present invention.

(overall structure)
In an information processing system 100 according to an embodiment of the present invention, as shown in FIG. 1, a management device 200 that manages product pages uploaded by a shop that sells products, a shop terminal 300 that is used by the shop (the person in charge of the shop), and a user terminal 400 that is used by the user are communicably connected via the Internet 900.
It is assumed that there are a large number of shop terminals 300 corresponding to the number of shops that publish product pages in the system. It is also assumed that there are many user terminals 400 according to the number of users who use the system.

The management device 200 is, for example, a server computer or the like, and manages the information processing system 100 as a whole.
For example, the management device 200 accepts and stores product pages (web pages for selling products) uploaded from the shop terminal 300, and publishes them on the Internet 900 so that they can be browsed from the user terminal 400 or the like. In addition, it is recommended to register multiple keywords (keyword group) as metadata (metatag) to be described later on the product page. In other words, when metadata containing appropriate keywords is registered on a product page by a shop, it is expected that the crawler of a predetermined search engine will collect more appropriate data on the product page.
Nevertheless, in reality, when a shop registers metadata on a product page, there are many cases in which invalid keywords are included in the metadata, or conversely, effective keywords are not included in the metadata. Furthermore, there are cases where the metadata itself is not registered in the product page.
Therefore, the management device 200 actually performs a web search using a search engine at a predetermined timing, and proposes to the shop terminal 300 an appropriate keyword group to be included in the metadata based on a keyword group (candidate keyword group to be described later) extracted from the retrieved search list.

The shop terminal 300 is, for example, a smart phone, a personal computer, or the like used by a person in charge of the shop. The shop terminal 300 uploads product pages for products sold at the shop to the management device 200 . Also, the shop terminal 300 registers a keyword group to be set as metadata in the uploaded product page from a predetermined management screen.

The user terminal 400 is, for example, a smart phone, a personal computer, or the like used by the user. In the user terminal 400, for example, when the user inputs a desired search query (search keyword) into the search window of the browser and instructs a search, the search engine set in the browser is used to search the web.
Titles and summary information of product pages may be displayed in a search list retrieved by such a search engine. When a user interested in the product page touches (clicks) a link to the product page in the search list, the product page is changed to the product page published by the management device 200, and the user terminal 400 displays the product page.

(Outline configuration of information processing device)
A typical information processing device 500 that implements the management device 200 according to the embodiment of the present invention will be described.

As shown in FIG. 2, the information processing device 500 includes a CPU (Central Processing Unit) 501, a ROM (Read Only Memory) 502, a RAM (Random Access Memory) 503, a NIC (Network Interface Card) 504, an image processing unit 505, an audio processing unit 506, an auxiliary storage unit 507, an interface 508, an operation unit 509, and a display unit 510.

A CPU 501 controls the operation of the entire information processing apparatus 500 and is connected to each component to exchange control signals and data.

The ROM 502 records an IPL (Initial Program Loader) that is executed immediately after the power is turned on. By executing this, the program stored in the auxiliary storage unit 507 is read to the RAM 503 and the CPU 501 starts executing the program.

The RAM 503 is for temporarily storing data and programs, and holds programs and data read from the auxiliary storage unit 507 and other data necessary for communication.

The NIC 504 is for connecting the information processing device 500 to a computer communication network such as the Internet, and is compliant with the 10BASE-T/100BASE-T standards used when configuring a LAN (Local Area Network), an analog modem for connecting to the Internet using a telephone line, an ISDN (Integrated Services Digital Network) modem, an ADSL (Asymmetric Digital Subscriber Line) modem, a cable modem for connecting to the Internet using a cable television line, and the like. Configured.

The image processing unit 505 processes the image data read from the auxiliary storage unit 507 or the like by the CPU 501 or an image arithmetic processor (not shown) included in the image processing unit 505, and then records the data in a frame memory (not shown) included in the image processing unit 505. The image information recorded in the frame memory is converted into a video signal at predetermined synchronization timing and output to the display unit 510 via the interface 508 or the like. In other words, under the control of the CPU 501 , the image processing unit 505 generates an image required during the progress of processing performed by the information processing apparatus 500 and causes the display unit 510 to display the image.

The audio processing unit 506 converts the music data and audio data read from the auxiliary storage unit 507 or the like into an audio signal, and outputs the audio signal to the outside via the interface 508 or the like. In addition, when the information processing apparatus 500 includes a speaker inside, the audio processing unit 506 outputs the converted audio signal to the speaker. In other words, under the control of the CPU 501, the audio processing unit 506 generates music sounds and sounds to be generated during the processing performed by the information processing apparatus 500, and outputs the music sounds and the like from internal or external speakers.

The auxiliary storage unit 507 is a hard disk, an SSD (Solid State Drive), or the like, and stores various programs and various data necessary for controlling the operation of the entire information processing apparatus 500 . For example, the auxiliary storage unit 507 stores a program for realizing the management device 200 according to the embodiment. Then, under the control of the CPU 501, the auxiliary storage unit 507 appropriately reads the stored programs and data, and temporarily stores them in the RAM 503 or the like.

The interface 508 conforms to standards such as HDMI (registered trademark), USB (Universal Serial Bus), I2C (Inter-Integrated Circuit), etc., and is connected to an operation unit 509 and a display unit 510 . Note that the interface 508 may transmit and receive necessary information to and from other connected external devices.

The operation unit 509 receives an operation input from a worker or the like who uses the information processing device 500 .

The display unit 510 draws an image according to the image data output by the image processing unit 505 and presents it to the operator or the like who uses the information processing device 500 .

In addition, the information processing apparatus 500 may be provided with a drive unit such as a DVD (Digital Versatile Disc)-ROM instead of the auxiliary storage unit 507 . In this case, the information processing device 500 reads programs and data from a DVD-ROM or the like mounted on the drive unit, and operates in the same manner as described above.

Functions and the like of the management device 200 implemented in the information processing device 500 will be described below with reference to FIGS. 3 to 8. FIG. When the information processing apparatus 500 is powered on, a program that causes the information processing apparatus 500 to function as the management apparatus 200 according to this embodiment is executed, and the management apparatus 200 according to this embodiment is realized.

(Outline configuration of management device 200)
FIG. 3 is a block diagram showing an example of a schematic configuration of the management device 200 according to this embodiment. As illustrated, the management device 200 includes a receiver 210 , a transmitter 220 , a storage 230 and a controller 240 .

The receiving unit 210 receives various information sent from the shop terminal 300 and the user terminal 400 via the Internet 900 .
For example, the receiving unit 210 receives product pages uploaded from the shop terminal 300 . Metadata (metatags) are registered in this product page as will be described later.
The receiving unit 210 also receives access requests to product pages from the user terminal 400 and search engines (crawlers).
The NIC 504 described above can function as such a receiver 210 .

The transmission unit 220 transmits various information to the shop terminal 300 and the user terminal 400 via the Internet 900 .
For example, the transmission unit 220 transmits data of a product page for which access is requested from the user terminal 400 or search engine to the user terminal 400 or search engine.
Further, the transmission unit 220 is controlled by the control unit 240 as will be described later, and transmits a proposal mail for making a proposal to the shop to the user terminal 400 .
The NIC 504 described above can function as such a transmitter 220 .

The storage unit 230 stores various information necessary for processing in the management device 200 .
For example, the storage unit 230 stores product pages uploaded from the shop terminal 300 .
Metadata MT as shown in FIG. 4, for example, is registered in this product page. This metadata MT is, for example, a meta tag called a meta description, in which a plurality of keywords (keyword group) are set. In the metadata MT shown in FIG. 4, for example, a group of keywords such as "○○ company", "game machine", "main unit", "new model", "Christmas", "present", "[new] △△", and "□□ model" are set.
It should be noted that such metadata (metadata itself) may not be registered in the product page uploaded from the shop terminal 300 in some cases.

In addition, the storage unit 230 stores shop management information about the shop using the shop terminal 300, user management information about the user using the user terminal 400, and the like.
Note that the auxiliary storage unit 507 and the like described above can function as such a storage unit 230 .

Returning to FIG. 3, the control unit 240 controls the management device 200 as a whole. The control unit 240 includes, for example, a generation unit 241, a collection unit 242, an extraction unit 243, a comparison unit 244, a proposal unit 245, and a registration unit 246.

The generation unit 241 generates a search query for searching product pages using a predetermined search engine.
For example, when an access to a product page from the user terminal 400 transitions from a search list searched by a search engine, the generation unit 241 generates a search query used for a web search of the search engine based on transition source information (referrer) indicating the transition source in the access.

Specifically, assuming that the user terminal 400 accesses the product page and the transition source information RF shown in FIG. 5 is obtained, the generation unit 241 determines that the transition has been made from the search list of the web search because the URL of the search engine "https://search.xyz.com" (fictitious URL) is included at the beginning of the transition source information RF, and the encoding unit EN (percent-encoded portion) used for the search is included. Then, the generation unit 241 decodes the encoding unit EN to generate a search query SQ of, for example, “XX company game machine main body △△ □□ model”.

Note that when it is determined that the access to the product page does not come from the search list, the generation unit 241 generates a search query based on the metadata registered in the product page. For example, when the metadata MT as shown in FIG. 4 described above is registered in the product page, the generation unit 241 refers to the keyword group (the character string described after "content=") in the metadata MT, and generates a search query "○○ company game machine main body new Christmas present [new] △△ □□ model".

Moreover, as described above, there are cases where metadata is not registered in the product page. In that case, the generation unit 241 generates a search query based on the content described in the product page. For example, the generation unit 241 morphologically analyzes the content of the title and text of the product page, extracts keywords that match common nouns and proper nouns, and extracts a group of keywords from which duplication is eliminated, thereby generating a search query.

Returning to FIG. 3, the collection unit 242 collects a search list obtained by using the search query generated by the generation unit 241 as a search engine.
For example, when a web search is performed with a search engine using a search query of "XX company game machine main body △△ □□ model", the collecting unit 242 collects a search list SR as shown in FIG. This search list SR includes overview information GI describing an overview of each web page. Note that when metadata (metatags) as described above is registered in a searched web page, the content of the metadata is often displayed in the overview information GI. In addition, when metadata is not registered in the retrieved web page, descriptions extracted from the text, title, etc. of the web page are appropriately displayed in the overview information GI.

Returning to FIG. 3, the extracting unit 243 extracts a candidate keyword group, which is a keyword group candidate, from the summary information describing the outline of each web page included in the search list collected by the collecting unit 242 described above.
For example, the extraction unit 243 morphologically analyzes each summary information GI included in the search list SR as shown in FIG.

The comparison unit 244 compares the keyword group extracted from the outline information by the extraction unit 243 with the keyword group in the metadata registered in the product page.
For example, if the candidate keyword group KW1 shown in the upper part of FIG. 7 is extracted from the summary information by the extraction unit 243, and the keyword group KW2 shown in the lower part of FIG.

By comparing the candidate keyword group KW1 and the keyword group KW2, for example, keywords contained in only one of them can be identified.
That is, if there is a keyword that is not included in the candidate keyword group KW1 extracted from the outline information among the keywords included in the keyword group KW2 in the registered metadata, the comparison unit 244 identifies that keyword as the first keyword. Specifically, in the example of FIG. 7, "present" in the keyword group KW2 is specified as the first keyword because it is not included in the candidate keyword group KW1.

If there is a keyword that is not included in the keyword group KW2 in the registered metadata among the keywords included in the candidate keyword group KW1 extracted from the summary information, the comparison unit 244 identifies that keyword as a second keyword. Specifically, in the example of FIG. 7, since "free shipping", "delivery within the year", "winter holiday", "restock", and "chance" of the candidate keyword group KW1 are not included in the keyword group KW2, these are specified as the second keywords.

Returning to FIG. 3, the proposing unit 245 proposes a keyword group to be included in the metadata based on the candidate keyword group extracted by the extracting unit 243 described above.
In addition, the proposal unit 245 proposes registration of metadata including candidate keywords when metadata is not registered in the product page.
Specifically, the proposal unit 245 transmits a proposal mail ML1 as shown in FIG. 8 to the shop terminal 300 (sent to the set mail address addressed to the shop). This proposal mail ML1 includes, for example, proposal content SJ1 that proposes registration of metadata including the content of the candidate keyword group KW1 described above (company XX, game machine, main unit, free shipping, Christmas, shipping within the year, winter vacation, restock, chance, new model, △△, and □□ model).

Further, when metadata is already registered in the product page, the proposal unit 245 proposes correction of the keyword group in the registered metadata to the shop based on the comparison result by the comparison unit 244 described above.
For example, when the comparison result by the comparison unit 244 indicates that the first keyword is present (when the keyword included in the keyword group of the registered metadata is not included in the candidate keyword group extracted from the overview information), the proposing unit 245 proposes deletion of the first keyword from the keyword group in the registered metadata.
Specifically, the proposal unit 245 transmits a proposal mail ML2 as shown in FIG. 9A to the shop terminal 300. This proposal mail ML2 includes, as an example, proposal content SJ2 that proposes to delete the keyword "present" (first keyword) from the registered metadata (keyword group).

Further, for example, when the comparison result by the comparison unit 244 indicates that there is a second keyword (when the keyword included in the candidate keyword group extracted from the outline information is not included in the keyword group in the registered metadata), the proposal unit 245 proposes addition of the second keyword to the keyword group in the metadata.
Specifically, the proposal unit 245 transmits a proposal mail ML3 as shown in FIG. 9B to the shop terminal 300. This proposal mail ML3 includes, as an example, proposal content SJ3 that proposes adding any of the keywords (second keywords) of "free shipping", "delivery within the year", "winter vacation", "restock", and "chance" to the registered metadata (keyword group).

The proposal unit 245 may transmit these proposal contents SJ1 to SJ3 to the shop terminal 300 by means other than e-mail. For example, the proposal unit 245 may transmit these proposal contents SJ1 to SJ3 to the shop terminal 300 by SMS (Short Message Service), push notification, or the like.

A registering part 246 registers metadata including a candidate keyword group in a product page when the metadata is not registered in the product page even after a certain period of time has passed since the proposal unit 245 proposed the registration of the metadata to the shop which has not registered the metadata in the product page.
Note that the registration unit 246 may correct the registered metadata (register metadata obtained by correcting the keyword group) even if the keyword group has not been corrected even after a certain period of time has passed since the proposal unit 245 proposed correction of the keyword group in the registered metadata to the shop in which the metadata has been registered.

Note that the above-described CPU 501 and the like can function as the control unit 240 configured as described above.

(Operation of management device 200)
The operation of the management device 200 will be described below with reference to FIG. FIG. 10 is a flowchart for explaining management processing according to this embodiment.
For example, after a new product page is uploaded to the management device 200, this management process is executed at least once for that product page. It is assumed that metadata MT (metatag) as shown in FIG. 4 is registered in the product page.

First, the management device 200 determines whether or not an item page has been accessed (step S11).
For example, the control unit 240 appropriately checks the receiving unit 210 and determines whether or not the user terminal 400 has accessed the target product page.
If the management device 200 determines that the product page has not been accessed (step S11; No), the management device 200 stands by.

On the other hand, when it is determined that the product page is accessed (step S11; Yes), the management device 200 determines whether the access is by search (step S12).
That is, the control unit 240 (generating unit 241) refers to the transition source information (referrer) indicating the transition source at the time of access, and determines whether or not the transition has been made from the search list retrieved by the search engine.
For example, when the transition source information RF as shown in FIG. 5 is obtained along with the access to the product page, the control unit 240 determines that the transition has been made from the search list because the URL of the search engine “https://search.xyz.com” is included at the beginning of the transition source information RF and the encoding unit EN used for the search is included.

When the management device 200 determines that the access is by search (step S12; Yes), it generates a search query based on the transition source information (step S13).
For example, the control unit 240 (generating unit 241) generates a search query SQ of "○○ company game machine main body △△ □□ model" by decoding the encoding part EN of the transition source information RF as shown in FIG.

On the other hand, if it is determined that the access is not by search (step S12; No), the management device 200 generates a search query from the product page (step S14).
For example, the control unit 240 (generating unit 241) generates a search query of “○○ company game machine main body new Christmas present [new] △△ □□ model” based on the metadata MT as shown in FIG.
Note that if no metadata is registered in the product page, the control unit 240 generates a search query based on the content described in the product page. For example, the control unit 240 morphologically analyzes the content of the title and text of the product page, extracts keywords that match common nouns and proper nouns, and extracts a group of keywords from which duplication is eliminated, thereby generating a search query.

The management device 200 collects the search list searched by the search engine using the search query (step S15).
For example, in the above-described step S13 or step S14, when the search query "○○ company game machine main body △△ □□ model" is acquired, the control unit 240 (collection unit 242) collects a search list SR as shown in FIG. 6 by actually performing a web search with a search engine using the search query. This search list SR includes overview information GI describing an overview of each web page.

The management device 200 extracts a candidate keyword group from the summary information of the search list (step S16).
For example, the control unit 240 (extraction unit 243) morphologically analyzes each summary information GI included in the search list SR as shown in FIG.

The management device 200 determines whether the metadata has been registered (step S17).
That is, the control unit 240 determines whether metadata including a group of keywords has been registered in the product page accessed in step S11 described above.

If the management device 200 determines that the metadata has not been registered (step S17; No), the management device 200 proposes the registration of the metadata including the candidate keyword group to the shop (step S18).
Specifically, control unit 240 (proposal unit 245) transmits proposal mail ML1 as shown in FIG. 8 to shop terminal 300 (sends to the set mail address addressed to the shop). This proposal mail ML1 includes, for example, proposal content SJ1 that proposes registration of metadata including the content of the candidate keyword group KW1 described above (company XX, game machine, main unit, free shipping, Christmas, shipping within the year, winter vacation, restock, chance, new model, △△, and □□ model).
Then, the management device 200 finishes the proposal process.

On the other hand, when it is determined that the metadata has been registered (step S17; Yes), the management device 200 compares the candidate keyword group extracted in step S16 with the keyword group included in the registered metadata (step S19).
For example, the control unit 240 (comparison unit 244) compares the candidate keyword group KW1 (candidate keyword group extracted from the overview information) as shown in FIG. 7 with the keyword group KW2 (keyword group of registered metadata).

The management device 200 determines whether or not a proposal to the shop is necessary (step S20).
For example, the control unit 240 (proposing unit 245) determines that a proposal to the shop is necessary when a keyword included in only one of the keywords is identified in the comparison result of step S19. That is, when the first keyword included in the keyword group in the registered metadata is not included in the candidate keyword group extracted from the overview information, or when the second keyword included in the candidate keyword group is not included in the keyword group in the registered metadata, the control unit 240 determines that the proposal to the shop is necessary.

When the management device 200 determines that the proposal to the shop is not necessary (Step S20; No), the management device 200 ends the proposal process.
On the other hand, if it is determined that a proposal to the shop is necessary (step S20; Yes), the management device 200 proposes correction of the keyword group in the registered metadata to the shop (step S21).
For example, the control unit 240 (proposal unit 245), when there is a first keyword (when a keyword included in the keyword group in the registered metadata is not included in the candidate keyword group extracted from the overview information), proposes deletion of the first keyword from the keyword group in the registered metadata.
Specifically, control unit 240 transmits to shop terminal 300 a proposal mail ML2 as shown in FIG. This proposal mail ML2 includes, as an example, proposal content SJ2 that proposes to delete the keyword "present" (first keyword) from the registered metadata (keyword group).
Further, when there is a second keyword (when a keyword included in the candidate keyword group extracted from the outline information is not included in the keyword group in the registered metadata), the control unit 240 proposes addition of the second keyword to the keyword group in the registered metadata.
Specifically, the control unit 240 transmits a proposal mail ML3 as shown in FIG. 9B to the shop terminal 300. FIG. This proposal mail ML3 includes, as an example, proposal content SJ3 that proposes adding any of the keywords (second keywords) of "free shipping", "delivery within the year", "winter vacation", "restock", and "chance" to the registered metadata (keyword group).
Then, the management device 200 finishes the proposal process.

Through such proposal processing, a web search using a search engine is actually performed, and a proper keyword group to be included in the metadata is proposed to the shop terminal 300 based on the candidate keyword group extracted from the retrieved search list.
In other words, when the metadata is not registered in the product page, it is possible to propose to the shop (shop terminal 300) to register the metadata including the candidate keyword group.
In addition, when metadata is already registered on the product page, the candidate keyword group is compared with the keyword group included in the metadata registered on the product page, and according to the comparison result, the keyword group in the registered metadata is proposed to the shop to be corrected. In other words, in the registered metadata, if invalid keywords are included in the metadata, or conversely, if they are not included in the valid keyword metadata, correction of those keywords can be proposed to the shop.
As a result, it is possible to appropriately manage product pages for which metadata registration is recommended.

(Other embodiments)
In the above-described embodiment, in the proposal processing of FIG. 10, the case of proposing the registration of metadata containing a candidate keyword group or the correction of a keyword group triggered by access to a product page has been described.
That is, as a modification of the proposal processing of FIG. 10, the management device 200 manages the access status of each managed product page, and starts the proposal processing when there is no access to the product page for a predetermined period of time. In that case, the process starts from the above-described step S14, and the steps S15 to S21 are similarly executed.
Also in this case, a web search is actually performed using a search engine, and appropriate keyword groups to be included in the metadata are proposed to the shop terminal 300 based on the candidate keyword groups extracted from the retrieved search list.
In other words, when the metadata is not registered in the product page, it is possible to propose to the shop (shop terminal 300) to register the metadata including the candidate keyword group. In addition, when metadata is already registered on a product page, a candidate keyword group is compared with a keyword group included in the metadata registered on the product page, and according to the comparison result, correction of the keyword group in the registered metadata can be proposed to the shop.
Also in this case, it is possible to appropriately manage product pages for which metadata registration is recommended.

In the above-described embodiment, the procedure up to the point of suggesting the registration of metadata and the modification of a keyword group to the shop terminal 300 has been described. However, after the proposal is made, if the metadata is registered in the product page, or if the keyword group in the registered metadata is modified, the search ranking of the product page in the search list retrieved after the registration or after the modification may be verified.
The management device 200 characterized by verifying the search order of product pages after registration or correction will be described below with reference to FIG. 11 .

FIG. 11 is a block diagram showing an example of a schematic configuration of a management device 200 according to another embodiment. As illustrated, the management device 200 includes a receiver 210 , a transmitter 220 , a storage 230 and a controller 250 .

The control unit 250 includes a generation unit 241, a collection unit 242, an extraction unit 243, a comparison unit 244, a proposal unit 245, a registration unit 246, and a verification unit 251, for example.
Note that the generation unit 241 to the registration unit 246 have the same configuration as the generation unit 241 to the registration unit 246 in the control unit 240 of the management apparatus 200 shown in FIG. 3 described above.

The verification unit 251 verifies the search ranking of the product page in the search list searched by the search engine using the keyword group after the registration or the correction when the metadata is registered in the product page after the proposal is made by the proposal unit 245, or when the keyword group in the registered metadata is corrected.
For example, the verification unit 251 issues a warning to the shop terminal 300 when the search order of the product page in the search list searched using the corrected keyword group as the search query does not fall within a predetermined upper range.
In addition, the verification unit 251 causes the search engine to search while changing the combination of keywords used for the search query among the corrected keyword group, and verifies the combination of keywords effective for the search based on the search ranking of the product page in the searched search list.

Further, the proposal unit 245 may re-propose correction of the keyword group included in the registered metadata according to the verification result by the verification unit 251 .
Also in this case, it is possible to appropriately manage product pages for which metadata registration is recommended.

In the above embodiment, the case of managing product pages for which it is recommended to register metadata (metatags) containing keywords about products has been described. However, in addition to product pages, it is similarly applicable to managing web pages that publish news, blogs, etc., for which it is recommended to register metadata containing keywords for the same reason.

As described above, according to the present invention, it is possible to provide a management device, a proposal method, and a program capable of appropriately managing product pages for which metadata registration is recommended.

REFERENCE SIGNS LIST 100 information processing system 200 management device 210 reception unit 220 transmission unit 230 storage unit 240, 250 control unit 241 generation unit 242 collection unit 243 extraction unit 244 comparison unit 245 proposal unit 246 registration unit 251 verification unit 300 shop terminal 400 user terminal 501 CPU
502 ROMs
503 RAM
504 NICs
505 Image processing unit 506 Audio processing unit 507 Auxiliary storage unit 508 Interface 509 Operation unit 510 Display unit 900 Internet

Claims (14)

A management device for managing product pages for which it is recommended to register metadata including keyword groups about products,
a generating unit that generates a search query for searching the product page using a predetermined search engine;
a collection unit that collects a search list obtained by searching using the search query generated by the generation unit in the search engine;
an extracting unit that extracts a candidate keyword group that is a candidate for the keyword group from summary information describing an outline of each web page included in the search list collected by the collecting unit;
a proposal unit that proposes the keyword group to be included in the metadata based on the candidate keyword group extracted by the extraction unit ;
The proposal unit proposes registration of the metadata including the candidate keyword group when the metadata is not registered on the product page.
A management device characterized by : A registration unit that registers the metadata including the candidate keyword group on the product page when the metadata is not registered on the product page even after a certain period of time has elapsed since the proposal unit proposed registration of the metadata,
The management device according to claim 1 , characterized by: A management device for managing product pages for which it is recommended to register metadata including keyword groups about products,
a generating unit that generates a search query for searching the product page using a predetermined search engine;
a collection unit that collects a search list obtained by searching using the search query generated by the generation unit in the search engine;
an extracting unit that extracts a candidate keyword group that is a candidate for the keyword group from summary information describing an outline of each web page included in the search list collected by the collecting unit;
a proposal unit that proposes the keyword group to be included in the metadata based on the candidate keyword group extracted by the extraction unit;
a comparison unit that compares the keyword group in the metadata registered in the product page with the candidate keyword group extracted from the summary information,
The proposing unit proposes correction of the keyword group in the metadata based on the comparison result by the comparing unit.
A management device characterized by: The proposing unit proposes deletion of the first keyword from the keyword group in the metadata when the first keyword included in the keyword group in the metadata is not included in the candidate keyword group in the comparison result by the comparing unit.
4. The management device according to claim 3 , characterized by: If the comparison result by the comparison unit shows that the second keyword included in the candidate keyword group is not included in the keyword group in the metadata, the proposal unit proposes addition of the second keyword to the keyword group in the metadata.
4. The management device according to claim 3 , characterized by: When the access to the product page transitions from the search list searched by the search engine, the generation unit generates the search query used by the search engine based on transition source information indicating the transition source in the access.
6. The management device according to any one of claims 1 to 5 , characterized in that: When the access to the product page has not transitioned from the search list, or when the access to the product page has not been made for a predetermined period of time, the generating unit generates the search query based on the metadata registered in the product page or the description content of the product page.
6. The management device according to any one of claims 1 to 5 , characterized in that: After the proposal is made by the proposal unit, if the metadata is registered on the product page, or if the keyword group in the metadata that has been registered on the product page is corrected, after the registration or after the correction A verification unit that verifies the search ranking of the product page in the search list searched by the search engine using the keyword group after the correction.
8. The management device according to any one of claims 1 to 7 , characterized by: A management device for managing product pages for which it is recommended to register metadata including keyword groups about products,
a generating unit that generates a search query for searching the product page using a predetermined search engine;
a collection unit that collects a search list obtained by searching using the search query generated by the generation unit in the search engine;
an extracting unit that extracts a candidate keyword group that is a candidate for the keyword group from summary information describing an outline of each web page included in the search list collected by the collecting unit;
a proposal unit that proposes the keyword group to be included in the metadata based on the candidate keyword group extracted by the extraction unit;
When the access to the product page transitions from the search list searched by the search engine, the generation unit generates the search query used by the search engine based on transition source information indicating the transition source in the access.
A management device characterized by: A management device for managing product pages for which it is recommended to register metadata including keyword groups about products,
a generating unit that generates a search query for searching the product page using a predetermined search engine;
a collection unit that collects a search list obtained by searching using the search query generated by the generation unit in the search engine;
an extracting unit that extracts a candidate keyword group that is a candidate for the keyword group from summary information describing an outline of each web page included in the search list collected by the collecting unit;
a proposal unit that proposes the keyword group to be included in the metadata based on the candidate keyword group extracted by the extraction unit;
When the access to the product page has not transitioned from the search list, or when the access to the product page has not been made for a predetermined period of time, the generating unit generates the search query based on the metadata registered in the product page or the description content of the product page.
A management device characterized by: After the proposal is made by the proposal unit, if the metadata is registered on the product page, or if the keyword group in the metadata that has been registered on the product page is corrected, after the registration or after the correction A verification unit that verifies the search ranking of the product page in the search list searched by the search engine using the keyword group after the correction.
11. The management device according to claim 9 or 10, characterized in that: A management device for managing product pages for which it is recommended to register metadata including keyword groups about products,
a generating unit that generates a search query for searching the product page using a predetermined search engine;
a collection unit that collects a search list obtained by searching using the search query generated by the generation unit in the search engine;
an extracting unit that extracts a candidate keyword group that is a candidate for the keyword group from summary information describing an outline of each web page included in the search list collected by the collecting unit;
a proposal unit that proposes the keyword group to be included in the metadata based on the candidate keyword group extracted by the extraction unit;
a verification unit that verifies the search ranking of the product page in the search list searched by the search engine using the keyword group after the registration or after the correction, when the metadata is registered on the product page after the proposal is made by the proposal unit, or when the keyword group in the metadata registered on the product page is corrected;
A management device comprising: A proposal method executed by a management device that manages product pages in which it is recommended to register metadata including keyword groups about products,
a generation step of generating a search query for searching the product page with a predetermined search engine;
a collecting step of collecting a search list obtained by searching using the search query generated in the generating step in the search engine;
an extracting step of extracting a candidate keyword group, which is a candidate for the keyword group, from summary information describing an outline of each web page included in the search list collected in the collecting step;
a proposal step of proposing the keyword group to be included in the metadata based on the candidate keyword group extracted in the extraction step ;
In the proposal step, when the metadata is not registered on the product page, registration of the metadata including the candidate keyword group is proposed.
A proposed method characterized by : The computer that manages the product page where it is recommended to register metadata that includes a group of keywords about the product,
A generation procedure for generating a search query for searching the product page with a predetermined search engine;
A collection procedure for collecting a search list obtained by searching using the search query generated in the generation procedure in the search engine;
An extraction step of extracting a candidate keyword group that is a candidate for the keyword group from summary information describing an overview of each web page included in the search list collected in the collection step;
executing a proposal procedure for proposing the keyword group to be included in the metadata based on the candidate keyword group extracted by the extraction procedure;
In the proposal procedure, when the metadata is not registered on the product page, registration of the metadata including the candidate keyword group is proposed.
A program characterized by

Images