Issue description
The content of the store is currently not accessible for hypertext search engines, because the links between pages are not sent in the response, but are only rendered via JavaScript. While the theoretical impact of this has (REST, follow your nose) is a serious issue, the currently urgent implication is that a search engine cannot index the content of a store. It should be possible to find the store content on google.
Created: 2008-12-13 11:53:16, Robert Cerny Modified: 2009-08-21 08:59:06, Robert Cerny
Link,
No reifier
Comment
This seems to be more complicated than expected, since search engine vendors, consider the varying of the representation for their spiders as "cloaking" and might blacklist sites that expose such behavior. Additionally the great number of links between pages might be considered an attempt to improve the ranking by illegal means. These harsh consequences are understandable because dark forces used such methods to trick search engines. Yet, it is very unfortunate because creating a HTML only presentation of every page for spider would be an optimal solution.
Created: 2008-12-15 17:37:28, Robert Cerny Modified: 2008-12-15 17:40:31, Robert Cerny
Link,
No reifier
A sitemap (a list of URLs and some additional information submitted separatly to the search engine vendor) will not help, since this only incereases the entry points for the spider, but does not avoid the visiting of the page.
Created: 2008-12-15 17:37:29, Robert Cerny Modified: 2008-12-15 17:37:29, Robert Cerny
Link,
No reifier
Maybe a sitemap for humans might help to expose at least the most important topics and their names and where to find more information about that topic.
Created: 2008-12-15 17:38:49, Robert Cerny Modified: 2008-12-15 17:38:49, Robert Cerny
Link,
No reifier
One possibility is to drop the necessity of the client to have a topic map engine and just server out HTML content (using the "rel" attribute of a link). The downside of this would be that the client does not have the power to merge two topic maps rendering the include/transclude feature dysfunctional.
Created: 2009-03-05 22:22:53, Robert Cerny Modified: 2009-03-05 22:22:53, Robert Cerny
Link,
No reifier
I think the best solution is to create a minimal html representation, which is augmented or replaced by the JTM. This has an impact on performance though.
Created: 2009-03-20 05:46:03, Robert Cerny Modified: 2009-03-20 05:46:03, Robert Cerny
Link,
No reifier
I implemented the solution with a html representation and linking from the start page in order to make the content crawlable.
Created: 2009-06-07 16:11:34, Robert Cerny Modified: 2009-06-07 16:11:34, Robert Cerny
Link,
No reifier
|
Reporting date2008-12-13+01:00 Created: 2008-12-13 11:53:17, Robert Cerny Modified: 2008-12-13 11:53:17, Robert Cerny
Link,
No reifier
Resolving date2009-06-07+02:00 Created: 2009-06-07 16:11:31, Robert Cerny Modified: 2009-06-07 16:11:31, Robert Cerny
Link,
No reifier
Planned for version
Topincs 3.1.0
Created: 2008-12-13 11:53:17, Robert Cerny Modified: 2008-12-13 11:53:17, Robert Cerny
Link,
No reifier
Topincs 3.2.0
Created: 2009-05-28 13:43:16, Robert Cerny Modified: 2009-05-28 13:43:16, Robert Cerny
Link,
No reifier
Has sub issue
Create a minimal HTML represenation of the Wiki topic map (Enhancement)
Created: 2009-03-24 09:10:32, Robert Cerny Modified: 2009-03-24 09:10:32, Robert Cerny
Link,
No reifier
Create an entry point for the search engine (Enhancement)
Created: 2009-03-24 09:11:28, Robert Cerny Modified: 2009-03-24 09:11:28, Robert Cerny
Link,
No reifier
Reported by
Robert Cerny
Created: 2008-12-13 11:53:17, Robert Cerny Modified: 2008-12-13 11:53:17, Robert Cerny
Link,
No reifier
Resolved by
Robert Cerny
Created: 2009-06-07 16:11:31, Robert Cerny Modified: 2009-06-07 16:11:31, Robert Cerny
Link,
No reifier
Resolved in version
Topincs 3.2.0
Created: 2009-06-07 16:11:31, Robert Cerny Modified: 2009-06-07 16:11:31, Robert Cerny
Link,
No reifier
|