You’re setting up your blog with the hopes and expectation it will be seen by someone other than you. Otherwise, you’d just keep an old-fashioned journal in hardcopy format (or perhaps in a Word document).
And, as we all know, Google can help with that — IF Google wants to, that is. And Google doesn’t always want to. It depends on a lot of things, like how popular your site already is, what other popular and well-respected (by Google) sites think of it (by linking to it), and so forth. And, as I mentioned the other day, how “sticky” your site is counts too.
One of the lesser-known “requirements” for getting Google to give a hoot about your site is whether or not you have the specific information Google wants all serious websites to have in the form of certain content almost always provided on separate navigable Pages. And surfers have come to rely on and look for such information to help them find out what they feel they need to about your blog as well.
Without further ado here’s what you need, and a few ideas about where to get them:
About – Can only be written by you: Who, What, When, Where, and don’t forget to add a photo
Contact Us - Contact 7 Plug-In (Free)
DMCA Policy – A whole page of various generators
Terms Of Service – Terms of Service and Privacy
ALSO SEE: Site Disclaimer generator and Disclosure Policy Generator
There! That should keep you busy for a few hours. (smile)
Oh! Another important inclusion, which needn’t be public but sometimes is, is a Site Map. This is something Google depends on for its work in scoping out your blog. The one I use is a free plug-in: Google (XML) Sitemaps Generator for WordPress It’s one of those set-it-and-forget-it plug-ins that just quietly does its work in the background. If you want a publicly available site map, I’m sure there are plenty out there to choose from.
Now by all means, if you know of better or just additional resources for any of these, please share them with us, eh?
UPDATE: Commenter Sue Neal was kind enough to remind me about Financial Disclosure or Disclaimers. That had been in the back of my mind, but I let it elude me. Good thing she mentioned it, too, because I’d been under the impression that I was covered on that, but I wasn’t. Here’s a good Disclosure Policy generator, but you can formulate your own copy as well, which I did and added it to my About Page. Thanks, Sue!!
Stay tuned: Next time I plan to disclose what I consider essential plug-ins, many of which are completely different from what I’ve seen listed elsewhere.