Dynamic Configurability of Web Pages Including Anchor Text

Abstract

In an embodiment, a processor receives anchor text configuration data for a web page, and determines whether the anchor text configuration data includes a preference to use at least a portion of a web page title as a string of anchor text that refers to that web page. If the anchor text configuration data includes the preference, then the processor determines whether software code underlying the web page includes at least one of: <h1>, <title>, and og:title. If the determination is positive, then a link is configured to display the string of anchor text on a different web page, the link being represented at least in part by the at least one of <h1>, <title>, and og:title. The link is further configured to, when included in the first web page, create a modified web page and send the configured link to the different web page.

We claim: 
     
         1 . A method, comprising:
 receiving, at a processor, anchor text configuration data for a second web page;   determining, at the processor, if the anchor text configuration data includes a preference to use at least a portion of a web page title as a string of anchor text that refers to the second web page;   if the anchor text configuration data includes the preference to use the at least a portion of a web page title as the string of anchor text, then determining, at the processor, whether software code underlying the second web page includes at least one of: an <h 1 > tag, a <title> tag, and an og:title;   if the software code underlying the second web page includes at least one of: an <h 1 > tag, a <title> tag, and an og:title, then:
 configuring a link, at the processor, to display the string of anchor text on a first web page, the link being represented at least in part by the at least one of the an <h 1 > tag, a <title> tag, and an og:title, the link further configured to, when included in the first web page, create a modified web page; and 
 sending the configured link to the first web page. 
   
     
     
         2 . The method of  claim 1 , further comprising:
 modifying software code of the first web page to create the modified web page.   
     
     
         3 . The method of  claim 2 , further comprising:
 serving the modified web page.   
     
     
         4 . The method of  claim 1 , wherein said receiving anchor text configuration data is received from a web page server system. 
     
     
         5 . The method of  claim 1 , wherein said determining, at the processor, whether software code underlying the second web page includes at least one of: an <h 1 > tag, a <title> tag, and an og:title, comprises determining, in a predetermined sequential order, whether the software code underlying the second web page includes the <h 1 > tag, the <title> tag, and the og:title. 
     
     
         6 . The method of  claim 1 , further comprising:
 determining, at the processor, whether the anchor text configuration data includes a preference to include a long description in the string of anchor text;   if the anchor text configuration data includes a preference to include a body description in the string of anchor text, then determining, at the processor, whether the software code underlying the second web page includes at least one of a meta description and an og:description;   if the software code underlying the second web page includes at least one of a meta description and an og:description, then configuring the link to include the at least one of the meta description and og:description in the string of anchor text.   
     
     
         7 . The method of  claim 6 , further comprising:
 if the software code underlying the second web page does not include at least one of a meta description and an og:description, then configuring the link to include the body text in the string of anchor text.   
     
     
         8 . The method of  claim 1 , wherein the anchor text configuration data includes an ordered preference for using at least two of the <h 1 > tag, the page title, and the og:title; and further comprising:
 configuring the link, at the processor, to include as anchor text at least a more preferred of the <h 1 > tag, the page title, and the og:title. 
 
     
     
         9 . A method, comprising:
 receiving, at a processor, anchor text configuration data for a second web page;   determining, at the processor, whether the anchor text configuration data includes a preference to use at least a portion of a keyword as a string of anchor text that refers to the second web page;   if the anchor text configuration data includes the preference to use the at least a portion of a keyword as the string of anchor text, then determining, at the processor, whether the anchor text configuration data includes a request to maintain a ranking in search engine results;   if the anchor text configuration data includes the request to maintain the ranking in search engine results, then receiving, at the processor, at least a top ranking keyword;   configuring a link, at the processor, to display the string of anchor text on a first web page, the link being represented at least in part by the top ranking keyword, the links further configured to, when inserted into the first web page, create a modified web page; and   sending the configured link to the first web page.   
     
     
         10 . The method of  claim 9 , further comprising:
 modifying software code of the first web page to create the modified web page.   
     
     
         11 . The method of  claim 10 , further comprising:
 serving the modified web page.   
     
     
         12 . The method of  claim 9 , further comprising:
 calculating a top ranking keyword for the second page.   
     
     
         13 . The method of  claim 9 , wherein said receiving anchor text configuration data is received from a web page server system. 
     
     
         12 . The method of  claim 9 , further comprising:
 calculating, at a processor, anchor text configuration data for the second web page; the anchor text configuration data calculated using at least one SEO-improving variable.   
     
     
         14 . The method of  claim 9 , further comprising:
 if the anchor text configuration data includes the preference to use the at least a portion of a keyword as the string of anchor text, then determining, at the processor, whether the anchor text configuration data includes a preference to improve ranking a ranking in search engine results;   if the anchor text configuration data includes a preference to improve ranking in search engine results, then receiving, at the processor, at least a keyword within a predetermined striking distance from a first set of search engine search results;   configuring a link, at the processor, to display the string of anchor text on a first web page, the link being represented at least in part by the keyword within the predetermined striking distance;   sending the configured link to the first web page.   
     
     
         15 . The method of  claim 9 , further comprising:
 determining, at the processor, whether the anchor text configuration data includes a preference to include a long description in the string of anchor text;   if the anchor text configuration data includes a preference to include a body description in the string of anchor text, then determining, at the processor, whether the software code underlying the second web page includes at least one of a meta description or an og:description;   if the software code underlying the second web page includes at least one of a meta description and an og:description, then configuring the link to include the at least one of the meta description and og:description in the string of anchor text.   
     
     
         16 . The method of  claim 15 , further comprising:
 if the software code underlying the second web page does not include at least one of a meta description and an og:description, then configuring the link to include at least a portion of a second page's body text in the string of anchor text.   
     
     
         17 . The method of  claim 15 , wherein the anchor text configuration data includes an ordered preference for using at least one of the meta description and the og:description; and further comprising:
 configuring the link, at the processor, to include as anchor text at least a most preferred of the meta description and the og:description.   
     
     
         18 . A method, comprising:
 receiving, at a processor, anchor text configuration data for a second web page;   determining, at the processor, whether the anchor text configuration data includes a preference to use a long description as a string of anchor text that refers to the second web page;   if the anchor text configuration data includes a preference to include a body description in the string of anchor text, then determining, at the processor, whether the software code underlying the second web page includes at least one of a meta description and an og:description;   if the software code underlying the second web page includes at least one of a meta description and an og:description, then configuring a link, at the processor, to display the string of anchor text on a first web page, the link being represented at least in part by the at least one of the meta data description and the og:description.   
     
     
         19 . The method of  claim 18 , further comprising:
 if the software code underlying the second web page does not include at least one of a meta description and an og:description, then configuring the link to include at least a portion of the second web page's body text in the string of anchor text.   
     
     
         20 . The method of  claim 18 , wherein the anchor text configuration data includes an ordered preference for using only one of the meta description and the og:description; and further comprising:
 configuring the link, at the processor, to include as anchor text at least a most preferred of the meta description and the og:description.