WordPress.com is an easy way to start blogging. Get a blog, check out our features, read the latest announcements, choose from great themes, or learn about the team behind it.
Need help? Check out our Support site, then
Hi, is there a way I can configure my blog so that when people click the categories and tags (for instance, in the tag cloud), they are taken only to my blogs posts for that tag? I find it very annoying that my users are sent to a WordPress list of posts that have nothing to do with my site.
The blog I need help with is effective-life.com.
Clicking on categories and tags in your sidebar does take you to your blog posts. Categories and tags in the post metadata link to the global WP pages; you may find that annoying, but some visitors may find it useful, and it's good for your traffic too. You can disable it if you select the middle privacy option in Settings>Privacy, or if you switch to iNove theme (has the option to hide tags from the metadata).
Also note that categories and tags are exactly the same thing: there's no point using the same word or phrase as both a tag and a category, plus you may run into technical problems when you do that.
[opinion]
This is something else, like the reblogging, that we should be able to opt out of if we desire.
[/opinion]
SacredPath: I agree with you, this should be at the user's discretion.
Panaghiotis: You hit it on the head when you say that some may find it annoying, but some may find it useful. Since it is not universally useful, why not let the author decide how the metadata links work on his/her site?
Also, people can use the same tag or category in different ways. Lumping all users together when a reader clicks on a tag on a post can be very cumbersome for the reader.
Summary: Dear WordPress, please give me the option to have the metadata tags and categories at the bottom of each post link only to tagged posts on my blog (not the entire WordPress universe).
The reason I suspect that AutoMATTic won't allow us to opt out is that having all our blog posts listed on the global tags pages gives wordpress a log of search engine juice which brings them in more money off the ads the "occasionally" show on our blogs to help pay for all this free service. Of course that search engine juice we all share in, so it is one of those double-edged swords.
Still I think we should be able to opt out.
The reason I suspect that AutoMATTic won't allow us to opt out is that having all our blog posts listed on the global tags pages gives wordpress a log of search engine juice which brings them in more money off the ads the "occasionally" show on our blogs to help pay for all this free service. Of course that search engine juice we all share in, so it is one of those double-edged swords.
Still I think we should be able to opt out.
Double post courtesy of the "server maintenance."
@TSP
Presently the only blogs that do not appear on the global wordpress.com tag pages are those marked mature (adult content) or those set to private. What you pointed about above I copy. The Freshly Pressed front page of wordpress.com has a PageRank of 9/10. The trending topics wordpress.com tag page main page has a PageRank of about 7/10 - 8/10. This forum has a PageRank of 8/10. You're right. Some means of paying for this "free ride" has to exist and of course advertising is required. Of course it will be found on the pages with the highest traffic. No I do not expect we will be given an opt out option on this and certainly not at this late date.
I believe that tags in the post metadata of P2 and Prologue themes remain internal, don't they?
Yes but I don't believe most bloggers use them as they aren't styled like "conventional" blogs.
I understand the juice argument. However, I support a number of small non-profits and community groups in the UK and this is a big issue for them. I know that a number of them have chosen not to use WordPress for this problem (as they see it) of linking out to irrelevant posts.
It's a great shame because WP.com is often an ideal solution for these groups. If there is a way to introduce an "opt out" facility into most themes, I think that it would be a very welcome move.
@hollingdeannews: Well, staff reply would be that you can hide them if you buy the CSS upgrade.
Ahh ha... I have the CSS upgrade for my (community newsletter) blog but I've only used it for some basic text tweaking. Can I adapt Tarski to stop the linking to the global categories?
The usual reply is that in Tarski all the post metadata are defined by the same selector, so you can't hide categories and tags without hiding the date stamp and the comments too. But better post your question at the CSS section of the forum: devblog or hallluke might know a way to isolate some of the metadata (hallluke had given a related suggestion here: http://en.forums.wordpress.com/topic/removing-items-from-the-menu?replies=9#post-478461 ).
Yeah, hallluke has hidden some stuff within metadata I believed couldn't be hidden.
Thanks all - will check out hallluke link. Much appreciated :)
Give me thie links to the blogs in question, or the themes that they are currently using and I will let you know if there is a way to remove tags and categories from the post metadata without hiding timestamps, authors or comments. Each theme has different underlying code so the CSS may well be different for each blog. You will also need to pay for the CSS upgrade for each individual blog you wish to modify.
lh
@lh: Tarski (mentioned above).
Not sure how I missed that thanks Panos.
The problem here is the word "in" following the datestamp. I can't find a way to reliably hide it because the preceeding text will take up more or less space depending on when you publish the post. One option would be to style the tags and categories links like normal text, you can even changing the mouse pointer so people are less likely to click on them. It won't solve your problem but it should mean people use your sidebar widgets to navigate within your blog rather being pointed to the wordpress global pages.
lfnovo
thenewsfatigue
sonofbruce
hollingdeannews
.post-metadata a {color:#a8a8a8; cursor:text; text-transform:capitalize;}
.post-metadata a[href$="/#respond"] {color:#006A80; cursor:pointer;}lh
This topic has been closed to new replies.
