Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

use a meta=description tag for better SEO (search engine optimization) #828

karenetheridge opened this Issue Apr 26, 2013 · 6 comments


None yet
4 participants

karenetheridge commented Apr 26, 2013

As described in http://www.modernperlbooks.com/mt/2013/04/perl-web-pages-and-search-engines.html -- metacpan module pages should have a meta tag whose description is the one line synopsis of the module. This will help search engines generate results pointing to metacpan.org, instead of search.cpan.org as they still do today.


oalders commented Apr 26, 2013

I'm not sure this is actually helpful SEO, but it does make fore easier to read search results when displayed on Google. That is, meta description helps with conversion but not with placement. http://www.youtube.com/watch?v=RBTBEfd7z_Y

@yanick yanick added a commit that referenced this issue Apr 30, 2013

@yanick yanick add <meta name="description">
Quick patch for #828. Naive approach where the meta description is
simply a copy of the <title> (itself a copy of the NAME pod section).

omega commented Aug 15, 2013

Looking at https://metacpan.org/module/TAP::Harness::Archive::MultipleHarnesses (randomly selected module), it now has a <meta name="description" content="Create an archive of multiple harnesses of TAP test results" />.

I guess that means this issue could be closed?


karenetheridge commented Aug 15, 2013

as far as this particular ticket, yes definitely. I'm not sure where the general "improve our SEO rankings" effort lies, however, or if there are other tickets covering it? the google rankings are better than before, but s.c.o still appears above metacpan in the results most of the time :(


ranguard commented Aug 15, 2013

Someone is working on sitemaps (#894)- I've had an SEO guy look at the site and other than 215k (SCO) vs 1.5k (MC) inbound links - Google sees MC as a non-authoritative source of the same data as SCO, so we get heavily penalised. The only real way to battle this is to get original content (from users - not just another site) onto the site.

But yes closing the ticket as this has been done

@ranguard ranguard closed this Aug 15, 2013


karenetheridge commented Aug 16, 2013

Google sees MC as a non-authoritative source of the same data as SCO

whaaa? who says that sco is authoritative and metacpan isn't? Both are simply different views of data from pause.perl.org; neither should have any claim of authority, as neither is actually producing the source data.

(corollary: how can this be fixed?)


oalders commented Aug 16, 2013

As @ranguard pointed out to me, s.c.o. has a massive number of inbound links, to the point that it dwarfs metacpan.org Also, since s.c.o. has been around forever, I would guess that it gets some points for longevity. The other issue is that Google may consider metacpan.org to be a duplicate of s.c.o. because much of the content is the same.

Solutions would be:

a) Increase the number of inbound links, especially from influential sites
b) Get more content on the site to differentiate us from s.c.o.
c) Be good at preventing Google from indexing too much duplicate content (robots.txt etc)

Maybe a small campaign to ask authors to link back to their MetaCPAN author pages would be a good start.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment