rah_metas // plugin for automatic metainformation

Gocom · 2007-09-19 14:58:00

Updated first post and outdated links.

Cheers!

maniqui · 2007-09-25 16:29:26

Great plug-in, Gocom.
It makes some SEO tasks lot easier.

I have some comments/suggestions/“bugs”:

- the option to define a custom field as the value for plug-in attributes (particulary, for the description attribute). This will allow more customizable texts in the meta tags.
Example: <txp:rah_metas description="custom_field:metadescription" />.
The description attribute will be filled with the content of the custom field named __metadescription_.

Of course, you may find a cleverer method to do this.
If the custom field is emtpy, then it use the excerpt/body.

- what about adding the “copyright” meta? Is that one important? I don’t know.

- bug? When viewing an sticky article (that is, when you are in the permlink for an individual sticky article), the meta tags are filled with the default values, not with the ones (keywords, excerpt/body) for that sticky article.

I think that’s all!
Thanks.

Gocom · 2007-09-25 17:30:54

Thank for your post maniqui.

bug? When viewing an sticky article (that is, when you are in the permlink for an individual sticky article), the meta tags are filled with the default values, not with the ones (keywords, excerpt/body) for that sticky article.

Textpattern case. One of the bugs of the sticky articles. I could look into that, if there is way to do something to that. But it isn’t actually a bug in the plugin. If I’m correct sticky article doesn’t support if_article_list in correct way, so $is_article_list == true won’t work for it. I could fix it by article status-check.

what about adding the “copyright” meta? Is that one important? I don’t know.

Copyright-meta isn’t important, not at all. Most of the biggest search engines won’t even use it for anything. Or not anything that changes how data is indexed by search engines. So, I won’t add it. Sorry. Not required ;)

the option to define a custom field as the value for plug-in attributes (particulary, for the description attribute). This will allow more customizable texts in the meta tags.

Add to the future-ideas.

Cheers!

maniqui · 2007-09-25 17:47:10

Thanks for yout reply, Gocom.

Textpattern case. One of the bugs of the sticky articles. I could look into that, if there is way to do something to that. But it isn’t actually a bug in the plugin. If I’m correct sticky article doesn’t support if_article_list in correct way, so $is_article_list == true won’t work for it. I could fix it by article status-check.

I’m afraid I didn’t explain well. I’m not talking about when you are viewing the sticky article in an article-list context (something that is very common when you are using stickies for a one-page-section static content).
I’m talking about when you click on an sticky article permlink so you view it in its permlink url (that is, in its individual-article context).

But you’re probably right about something not working as expected in sticky articles, because I have found when you are in sticky-individual-article context, TxP article form tags don’t work in page templates. Ruud said that bug will be fixed in 4.0.6

Gocom · 2007-09-25 19:20:14

maniqui,

I understood what you were saing at the first time. I mean that the plugin only pulls a keywords and a description form a article only when viewing single article. And the case is that sticky article isn’t single article, even when you’re viewing individual sticky article.

When viewing sticky it always says $is_article_list = true. So it’s never individual/single for Textpattern.

Cheers!

Last edited by Gocom (2007-09-25 19:21:36)

maniqui · 2007-10-12 04:47:01

A “less-than-minor issue”: the meta keyword tag is outputted as <meta name="Keywords"...>.
Is there a reason for the capitalization? Don’t kill me! :D

Gocom · 2007-10-12 08:24:22

maniqui wrote:

A “less-than-minor issue”: the meta keyword tag is outputted as <meta name=“Keywords”…>.
Is there a reason for the capitalization? Don’t kill me! :D

Because I just copied outputting style from my blog. And I supose it have nothing to do how it works in terms of SEO.

PS. Argentina is too far, so I won’t kill you — or not yet, maybe in next summer :D

Cheers!

maniqui · 2007-11-02 04:30:54

Hi Jukka,

although the order of meta tags doesn’t seem to be important for SEO purposes (or for any other purpose), I’ve read several time that the <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> should be before the <title> so any non-ASCII character in the title will display correctly.

The most common order for meta tags is usually:

- meta http-equiv content charset
- title
- description
- keywords
- etc

My question is: is there anyway for rah_metas to avoid the output of the first one (meta charset)?
That’s because I will put it manually on top of the title tag, and then, after the title tag, I will output the other metatags (using rah_metas, of course).

I have tested and if charset attribute (in the plug-in tag) is left empty, the output is <meta http-equiv="content-language" content="es" />.
So I will have that meta “semi” duplicate (because http-equiv and content are in the manually added tag by me).

Of course, I could use <txp_rah_metas /> and then, at the end of its output, add the <title />, but that will put the <title> at the very bottom of the <head>.

Of course, any advice from you on topic this will be appreciated.

maniqui · 2007-11-02 04:32:33

Ah, and now, I notice another difference:

your plug-in outputs http-equiv="content-language" while I usually used http-equiv="Content-Type".

Do you know what’s the difference?

maniqui · 2007-11-02 04:34:22

Sorry, Jukka.
I’m totally messing things:

<meta http-equiv="content-language" content="es" /> is about the language, hehehe.

And, of course, leaving the rah_metas charset attribute empty, doesn’t output anything.

Perfect!

Pat64 · 2007-11-02 12:32:50

Hi Jukka.

I’m looking for a way to display all keywords from articles in an article list context. I use only 2 articles by page. It seems interesting to grab all the keywords into a page list to optimize this SEO page.

Any ideas how to make that rule?

Gocom · 2007-11-02 14:26:57

Don’t worry Julián, I won’t eat you :)

<meta http-equiv="content-language" content="es" /> is about the language, hehehe.

My question is: is there anyway for rah_metas to avoid the output of the first one (meta charset)?

Yep, it is about the language not about the charset – and yes charset is left empty if the attribute is empty.

And after all, title should be placed after every other metas, before the </head> – title is content and meta in the same time.

I’m looking for a way to display all keywords from articles in an article list context. I use only 2 articles by page. It seems interesting to grab all the keywords into a page list to optimize this SEO page.

Patrick, it could be done. But in some way it could be hard. After all what happens if the current section haven’t any articles, but it outputs content with <txp:article_custom />? Then is quite hard to output right keywords. Also TXP’s sticky-articles are quite messy and bug little in these kind of things.

But if section uses <txp:article /> and has articles posted into it, then it could be quite easy to optain, by using in-build article-function.

I could look into it, when I have some time.

Cheers!

maniqui · 2007-11-02 15:54:57

Thanks, Gocom, for your advices.

I’ve seen that rah_metas doesn’t strip out the textile mark-up, so the meta description is filled like:

<meta description="This is an article *about a great topic* and you will _love it_ and …" />

Is that intended?

Because, if I’m not wrong, that’s the way it will look on a search results page.
Would it be possible to strip Textile out? :D

Gocom · 2007-11-02 15:57:26

Yeah, I could do that :-) Wait and see.

Cheers!

Pat64 · 2007-11-02 17:03:19

I’m looking for a way to display all keywords from articles in an article list context. I use only 2 articles by page. It seems interesting to grab all the keywords into a page list to optimize this SEO page.
Patrick, it could be done. But in some way it could be hard. After all what happens if the current section haven’t any articles, but it outputs content with <txp:article_custom />? Then is quite hard to output right keywords. Also TXP’s sticky-articles are quite messy and bug little in these kind of things.
But if section uses <txp:article /> and has articles posted into it, then it could be quite easy to optain, by using in-build article-function.
I could look into it, when I have some time.

Fine, Jukka. It’ll be a very good feature.

Regards,

Textpattern CMS

Textpattern CMS support forum

#16 2007-09-19 14:58:00

Re: rah_metas // plugin for automatic metainformation

#17 2007-09-25 16:29:26

Re: rah_metas // plugin for automatic metainformation

#18 2007-09-25 17:30:54

Re: rah_metas // plugin for automatic metainformation

#19 2007-09-25 17:47:10

Re: rah_metas // plugin for automatic metainformation

#20 2007-09-25 19:20:14

Re: rah_metas // plugin for automatic metainformation

#21 2007-10-12 04:47:01

Re: rah_metas // plugin for automatic metainformation

#22 2007-10-12 08:24:22

Re: rah_metas // plugin for automatic metainformation

#23 2007-11-02 04:30:54

Re: rah_metas // plugin for automatic metainformation

#24 2007-11-02 04:32:33

Re: rah_metas // plugin for automatic metainformation

#25 2007-11-02 04:34:22

Re: rah_metas // plugin for automatic metainformation

#26 2007-11-02 12:32:50

Re: rah_metas // plugin for automatic metainformation

#27 2007-11-02 14:26:57

Re: rah_metas // plugin for automatic metainformation

#28 2007-11-02 15:54:57

Re: rah_metas // plugin for automatic metainformation

#29 2007-11-02 15:57:26

Re: rah_metas // plugin for automatic metainformation

#30 2007-11-02 17:03:19

Re: rah_metas // plugin for automatic metainformation

Board footer