AutoMeta: Automatic Meta & Technorati Tags for WordPress

This plugin will automatically generate and include HTML Meta Tags and Technorati Tags based on the full text of your post.

What’s it for?

The explosion of people with their own websites (often called ‘blogs) has gone hand in hand with the rise of automated aggregation systems, which attempt to filter out the irrelevant majority so that the end user sees more content that is useful. The digital equivalent of separating the wheat from the chaff.

Sites such as Technorati have taken this concept further by introducing the concept of tags. A tag is a word or phrase that describes what a particular web page is about. It’s essentially a proprietary version of the HTML meta tag – this plugin manages both kinds of tags for you.

Installation instructions

To use it:

  1. Download this fileDownload this file – this is the stable release, which is what most people want – if you’d like to try an advance copy of the next version then scroll down
  2. Unzip the file and copy it’s contents to your /wp-content/plugins/ directory (so that it’s path is /wp-content/plugins/autometa/).
  3. Enable it on the plugins page.
  4. Look for the AutoMeta menu which appears on the plugins page once the plugin is enabled.
  5. Click the “Add the index” button to create the necessary indexes.
  6. That’s it.

Automatic Tag Generation

This plugin will automatically generate and include HTML Meta Tags and Technorati Tags based on the full text of your post. When you save your post (and before you publish it) the plugin checks to see if any tags have been associated with it.

The Autometa custom field showing the auto-generated tags.

If no tags are found then it generates them based on the content of the post.

Hand Written Tags

Automatic extraction of words can never be perfect, so once tags are generated they can be edited and improved by hand.

If, like me, your article goes through several drafts before publication then you’ll notice that the words are generated the first time you save the document, but then they remain unchanged as the finished document evolves. The plugin will automatically regenerate the tags whenever there is no autometa custom field, so if you click on the Delete action, you’ll get a fresh set of auto-generated tags that you can refine by hand.


I don’t recommend that you use the plugin without hand-tweaking the tags; instead, think of it as a useful guide. If you wish to include tags with a space such as “world wide web” then you should insert dashes where you’d like the spaces to be, i.e. “world-wide-web”.


  1. Where can I see the tags/keywords in my output?Meta Keywords are added to the document header for each post (you won’t see them on the index page), so load one of a recent post in your browser (one that that you’ve written or saved since the plugin was installed) then view the source of the page. Near the top you’ll see a message detailing the version of autometa that’s in use, and a list of keywords. Technorati tags are either added to the footer (so scroll to the bottom) or, if you’re using a more recent release, the tags may have been included in the document body, so you’ll see them without looking at the source.
  2. The plugin is installed and appears to work, but I see just a set of empty quotes where the list of tags should be; what’s wrong?99 times out of 100 you are hitting a bug that existed for a very short time in WordPress 2.0 – it’s been solved as of WordPress 2.0.1, so the problem should disappear when you upgrade.
  3. How do I show the Technorati Tags in my sidebar/theme?If you want to add the tags to your sidebar, then that add <?php AutoMeta::includeTechnoratiTags();?> to your theme wherever you want the taglist to appear.
  4. Can I customize the output a bit?Yes, you can customize the output a lot. Use the more parameterized <?php AutoMeta::echoTechnoratiTags("headline", "tail", "line prefix","line_suffix", "no_tags_message");?>, modifying the parameters as necessary to fit your theme. For example: <?php AutoMeta::echoTechnoratiTags("<h1>Technorati</h1><ul>", "</ul>", "<li>","</li>", "Zarro Taags!");?>
  5. Do I have to have the tags on my page?No. Technorati can discover your tags from the feed (where the tags are included as categories), so (based on experience) it appears that you don’t need visible tags on your page, so just include them if you want to.
  6. I want to be as lazy as possible, can the plugin do it’s work when I publish without me having to save it?Yes, that’s the default behaviour, but there is a caveat. If you want to be lazy and just publish then that’s fine, you can, the plugin will still extract the most important words from the article and turn them into tags/keywords. The downside is that if you’ve not mentioned a term in an article then it cannot appear as a tag – so if (for example) you write an article about iPods and don’t mention Apple, then “Apple” can’t be a tag, so there’s an audience group that you’re possibly missing. This is why hand-finishing your tags is recommended.
  7. Can I create keywords/tags that are not just single words, like “mostly harmless”, “ford prefect” or “chesterfield sofa”?Yes. These can be created using either the minus or plus characters to separate the words you wish to join. The tags “ford-prefect” and “ford+prefect” both turn out as “ford prefect”. It is recommended that you use the “+” character; the “-” is a hangover from an earlier version and (if people request it) could one day be removed to allow for hyphenated tags.

Planned/Unplanned Features

I don’t have time to extend this at the moment, but I’d like to to have:

  1. default set of metadata/tags for use in non article pages
  2. a better admin interface
  3. user editable tag list length
  4. user editable the minimum word length
  5. user editable stop list
  6. thesaurus lookup, so similar words could be group scored
  7. Optional Visible/Invisible technorati tags
  8. Tag list in Admin side bar


Embrace and Extend

If anyone would like to extend it, or use the code elsewhere, it’s released under a GPL license. Derivative works must also be free and must credit this work.

Alpha/Beta Testing

A development version of the next release is sometimes available too [nothing is currently available]. If you’re familiar with PHP and comfortable with wordpress hacking, then please, be my guest and help with giving it a jolly good shake to help get all the bugs out. If you’re feeling creative, invent a feature, or try implementing one of the ones listed above. Many hands make light work!


Ideas, opinions and descriptions of problems are what can help this plugin get better – share your sparks of inspiration on the forum (or just describe the mists that are clouding your way).

446 thoughts on “AutoMeta: Automatic Meta & Technorati Tags for WordPress

  1. Meta Tags are always hidden, and Technorati Tags are just links to Technorati for the benefit of Technorati, so they still get found correctly.

    I agree though, that it would be nice if the taglist could be made visible, so I’ll add that to the list of feature requests.

  2. Good catch thanks. That’s a hangover from the fact that I’ve been using it on this site for several months, so in cases where I hadn’t set a keyword at all I still wanted some content because it was on this site. You can safely remove it for now, or download the latest release in which it is removed.

    Once there is an admin interface this’ll be something to add back in so it can be configured and used, but for now, if anyone wants to do similar, just uncomment lines 151 to 153 and change $keywords to whatever you want the default to be.

  3. ;) Since you are so friendly, I have another question. I have setup a meta name=”Keywords” already in my template. When I enable your plugin, it adds another one. The result validates as XHTML but is that an ok thing to have? Should we remove our meta name=”Keywords” from the templates when using the plugin? And is there a way to have the tags generated for old post?
    Thanks! :D

  4. As you suggest, multiple keyword meta tags validate, so it falls to the interpreter of the document (GooleBot, MSNBot, etc.) to decide how to handle them. Anything that I (or just about anyone else) can suggest to describe how multiple entries are processed would be pure speculation since only those with access to the source of the major search engines can tell you exactly how data is processed.

    So on to the bit I can answer… I have considered writing a “convert old documents” utility – it would actually be quite simple to do, but there are two hurdles. Firstly there’s no admin interface, yet, and it should really be a one-time button that exists there.

    The second (and main) reason for it not existing is that I don’t want Technorati to be suddenly deluged with machine generated tags.

    Having the machine generate tags, and then hand-finishing them is okay, but if the tags are just machine generated then that could reduce the overall effectiveness of Technorati to being no better than Google BlogSearch (i.e. a machine driven search engine). The unique selling point of Technorati is the human authored semantic markup – this plugin assists that, but doesn’t seek to replace it.

    Having said that, you can add tags to old posts – just edit, and save the post, and the autometa plugin will spot that there are no tags, and add them for you, leaving you free to improve them by hand.

  5. Hi Jakob, there’s a signature in the plugin (which says the name and version of the plugin) that gets printed to every page to assist with remote debugging such as this. That signature is missing, so my guess is that you’ve maybe installed the plugin, but not enabled it.

  6. I seem to be having the same problem Jakob has (or at least, similar symptoms)… autometa doesn’t seem to want to do its thing for me. It’s definitely enabled, as an autometa custom field is being generated on my write post page, but it’s empty. When using v 0.2, it did put “boakes” in, but that was it. Posts for which I have attempted to auto-generate keywords just have <meta name=”keywords” content=”” /> in their head

  7. Looking at the source of slakethirst I can see the Autometa signature, but it’s not there on Jakob’s site, so they’re two separate issues I think.

    C, your problem may just be that the autometa tag was generated before you added your text, if that’s not the case (RSVP!) then I have an idea of what the problem might be so a fix won’t take long.

  8. C, your problem may just be that the autometa tag was generated before you added your text, if that’s not the case (RSVP!) then I have an idea of what the problem might be so a fix won’t take long.

    Hey, Rich. I don’t believe that’s the case… I’ve tried deleting the custom field and re-saving the post(s) countless times, but nothing happens other than that a new, empty autometa field is created. Looking forward to hearing your ideas/fixes.

  9. It’s time to break out the theory of what might be missing, and my guess is that it’s the full text index.

    My first suggestion is that this SQL will fix the problem:

    ALTER TABLE wp_posts ADD FULLTEXT post_related ( post_name , post_content )

    I’ll wrap this into the next version, but if it can be proven that it fixes the problem before that release then so much the better.

  10. Hiya Rich,

    I’m having the same exact problem as C, except I’m a little wary on how to fix this SQL thing. How do I execute that code? :P I’m not very good with this back end kinda stuff, I’m more of a make-things-pretty designer girl.

  11. Hi Lara, if you’re not comfy with technical gubbins, then hold fast until the next release which will include the code so you don’t have to do anything.

  12. Thanks for the feedback everyone. I’ve created a 0.4 release (though I’ve not linked to it as the the main downloadable yet).

    This version which includes an admin page under the Plug-ins tab. Once you install and activate this version, go to the admin page and click on the “Add the index” button. If all goes well it will tell you that the update was successful, and hanceforth automatic keyword suggestions should be generated.

    It appears to work on my test blog but if someone who’s experienced the problem could have a go with it and confirm if this solves things for them, then that would be great. If/when I get confirmation of it working then I’ll link to it from the article.

  13. Using 0.4 on 2.0 RC1 I get the following error:

    Warning: Invalid argument supplied for foreach() in /home/rouge8c/public_html/politics/wp-content/plugins/autometa/autometa.php on line 170

    I have the same error on all of my blogs.

  14. I must be missing something. I’ve created a new post, saved it, and then published it. However, the following is all that I’m seeing when I vew the source:

    I’ve also tried editing and saving existing posts with the same result.

  15. After a little head scratching, hopefully 0.4a will solve any remaining problems for WordPress 1.5.

    Download version 0.4a.

    Andy, I’m asking around for WordPress 2.0 information because I can see there is a change in the post_meta_data method which appears to be causing your problem.

  16. TwisterMc, great to hear thanks.

    I’ve just released 0.4b which fixes a (stoopid) typo’ in 0.4a). I’ve tested 0.4b successfully on a vanilla blog so the people that have had problems should be able to use the plugin successfully now – fingers crossed & let me know if there are still any problems!

    Download version 0.4a.

  17. Having said that, you can add tags to old posts – just edit, and save the post, and the autometa plugin will spot that there are no tags, and add them for you, leaving you free to improve them by hand.

    I do this, but when I view the source on my post the meta tag is nowhere to be seen.

    What would be the best way to go back through 150 posts and add the tags?

  18. Hi Ryan, looking at the site I can see the meta tag constuct correctly on every article, so it’s definitely installed and working. Also, I can see two of the articles have tag content, which looks like it’s generated by the plugin. So can you clarify what “nowhere to be seen” means (i.e. do you mean that the meta keyword tag “content” field is empty)?

    As for going through “previous” posts, if anyone would like to submit a patch for a convenience interface then that would be useful. In the mean time I recommend using a tabbed browser such as Firefox – once you’re in the “Manage | Posts” section you can use the middle mouse button to edit multiple posts at once. This can significantly speed the process of tagging your existing articles.

  19. Thanks for the prompt reply. Sorry, I managed to fix what I did shortly after posting that. It looks to be working now. I went through a few old posts but find it to be pretty daunting task. I’m content just having different meta tags to make sure google doesn’t think I have dup content. How does the Technorati part of this work exactly?

  20. So, I’ve installed the plugin and enabled it, and a first glance it seemed to work correctly, except now that I’m looking at it, I’m seeing really weird things. There’s only output from the plugin in two places:

    1)The meta keywords for the first post on the index page show up before the first post, as I would expect, but they only show up for that post, no subsequent posts show any autometa output for the meta keywords.

    2)The technorati tags for the last post on the index page show up after the last post, at the very end of the code, but they only show up for that post, no subsequent posts show any autometa output for the technorati tags.

    I use a modified index.php for the default them so that I can have a collapsible comments section on the post on the index page, so that might be causing the problems, or I could just be misunderstanding how it is intended to work. Should all of the posts displayed on the index have both keywords and technorati tages?

  21. The good news- installed it and it worked quite nicely. Easy install, simple use, I like it.

    The bad news- Since the Jagger update hidden text using css is a huge no-no, and when I looked in source and saw how that was handled . . . ooh no. Deactivated.

    Any way you can get rid of that? Any way we can put the tech tags in the template where we want them AND visible? Oh, and why just a keyword meta, where’s the description meta?

  22. I was working fine with WP 2.0 RC2, until I installed the 12/14 nightly build. Now I’m getting the “Warning: Invalid argument supplied for foreach() in MyURL/wp-content/plugins/autometa.php on line 169”.

    I tried using 0.4b, no luck, and no tags. Any help would be appreciated.

    And Kickass, you might want to try something like Ultimate Tag Warrior if you want your tags to display. Me, I didn’t want to clutter my posts up with a geeky tag cloud or a line of tags (but wanted Technorati to have something to eat), so I loved the fact that Autometa did invisible tags, and really didn’t care if Google lowered my PR, since it was non-existant anyway. ;)

  23. David, the plugin is behaving as I’d expect it to, you’ve identified something that needs improving. The way I use WP is that the index page is JUST an index, and you have to click on the story to read it. Other people use the index page to display several stories. The plugin was designed for the second kind of usage.

    Kickass, the technorati tags are not intended for Google, they are intended for Technorati, that’s why they’re hidden. A future version could include a set of tick boxes in the admin page which woudl add technorati tags to the sidebar or add a function that woudl output them on demand. I’m too short on time to do this right now, but patches are always gratefully received.

    Croak, there’s no reason for Google to lower your PR because you have hidden links. What they almost certainly will do is not increase the rating of the page you’re linking to.

  24. Rich,

    Any idea what changed in WP’s 2.0 RC2 nightly build that’s causing my error listed above?

    “Warning: Invalid argument supplied for foreach() in MyURL/wp-content/plugins/autometa.php on line 169″.

  25. I’ve not installed it on a 2.0 version yet. Once I do I’ll know the answer to any 2.0 issues. In the mean time if anyone has success or works out any necessary tweaks, please feel free to paste a patch here and I’ll incorporate it.

  26. So perhaps I’m misundeerstanding, but you state:

    “The way I use WP is that the index page is JUST an index, and you have to click on the story to read it. Other people use the index page to display several stories. The plugin was designed for the second kind of usage.”

    So, the plugin was designed for the people who use the index page to display several stories? If that’s the case, it doesn’t seem to be working as it should, as it only adds meta keywords for the first story, and technorati tags for the last story, and nothing in between. If it were designed to work on index pages that display a few stories, I would expect the meta keywords and technorati tags to be inserted for every story displayed on the index page.

    Did you mean that it was intended to function with blogs that use the index page as you do, only as an index and not to display stories? If it was only intended to work on individual post pages, it’s behaving as I would expect it to. (Though Technorati still isn’t indexing my site according to those tags… I’m still trying to figure that out…)

  27. Forgive me, but I’m a novice — and I don’t get it. I have added the Autometa plugin to my blog. It appears as a custom field on my “Write Post” screen. So I have it — and I guess it is working. However:

    (1) Is it completely automatic on every post? Will Autometa do its thing — without me asking it to do something on each post?

    (2) When I first start writing a new post, the Autometa field is NOT opened up on the screen. However, after my first save, it appears. So that tells me it is working. However, there are no keywords in the “values” box. Shouldn’t there be? Isn’t that the idea — that it creates them automatically?

    (3) I don’t understand what this paragraph of yours means:

    “If, like me, your article goes through several drafts
    before publication then you’ll notice that the words are
    generated the first time you save the document, but then
    they remain unchanged as the finished document evolves.
    The plugin will automatically regenerate the tags whenever
    there is no autometa custom field, so if you click on the
    Delete action, you’ll get a fresh set of auto-generated
    tags that you can refine by hand.’

    No, I DON’T have any words, even after the first save. But does this say what it sounds like it says — that after the first sve, no new keywords are added automatically. In other words, is the best way to make Autometa work to add keywords into the “Values” box manually?

    And I sure don’t understand what you mean about hitting the delete button. When I do that, I do NOT get a fresh set of keywords — I’m still getting no keywords at all. So far, the only way I have gotten any keywords into that Values box is to add them myself.

    What am I not getting? Thanks very much for your help.

    Terry Hull

  28. Warning: Invalid argument supplied for foreach() in /homepages/16/d141775704/htdocs/warbly/wp-content/plugins/autometa.php on line 169

    getting this error since WP 2.0 upgrade.
    any ideas how to get it working again?

  29. Since I updated to WordPress 2.0, whenever the Autometa plugin is activated this line appears at the top of my site’s index page:

    “Warning: Invalid argument supplied for foreach() in /hsphere/local/home/shortstu/ on line 169”

    I tried uninstalling and reinstalling the Autometa plugin, however this line continues to appear at the top of the page whenever the plugin is enabled. I’m using the newest version (0.4b).

    Could someone help me get this fixed?

  30. I’m flying bling here (because I’m not on 2.0 yet) so this will be a stepwise process. I think the “Invalid argument” errors are caused by the get_post_meta method which no longer returns an empty array. I’ve added two fixes for this at lines 145 and 169, and assembled a 0.5a release. If it fixes the problem please let me know, and likewise, if it doesn’t, or if there are other errors once this one is hurdled, leave me the details and I’ll see what I can come up with (feel free to submit your own patches too if you find solutions).

    The official release is still 0.4b until I know this one works. Download 0.5a here.

  31. 0.5a cured the error display, but the keywords aren’t making it into the page source. All looks well on the admin side, keywords show in auto meta field, but not in page source on display page.

    Bless you and your children and your children’s children.
    Great plugin.

  32. Sorry my English.
    Warning: Invalid argument supplied for foreach() in /home/goofree/public_html/wp-content/plugins/autometa.php on line


  33. Hi Rich

    Loving your plugin… but can’t get it to work yet.

    Got the “invalid argument for foreach..” problem on the 04.b on the wp2.0.

    Problem disapeared again after installing 0.5a, but after editing a post I didn’t get any meta.

    I hope you decide to upgrade your wp to 2.0… then I bet we would get a solution that works pretty soon ;-)

    Crossing my fingers here..


  34. I ma getting the following error, quite suddenly I might add. It was working then this:

    Warning: Invalid argument supplied for foreach() in /home/particle/public_html/wp-content/plugins/autometa.php on line 169

    I am running WordPress 2.0 :(

    Any ideas?

  35. The Good News: I’ve now upgraded to WordPress 2.0 and I’m happy to report that AutoMeta version 0.5a is working perfectly with it!

    The Bad News: WordPress 2.0 has a bug which is what’s been affecting everyone :(

    The Fix: If you can’t wait for 2.0.1, the fix is VERY simple – you just need to remove “[0]” from line 475 of wp-includes/functions.php.

  36. Hi Rich

    You are amazing – one little [0] gone and everything seems to work. At least I’m getting some keywords now.

    One problem though:
    (We are on WP2.0 with autometa version 0.5a and removed [0] from line 475 in wp-incudes/functions.php)

    I only get 7 (seven) keywords out of a lengthy article that ought to provide me with a lot more keywords.

    I changed the autometa.php in the plugin editor like this:



    end edited 5 (five) posts.

    Still just 7 keywords…

    What seems to be the problem?

    I have analyzed each article and have more than one keyword in each article that is used more than the 7 (seven) but still they don’t get counted.

    It’s like the plugin only reads to a certain length…

  37. Hi Coffee – that’s an “easy” one to answer. The threshold is a score threshold, not a number of words to match. All words that score above the threshold value value will be returned. If there are n words that score above the threshold, then the highest of these are skimmed off the top and returned (using $autometa_maxWords).

    So, if you want 7 words, try:

    At least; that’s how it should work; so let me know if it doesn’t!

  38. Hi Rich
    Your prompt assistance is truly appriciated.
    I have been fidling with autometa 0.5a now, and it appears to do what I want it to.
    One detail keeps bugging me though: My blog is about coffee, I use the word a lot (usually no. one or two highest word count – common words aside), and yet the word coffee never made it to the autometa keyword section. Is that the way it is supposed to work?
    (my website is

  39. Nice plugin, rich!

    I hacked the code such that the hidden div is visible instead of hidden. This way I can see the “links”, edit them if necessary while my readers get to click on them to find related blogs by searching in Technorati.

    But as of version 0.5a, the plugin inserts the div even when the page in concern has no autometa. Would you consider changing the codes such that if there’s no autometa the plugin doesn’t insert the div at all please? Thanks.

    (off topic) Btw the “bookmark on” link doesn’t work. I believe the correct format should be “…”

  40. Ah, excellent. It’s working a treat now that I’ve edited functions.php. Thanks!

    One niggling detail: Technorati seems to prefer that links for multi-word tags use a + instead of %20 between words — at least, when one searches for a multi-word tag that isn’t found, the suggested format for the tag’s link is: <a href=”” rel=”tag”>tag with spaces</a>. It doesn’t really seem to matter — %2B, + and %20 appear to be parsed the same by technorati — but it might be nice if Autometa treated a + the same as a – when generating keywords.

  41. I would suggest that the plugin can also allow us to enter “description” for the meta tag. For the time being, we can only add “keywords”. How about “description”? It would benefit publisher if each post have their own description as well.

    Btw, thanks 4 d plugin.

  42. This is the Empty Word List for french :

    $autometa_common = array( “à“,”allô”,”aucuns”,”auriez”,”auxdits”,”aviez”,”ayons”,”bof”,”çà“,”certaines”,”chez”,”comment”,”da”,”desquels”,”deviez”,”devras”,”doit”,”dues”,”dût”,”es”,”êtes”,”eurêka”,”excepté”,”fouchtra”,”fûmes”,”ho”,”hurrah”,”laquelle”,”leur”,”mazette”,”mâtin”,”ne”,”nulle”,”or”,”outre”,”pas”,”plein”,”pourraient”,”pourvu”,”pouviez”,”puis”,”pussent”,”que”,”quoi”,”saperlipopette”,”serait”,”sien”,”sommes”,”ta”,”telles”,”touchant”,”une”,”veuillez”,”voilà“,”voudrez”,”voulante”,”voulue”,”vôtre”,”afin”,”alors”,”auquel”,”aurions”,”auxquelles”,”avions”,”aïe”,”boum”,”car”,”certains”,”chic”,”concernant”,”dans”,”devaient”,”devions”,”devrez”,”doive”,”duquel”,”eh”,”et”,”étiez”,”eus”,”eûmes”,”furent”,”fût”,”holà“,”hé”,”le”,”leurs”,”me”,”miséricorde”,”ni”,”nulles”,”ôté”,”palsambleu”,”patatras”,”plouf”,”pourrais”,”pouvaient”,”pouvions”,”puisque”,”put”,”quel”,”quoique”,”sapristi”,”seras”,”sienne”,”son”,”tandis”,”tels”,”tous”,”unième”,”veuillons”,”vos”,”voudriez”,”voulantes”,”voulues”,”vôtres”,”ah”,”apr.”,”aura”,”aurons”,”auxquels”,”avoir”,”bah”,”bravissimo”,”ce”,”ces”,”chiche”,”contre”,”de”,”devais”,”devoir”,”devriez”,”doivent”,”durant”,”elle”,”étaient”,”étions”,”eusse”,”eût”,”fus”,”fûtes”,”hop”,”il”,”ledit”,”lorsque”,”merci”,”moi”,”nonobstant”,”nuls”,”ou”,”pan”,”pechère”,”plus”,”pourrait”,”pouvais”,”pouvoir”,”puisse”,”pécaïre”,”quelle”,”rataplan”,”sauf”,”serez”,”siennes”,”sont”,”tant”,”tes”,”tout”,”unièmes”,”veulent”,”votre”,”voudrions”,”voulants”,”voulurent”,”zut”,”ai”,”as”,”aurai”,”auront”,”avaient”,”avons”,”basta”,”bravo”,”ceci”,”cet”,”chouette”,”corbleu”,”debout”,”devait”,”devons”,”devrions”,”doives”,”durent”,”elles”,”étais”,”être”,”eussent”,”eûtes”,”fusse”,”grâce”,”hormis”,”ils”,”lequel”,”lui”,”merde”,”moins”,”nos”,”ô”,”où”,”par”,”pendant”,”plusieurs”,”pourras”,”pouvait”,”pouvons”,”puissent”,”pût”,”quelles”,”revoici”,”se”,”seriez”,”siens”,”sous”,”taratata”,”tien”,”toute”,”v’lan”,”veut”,”voudra”,”voudrons”,”voulez”,”voulus”,”aie”,”attendu”,”auraient”,”autant”,”avais”,”ayant”,”beaucoup”,”ç’a”,”cela”,”cette”,”chut”,”coucou”,”depuis”,”devant”,”devra”,”devrons”,”donc”,”dus”,”en”,”était”,”eu”,”eusses”,”évohé”,”fussent”,”ha”,”hors”,”jarnicoton”,”les”,”là“,”mes”,”mon”,”notre”,”oh”,”ouais”,”parbleu”,”peu”,”pouah”,”pourrez”,”pouvant”,”psitt”,”puisses”,”qq.”,”quelqu’un”,”revoilà“,”selon”,”serions”,”sinon”,”soyez”,”tayaut”,”tienne”,”toutes”,”va”,”veux”,”voudrai”,”voudront”,”vouliez”,”voulussent”,”aient”,”au”,”aurais”,”autre”,”avait”,”ayante”,”bernique”,”ç’aura”,”celle”,”ceux”,”ciao”,”couic”,”des”,”devante”,”devrai”,”devront”,”dont”,”dussent”,”encontre”,”étant”,”eue”,”eussiez”,”évoé”,”fusses”,”hein”,”hou”,”je”,”lesdites”,”ma”,”mien”,”morbleu”,”nôtre”,”ohé”,”ouf”,”parce”,”peuchère”,”pour”,”pourriez”,”pouvante”,”pst”,”puissiez”,”qqch.”,”quelqu’une”,”rien”,”sera”,”serons”,”soi”,”soyons”,”taïaut”,”tiennes”,”tu”,”vers”,”via”,”voudraient”,”voulaient”,”voulions”,”voulut”,”aies”,”aucun”,”aurait”,”autres”,”avant”,”ayantes”,”bien”,”ç’aurait”,”celles”,”chacun”,”clic”,”crac”,”desdites”,”devantes”,”devraient”,”dia”,”du”,”dut”,”endéans”,”étante”,”eues”,”eussions”,”fi”,”fussiez”,”hem”,”hourra”,”jusque”,”lesdits”,”made”,”mienne”,”motus”,”nôtres”,”olé”,”ouille”,”pardi”,”peut”,”pourquoi”,”pourrions”,”pouvantes”,”pu”,”puissions”,”qqn”,”quels”,”sa”,”serai”,”seront”,”soient”,”stop”,”te”,”tiens”,”tudieu”,”veuille”,”vivement”,”voudrais”,”voulais”,”vouloir”,”voulût”,”ait”,”aucune”,”auras”,”aux”,”avec”,”ayants”,”bigre”,”ç’avait”,”celui”,”chacune”,”clac”,”cric”,”desdits”,”devants”,”devrais”,”diantre”,”dudit”,”dès”,”entre”,”étantes”,”euh”,”eut”,”fichtre”,”fussions”,”hep”,”hue”,”la”,”lesquelles”,”mais”,”miennes”,”moyennant”,”nous”,”on”,”oust”,”pardieu”,”peuvent”,”pourra”,”pourrons”,”pouvants”,”pue”,”purent”,”quand”,”qui”,”sacristi”,”seraient”,”ses”,”sois”,”suis”,”tel”,”toi”,”turlututu”,”veuillent”,”vlan”,”voudrait”,”voulait”,”voulons”,”vous”,”al.”,”aucunes”,”aurez”,”auxdites”,”avez”,”ayez”,”bis”,”ça”,”cependant”,”chaque”,”comme”,”crénom”,”desquelles”,”devez”,”devrait”,”dois”,”due”,”dû”,”envers”,”étants”,”eurent”,”eux”,”fors”,”fut”,”heu”,”hum”,”ladite”,”lesquels”,”malgré”,”miens”,”na”,”nul”,”ont”,”ouste”,”parmi”,”peux”,”pourrai”,”pourront”,”pouvez”,”pues”,”pus”,”quant”,”quiconque”,”sans”,”serais”,”si”,”soit”,”sur”,”telle”,”ton”,”un”,”veuilles”,”voici”,”voudras”,”voulant”,”voulu”,”vu”);

  43. Hi,

    I’ve installed the plugin and for some reason the keywords are not showing up in the area where they should. I don’t know what I’m doing wrong. Can anyone help me?

  44. So, I’m having the most bizarre problem: The autometa plugin is placing the tags in the posts just fine, but Technorati isn’t indexing the tags for some reason. I’ve searched and not found anything, I’ve also submitted multiple trouble tickets with Technorati and no response, so I’m hoping someone can shed some light on things here. I use the default theme, completely unmodified minus the plugins I’m using. Pages validate as XHTML 1.0 transitional, and if I manually enter tag links in the body of my posts, they seem to get indexed by Technorati. However, there are two things I’m doing differently than the plugin, as far as I can tell, when I put the links in the body of the post: 1)I’m not using CSS to style them as hidden, and 2)I’m putting them in the body of the post, whereas the plugin puts them after the body of the post. I’m not sure if either of these things may be causing my problem, but I’m completely stumped. Can anyone suggest anything I need to look at, or read that might help me get this working? In case you’re not pulling it from above, the site is for anyone nice enough to look it up for me.

    Thanks in advance!

  45. Hi,
    Autometa doesnt work on my WordPress 2.0 installation.
    I activate the plugin and after saving post changes I see this a list of errors like this:

    WordPress database error: [Can’t find FULLTEXT index matching the column list]
    SELECT MATCH(post_content, post_title) against (‘este’) as score FROM wp_posts where id=41;

    any help?

  46. smdani: the 1st thing to check is that autometa has been configured properly. if you go into the wordpress admin screen and open the AutoMeta tab (which is under the Plugins tab) does it tell you that AutoMeta is “ready for use”?

  47. Where are the meta tags being written. I see it on the “write” page of wordpress and it is populated with fields but I do not see it when I look at the source code for the post after publishing. I have already created the index as well from wordpress.

    any ideas?

  48. Pingback: . » Updates
  49. Hmm… it seems that with the new version of Autometa combined with WordPress 2.0.1, there are NO keywords in the source code of ANY of my posts, just two quotation marks side by side.

  50. Well, I somehow managed to get autometa to start making tags, but now I have a new problem – the same problem the people above have been talking about. Autometa makes the tags fine and my entries get posted, but each time I make a post I’m brought to a screen that says this:

    “Warning: uasort(): Invalid comparison function. in /hsphere/local/home/shortstu/ on line 73

    Warning: Cannot modify header information – headers already sent by (output started at /hsphere/local/home/shortstu/ in /hsphere/local/home/shortstu/ on line 59”

  51. 2.0.1 failure duplicated here too.
    Still looking at it.
    The custom field does get added to the page.
    And the admin page is there. I did have to add the full index.
    When I do save and edit on an old post, the field is added, but the metadata is not updated.
    If I manually update the field, the keywords are inserted.
    So, it is definatly the generation that is broken.
    I’ll see later what more I can find out….

  52. Whats odd is that the plugin works fine if I’m posting via the write interface in the admin panel, but if I post via an XMLRPC client, it doesnt update the tags and also produces an error to the client. But the post still gets posted.. its strange.

  53. Hello, I have never used your plugin and it seems to be very powerfull and helpfull. I would like to test it. Unfortunately, I got a similar already described by Jonquil. The same error message and keywords added to my post (very strange). Any news about this potential bug.

    My provider is “providing” WP 2.0.1, PHP 4.3.10, MySQL 4.1.15 under Linux.

    Thx by advance for your answer.

  54. I’m a smidge confused. (yes, a “smidge” – live with it. :p ) I do get automatically generated keywords (awesome, by the way!) but I don’t get the keywords showing up in the keyword meta tag in the html once all has been saved. Should I be adding some code to the “Single Post” (single.php) template? Or am I just not understanding how this thing works? I am assuming that it is supposed to add meta keywords into the html, right?

    Thanks for the great plugin!!

  55. On WP 2.0, Autometa plugin seems to create custom headers okay, but also produces the following error each time it does so:

    “…uasort(): Invalid comparison function…”

    This error seems to occur with every single post view.
    I hope you find the time to look into this.

    Otherwise thank you for a great plugin.

  56. I am getting this error
    Warning: uasort(): Invalid comparison function. in …./wp-content/plugins/autometa.php on line 73

    Warning: Cannot modify header information – headers already sent by (output started at …./wp-content/plugins/autometa.php:73) in …./wp-admin/post.php on line 59

  57. I’m having the same problem, running WP 1.52, where the plugin installed fine, I have the fulltext index installed and it’s reporting it’s installed fine.

    The keyword tags are showing in the post, but no actual keywords are showing up in each individual post. Each post has keywords when I go to edit it, so they are there. They’re just not being displayed when the page is rendered.

    Running the latest version of the plugin as well.

  58. Hi Rich,
    I just installed the autometa for my website. Everytime I initially save a post I get a number of error messages:
    Warning: uasort(): Invalid comparison function. in /homepages/45/d153500400/htdocs/Blog/wp-content/plugins/autometa/autometa.php on line 73

    Warning: Cannot modify header information – headers already sent by (output started at /homepages/45/d153500400/htdocs/Blog/wp-content/plugins/autometa/autometa.php:73) in /homepages/45/d153500400/htdocs/Blog/wp-admin/post.php on line 59

    when I hit the “back” button and try again, there seems to be no problem.

    I am fairly new to all of this so I was hoping you could tell me what the problem might be and how I might fix it.


  59. Anyone who’s seeing the “uasort bug” – I think i’ve fixed it. If you donwload the current version (0.5b) it should solve the problem.

  60. Thanks for the update FreakingGenius; glad it’s fixed the problem. If anyone with the uasort problem can confirm if it’s fixed that would be very helpful too.

  61. Dear Rich,

    I am running v0.5b in wordpess 2.0 and have added tags to an existing post and resaved the post but they don’t show up in the post. Viewing the page source for the Meta Tags shows no keywords:

    I made a test post, saved it to generate tags and then published it but I see the same thign as aboe … no keywords anywhere in the page source.

    I hope this information is helpful.



  62. Thanks for the update James – I can indeed see some output in your blog, suggesting that the plugin is installed OK, so there’s some kind of operational issue here that we need to get to the bottom of. Before I start coming up with less likely possibilities, the first thing to check is that the Plugins>AutoMeta page shows that the plugin is correctly configured and ready to go.

  63. Dear Rich,

    I had the famous “uasort” problem. In last version 0.5b, the bug is fixed. Thank you very much!

    It is the first time I am using your plugin and I am really impressed. Very good job!

    Thanks to share with us your work.


  64. hum..
    I’ve read the post but oddly enought I have another blog v2.0.1 and the Autometa fields don’t even show up when I’m editing a post. This problem is even worse. No one else is having this problem with version 2.0.1?

  65. oops neverming, that was me panicking… it works great with version 2.0.1 I guess I’ll have to upgrade my other blog.

    Thank you, this plug in is great.

  66. Thanks for the swift update! (0.5b / ‘uasort’ fix) — I am running it now and checking for errors. From what I’ve read, it sounds like a done deal. Thanks again for a great plugin!

  67. Looking through these comments, I was beginning to wonder if I was the only person having the “headers already sent” issue under 2.0.1 (and therefore wondering if I had a horked WP installation)….however I’m apparently not alone. You might want to see this post over on the WP support site for an additional description of the problem.

    In my case — any post that I make under WP2.0.1 which contains quotes generates a set of errors. E.g.,

    WordPress database error: [You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ”today’) as score FROM wp_posts where id=493′ at line 1]
    SELECT MATCH(post_content, post_title) against (‘today’) as score FROM wp_posts where id=493;

    Warning: Cannot modify header information – headers already sent by (output started at [blah]/wp-includes/wp-db.php:102) in [blah]/wp-admin/post.php on line 59

  68. I’ve just uploaded AutoMeta version 0.6, which sports a number of changes. First and foremost is a bugfix for the problem Mike just described.

    To upgrade, delete your old autometa.php file and upload the new autometa directory to your plugins folder.

    If you want it to “just work” then so long as the new plugin is enabled then that’s exactly what it should do.

    The other changes in this release are the inclusion of the French stop-word set in the distribution (though you still have to manually configure which language to use; suggestions on how to code this so it’s automatic would be appreciated).

    I’ve also had requests to make the Technorati Tags visible, and I’ve made a first pass at the necessary internal changes that make this possible. You can now opt to switch off the automatic insertion of hidden technorati tags, and directly call the method from within your theme as follows: <?php technorati_tag(false, ", "); ?> this should include a non-hidden, comma separated, list of tags wherever it’s used.

    Feedback in the little box below would be appreciated as always!

  69. Hello again, I posted back on page 9 of your comments about this problem I’m having. I’m have actual code to add to this:

    As you can see, no keyword meta data is being added at all. Am I just missing a step in the installation process? Do I need to add anything to the code? It seems not seeing as the code already has a section labeled “AutoMeta Plugin.” I have confirmed that in the posts I am checking this with, I do have autometa data added to them.

    Am I missing something? :/ Thanks.

  70. Hi Ryan, the code you typed got stripped by the parser so I can’t see it. Anyhow, you shouldn’t have to do anything after you install the plugin and generate the index. You said previously that you do see automatically generated keywords, but they don’t end up in the page, is that correct? Can you give me an example of the keywords that were generated, but are not displayed, for your story about the revolution controller pics?

  71. Sure! Thanks for taking the time to help. I LOVE the idea of what this plug-in does. I got your SmileTag message, btw, the next day – lol. Sorry about that.

    Assuming you’re looking for the meta data for the ‘Revolution Images Leaked’ post:

    The keywords “generated” during the writing of the post are: “images nintendo history fake book concepts authentic” I changed them up a bit to be the list I just posted, then clicked Update. Then I just clicked the “Save” button again to save the post. Assuming that is correct.

    I’ll try to post the meta data again without HTML formatting… so use your imagination, lol:

    !– AutoMeta Plugin for WordPress —
    meta name=”keywords” content=”” /

    That should be clear enough, assuming it does not get stripped again. This was pulled from the individual post page in the code AFTER updating the post. Does this help? If it does not come through, feel free to e-mail me using this comment’s address.

    Really – thanks again.

  72. Arg!! I’m sorry to have waisted your time. I wans’t even aware of that bug. I heard others talking about something, but didn’t research it. You’re da man. Thanks again!

  73. Hi again, I have to say that now that I’ve updated wordpress and I also updated you plugin too, it now works ok.

    But there’s something I need to ask, now I get these technorati tags just before the closing of the body, how can I use then else where without using absolute positioning?

    They look pretty strange where they are at and I would like to do more than just hidde them.

  74. Hi Rui, making the tags visible is something that’s coming in a later release. I’ve received a few suggestions and patches lately so when I get time I’ll be putting out a new version.

  75. Right now it seems that each word is a seperate “key word” unto itself. Is there a way to make to where you can have phrases?

  76. It is a great plugin. I have a lot of information on my homepage, and often autometa wouldn’t give me keywords I like to have. Is it possible to have keywords generated by autometa for posts, but have manual meta tags for homepage. Thanks.

  77. I’m growing more and mor fond of a “default” set of metadata, so I’ll look into the nicest way of adding tha for the next release.

  78. Hello,
    i have insert your plugin. it is not display the metas and the links in the footer.
    can you help me?
    I have install the and configured script .
    Thx Mike

  79. Hi Mike, you’ve got two initial problems that are stopping me from helping you. Firstly, you’ve altered the wordpress headers so that they don’t show the version you’re using. I need to know this. Secondly, you appear to have altered the code of the plugin so that it doesn’t print it’s version signature along with the metadata. Again, this is something I need to know, since you’re asking me to advise you on debiugging a system to which I have no access. I can see a referrer from your wp-admin pages in my logs, so I know you’ve got somehting of mine installed, but I have no visibility of what it is.

    P.S. Since your domain contains what I shall call “fruity content”, I’ve taken the liberty of not republishing the URL due to the diverse readership of this site.

  80. Hi there, have I missed somethign here, but none of my tags are visible on my posts (I have uploaded the latest version) and does the post have to be saved BEFORE publishing?
    Cheers for your help!

  81. Hi Paul, you don’t have to save before publishing, but if you don’t you’re not going to have the opportunity to hand finish the tags – the result will be totally automatic tags, which are never optimal. It’s not possible to generate the tags without saving (yet) because AutoMeta gets it’s words from the full text index… which is only generated on save.

    Also, I notice from looking at your blog that you’re using on WordPress 2.0, so you’ll be affected by the “[0]” bug, so if things aren’t happening as you’d expect, then that’s the prime suspect.

  82. Maybe I am just way too confused, but for some reason I was expecting to see a meta tag for keywords in my source code, but I see nothing.
    I do see the tags being generated on the “write post” page, but how do I verify that it is actually in the source code being spidered by the search engines?

    I have read through almost all of these post and am starting to get a little discouraged. Please help me understand how this works and where I can see the meta tags it generates.

    Thanks in advance.

  83. Hi Clifton, I’ve just looked at the source on your page and you’re using wordpress 2.0 and not 2.0.1, this measn you’re going to be haviong the same “[0] bug” problem as paul above. Upgrade wordpress to 2.0.1 and the lack of tags you’re seeing should turn into a plethora when the article is saved.

  84. Hi Will, good-ish news. The index page issue you describe has been solved in the next release (thanks to one of Manuel Amador’s suggestions and code patches) so if you’re really keen to have a fix, you might like to try the alpha version which is linked in the article above. Alternatively, if you can wait a few weeks, that code will improve, stabilize and be “officially” released.

  85. Hi,

    I am using v0.5b with WordPress 2.0. I have applied the [0] fix and by viewing the page source on any of my site pages I see that Meta tags and Technorati tags are now added to all my old posts as well as new posts as I publish them.

    However, I am unable to locate any of my posts via a tag search on the Autometa keywords in Technorati despite having waited 3 week or so. I can locate posts in technorati via the category tags. I have contacted technorati twice but have heard no reply. It is a little bit frustrating since my main reason for installing the plugin was for Technorati.

    Can anyone who has faced this problem before give me any advice?


  86. Hello,

    Technorati just got back to me and said that my tags are on the main page of the blog rather than in the body of the posts.

    I looked and their statement is partially true; it turns out that the tags for the most recent post are present on the main page (is this a bug?), however the tags are also present and correct for each post.

    I have sent them an email to ask if tags appearing on the main page of the blog where recent posts are listed is a problem.


  87. Hi James, very useful info, thanks – and a synchonicity of sorts…
    I mentioned just a smidge earlier, that the next release of the plugin removes the tags from the front page and now only includes them on the actual article pages. It also includes the tags as categories in the RSS feed (if anyone knows of a “better” way then let me know). Why they think front page tags might be confusing things I don’t know, but any insight you can throw up will be assimilated! If you’d like to try it, it’s available as an alpha.

  88. I’m using the alpha 0.7 version at the mo to see how it’s progressing. I’ve some feedback/suggestions for you:-

    btw – I’m using WP2.02 on a windows/IIS sever (in case it’s relevant)

    1) UPDATing the autometa from the WRITE POST screen usually works, but then results in a different outcome when the post is PUBLISHED. In other words – if I don’t mod the autometa and then publish a post (having already SAVED and CONTINUED) it will publish it as requested and then return the screen to a blank WRITE A POST page. If I do mod the autometa and then publish the post is actually published, but you can’t tell from the screen because it stays the same (e.g. you don’t end up with a blank WRITE A POST screen). So – I guess it works, but you don’t know it by default until you view the post status or view the site front page.

    2) I note that the tags are no longer displayed on the index page in this alpha release, however they seem to be displayed after the footer as a bullet list instead for each post. I’d suggest enabling the tags to be displayed either directly after the post, or within the post rather than after the footer of the page as it looks crap and ‘outside’ the context of the post, especially if he post is short, but the page/sidebars/design is longer. Just a thought.

  89. I am running wordpress 2.01, autometa 6 and i am getting no meta keywords – only empty “” in the keyword block generated on my page….. sounds like the ‘old’ pre 2.01 errors – I just can’t get it to work. I have removed, re-added the plugin, etc – it just does not want to work :(

    Any help would be great; Thanks;

  90. Hi, I’m having problems calling the technorati tags manually – I’m using the code but seem to get the following error – “Fatal error: Call to undefined function: technorati_tag() … etc.,”

    I’m using wp 2.0.2, and the auto (hidden) tags work fine if I set them to true, so any help would be great as I really want to use this plugin.

    Thanks in advance

  91. Hi Dave, I think this is a simple one… you need to specify the class name as well as the method name – this ensures two plugins with the same method name never clash.

    … and you might want to try the 0.7alpha version since this has been specifically re-written to better display tags inline using the following php snippet:
    <?php AutoMeta::includeTechnoratiTags();?>

  92. Chris Donnan, I’ve just looked at the top story on your blog, and the tags are there. Seems like you got it working… any idea what was up in case someone else travels the same path?

  93. Coyote, thanks for those thoughts. Point 2, re: tag positioning… you can now specifically place the tags anywhere in your template <?php AutoMeta::includeTechnoratiTags();?> but if you don’t then the code is automatically added to the page footer and (eventually) the tags will be hidden using CSS.

    I’m still trying to understand your first point – I think I get it – and I think it’s something I may not be able to fix, but I’m not sure, ’cause it’s all to do with which filter hooks can be used. Lats see how 0.7 progresses.

  94. Rich, thanks for your help, I’ve downloaded the beta and used the suggested tags and it works a treat – all I need to do is config my css – thanks again, this is an excellent plugin.

  95. Hi Rich, hope you don’t mind me asking another question – I’m trying to call in the Technorati tags manually, it works if I use the AutoMeta::includeTechnoratiTags() etc, but it’s loading as a list, I’d ideally like the tags to just load one, two, three, etc in a line with a comma separating them – can I just do this with AutoMeta::includeTechnoratiTags(‘something in here‘) or will I have to use a custom css style?

    Thanks in advance.

  96. Hi everyone,

    I’ve been testing Christoph Boecken’s Lush theme for WordPress 2.0.2 and it seems that it conflicts with autometa 0.6. I’ve checked the plugin was active and tested it with different other themes and it works.

    Has anyone else experienced this problem?


  97. Hi Alex, can you describe the error, or pop up a copy of a page which has borked? I’ve taken a 20 second look at lush and it’s a “theme++” (insofar as it looks like it includes some quite advanced capabilities) that (a) may be assuming that other plugins won’t have altered the content or (b) may be altering the content so that the regular expressions used to add the analytics code no longer work properly.

  98. It’s because of a missing wp_head() function, which provides the ability for plugins to include stuff in the header. Until last week, I did not know that a function like this existed. I’m currently wrapping up the new version with many bugfixes as well as some new functionality. And yeah, it makes heavy use of AJAX, but that shouldn’t conflict at all with this plugin (or any plugin at all…)

    @Alex and everyone else: It was some sort of coincidence that I found your comment. For further questions, please use my site as this is my main source for requests, wishes, error reportings and so on.

    Cheers, Christoph

  99. What am I missing? WP 2.01, AutoMeta 0.7, theme Automatic Midnight, which does add some basic title/description data on its own.
    I can see the keywords generated in the Custom Field after Save and Publish, but not in the source code. No keyword metadata at all?

  100. Suggestion: Right now one has to save the post before actually publishing it. If there’s anyway you could get the plugin to do it’s work when a post gets published, without having to save it, that would be useful for lazy bums like me. :)

  101. Great plugin — thanks!
    One thing (which I may have missed the correct procedure for) is that I’d like to be able to use phrases. When I hand input them into the meta form on the blog entry, I can connect them using “+” symbols. In the outputted entry, in my inline Technorati Tags the + symbol gets stripped, but it shows up in my meta keywords tags; I’d sure like this to be the other way around.

    Any tips for what I’m trying to do?

  102. Hi Jesse, can you give me an example of some tags you’d like to be able to use; then I can have a more effective poke.

  103. Thanks, Rich.

    I just looked at your source for this page, and it seems to be doing what I want to do (bar the + symbol, which I’m not entirely sure is necessary.)
    You use the phrase “technorati tags” – how did you input that in your list on the meta update text field in your wp-admin?

  104. Thanks for adding that to the FAQ, Rich. But the weird thing in my install, it still properly strips the “+” sign out of the inline Technorati Tags, but leaves them in the hidden meta keywords. Wonder why that might be happening…

  105. I had a problem with this plugin that was really frustrating me for quite a while: some of my tags would be duplicated, despite the obvious steps that were taken within the plugin to eliminate duplicate tags. Turns out that the solution was to add checking for backslashes in the $autometa_quotes array, i.e. added “\”. Problem solved!!

  106. BTW, thanks for this plugin! It saved me the time of porting over my popular MovableType MTKeywords plugin — and it does almost exactly the same thing! I kinda miss the functionality of including high-frequency bigrams, though.
    hint, hint… :o)

  107. Sorry for all the posts! I just solved my problem with “Warning: Invalid argument supplied for foreach()” message in my RSS feed: in your copy of the getTagArray function, swap the “$result = array();” and “if ($tagarrays) {” lines — I believe they are lines 242 and 243. The problem is that $result sometimes isn’t defined and the function doesn’t return an array object…

  108. Thank you for designing this plugin. I just completed my first wordpress theme and I’m making it a resolution to update my new blog every single day. Plugins like this will save me a lot of time that I can devote to writing good posts. Ofcourse I’ll still hand edit or finish off my best posts, but for an average update auto tags seem GREAT. Thanks again.

  109. great plugin!
    my thoughts:

    instead of generating tags by some algorithms or what ever why don’t use a list of ‘my tags’. So everybody could edit his own list of tags that are matched against the post content. That would be great and you don’t have to edit tags manually anymore!


  110. Hi Rich, hope you don’t mind me asking another question – I’m trying to call in the Technorati tags manually, it works if I use the AutoMeta::includeTechnoratiTags() etc, but it’s loading as a list, I’d ideally like the tags to just load one, two, three, etc in a line with a comma separating them – can I just do this with AutoMeta::includeTechnoratiTags(’something in here‘) or will I have to use a custom css style?

    Thanks in advance.

    How was this sorted out – because this is exactly what I would like to do rather than have a list.


  111. I like this a lot.. I think it helped google recognize my site, I just wish there is a button that would show all the meta tags in all the pages. like you click this, you see tags per page. if you click this you see tags for the whole site.. etc etc.. :) that way theres gonna be more information. and people using it will be more comfortable cuz they see its effects. thanks for working on it :)

  112. Trying out the development version because the stable one just left the custom field blank and never generated any keywords. As soon as I tried to install it, I got a PHP syntax error. There’s an extra close-parenthesis at the end of line 287. Removing the parenthesis fixes it.

  113. Figured out the problem with the blank tags, by the way (at least my own problem). Fulltext MATCH() AGAINST() searches are broken in some versions of MySQL 4.0, but OK in the latest 4.1.

  114. Hey Rich,
    I really like the idea behind this plugin, but I’ve having one major issue (and one very minor one)

    The minor issue is that in alpha 2 that you have for download, on line 287 there’s an extra right parenthesis :-)

    The major issue is that I’m not getting any keywords generated (WordPress 2.0.3). When I “manage” a post and save it, I get a page full of error that look like this:

    WordPress database error: [Can’t find FULLTEXT index matching the column list]
    SELECT MATCH(post_content, post_title) against (‘here’) as score FROM jordan_posts where id=71;

    Quite annoying, I’m sure you can imagine. Any idea what could be causing this?


  115. Hey again,
    Okay, I got rid of the page of errors by using the following SQL command:

    ALTER TABLE `jordan_posts` ADD FULLTEXT `post_related` (
    `post_name` ,

    However, I still don’t get tags that are generated (just one that says autometa).

  116. Sorry to nearly spam your comments section – using that SQL command did not in fact get rid of the error. Saving any given post twice gets rid of the error and leaves only autometa as a choice.

  117. Hi Jordan, post away, you have a lot of useful stuff to say :)

    The error you see may be because you’ve jumped straight in and not read the installation instructions.

    Something very similar to the solution you came up with is already part of the plugin. The creation of the necessary indexes should be handled when you do this:

    Look for the AutoMeta menu which appears on the plugins page once the plugin is enabled.
    Click the “Add the index” button to create the necessary indexes.

    I hope… if it’s not, then it might eb a quirk of your software versions which might need to be understood.

    As for the “Alpha-release-bracket-issue” – thanks – I’ll check and update.

  118. Hey Rich, thanks for replying.

    I don’t have an “Add to index” button. The page says everything is okay and “Correctly configured and ready for use”. Is there a way to have a button on there to “Re-add the index”? It sounds like that’s what I need.


  119. Hi

    I’ve installed the plugin and it works great. Is there a way to include the get the tags to center on the page better? I’ve managed to remove the and I’ve got the text to wrap by doing the following:

    function includeTechnoratiTags($hidden = false) {
    if (isset($autometa_technorati_shown)) return;
    if ($hidden) { echo ”, ”, ‘, ‘
    if ($hidden) { echo ”; }



  120. Sir , i use BlogDesk , to do my publishing .
    Will the plugin work , even if i use it or should i use the “Write Page Option ” of Dashboard , for the plugin to work .

    Can the plugin automatically , add keywords , even if i post using the Blog client .

  121. I think my install got messed up because initially the db user in my wp-config.php did NOT have ALTER permissions …

    Now, I get zero suggested keywords.

    Here’s what I get if I run the select from the plug-in itself:

    select match (post_content, post_title)
    against (‘TV’) as score
    from wp_posts where id = 66;

    | score |
    | 0 |

    1 row in set (0.04 sec)

    Of course, I chose a post where “TV” was repeated a couple of times:


    Am I understanding your code correctly? Is there any way to re-initialize this?

    Thanks for creating this — it just bums me out that I messed it up. :-(

  122. Sorry. That last post was a dumb mistake on my part. I didn’t realize that you were filtering out words whose length was less than three.

    I tried a different value and post and got a score of ~ 2.73.

    Guess I’ll have to try another new post and see if it works now …

    Thanks. :-)

  123. Cool! I updated to WP 2.03 and Autometa 0.7 and it actually works. :-)

    Didn’t need to re-initialize the plug-in after all.

    Thanks for all your work on this. :-)

  124. Excellent, excellent plugin but I – and a few others here – desperately need to edit the styling of tag list outputted. Ideally, I’d have “one, two, three four” etc. Is there any way to achieve this without hacking your lovely code?

  125. Well, now it is actually generating tags, but only on posts that I’ve never clicked “Save” on with the plugin enabled before.

    Once I get these few other posts tagged, I’ll be a happy…uhh…clam!


  126. I am using WP 2.0.3 and AM 0.7 and it does not work. I have also tried this with 1.5 to no avail. When originally configuring it, it tried to build and index of some type, to which I don’t think worked properly. To top it all off, I have one SQL database for 4 different blogs (3 have been added as tables), so I am not sure what kind of dictionary would be formulated. The first one I tried running it on on 1.5 is a huge blog.

    It seems to do the same thing….it gives me a message in the source both in the header and footer with the little bloakes dealie telling me it isn’t working for the respective section.


    I don’t see anything in the write post box at all relative to AM.

    I must be missing something simple here…



  127. This is really driving me nuts, Ive used your plugin before, and it worked great. but in the recent build… it still works great, but I cant find a way to hide the technorati tags, i dont want them to show in my page… just in the code so that technorati can pick them up. Meanwhile ive set the includeTechnoratiTagsInFooter = false to avoid displaying the tags in the page, but they arent showing in the code.

    also… I already have a meta keywords tag in my template for my whole site, so this plugin adds another one with the keywords just for the post that is displayed. Is that ok with search pages and stuff? having 2 meta keywords tags?

    Thanks a lot, and great plugin :D

  128. I’ve copied the autometa folder to the appropriate directory, but it’s not showing up on the plugins page for me to activate it. Is this a common problem?

  129. Hi Felix, I’ve not heard of it before – could it be down to permissions? i.e. does the server have read permission on the autometa.php file (and it’s parent/sub directory)?

  130. Hi, Is there any way to tag posts that are already in the blog?

    I have about 1000 posts and it would be great to get them all tagged this way….


  131. Hi Damian, that capability does not exist yet. When I get more time I’ll add it (because people keep asking).

    (In the mean time if anyone would like to submit a patch, please do, it shouldn’t be too much, just a query and then a loop that calls the plugin a few times…)

  132. Hey, I finally got it up and activated on It successfully added meta tags to the two posts from today- one before I activated and one after, but for everything posted previous to today, it enters “no keywords available for meta tag” in a comment tag.

  133. Autometa is working great! Just one quick question. How can I get meta tags for desciption and keywords on only the index page?


  134. I’m just looking for a meta tag plugin for WordPress as it doesn’t publish meta data by default

  135. I installed AutoMeta tonight and it’s generating meta tags just fine, as well as technorati tags.. however when I click the generated tags, my posts aren’t listed on technorati.. I was using SimpleTags previously, and that worked well but I want something automated.

    Have I set something up wrong?

  136. Hi Steve, nice site you have there; it all looks to be setup correctly, so it might be worth contacting Technorati. I’ve known times when their tracking/ranking machines have needed a poke in order to get stuff appearing, but if they know of a technical reason for a failure to pickup the tags, then please let me know and I’ll update as necessary.

  137. Hey there!

    The plugin is not working for me :-( can you check my blog and tell me what I’m doing wrong?! I installed it and activated it. And I clicked that “index” button. But when publish a new post … nothing happens … any help is appreciated! Thank you!

  138. Hi Michael, I’ve just taken a look and I don’t see the plugin signature in the page – the signature shows me which version you’re using and also confirms that the plugin is getting hooked into the page creation process, so do you have it disabled or is this an indication of the problem?

  139. Absolutely wonderful plugin! I have been trying to figure out some method of including tags/meta keywords which were relevent for each post and had just begun looking at plugins but this one was by far the simplest and does exactly what I want it to an nothing else.

    Brilliant. Thanks again.

  140. Nice plugin. I have a small request tho:
    Would it be possible for the plugin to look at the subject of the post too and not just the body? Quite often I don’t bother to duplitate stuff from the subject into the body of the message.

  141. Hi Noemi, the plugin already partially does this. The titles of the posts that already exist are searched, but the title of the current post is not part of the search terms that are used against the database, so I’ll add this for the next version.

  142. It would be cool if you had an option that would just generate the keywords on the fly without having to go in and enabling them for each post.

  143. Excellent plugin, since I am using wordpress mainly as a CMS solution this plugin fits perfectly in bringing together ease of use and SEO – all in one easy plugin.

    Great work.


  144. Hey Rich,
    Great plugin – very helpful. Perhaps you’ve already answered this – is there a reason why my tags are showing at the bottom of every page? I don’t remember trying to include them on the page, so is it a default setting?

    Thanks again! Keep up the great work!


  145. Hi Steve – I just looked at your site and I see you’re running version 0.6. The latest version, 0.8, changes the default behaviour such that tags are not included in the article content by default, so updating should fix it for you.

  146. Hi Norman, when you edit the post there is a section called “Custom Fields” under the post content. Open up this section and you’ll see the autometa data. Edit this, then save the post.

  147. Is there an easy way to add the “description” field to this plugin, so that there is the option to write the text that will show up in the search results? Nice job on this though!

  148. The “copied the autometa folder to the appropriate directory, but it’s not showing up on the plugins page” is happening to me also, and the suggestion given by Rich is not the answer to my problem. The server has read permissions for the folder(s) and the php file. I’m stuck!

  149. Hi Dave, looking at the source here, I can see what look like a whole gaggle of autometa tags… did you fix it, or are these manually entered, or, perhaps you were just looking on the front page…?

  150. D’oh. I was looking for them to be closer to the post in the code, not above all the scripting. I’m sorry about that, my bad. And BTW I love this little pluging.

  151. OK I got me another question.

    I post my blog. Then I head on to technorati and do a search on my tags. First I use my category tags, and my blog post pops up. Then I use the tags from autometa and do a search and they never pop-up. Am I doing something wrong here or is the plug-in not working?

  152. I’ve installed autometa and it generates the custom field entries but I see nothing in my pages for the keywords meta tag or the autometa version tag. What am I doing wrong?

  153. Hi warlord0, since you say the plugin is generating tags ok, but not displaying them, the first suspect is your theme, which may not be triggering the “wp_head” action. Just seach for “wp_head” and if it’s not there, adding “wp_head();” within a php section or <?pgp wp_head(); ?> within an html section of your header should fix it.

    /me crosses fingers

  154. Well, I solved my own problem (#243), so I’ll share the solution. When I extracted the contents of the zip folder, it made an ‘autometa’ folder. Inside this folder were three other folders, one of which was also named ‘autometa’. The solution was to only upload the INNER folder to the ‘plugins’ folder. ( I had previously uploaded the outer folder. )

  155. Can’t get the plugin Visible to be able to activate it.

    I’ve just installed WordPress 2.0.3 and have created the folder autometa under the plugins folder and uploaded it to the server but can not see it in the plugins that are listed to be able to activate it.

    I’ve tried uploaded the contents of the folder i’ve downloaded. didn’t work.

    I’ve followed the Professor advice above
    “Well, I solved my own problem (#243), so I’ll share the solution. When I extracted the contents of the zip folder, it made an ‘autometa’ folder. Inside this folder were three other folders, one of which was also named ‘autometa’. The solution was to only upload the INNER folder to the ‘plugins’ folder. ( I had previously uploaded the outer folder. )”

    and it did not work either. the other plugins I have work fine.

    Any ideas?



  156. I have just started to use this plugin (had no idea the other plugin I was using wasn’t even working. This is really a helpful tool. I find the auto-generated key tags a very useful guide for clearly defining the page. I don’t know if it generates the tags the same way a search engines look at a site, but if it does, it really gives keen insight on why a page may not be getting better results than you think it should. And it can even be used as a pointer for how to better edit the actual content of the post as well. Thanks.

  157. I have a site that is a compilation of all my blog posts. Every time I post on one of my blogs, my tool autoposts onto my compilation blog (it uses the rss feeds for my sites). I love your plugin but unfortunately it won’t create technorati tags for my autoposts. Do I have to physically press the publish button for the tag generator to work? Help!

  158. It looks like a great plugin, but can it also do META descriptions? I need to be able to generate both META description and keywords.

  159. Hi Fred, you could rig it to duplicate the content of the meta keywords and call them the description, but that would defeat the point because the description field is supposed to be “concise and attractive to a user”. I’ve not really thought of adding a description field, but the prime candidate for me would be to add the first 200 words or all words until the “more” tag (whichever comes first).

  160. Hi there. I’ve found a couple of quirks/features/bugs.

    1) For some reason (most likely another misbehaving plugin), my site is not creating the “post slug” until I publish the message. Your plugin adds the autometa attribute when I “save and continue editing”, but it comes up blank. If I manually enter a slug (and do everything else exactly the same), the automatic generation of the keywords kicks in just fine.

    2) If an autometa attribute already has been added to an article, there seems to be no way to have the plugin regenerate the tags again. The update button doesn’t seem to do anything different than saving the article again. To me, the update button should regenerate the keywords. Perhaps, if there are already words there, a dialog should appear confirming that you wish to replace the existing ones with auto ones.

    Maybe that’s the way that button is supposed to work, but whatever is causing my slugs to not appear could be messing with your plugin. I’m still fairly new to WordPress and I’m experimenting with a lot of plugins to find the ones I like and don’t. I’m willing to work with you to help troubleshoot this.

    Thanks in advance!

  161. I followed the directions on this page but nothing ‘autometa’ related is showing up in my wordpress admin area for plugins. I’ve tried a few times now. Anything I should be looking for that might stop it from showing up? Thanks


  162. Hi Cassie, I’ve looked on your whattheblog site and can’t see any evidence of the plugin’s fingerprint, so this is purely an installation issue, which is very difficult to assist with. If you see the plugin in the list, make sure it’s activated. If it’s not in the list of plugins, then it’s a lower level issue.

  163. I’ve been using this plugin for a while now and think it’s great.

    The only feature I would really like to see (I noticed it was on the list of things to do) is default tags for non article pages. I’ve hacked the source for now but it would be nice to just use the plugin as is.

  164. I love this plugin, how ever I am interested in knowing how to use it to create related posts when viewing a single post based on the contents of the auto-generated tags (much like the ones you have on your website). Could you please give some information on how to do something like that? Thanks for your plugins.

  165. Awesome concept.

    I’m having some difficulties with it, though – I can’t seem to make it work. I can’t figure out what I could possibly be doing wrong! I set it up, followed the directions, and nothing. I wouldn’t consider myself tech-unsavvy, either – but why it isn’t working is beyond me :(

    My install of wordpress is a little weird, though – I have a lot of trouble with LJ-Xpost too.

    I’ll keep poking at it, though – this is the only worthwhile technorati tag plugin I’ve seen :)


  166. Nevermind! Of course now that I’ve said it wasn’t working, it’s started working.

    Did you build it with a sense of humour? ;)

    Anyway, it works like a charm, now. Thanks for the awesome plugin!


  167. I changed my theme and the autometa tags vanished. I’m on WP 2.0.3 and Autometa 0.8. And if I go back to the first theme I used with Autometa, it returns.

  168. Just upgraded to 2.0.4 and that didn’t fix it. I see the meta keywords in the code but not the technorati links that used to appear at the bottom of the page.

  169. Backslashes at end of word (/w\/) in the text cause autometa (0.7v) to barf with database errors. I had to deactivate the plugin to get such a post to save.

    The backslash doesn’t get escaped, so when it is passed into a SQL statement, it is treated like it is escaping the quote character in the SQL:

    WordPress database error: [You have an error in your SQL syntax near ”word’) as score FROM wp_posts where id=60′ at line 1]
    SELECT MATCH(post_content, post_title) against (‘word’) as score FROM wp_posts where id=60;

  170. Nice plugin…

    Does the work for post but not for the main page, perhaps aggregating the meta for the post of main page could be used to generate the meta keyword for the main page, even though this content will change very often.

    I did not read all the post but there is only the meta tags keyword that is generated how about

    is there any option that can enable these, or this feature does not exist yet…

    i’ll take a look at the code to see if i can draw something from it. :)

    Thanks for the great work…


  171. Re my problems with 287-288, is there a way to do a complete uninstall so that all Autometa stuff is removed from the database, too? I would like to attempt a complete clean re-install.

  172. Pingback: Hastings Reads
  173. Pingback: Banalità » Tag
  174. Pingback: whatithink
  175. Pingback:
  176. Pingback: More Great Plugins
  177. Pingback: whatithink
  178. Pingback: at Zechary White
  179. Pingback: Akkam’s Razor
  180. Pingback:!!! » test
  181. Pingback: SEO | Likoma
  182. Pingback: Primer aniversario

Comments are closed.