1. Martin

    Normally when I build sites I get access to the customers webhosting (which you need when making sites live) and just create a random email account using their own domain name just for the purpose of signing up to services like WordPress.com, Akismet, Email marketing services etc etc. I always then just forward emails from that email address to the customers other email address or one of my own emails…

    For storing logins and api’s I just save them in a .doc file along with any other logins and details I have of the clients.

    This system has always worked for me.


  2. Janw Oostendorp

    I’m surprised you didn’t mention the option to add the key to your wp-config.php that way a person with login can’t know the key. They at least need FTP to view that file.

    I know you know about the possibility: http://wpmu.org/how-to-use-akismet-on-wordpress-multisite-with-1-license-key/ ;)


  3. Ryan Hellyer

    Handing out your API key does not seem like a very good idea. Plenty of people do seem to do that though.


  4. Otto

    Create the account for them, or walk them through it, in person, explaining why and the differences.


  5. Jeremy

    Kirk Wight wrote a good post about this a few months ago: Jetpack and WordPress.com accounts

    tl;dr: You’ll want your client to create their own WordPress.com account if they don’t already have one. If you connect Jetpack to your own WordPress.com account, they will still have to link to their account to use features such as Likes, Notifications, or Post by Email.

    It will also make things easier if they ever need some help with their Jetpack site and don’t want to go through you.

    It’s also worth noting that a lot of people may already have an account, if they signed up for Gravatar for example.


  6. Sarah Gooding

    @Jeremy -Thanks for that link – the article does make some very important points about not leaving a client stranded with your login.


  7. Cris.

    I’d go with Ottos comment using Martins method. It’s a courteous way of having your client deeper involved in the project.


  8. Sarah Gooding

    @Cris. – Yes seems like a good way to go about it. I just wasn’t sure whether it’s acceptable to agree to terms of use for someone else.


  9. September 20, 2013: Weekly Roundup of Web Development and Design Resources

    […] How Do You Manage WordPress.com Account Use On Multiple Sites?: Do you use your own WordPress.com account? Or do you set up a WordPress.com account for each of your clients? Sarah Gooding discusses the pros and cons of each approach. […]


  10. Terence Milbourn

    I am surprised nobody has so far mentioned using the API key in the wp-config.php file…

    /** Define WordPress.com API Key */

    That way, your client will never know.


    • Sebastian “Angelo” Cork

      I believe someone did mention it (not in the article) in the second comment. Indeed, this is a possible solution. You’d of course, just have to remember to get them set up with their own account, should your business relationship end and you part ways. In which case, I feel like this might double your work, versus following the advice of Otto and a method similar to what Martin shared.


  11. FuturityWEB

    When I take on a new client, the first thing I get them to agree too, is the creation of a new Gmail Account that will be used for everything related to their WordPress Website. I then use this mailbox to setup their Google Webmaster Tools, Google Analytics, WordPress.com Account (Akismet etc).

    When I hand over the website, I hand over the Gmail Account; This ensures separate API Keys, frees the client up from doing stuff he/she doesn’t want to do and in the end gives them complete freedom to do with the accounts as they please once my job is done (assuming they don’t want me to continue with site maintenance etc)


Comments are closed.

%d bloggers like this: