// best practices for good posts

Good postings give you good SEO (search engine optimization) and result in a cleaner more informative site.

1. Create good SEO (search engine optimization)

Always use actual text vs. text in images in any post on your website.

This is crucial if you want search engines to be able to see your postings. Search engines can’t see text in images. The more postings are done correctly the better you will rank in search engines. Although there are many factors that play a role with SEO (search engine optimization) this is just one but it’s an important one.

If you’ve created a JPG for your invitation that included the text for the even details, you need to grab that text so it can be placed in the postings on your site as text along side any images you include.

This doesn’t mean no text in images. It just mean the event info should also be in the post as just text outside of what is in the image.

2. Clean POSTS

Clean postings result in a cleaner more informative site.

Samples of good postings

– The image shows a suggestion of what the even it about.
– The title underneath it spells it out
– Date – including a date lets people instantly see if the even is still on or not

Let than ideal postings

Text heavy images cause the over all look of your NEWS page or BLOG to be more cluttered
while the information is less clear.

I cleaned up the one on the left but text images over all are less appealing.

Also with text images you have to worry about which device the posting is being viewed on. While the text image might look ok on a computer screen it might look tiny or illegible on a phone.

Text outside of an image will adapt for optimal viewing all devices.

For the header image, instead of using the invite JPG you might have created for your announcement use an image without text . This allows for the visitor to get a feel for what the posting is about without shouting at them.
If all postings have text images we are left with less visuals and more clutter and chaos without optimally communicating.

See this example here