Skip to main content

You Can't Get Paid If They Can't Find Your Payment Info

Most of my earned income is made on the internet. I do some website work for local clients in the small town where I live, but most of it comes from resume editing, freelance writing and blogging and all of that gets done online.

Trying to monetize creative work online, like blogging, is a constant challenge. One of the biggest stumbling blocks I keep running into is just trying to make it easy for people to give me money.

It's surprisingly hard to make sure people can readily find that information.

This post was written because I had someone email me and tell me they couldn't find that information ANYWHERE. They had looked!

I verified my payment info for them and asked which of my many websites they had been on while looking for that information and they said it was my personal blog. I thought it was very prominently displayed on my personal blog.

Well, maybe if you are on a PC with a big screen. Not so much if you are on a laptop, tablet or smartphone.

They were on a smartphone, so, for them, that information was hidden behind a "hamburger" drop-down menu. They simply hadn't noticed the "hamburger."

This was someone I had reason to believe was fairly tech savvy, so this was concerning. If they couldn't readily find it, then I had a serious problem.

More than half of all searches these days are performed on a smartphone. So if your mobile website has a problem, you have a big problem because this is probably the primary way your visitors will view your site.

I promptly set out to remedy that. This was how it looked on my PC:


Desktop

But this was how it looked on my cheap smartphone:

Mobile view

You had to click into that "hamburger" menu icon to get to the sidebar where the payment info was:

Sidebar

I tried a few different things, including putting the payment info in its own section between the header and the page menu, which was really ugly and bad UI design:

I then decided to replace the descriptor -- The personal blog of Doreen Traylor -- with the payment information. This seemed to be the best solution for that issue, but it also prompted me to look at some other things going on with the main landing page.

I ultimately did more tweaks, including moving some lower traffic pages from the Page menu to their own section in the sidebar and putting a photo of me in the sidebar in place of where the payment info used to be. This made a big difference in moving important information to prominent positions and deprecating or eliminating other information that is just noise for most people, most of the time.


Final Layout (Mainpage)



Final Layout (Sidebar)



Final Layout, Desktop Version


Popular posts from this blog

Sticky This: See a typo? Submit a pull request.

For the first time ever, I submitted a pull request yesterday to an open source project notifying them of a typo. It was accepted within hours. Submitting the pull request was easy and took almost no time. The process of submitting it gave me valuable prompts, such as "This field is typically no more than 50 characters." I've been on Hacker News for over eleven years. I began wondering how on earth I can contribute to open source as a non-coder a few years back. I've talked to other non-coders who were just as mystified as I was -- or more mystified -- as to how on earth you get into open source as a non coder. So, no, it isn't just me. I spent probably a few hours yesterday trying to sort out how on earth to notify them of their typo. It took me far, far longer to figure out what I needed to do than it took to do it. This is a huge barrier to entry and will stop most people before they begin. Most people simply can't give you three hours of their t

My First Pull Request Was Approved! Huzzah!

A few hours ago, I submitted my first ever pull request . I mean to something other than the Hello World project Github walks you through to show you the basics. It has now been approved by the maintainer and merged. And, wow, I need to get this off my chest: You programmers are completely unnecessarily scaring off non-programmers from your Open Source projects. This is how this went down: I saw a piece on Hacker News that interested me and I opened it up to find that it was a Github repository. I began reading the documentation and noticed a typo. One of the titles said "Funtion" instead of "Function" in it. So I was like "I would like to tell them." Now the last time I wanted to tell someone in Open Source they had a typo, I left a comment on Hacker News to do it. They did fix it and apparently took some of my other advice as well. But this time the article didn't have a lot of comments. It only has two, in fact. So I felt like le

A Lean, (Ever)Green Machine: Website Tips for Small Shops

I've been making little websites to serve up information on various topics for close to two decades. I'm basically a one-woman shop, so my websites have to be lean, evergreen, low cost and low maintenance to make any sense at all. I currently live in a small town and I sometimes attend public meetings where people are enamored of shiny tech but don't know how to use it. They get all envious of projects and talk in glowing terms about "Wouldn't it be GREAT if we did something like that?!" and I bite my tongue and don't say "You have no idea what on earth you are talking about. You have neither the resources nor the expertise to do a project like that." Those experiences inspired me to write this post. I would love to help people in the small town where I live to establish an effective web presence, but I really am going to need to do a lot of educating if that is ever going to happen. Most locals have no idea how to make a website that'