Introduction
This product adds some viewlet to improve SEO in Plone sites:
Meta tag to tell robots “noindex, follow” the batch pages
Canonical url link for all pages. We have followed these rules for canonical urls:
For normal content, the url is the object’s url without the trailing ‘/’:
yoursite.com/news/ -> yoursite.com/news
Default page (and its trailing ‘/’) is removed from the canonical url:
yoursite.com/news/aggregator -> yoursite.com/news (aggregator is the default page of news)
yoursite.com/news/aggregator/ -> yoursite.com/news (aggregator is the default page of news)
View or template name is preserved in the canonical url:
yoursite.com/@@search?SearchableText=query -> yoursite.com/@@search?SearchableText=query
yoursite.com/folder1/folder_listing -> yoursite.com/folder1/folder_listing
Customized batching template to create batching base urls based on canonical urls.
Tested with Plone 4.2.x. It should work all previous Plone 4 versions, but it’s untested.
In Plone 4.3.x the changes in batching template will not be available, because of the use of plone.batching product and this product provides replacement just for batch_macros.pt template.
Changelog
1.1 (2013-11-18)
Added <meta name=”robots” value=”noindex,follow” /> for the default pages [libargutxi]
Added zcml:condition=”not-have plone-43” for canonical viewlet [libargutxi]
1.0.3 (2012/09/10)
Batch template needs base urls without parameters [erral]
1.0.2.1 (2012/09/10)
Brown bag release: Remove debugging output from template. [erral]
1.0.2 (2012/09/10)
Fix batch url for 2nd and next pages [erral]
1.0.1 (2012/09/07)
One more check in baching [erral]
1.0 (2012/09/07)
Fix batches’ base url with canonical urls [erral]
Remove trailing / for the canonical urls, rely on the default view (template or default page) [erral]
Added <link rel=”canonical” …> tag for all pages. [erral]
Added meta noindex, follow tag for batch pages [erral]
1 maintainer
Metadata
1 maintainer
Release files for cs.seopack 1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| cs.seopack-1.1.zip | 19.6 kB | Without provenance | Details for cs.seopack-1.1.zip |
Release files / cs.seopack-1.1.zip
| Download URL | cs.seopack-1.1.zip |
|---|---|
| Size | 19.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8dbd1854580b55d6a396514415105a5aae5f09f2e9fdc8ef7cf30a506a117400
|
|
BLAKE2b-256 checksum How to use checksums |
eab286d0dd1c466af8b90bbb786f54243e9ce915b3332008b9a0aadf964781ef
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for cs.seopack 1.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
