Last modified: 2008-11-17 13:53:20 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T16882, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 14882 - Install MetaKeywords extension on en.wiktionary
Install MetaKeywords extension on en.wiktionary
Status: RESOLVED INVALID
Product: Wikimedia
Classification: Unclassified
Site requests (Other open bugs)
unspecified
All All
: Normal enhancement with 3 votes (vote)
: ---
Assigned To: Nobody - You can work on this!
: patch-need-review, shell
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-07-21 23:38 UTC by Conrad Irwin
Modified: 2008-11-17 13:53 UTC (History)
6 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments
Fixes several issues with MetaKeywords. (5.21 KB, patch)
2008-08-12 23:01 UTC, Conrad Irwin
Details

Description Conrad Irwin 2008-07-21 23:38:03 UTC
The Wiktionary community has voted to install the MetaKeywords extension to allow us to have some manual control over the <meta> tags that are used on the site.

The extension can be found at
http://en.wiktionary.org/wiki/User:Conrad.Irwin/MetaKeywords.php

and the vote can be found at
http://en.wiktionary.org/wiki/Wiktionary:Votes/2008-06/Install_MetaKeywords_Extension
Comment 1 msh210 2008-07-22 16:25:23 UTC
The *English* Wiktionary community has voted. (That should be obvious from other clues, but it can't hurt to clarify.)
Comment 2 Niklas Laxström 2008-07-22 16:48:59 UTC
Is this extension in the SVN repository?
Comment 3 Conrad Irwin 2008-07-22 16:52:01 UTC
No, though it presumably needs to be, how would I get it there given that I don't have commit access?
Comment 4 Conrad Irwin 2008-07-28 21:15:47 UTC
This can now be found at http://svn.wikimedia.org/svnroot/mediawiki/trunk/extensions/MetaKeywords/ and so it can now be checked out and required by the en.wiktionary config file.

require_once ("$IP/extensions/MetaKeywords/MetaKeywords.php")
Comment 5 Siebrand Mazeland 2008-08-11 12:18:45 UTC
Add keyword 'need-review'. Only adding the require_once to the config gives 4 notices (see below). Requested a patch from the author. May consider to spit off the hooks into a class. Made some minor updates in r39132.

Notice:  Undefined offset:  -1 in phase3\extensions\MetaKeywords\MetaKeywords.php on line 51
Notice:  Undefined index:  * in phase3\extensions\MetaKeywords\MetaKeywords.php on line 53
Notice:  Undefined offset:  -1 in phase3\extensions\MetaKeywords\MetaKeywords.php on line 65
Notice:  Undefined index:  * in phase3\extensions\MetaKeywords\MetaKeywords.php on line 67

Suggested to add some defaults in MetaKeywords.i18n.php for Mediawiki:Metakeywords and Mediawiki:Metadescription.
Comment 6 Conrad Irwin 2008-08-12 23:01:34 UTC
Created attachment 5173 [details]
Fixes several issues with MetaKeywords.

Thanks Siebrand. This patch fixes a few major/minor bugs (some of which I fixed before, but got lost somehow), clears up all the warnings, adds some default documentation to the messages, and works on svn head.
Comment 7 Siebrand Mazeland 2008-08-13 06:41:47 UTC
Comment on attachment 5173 [details]
Fixes several issues with MetaKeywords.

Applied in r39275. Thanks.
Comment 8 Brion Vibber 2008-11-17 06:00:09 UTC
Resolving this as INVALID -- will not install this extension.

1) <meta keywords> are obsolete, ignored by most or all modern search spiders. Absent specific documentation indicating that there is some specific benefit we can get, we should not bother producing them. (Removing the existing crappy default <meta keywords> is on my todo list!)

2) If they were known to be useful, then we would need smarter generation which produces relevant keywords based on the actual page -- applying the same keywords to the entire wiki's content namespace would be misleading at best.

3) <meta description> appears to actually be used, at least sometimes, for search engine result listings. But again, making use of this would require sensible and appropriate descriptions to be created for each page; a general "definition of XYZ" for every single entry would harm more than it helps, since if it were used it would make search results much less useful -- they would lack any actual definition text!

4) Nor is it clear that a <meta description> would help at all with *ranking*.
Comment 9 msh210 2008-11-17 06:02:50 UTC
<meta description> will help with ranking on searches for "definition of" if "definition of" appears in the meta tag and not the text, for example. Please reconsider resolution.
Comment 10 Brion Vibber 2008-11-17 06:03:53 UTC
A general description of <meta description> best practices:

http://googlewebmastercentral.blogspot.com/2007/09/improve-snippets-with-meta-description.html

"Using identical or similar descriptions on every page of a site isn't very helpful when individual pages appear in the web results."
Comment 11 Brion Vibber 2008-11-17 06:04:38 UTC
Oh, and:

"And it's worth noting that while accurate meta descriptions can improve clickthrough, they won't affect your ranking within search results."

Sorry guys, no Google juice.
Comment 12 Melancholie 2008-11-17 09:55:32 UTC
Note that there is not just Google out there (although behaviour may be pretty the same for almost all search engines today).

Note that there is an easy way for certain pages to have accurate keywords in the meta tag!
See [[wikt:User:Melancholie/meta-keywords]] (the only point that has to be met is that the keywords have to be re-mentioned in text itself)

Oh, and do not use ImageMaps, use |link= ...
Comment 13 Melancholie 2008-11-17 10:01:36 UTC
Oh, and: Isn't improved clickthrough something we want to achieve?

Currently, Google often shows that "Jump to: navigation search" stuff! Is that better?
Comment 14 Conrad Irwin 2008-11-17 13:52:27 UTC
The motivation for requesting this changes was that our pages did not contain the word "dictionary", "definition" or other words people use to search for dictionaries. This meant, that until we added a hidden tagline to each page, searches for "definition of word" "word dictionary" did not include Wiktionary at all (even when wiktionary was in the top 10 for "word" on its own). The extension should probably be named meta-description, as that was its main intended use - however I saved the file as keywords, and it stuck. It would be neater from every point of view to have "Definitions of $1 from Wiktionary, a free dictionary" in the <meta description> instead of in a hidden <span> on each page, though it is not necessary that necessary except to avoid misleading people.

Compare http://www.google.com/search?q=chalcidology+dictionary and http://www.google.com/search?q=chalcidology . (At the time of writing the second search contains wiktionary, the first doesn't - google haven't recrawled this page recently) Luckily Google now (in the past few months) uses Wiktionary as a source of definitions, so we can provide useful information at http://www.google.com/search?q=definition+of+chalcidology even though the website itself doesn't appear. The problem with using the tagline for this can be seen at http://search.live.com/results.aspx?q=chalcidology+dictionary&go=&form=QBRE where the talk page appears even though it is irrelevant.

Comment 15 Ran Ari-Gur (User:Ruakh on WMF projects) 2008-11-17 13:53:20 UTC
Re: comment 10: Brion, please read the sentence after that. It's talking about something completely different -- it's talking about the snippets Google will *display*. We don't care if Google displays "definition of ____" for its snippet, or if it uses its normal snippeting algorithm.

The problem addressed by this extension is that (for example) a user Googling for "definition" + [word] would probably be interested in the English Wiktionary's entry for the word, but because we're a dictionary site, we don't generally put the word "definition" on every single page. (Technically we do have it in hidden text, but that's generally considered "cheating"; that sort of thing is supposed to go in the keywords metadata, not in hidden text.)

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links