|
Posted on 09.30.07 by Widge @ 5:52 am
Technically, it's correct: you don't need a robots.txt for good SEO. However, it's not that simple. Part of the problems I was having on my sites was that the search engine bots weren't just crawling my site, they were freaking pounding it into a fine powder. Oh sure, if you've got a big enough server, you can afford to let them run all over you–but I'm doing this crap on a budget. If you're on a budget hosting service, or to put it another way, if you're using the cheapest hosting you feel you can get away with–you have to make sure you're not throwing away bandwidth or CPU cycles. Look at your access logs. Are you getting hammered every couple of seconds by Googlebot? Or the Yahoo bot? Or any bot for that matter? If you have a robots.txt, are the bots reading it and heeding it? It's one thing if you've got flat HTML pages for your site, but even with wp-cache running, Wordpress can bog down if a bot is allowed to run rampant. And if your site is slow or can't be crawled properly because the bots have bogged it down, then yeah, that can affect your SEO. Now you know. And knowing is half the battle. Filed under: Fun With SEO
|
|
Posted on 09.30.07 by Widge @ 1:53 am
Okay, next up: the link quicktag. On Needcoffee, we have internal links and external links. Internal links are just plain old links. External links open in a new window. I know that irritates a few people, but I have no idea why. You close the window and you're where you came from. Seems like a no brainer to me. Anyway. Same deal as before: 1. Go to /wp-includes/js/ 2. Edit quicktags.js 3. Look for this code:
Filed under: Wordpress
|
|
Posted on 09.29.07 by Widge @ 10:55 pm
Okay, so here's some fun. At Needcoffee, we pretty much draw from a single directory for images. But if you do the IMG quicktag by itself, all you get is it asking you for the full URL. That's no fun. How can you hardcode the img directory in there? Simple. 1. Go to wp-includes/js/ 2. Edit your quicktags.js 3. Look for this code (I've killed some tabs just to keep it from being too wide for the theme):
Filed under: Wordpress
|
|
Posted on 09.27.07 by Widge @ 1:03 am
Seriously, think about it: Wordpress 2.3. 2+3 = 5. Law of Fives. I just saw realized this when I ran the Ultimate Tag Warrior converter: Import Complete! OK, so we lied about this being a 5-step program! You’re done! Now wasn’t that easy? Remember how AUM had cocaine added to it simply to allow for the Law of Fives? Yeah. Law of Fives. Hail Discordia. Filed under: Wordpress
|
|
Posted on 09.25.07 by Widge @ 11:10 pm
Okay, folks. Seems to have worked…so far. And because this is the first thing I wanted to be able to do: let's talk tags. The UTW importer seems to work very well–although, come on, guys: UTW was a good plugin. Do you really have to refer to it as a "nasty habit"? Kinda tacky. Anyway, it zapped my 500-some odd tags fairly quickly. There were four very odd errors where it appears tags didn't make the leap–some sort of database error–but I didn't take down the error. If I see it again, I will. But here's the part that's a little wonky–and a little unnerving. There's nothing in the Wordpress admin area to let you tinker with tags. They're just sort of there. I understand there's some plugins to help the tag admin thing, but as long as it works, I don't care. I had to strip the UTW code out of my theme because it was causing errors (and of course, reactivating the UTW plugin caused a fatal error which Wordpress mercifully put the kibosh on before it could do any damage). So how to get the tags back in? Well, this post is a good start, and the followup's not bad, but what if you just want to say something witty and then list your tags in a comma-separated list? It's not obvious.
That's how I do the tags on this theme. And as for context of where it goes?
Tinker with it till you get it to look like what you want. I'm going to be changing themes anyway. This one just looks like a giant nasty kluge. Filed under: Wordpress
|
|
Posted on 09.25.07 by Widge @ 9:08 pm
If you see anything weird, that's probably why. Yes, this blog is the guinea pig. I'll let you know how it goes. Filed under: Wordpress
|
|
Posted on 06.01.07 by Widge @ 11:49 pm
Wordpress does about 90% of things well and in sane, sane fashion. The other 10% will make you want to gnaw a limb off a cute little kitten. After putting up with the whole "–" becoming "-" for as long as I could, I finally snapped and tried to look around for a solution. I had fixed this at one point, in a previous version of Wordpress, but for some reason they moved stuff around and the first time I tried to find it I couldn't. I tried to find something that would take care of it for me, or at least the good word on how to make it go away, but the hits I found on Google weren't very helpful. There's nothing worse than "helpful assholes" who try to tell you that you should just get used to something and why would you ever want to do it That Way to begin with? It seems like every time somebody wants to change something formatting-wise in Wordpress, some of these HAs show up and want to waste your time with trying to convince you instead of just telling you what the hell you need. So here's what I needed, in case anybody else needs it: Filed under: Wordpress
|
|
Posted on 04.27.07 by Widge @ 12:02 am
Well, you haven't seen me a lot around here because I've been up to my elbows in code over on Needcoffee. I've been trying to optimize the site while fighting with WP-Cache, which I can't live without due to my traffic, but which also kills me if I try to update the site while it's turned on. I'm still trying to figure out that silly shit. Anyway, now that I've finally gotten a bunch of superfluous ne'er-do-wells gone from my access.log file, I can finally look at it and see what's happening moment by moment to try and address the problem. One thing I wanted to see, though, is what is really taxing the memory of my server space. Trouble is, the access.log I get from Dreamhost (which I can only assume is the same sort you get from where you are) looks like this: x.x.x.x - - [26/Apr/2007:00:36:50 -0700] "GET /wp-content/plugins/podpress/podpress_js.php HTTP/1.1" 200 2311 "http://www.needcoffee.com/2006/03/08/power-rangers-dino-thunder-vol-3-dvd-review/" "Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8.1.3) Gecko/20070309 Firefox/2.0.0.3" Filed under: Fun With SEO
|
|
Posted on 12.25.06 by Widge @ 5:41 am
Okay, as promised, I'm giving you the gory details on my battle with comment spam on Needcoffee. I wouldn't exactly call what has happened a surrender–I have had to close down all comments on Needcoffee just to keep the server from crashing–I prefer to think of it as a scorched earth policy. Basically, here's what's been happening. And here's why nothing I tried has worked. There's a file in Wordpress that is pinged/called up when you want to post a comment. It's called wp-comments-post.php by default. What the spammers have been doing is hitting that file in order to post their spam on my site. Do they succeed? No, not in the least. For the first part, I have…well, had…all comments moderated. Nothing was ever posted to Needcoffee as a comment without going through me, unless you were a member of the staff and logged into the site. Why do they want to post spam? People ask me this all the time. Basically, there are lots of blogs that have no protection up whatsoever. As a result, these spam bits have links to the spam sites. Sites get Page Rank from Google depending on how many sites link to them, propping up their Page Rank score. That's a simple way of putting it, but that's the gist. So they hammer you with spam in the hopes of improving their standing in Google search findings. Now. This wouldn't succeed even if they did manage to post something, since a rel="nofollow" tag will negate Page Rank boostage from happening. But these spammers and their spammer zombie whateverbots don't care. They will persist regardless of whether or not any comments actually succeed in getting posted. Why? Because they can, that's why. The first thing people say is Akismet. Use Akismet. Well, Akismet is bogus for two reasons. First, just because the comment gets auto-moderated and left off the roll call, that doesn't mean it hasn't taken up space in your Wordpress database. I found this out the hard way after the first 21,000 spam comments rolled through, got caught, and now I have to clean out my database because they're taking up gobs of space. Second, just because the comment gets auto-moderated and left off the roll call, that doesn't mean the spambot hasn't hit your wp-comments-post.php file anyway. It has. And when you've got them coming in like a spam tsunami, sure Akismet keeps them from being posted or even from you having to moderate, but your site will 503 nonetheless. The second thing people say is Bad Behavior. Use Bad Behavior. Bad Behavior helps, but it can be overwhelmed. I can't tell you how BB works, but I literally saw dozens and dozens of bot smacks against wp-comments-post.php a minute coming in. If this is BB when it's on full on strict mode, then without it, gah. So BB doesn't help. Then, I renamed and eventually deleted wp-comments-post.php. Fuck it, says I, if you can't get to the file at all, you can't mess with me, right? Wrong! They're trying to hit the file, there or not, which means the server takes a hit, which means…503. Then, I had DreamHost alter my htaccess file to block hits to the wp-comments-post.php file unless the referrer site is needcoffee. So you can't hit the site from anywhere else. Should help, right? Wrong! They can spoof shit so it looks like it's coming from my site. So I started going in and trying to add bits to the htaccess file to weed out casino and poker spams along with certain IP addresses. The spam detail file I pulled down from BB was so large, I couldn't even process it. I finally deleted everything but the last seven hours, and even that was about 10,000 lines in the CSV file I used to pull it down so I could try and manipulate it. Nothing worked. 503 errors on IE constantly, although strangely Firefox was slow but it could get through. No telling. So finally, boom. Comments go bye-bye. Now at least you can get to the site. If anybody has any ideas on how to effectively stop not comment spam, but the server strain of the spam equivalent of a DDOS attack, let me know. Otherwise, I'm spent. Night. Filed under: General BS
|

John Robinson is a writer of prose, poetry and comics who also writes under
the pseudonym of Widgett Walls.
This is my latest book. Short stories written especially for you, or at least someone who reminded me a lot of you at the time.