source: products/quintagroup.seoptimizer/trunk/README.txt @ 2970

Last change on this file since 2970 was 2970, checked in by mylan, 14 years ago

Merged branches/plone4 into /trunk:

merged revisions 3475-3477,3480,3483,3513,3761-3762,3998-3999,4002-4003,4005-4007
via svnmerge from ​http://svn.quintagroup.com/products/quintagroup.seoptimizer/branches/plone4

........

r3475 | mylan | 2010-06-01 19:58:16 +0300 (Tue, 01 Jun 2010) | 1 line


#144: Bump version to 4.0

........

r3476 | mylan | 2010-06-01 20:00:54 +0300 (Tue, 01 Jun 2010) | 1 line


#144: Update history

........

r3477 | mylan | 2010-06-01 20:14:44 +0300 (Tue, 01 Jun 2010) | 1 line


Fix typo in HISTORY

........

r3480 | mylan | 2010-06-01 22:13:26 +0300 (Tue, 01 Jun 2010) | 1 line


#144: Merged [3479] bugfix commit from /trunk

........

r3483 | olha | 2010-06-02 12:33:10 +0300 (Wed, 02 Jun 2010) | 1 line


README file updated

........

r3513 | olha | 2010-06-04 15:03:56 +0300 (Fri, 04 Jun 2010) | 1 line


info about product version for buildout added

........

r3761 | mylan | 2010-08-04 20:31:59 +0300 (Wed, 04 Aug 2010) | 1 line


Remove tabindex from seo_context_properties template

........

r3762 | mylan | 2010-08-04 21:23:03 +0300 (Wed, 04 Aug 2010) | 1 line


Bump version to 4.0.1, update HISTORY

........

r3998 | mylan | 2010-11-02 13:31:16 +0200 (Tue, 02 Nov 2010) | 1 line


#233: Fixed seotab-visibility view permission

........

r3999 | mylan | 2010-11-02 13:31:57 +0200 (Tue, 02 Nov 2010) | 1 line


#233: Removed debugging coded from testBugs module

........

r4002 | mylan | 2010-11-02 14:31:41 +0200 (Tue, 02 Nov 2010) | 1 line


#233: tests plone4 branch with plone-3.x: removed fixint plone version to 4.0

........

r4003 | mylan | 2010-11-02 14:45:50 +0200 (Tue, 02 Nov 2010) | 1 line


#233: tests plone4 branch with plone-3.x: removed Plone as required package for run tests in Plone<3.3

........

r4005 | mylan | 2010-11-02 15:17:46 +0200 (Tue, 02 Nov 2010) | 1 line


#233: tests plone4 branch with plone-3.x: leave commented Plone>=4.0a requirement. This allows package to be used with plone-3.X

........

r4006 | mylan | 2010-11-02 15:21:46 +0200 (Tue, 02 Nov 2010) | 1 line


#233: little cleanup testBugs code

........

r4007 | mylan | 2010-11-02 15:22:18 +0200 (Tue, 02 Nov 2010) | 1 line


#233: Up version of the package in metadata.xml

........
File size: 3.3 KB
Line 
1Introduction
2============
3
4quintagroup.seoptimizer was created to enhance SE visibility of Plone sites.
5
6
7Features
8--------
9
10quintagroup.seoptimizer allows per document editing of:
11
12* HTML Title tag
13
14* META description tag
15
16* META keywords tag
17
18* HTML comment into page header
19
20* META robots tag
21
22* META Disposition tag
23
24* Canonical URl http://projects.quintagroup.com/products/wiki/qSEOptimizer#CanonicalURL
25
26For Title, description keywords and comment you have statistics (total/stop/used words, field length counter).
27
28IMPORTANT
29---------
30
31**Starting from 3.0 release - quintagroup.seoptimizer package does not need 'overrides.zcml' file. So please remove 'quintagroup.seoptimizer-overrides' line from your buildout's ZCML area.**
32 
33Usage
34-----
35
36* Go to Plone Control Panel, enable Plone SEO for desired content types
37
38* Go to a document (Blog entry, news item, event, etc)
39
40* Switch to *SEO Properties* tab
41
42* Select *Override* checkboxes of features you want to override
43
44* Type-in your SEO values
45
46* Save changes
47
48* Do this for all documents that need enhanced SEO properties
49
50
51Requirements
52------------
53
54* Plone 3.x, Plone 4
55
56quintagroup.seoptimizer requires plone.browserlayer package to be installed in your site. plone.browserlayer package is shipped with Plone >= 3.1 and thus you don't need anything extra when you have that version of Plone.
57
58But for Plone 3.0.x < 3.1 the process looks like this:
59
60    * if you are creating a new Plone site and want it to support Quintagroup Search Engine Optimization Tool, just select 2 extension profiles Local browser layer support and quintagroup.seoptimizer profile in 'Extension Profiles' when adding a new Plone site;
61    * if you want to add quintagroup.seoptimizer to already-existing Plone site, you need to apply Local browser layer support extension profile and then quintagroup.seoptimizer profile. You can do it either in  portal_setup/Import or in portal_quickinstaller by simple installation procedure.
62
63In Plone 3.1 you can simply install quintagroup.seoptimizer profile in portal_quickinstaller without need of prior installation of Local browser layer support (that is not available for installation anyway, since it is a part of core system).
64
65IMPORTANT! For Plone 3.0.x you should use plone.browserlayer 1.0.rc3. Be sure to define the right version of plone.browserlayer in your buildout.cfg. For Plone 3.1.x just use the version you have.
66
67
68Notes
69-----
70
71* For Plone 4 versions - use Plone SEO 4.0 release and up http://plone.org/products/plone-seo/releases/4.0. In your buildout.cfg file's egg section set product version::
72
73   [buildout]
74   ....
75   eggs =
76        ...
77        quintagroup.seoptimizer >=4.0
78
79* For Plone 3 versions - use the latest Plone SEO 3.x release http://plone.org/products/plone-seo/releases/3.0.5. In your buildout.cfg file's egg section set product version::
80
81   [buildout]
82   ....
83   eggs =
84        ...
85        quintagroup.seoptimizer >3.0,<4.0
86
87
88* For Plone 2.x versions - use Plone SEO 1.7.1  release http://plone.org/products/plone-seo/releases/1.7.1
89
90
91Links
92-----
93
94Watch Plone SEO screencast http://quintagroup.com/cms/screencasts/plone-seo to learn how to install and set up Plone SEO on a buildout-based Plone instance for Plone 3.2 or above.
95
96
97Authors
98-------
99
100* Myroslav Opyr
101
102* Andriy Mylenkyy
103
104* Volodymyr Cherepanyak
105
106* Vitaliy Podoba
107
108* Taras Melnychuk
109
110* Mykola Kharechko
111
112* Vitaliy Stepanov
113
114* Volodymyr Romaniuk
115
Note: See TracBrowser for help on using the repository browser.