Jun 172010
 

Two years.

500 posts.

5700 comments.

386,000 visitors to my site.

~1,000 subscribers to my feed.

80 sex toy / sexy fun items reviewed.

4 trips to NYC, 1 trip to Seattle, and 1 upcoming calendar.

3 projects – e[lust], the sex blogger co-op and toyswap network.

Countless awesome peers, acquaintances, friendlies and supportive friends that I wouldn’t have without this blog? Priceless.


I’m in a different place than I was a year ago. Some things for better, some things….not. But I’m still grateful. I’m finally able to do things like my side projects to give a little back to the community that’s given me so much. I’m still learning, I’m still growing. I’ve hit some very recent number milestones and I’ve got this mild obsession with numbers and statistics. The 500 posts and just last week hitting 1000 readers tickles me.

Thank you for having me.


On a side note, if you’ve happened to enjoy me & my blog, consider nominating me for the 2010 Sexy Bloggers list, along with your other favorite sexy bloggers.

Apr 012010
 

The other day I found that Fleshbot, previous home of the traffic-boosting Sex Blog Round-Up, is getting bloggers to agree to letting them re-post content. Specifically, YOU write a post and it’s published on your blog. Fleshbot comes along and says “oh! I just lurve it! You gets lots of wunnerful traffic if you let me re-post the whole thing on Fleshbot!”. Your link is at the end of the post; Fleshbot is getting free content that fills up their site (they paid the people who did the Sex Blog Round-Ups so it’s a big $$ saver to them); you get empty traffic for a few days.

Sure, Fleshbot traffic was nice for the numbers, but I never received a comment from a FB reader.

We were discussing this all yesterday at the Sex Blogger Co-Op and Jake (such a smart young man) made these wonderful points:

– It’s my content, it belongs on my site, that’s just what feels natural.
– It goes against the ethos of linking to blogs so that readers can discover new blogs to subscribe to. I’m not going to get any new readers or RSS subscribers by having my content lifted and put on someone else’s site.
– If it’s on their site, it’s surrounded by their adverts and making FB money, not making little me money from the ads on my site.

We’re bloggers – we’re attention whores to some degree, every one of us. So yeah some are going to be blinded by the compliments and promises of traffic but just keep in mind that in the end….Fleshbot wins, not you.

The House always wins.




(pssst: some happy news where YOU win! Edenfantasys put the holy grail sex toy, The Pure Wand, on sale for Thursday only at $75, free shipping! Or if you always wanted a Pure Plug they’re on sale too!)


Mar 252010
 

When I started e[lust], it wasn’t a completely altruistic venture. Sure it helps out any blogger who joins but I knew that my own traffic numbers were going to start declining once Sugasm died and then especially Fleshbot sex blog round-ups. And as Luka pointed out recently (somewhere, I forget where, but she did) a decent chunk of the traffic we might get from Fleshbot/Sugasm/e[lust] mentions results in a numbers boost but not a tangible readership boost (i.e. comments) it still helps in the end. Maybe the post featured in those places didn’t get extra comments, but I’d bet you gained a new reader or two. For me personally, having decent traffic and ratings means I get to keep my advertisers who help keep the site paid for, as well as my blogger-related trips. Fun trips that I won’t go out begging others to help fund. I depend on me. But that’s a rant for another day, folks.

This post is to highlight my most recent project: the e[lust] Sex Blogger Co-Op network. It’s a private network I created at ning.com, so that sex bloggers can freely speak their mind to other sex bloggers and sex bloggy issues. One of the first reasons I created this was finding out how many sex bloggers know little to nothing about what to do when approached with an offer for paid advertising (or what their peers are doing about it). But there’s a lot of shit out there that we can all help each other with. So I might know a few things about advertising. Someone else knows more than me, and I wish they’d share it. Maybe someone else knows a lot about CSS and give tips. We all have *something* to contribute, even if its just asking questions so that answers are put forth for the benefit of others.

 

 

Clipped from: elustsexblogs.com by clp.ly

You can read more about it over at e[lust]. (actually I took down the page once the network closed, so you can read most of that page’s content below) If you’re a reader and a blogger, I encourage you to join. The larger the community, the more information shared, the more we all benefit. Some things we’ve talked about recently include advertising basics; patents; post prompts; differences between blogpost and wordpress; what hotlinking is and why you should care about it; and some fun shit about sex toys and google search phrases. There’s a lot going on, a lot of information being shared that could be helpful to even the most casual of sex bloggers. I love for you to join us! Like I said, go read more about it over at e[lust], including how to snag an invite.

 

“A sanctuary of knowledge-sharing for all sex/adult bloggers”. Sex bloggers, IMO, have different bloggy needs than the day-to-day diarists or mommy/daddy bloggers. Namely, we’re various levels of “Not Safe for Work”. Which means that we have different issues and resources for blog directory listings, reader bases, advertising, contest giveaways, etc. I mean, no matter how much I might talk up XYZ makeup or something, I’m never going to be approached by the company or Sephora or whomever to do a review and a giveaway. They don’t want to be associated with adult bloggers. And, as example, back when I used Blogspot, I tried signing up for the google adsense….and got rejected. For awhile there I didn’t know that advertisers would ever want to affiliate with me.

 This social networking site is hosted at Ning.com, and is a private, invite-only safe space for sex bloggers only. So who is considered to be a sex blogger?

 If you’re on Blogspot and you have a Content Warning splashpage

  • If you put your own “Over 18!” warning in your blogs sidebar
  • If you talk about sex on your blog
  • If you blog but also post erotic/nude/pornographic photos
  • If you do adult product reviews on your own blog (if toy reviews are the only sex/adult part of your blog, you may find that the ToySwap Networkwould serve you better)
  • If you write and post erotica on your blog

 And there’s more, I’m sure. And we’re all in various circles/cliques. But for the purposes of this site? We’re all just sex bloggers. Be it LGBTQ, kinky, perverted, affairs, dating, vanilla, educational….whatever your branch is, I don’t care – we all share a commonality. I hope to have members who are veteran bloggers as well as the newbies who just started last month. We all have something to give and something to learn.

 Want an invite? Keep in mind this isn’t a place to garner more readers and/or blog hits from, this is information-sharing between sex bloggers and we’re looking for members who are willing to participate and be active.

 Some recent discussions include:

 tutorial on hotlinking of photos

  • tutorial on advertising
  • fun discussions like toy storage & care or google search phrases
  • post prompts, writing groups and more
  • blogger vs wordpress, free vs self-hosted


Feb 222010
 

So yesterday I told you about these evil crawler bots and how they’re able to silently corrupting blog files into oblivion if you don’t catch it soon enough.

Even if you do figure it out quickly, 98% of the time your files are already affected. Even if you remove the “bug” there’s still going to be some issues. Thing is though, unless you’re a programming geek, you’re not going to be able to manually pick out all the little bug poop bits from your files. What you need is a clean version of your blog.

Except….you don’t have it, do you.

No, you likely do not.

Some people that I’ve talked to use a WP plugin that creates an automatic backup of their database and it gets emailed to them. Ok, great. But guess what? It’s not enough.Some of you are gonna be all “WHAT database??? There’s a database??” cause I know I was.

Last week when dealing with SBC.com, we found that out. We also found out that SQL databases are tricky bitches. If you don’t know anything about backing up the database, when you do figure out how to do it manually you’re just going to let the default options go. Except those default options leave extraneous info that is actually bad; it confuses the restore (at least with GoDaddy). The default DB backup included “Create” lines and lines for the “information schema” which are essentially duplicate commands and duplicate commands are NOT friends with SQL. They made the restore attempts spit back errors at me like mad.

Let me back up. First of all, the problems with SBC are not ones that most of you will encounter when needing to rebuild your site. The reason being is that we didn’t have access to the domain files because they were under someone else’s account. The database, so we all thought, contains the posts and the comments and all that good stuff. So that’s all you need, right? A few Godaddy guys lead me to believe that. It’s  not the case. You need a whole shit ton of .php files that are running amok through your WP files. These .php files talk to the database and link everybody up.

There’s two ways to get these .php files.

1. If you have access to the hosting account, you can go into the file manager and copy everything to your hard drive.This is the more complicated way I guess, bc the next option just involves a few clicks and one file, however this method will also backup all your theme files, stylesheets if you’ve tweaked the theme, etc. But there might be an instance when this option is your only option.

2. You can go into the WordPress dashboard and do an Export. ” When you click the button below WordPress will create an XML file for you to save to your computer. This format, which we call WordPress eXtended RSS or WXR, will contain your posts, pages, comments, custom fields, categories, and tags. Once you’ve saved the download file, you can use the Import function on another WordPress blog to import this blog.” This option is simple. It saved everything except the tweaks I’d done to the stylesheet.css for the theme (since I had to re-upload the theme) and the contents of the widgets in the sidebar.

For 3 days, I couldn’t do either of these options. The moment Diva was told by GoDaddy that we hadn’t actually truly transferred the blog, they had her change something called the “nameservers”. The nameserver is what tells the site where to find its files. Once the nameserver was changed from pointing at Dreamhost to pointing at Godaddy…..buhbye blog as we knew it. Suddenly we were staring at a blank “baby” blog. No posts, no theme, no nuttin. Some asshat at GD said “well you can just go into the WP dashboard and export” um no, no we can’t, since the dashboard sees the baby blog, too. It’s not like we could go to another http site address and snag the files, that wasn’t the case. When we FINALLY after 37 attempts got the stupid database to restore properly we were gutted to find out that nothing had changed on the blog. But thank you, GoDaddy, for not explicitly telling us what would happen when we changed the nameservers and asking us if we had ALL the files backed up from the WP dashboard.

My final call to GoDaddy was at first hopeless; he informed me that we *needed* all those WP files, the database alone wouldn’t bring back the posts even if I could recreate the theme by myself. Then it occurred to me. Wait a minute. This all went to hell the moment we changed the nameservers. Couldn’t we change them BACK to pointing at Dreamhost, and I could go into the WP Dashboard and export, then change them back to pointing to GD and import? Well…..he’d never done that before, but he supposed I could.

And I could. It took a few hours from the time at which I changed the nameserver values until I was able to go into the WP dashboard and be accessing the correct version/location of the blog. Since I had to do this twice because my first g-round I didn’t realize I had to copy the contents of the widgets, the whole import process took about 24 hours.  And once I imported? *cue angels singing from heaven* The beautiful pretty blog! It was back! Everything was there! We all jumped around and were excited. A few quirks with some photos were fixed and all was well. (this folks, is a shining example of how sometimes my weird ADD odd way of thinking can actually be a help)

So. What’s the moral of this story, kids?

Backing up WordPress is necessary. Backing up the database is not as useful as you’d like to think. Don’t get me wrong, you should do it, but don’t count on it to be your saving grace if all else is lost. If you have nothing but the database, it’s like having cherries and flour and butter and sugar and whatnot but no recipe or equipment to turn it from ingredients to pie.

As I said yesterday, I didn’t have to worry about this backing up with e[lust] because GoDaddy backs up everything (they have a “snapshot” of your files for every day of the last 3 weeks I think). Every file, they have – except for the database, since it’s always in use it can’t be automatically backed up. Because my site was hacked, it wasn’t the posts that I needed to restore, it was the php files.

If You Have a Self-Hosted WordPress Blog (and you don’t have Godaddy as a host)

1. Like your theme? Have you made changes to the stylesheet at all? (if not you, then someone else?) Then you need to back up the stylesheet/phps because the WP export won’t do it all. When I imported the WP dashboard export, the theme didn’t follow along. And of course, you know me, I had made changes to the theme from the original.  Luckily though I had also manually copied the contents of the css and the php files from the theme editor over to text files. Some copy/pasting and we were visually pretty again.

2. As often as you can think to do it, manually perform the WP export from the dashboard. I tried looking for WP plugins that will automatically do this but there were either complicated as fuck or not compatible with the recent upgraded version of WP. Extra precautions would tell you to save these XML files someplace other than your harddrive, because you never know when that could die.**This export backup won’t save your sidebar/widget contents. If you’ve got a lot of text boxes filled with banners and links and fun stuff in the sidebar, you should do a copy/paste as I instructed for the theme files**

3. Add the plugin called “WP – DB – Backup”. Go to “Plugins” then “Add New” and then search for that one and click on “install”. Then activate and go to “Tools”, “Backup” to check off all the boxes (I left the “exclude post revisions” unchecked because who knows, I might need that) and tell it to email you the backup zip file. (don’t forget to schedule daily or weekly backups, depending on how often you put up a new post).

Now then, why am I telling you to do step 3 if step 2 saves the posts/comments that the DB saves but can’t “read” without the php files? Because at least step 3 is automatic and daily. Step 2 relies upon you remembering to do it. Even if your last WP backup was a month ago, you could still import that database backup and then go to your hosting provider (PHPMyAdmin control panel or similar) and restore yesterday’s DB, bringing your recent posts and comments back.

If You Have a Self-Hosted WordPress Blog (and you DO have GoDaddy as a host)

1. Like your theme? Have you made changes to the stylesheet at all? (if not you, then someone else?) Then you need to back up the stylesheet/phps because the WP export won’t do it all. When I imported the WP dashboard export, the theme didn’t follow along. And of course, you know me, I had made changes to the theme from the original.  Luckily though I had also manually copied the contents of the css and the php files from the theme editor over to text files. Some copy/pasting and we were visually pretty again.

3. Add the plugin called “WP – DB – Backup”. Go to “Plugins” then “Add New” and then search for that one and click on “install”. Then activate and go to “Tools”, “Backup” to check off all the boxes (I left the “exclude post revisions” unchecked because who knows, I might need that) and tell it to email you the backup zip file. (don’t forget to schedule daily or weekly backups, depending on how often you put up a new post).

Don’t worry about Step 2 unless you foresee yourself changing to another host. GD’s file snapshots will be there for you, ready to roll back to if something happens. You don’t have to pay extra for it, you don’t have to ask GD to do it for you. If you need to roll back, you log into your account, go to the hosting control panel and go to the File Manager. There’s two tabs there on the left. Current and History. If you were to click History you can see the files, and only one button is highlighted….”restore”. You’d just check off all the folders/files you need to have restored, and then click restore, and the roll back is complete. The only portion I’d recommend backing up on your own are the widgets, I don’t believe that there is any file in your directories that have the info of whats contained in the widgets. I need confirmation on this.

If You Have a WordPress Hosted Blog (i.e. http://yournamehere.wordpress.com)

You have one option. You do a WordPress Export via your dashboard as often as you can think of it. You can’t use plug-ins, and there’s no database to access. I read somewhere while searching for all this info that doing this Export won’t save your photos. But it did. When you go to Import, and you re-map the users (if you need to) there’s a section that says Import File Attachments and you have to check off that box. Voila, your photos appear.Again though your blogroll and sidebar widget contents aren’t saved in this. Manually copy them to a text file.

Understanding your Self-Hosted WordPress Blog’s Host Control Panel

Let’s say you have a self-hosted WP blog and you didn’t set things up yourself, you had help from a friend or fellow blogger. I don’t care who they are, you need to be able to rely on yourself to fix things should it all go to hell. You never know if one day you stop speaking to this person or they just simply aren’t available immediately to help you fix it. You need to learn how it works at the core level, which can be more complicated. But in the end, it’s worth it to be able to rely on yourself for bringing it all back up to speed. I know that there are companies now like Discreet Press who are taking advantage of the blogger who doesn’t want to have to deal with this stuff by charging a lot more than I’d ever pay by offering more than just hosting. They can do design, they can repair your site, etc. However in my opinion most of us bloggers can only afford the least expensive hosting plans. Which Godaddy DOES offer. And for the services they give you in comparison to other plain hosts (like Midphase) it’s a damn good deal. I don’t care how technically inept you might think you are right now you CAN learn the basic shit. I did. So many times over the last week and even just while writing this post I had these Algebra Class moments. I can’t tell you how many times I was able to come up with the right answer but got points knocked off because I couldn’t show my work. Don’t know how I got there, or I couldn’t explain how I got there, but I did and that wasn’t good enough for the math teachers. Anywho. If you’re financially stable enough to willingly hand over full control and reliance over to a company, then go for it I guess. In the end though I don’t care how stressful this all was, I didn’t like having to rely on others and would have taken on more stress if I could have just done it all myself. I hated having to ask Alec a million times for help. I hated having to wait for someone else to have the time to help me; I wasn’t paying them, I couldn’t just say DO IT NOW!!

What could happen to precipitate this need for self-preservation, in addition to the hacking I talked about yesterday?

Simple. You installed a WP plugin that wasn’t compatible. Shit, I just did it yesterday when searching for automatic full backup plugins and the like. One of them made site visitors see some wonky ass code after they commented. A second one rendered my WP dashboard completely fucking useless. I had to go into the GoDaddy hosting control panel to the File Manager or their java-based on-site FTP client and remove the plugins manually. That meant going to wp-content folder, plugin folder, and deleting the whole folder of the plugin I just installed. Like magic, my dashboard/site were working fine again. If you don’t know how to do this, your site will sit there all sad and broken for awhile while you panic and stress and maybe even cry as you wring your hands and wait for help to come, and you don’t want that. But you also have to understand those files which you CANNOT just delete, otherwise, you’ll render your blog sad and broken all over again.


A Final Word on GoDaddy

You’ll notice, if you actually managed to read the whole post, that sometimes the GoDaddy tech support people I had to call weren’t giving me 100% perfect information/instructions. Every tech support person there knows their basic GoDaddyWorld facts; some know more personally about how WP blogs work and how databases work. Some are better able to explain techy stuff to a clueless moron such as I was, and some left me more confused. Some fixed one little part of the database restore problem but not all of it (bc GD doesn’t support our database health in transferring from another host and restoring, database programmers are paid big bucks to understand the coding of it). Even though GD could have saved us 3 days of stress & anxiety by giving us the correct help and answers……you’re going to encounter that anytime you have to call any tech support. This doesn’t negate the fact that I still will fully recommend GoDaddy for what they provide to you at the cost they provide it at.


So, please, if you’ve ever gone through backing up, moving blogs, fixing blogs, restoring databases, managing your files thru the hosting control panel and can give information that I got wrong or didn’t list, tell me about it in comments!

Some links to help you further:

How to export the database from PHPMyAdmin: http://codex.wordpress.org/Backing_Up_Your_Database

Some screencaps to illustrate further:


Feb 212010
 

Wondering where I’ve been? This post should give you a good idea. However, this post has nothing to do with sex. It’s pure blogging geek. Feel free to skip this is you’re not a  blogger. If you ARE a blogger? I suggest you read this, and if you’ve got your own contingency plans, share them in the comments.


One day you can be skipping along, tra la la, and all is right in your little bloggy corner of the intarwebz. The next it could all go kablooey and you’re surrounded by rubble goin “WTF just happened and where the hell is my blog?!?!” It can be your own doing, or it could be thanks to a nasty strain of crawler bots that I’ve seen making the rounds lately. I’m going to talk about both situations that I’ve been through this week because it might help someone else.

Part 1: The Sneak Attack Crawler Bots

In the last few weeks, I’ve seen “crawler bots” hit e[lust], Coy Pink, Panthera Pardus and Tied Up Events (as of this writing it’s still being fixed/moved). Each acted a little bit different but the result was the same – they got in through a sidedoor and either inserted a php file, a virus or changed php files. This resulted in redirects (visitor comes to your blog and then gets automatically sent elsewhere), trojan/phishing thingies laying in wait for visitors to arrive, an inoperable WP dashboard, or your hosting provider suspending your account because suspect that YOU are running a phishing site.

The only common thread between the aforementioned sites is that we’re all self-hosted WordPress blogs. Perhaps we all had a plug-in that had a security hole; I’m not really sure. Coy Pink’s wonderful hub Alec helped me get e[lust] back up and running a few days before their site got snagged. On e[lust], according to the log files, the crawler bot came in through my contact form (cformsII) which hadn’t been upgraded in a little while. We know it was a crawler bot because we could see the site who accessed it; visiting their website they claimed to be an SEO crawler, who harmlessly goes through your site and if you want a report on how ot better your SEO, you can email them. Ummmm, they’re doing it without permission. Website Grader does the same thing except you sign-up for it FIRST and give permission and it’s all above-board. The only way that e[lust] was easily saved was because my domain & hosting is through GoDaddy. GoDaddy automatically backs up my site files and keeps at least a few days worth. All we had to do was go into my hosting control panel there and do a restore/rollback to a few days before the crawler bot hit me and changed all my files. Yes, it changed all my files. How did I know? Because in the file manager at GoDaddy I can see the “file last modified” date and it was all the same.

On Monday, Diva was checking her stat counter for her sites and noticed some very odd activity. Namely, IP addresses all over the world were accessing (or trying to access) WP files, some of which didn’t even exist. Somewhere along the line they managed to install something and I think a phishing email was sent out – hence all the attempts from various IP’s. We think it was an email sent because most had no referring site, they just appeared, but one had a referral of an email program. It acted like a virus but yet even a “security scanner” plug in couldn’t detect it. Since she hadn’t checked Stat Counter in a week or two, it wasn’t caught in time. The damage was done. Shortly after it was noticed, their host (Midphase) decided to suspend their site/account while we were trying to get into the file manager control panel. After following Midphase’s instructions of what needed to be done before they’d unsuspend, directories/files that the crawler had created for phishing were deleted…..but it harmed the structure of the database. The WP dashboard was gone. Images were disappearing because database “links” were broken. The site is still there but just barely. Since Midphase charges you $30 to rollback to the night before’s file-snapshot, that did us no good. The day before was also corrupt……plus it was $30. The log files also only went back a day, so we couldn’t learn the origination of the attack. We couldn’t fix the current problem, but we could prevent it from ever happening again, so they’re in the middle of transferring the domain and hosting to Godaddy. Some people might not like Godaddy but I can tell you this: My blogs have never gone down because of server downtime, my ass was saved because of their automatic backing up and free rollback options, and I feel that their control panels are easier to navigate. Plus their hosting deal was less than half the cost of Midphase.



Tonight I am going to be working on e[lust], as we expect TiedUpEvents.com to be fully transferred over to GoDaddy sometime tomorrow. The moment it is, and I can access the file manager, I’ll be restoring their posts (thankfully only a few so we can do it the harder way) and designing them a new theme. This past week though my time was spent trying to fix up the NYC Sex Blogger Calendar site that I designed just a few weeks ago for Tess and Diva. We had found it necessary to transfer the domain and hosting from the name of the blogger who originally set it up over to Diva & Tess and therefore GoDaddy so that I was able to change the theme and design. We didn’t ask the right questions after the transfer was “complete” and as it turned out, we found on Monday while dealing with TUE that SBC had actually not truly transferred. When we were altering the theme, creating new posts, etc we were still accessing the old blog at the old host. I had 4 days of gut-wrenching stress and pins-and-needles while trying to untwist the messes of the funky database export and the lack of some very, very necessary files that would have gotten this all over and done with in half a day instead of 4 (also if all of Godaddy’s tech support people were as knowledgeable as the one who finally helped me get what I need and make it all work together, it wouldn’t have taken 4 days). I’ve learned to never rely fully on anyone now no matter what.  However in Part 2 I want to talk about this kind of a blog mess and how you can prevent it for yourself.


Sep 262009
 

Last Saturday, the floodgates opened for traffic to my blog. This screencap shows Saturday’s hourly numbers – the jump from normal to holymotherofgod!

kristenvisits

While I had already been getting perhaps 50-75 hits a day for the last week from The Kristen Archives, a site containing a monstrous compendium of erotica in all 687 flavors, I wasn’t prepared for what would happen when my site name got featured for a week. Because I have a link to the site over there in my side bar, my blog name was on the site’s referral section at the bottom of the main page (I think it happens automatically as soon as their referral-grabber-bot finds the link). I was pretty close to the bottom of the list even, but still got nice traffic. So on Saturday when my numbers flew through the roof, I kept checking the site wondering what the hell happened. A few of  my friends looked, I checked the site with all 3 browsers that I have, and still nothing showed as being different. Until Sunday when it was then pointed out to me that my blog name was featured up at the top of the site.Why it took us 24 hours to see that, I’m not really sure. I’m confused, honestly. If I thought Saturday was ridiculous, Sunday was even moreso.

kristenvisitsday2

These hourly numbers? That’s what I get on a really good day. A whole day! A few people asked me on Twitter either Saturday or Sunday what the hell was up with my blog because it seemed that every 3rd referral to them in their stat counters was from me. Awesome! For those that have stat counters, what was your traffic boost, I’m curious? I know that watching the exit links showed a whole ton of activity going on from out-clicks of either commenters or those in my blogroll.

I find this all funny for numerous reasons, one of which was that this flood made the one from indienudes.com last November seem small. And I freaked out over that, asked them to move my link from the front page because I was afraid my bandwidth couldn’t handle it or that the numbers would increase my monthly page view numbers to be over the limit for SiteMeter. See, I pay for the premium SiteMeter tracker just because I get a kick out of the statistical things. The price you pay is based on your monthly traffic…..or so I thought. Because back in November I did go over that bottom tier pricing, which is what I pay. In fact I’ve now gone over that number consistenly in the last 4 months but they’ve never billed me anything more. It wouldn’t be a huge increase obviously, but back in November I worried, lol.

sitemeterprices

kristenvisitslast30days


The traffic wasn’t all one-hit-wonders either, a very good percentage poked around for a few pages or 20. I’m not sure of course how many might ever come back. So if you’re still reading and you got here from The Kristen Archives, please comment and say hello :)


Now my numbers are going back down to normal-ish and I can go back to being able to see a weeks worth of stats in my log rather than 1 day, hehe. Fellow bloggers, if you could use a little daily boost in traffic, I suggest you add a link to Kristen in your blogroll.