rah_metas

Published under current TXP projects

A tiny SEO- and meta-tool for Textpattern CMS. Build descriptions, simple meta info, rel links and prevent double content.

Download rah_metas v1.1

Image: rah_metas

Image: rah_metas

Intro and description

A Textpattern plugin used for SEO. The plugin includes basic SEO tools, from semi-automatic metainformation generation to useful redirections that prevent double content as rah_metas is also able redirect requested messy urls to cleans, leaving no space for the double content fault.

List of features

Requirements

Minimum requirements:

Recommended:

Installation and usage

The general behavior stands: paste plugin code to the plugin installer textarea and run the automatic setup. Then just activate the plugin and you are ready to use new tags that plugin includes like others.

For usage, basically just put <txp:rah_metas />-tag with wanted attributes to inside your site’s <head>-tags. As the plugin’s tag outputs metainformation, and meta-tags, it shouldn’t be used outside <head>-tags.

Attributes

The tag is <txp:rah_metas /> and attributes for it follow. Default value "" means that the attribute is unset and defaultly non-used.

imagetoolbar
To block an browser’s imagetoolbar. Allowed attributes true or false.
Example: imagetoolbar="false" Default: ""

language
Language used by the site, in example: fi, en, de, se.
Example: language="en" Default: ""

robots
How should robots navigate. Valid values are index, noindex, follow, nofollow that can be compined.
Example: robots="index, follow" Default: ""

author
Author name that you wan’t to show as page’s author. Usually you, company or the website’s name.
Example: author="John Doe" Default: ""

useauthor
If selected and filled, <txp:author /> is used for the author-meta, and author-attribute will be overrided, when viewing an induvidual article.
Example: useauthor="1" Default: ""

copyright
Outputs copyright-meta. Used for the content.
Example: copyright="Copyrihts &copy; 2007 John Doe" Default: ""

Description related attributes

description
A default metadescription that will be used as description if an user is browsing an article list, or there isn’t any description to show and description_replacement is on.
Example: description="Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Fusce at dui eget est congue aliquet. Quisque sed nunc" Default: ""

description_from
Which field we use for the automatic metadescription. Available values: body, excerpt or custom field's name that is set via Textpattern’s preferences. If empty, then automatic description isn’t used – only description-attribute instead, if it’s filled and description_replament is set on.
Example: description_from="metadescription" Default: "body"

description_trail
Ending trail and marks used by the automatic metadescription.
Example: description_trail="" Default: "&hellip;"

words
Limits the amount of words that can be used in the automatic metadescription.
Example: words="15" Default: "25"

maxchars
The maximum number of characters in the generated automatic metadescription.
Example: maxchars="170" Default: "250"

prefercontent
Automatic description prefers a filled field over an empty one. If excerpt or body is used for description, and excerpt is left empty, then body is used. Instead if body is empty, then the used one is excerpt. If custom_field is used for description, and prefercontent is used, then description is tried to taken from excerpt and body untill it finds filled field. If prefercontent is empty, this option isn’t used, if filled used.
Example: prefercontent="1" Default: ""

description_replacement
If there isn’t automatic description available, use description-attribute instead, but limit it too in same way as usually.
Example: description_replacement="1" Default: ""

escape
Will escape HTML and Textile, if usign a custom field as a description. If filled, feature will be used. Default unset, not used.
Example: escape="1" Default: ""

Keyword related attributes

keywords
Default keywords that will be used as keyword meta, when an user is browsing an article list, or if there isn’t any keywords defined for article and keywords_replacement attribute is on.
Example: keywords="life, Doe, cat, dog" Default: ""

keywords_from
Which field we use for the keyword-meta. Available values: keywords or custom field's name that is set via Textpattern’s preferences. If empty, then isn’t used.
Example: keywords_from="" Default: "keywords"

keywords_replacement
If there isn’t dynamically pulled keywords available in single article, use keywords-attribute instead.
Example: keywords_replacement="1" Default: ""

keywords_limit
Limits the amount of words that can be used in the keywords.
Example: keywords_limit="5" Default: "25"

Redirect related attributes

messy_to_clean_redirect
Use messy to clean redirect. Use this only if you use clean urls. With messy urls this only causes eternal loop.
Example: messy_to_clean_redirect="1" Default: ""

redirect_code
The code of redirection, value should be three numeric stannard status code protocol.
Example: redirect_code="302" Default: "301"

Rel link related attributes

relnext
Use rel link to point next page’s location to browsers. relnext-attribute should be filled with <link rel="next" /> tag’s title attribute. Ideal values are Next, Go to next and so on. The attribute, relnext, adds a next rel link meta that points to the next section page or article by posting date. If attribute is used (filled) then used, if unset (empty) then not.
Example: relnext="Next" Default: ""

relprev
Use rel link to point previous page’s location to browsers. relprev-attribute should be filled with <link rel="prev" /> tag’s title attribute. Ideal values are Previous, Go to prev and so on. The attribute, relprev, adds a next rel link meta that points to the previous section page or article by posting date. If attribute is used (filled) then used, if unset (empty) then not.
Example: relprev="Previous" Default: ""

prev_url
Manually defines relative prev url. Value should be a URL address. The URL is only used if automatic URL isn’t found.
Example: prev_url="http://www.example.com/path/to/id" Default: ""

next_url
Manually defines relative next url. Value should be a URL address. The URL is only used if automatic URL isn’t found.
Example: prev_url="http://www.example.com/path/to/id" Default: ""

Examples

#1: Basic usage

<txp:rah_metas keywords="dog, cat, house" description="Lorem lipsum" maxchars="170" words="15" />

#2: Using content preferring. First look at custom field, then main (excerpt, body) fields.

<txp:rah_metas description_from="MyCustomFieldName" prefercontent="1" />

#3: Tags-in-tags example. Pull data from space.

<txp:rah_metas keywords='<txp:article><txp:keywords /></txp:article>' description='<txp:article_custom id="1" status="5"><txp:body /></txp:article>' />

Changelog

Main 1.0-series, “Stupido Rattle”

Version 1.1

Version 1.0.5

Version 1.0.4

Version 1.0.3

Version 1.0.2

Version 1.0.1

Version 1.0

Beta-series

Version minor 0.9.2

Version minor 0.9.1

Version 0.9

Version 0.8

Version 0.7

Version 0.6

Version 0.5

Version 0.4

Version 0.3

Version 0.2

Version 0.1

Contact

Known issues

Redirects might not always work on old fast-cgi (requires clarifation), but on other systems fine.

Thanks to