Last modified: 2014-06-07 16:15:53 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 T14196, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 12196 - Use a meta description tag for better search-engine indexing
Use a meta description tag for better search-engine indexing
Status: RESOLVED WONTFIX
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
unspecified
All All
: Lowest enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
http://en.wikibooks.org/wiki/Wikibook...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-12-04 18:33 UTC by Andrew Whitworth
Modified: 2014-06-07 16:15 UTC (History)
1 user (show)

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


Attachments

Description Andrew Whitworth 2007-12-04 18:33:14 UTC
Pages are generated with a meta keywords tag such as <meta name="keywords" ...> but many modern search engines also make heavy use of the <meta name="description" ...> tags for indexing. Would it be possible to automatically generate such a tag for pages so that they were better-indexed in search engines?
Comment 1 Brion Vibber 2007-12-06 19:01:52 UTC
Since the auto-generated keywords are generally agreed to be seemingly random and near-useless, I'd be pretty leery of trying to invent a description as well.

The text and the links speak for themselves...
Comment 2 Nemo 2014-06-07 16:15:53 UTC
(In reply to Brion Vibber from comment #1)
> Since the auto-generated keywords are generally agreed to be seemingly
> random and near-useless,

In fact they were removed in 2009: bug 19761.

> I'd be pretty leery of trying to invent a
> description as well.
> 
> The text and the links speak for themselves...

I think there is a remote chance of this happening in an extension instead: bug 66325.

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


Navigation
Links