why collective.perseo?

collective.perseo was born during a collaboration with Irene Capatti, Federica D'Elia and SEO Specialist Andrea Pernici. The product quintagroup.seoptimaizer is very useful, but Andrea needed something more.

Features

With collective.perseo you can manage:

• globally (configurations applied to each page of the site), through “PerSEO” tool under Add-on Configuration:

  • Webmaster Tools (Google Webmaster Tools, Yahoo Site Explorer, Bing Webmaster Tools)
    

  • tag title, description and keywords meta tags, separately for:

    • Home page

    • Single page

    • Search page

    • Not Found page

    • Author page

    • Site Map page

    • Contact page

    • Event

    • File

    • Folder

    • Image

    • Link

    • News Item

    • Topic

  • Disable the indexing of resources using noindex and nofollow, separately for:

    • Search page

    • Login and Registration pages

    • Administration pages

    • Single pages

    • Event

    • File

    • Folder

    • Image

    • Link

    • News Item

    • Topic

    • (also handle noodp, noydir, noarchive, nosnippet)

  • Content types included in the sitemap.xml.gz

  • Ping sites (Google, Bing, Ask) automatically when the Site Map is updated

  • Indexing RSS feeds

  • Add itemscope and itemtype attributes to body tag (if you install the extension collective.perseoschema for Schema.org)

• one by one, through “SEO” tab on each content of the site (allows you to change SEO settings for that specific content):

  • tag title and description and Keywords meta tags

  • Meta Robots Follow Tag (follow/nofollow)

  • Meta Robots Index Tag (index/noindex)

  • Meta Robots Advanced Tag (noodp, noydir, noarchive, nosnippet)

  • Canonical URL

  • Content included in the sitemap.xml.gz (yes/no).

  • Priority of content in sitemap.xml.gz

  • itemtype attribute (if you install the extension collective.perseoschema for Schema.org)

Useful links

http://pypi.python.org/pypi/collective.perseo

http://pypi.python.org/pypi/collective.perseoschema

http://plone.org/products/collective.perseo

http://plone.org/products/collective.perseoschema

I'm still working on collective.solr branch. To help our customer to understand how certain documents has been scored, I've included in Plone search results an configurable option - debug query.

Using it you can check directly in Plone, Solr score explanation (it's toggled by jQuery).

hidden:

and unfold:

For one of our customer we have been developing Solr score configuration in Plone. After a short discussion with witsch we have decided to contribute our efforts and merge everything to collective.solr branch. This is just a simple configuration panel with additional score query builder. Every score-boost entry has 3 fields: index, value and score. In current implementation if you leave value empty - it will be populated with SearchableText index value - when building the query. This approach allows flexibility our customer needs.

Let's assume you want to sort results as follow:

• Description has a query boost 10.0
• portal_type=Document has a query boost 15.0
• review_state=published has a query boost 20.0

In this way you can boost Description index (for which the value will be taken from SearchableText) and portal_type index (for which you can define the value manualy) at the same time.

to-do: we would like to add as an option Solr score explanation in search results (for users who want to know why certain document has certain score).

We have found also some problems with Lucene proximity algorithm which can give some problems (it should be configurable in Solr 1.4.0). 

Description:%(searchterm)s^10 Title:%(searchterm)s^20 portal_type:Folder^10 portal_type:Document^30 review_state:published^100