You often write blog posts that talk about or even promote events that you are planning and hosting. Events can involve either one or several venues, but either way location is usually a big factor. You may or may not have heard of Mapme, but you should probably look into it if these types of blogs are up your alley.
You may also just be discussing a topic or piece of content that has to do with places and locations.
Nowadays (and often in the olden days), readers gravitate towards visual content over written content. For blog posts, that means you want your content and the information it involves to be all the more visual, and less ‘texty’.
But to achieve this, you need visual tools that are super appropriate for your subject matter, and that engage people with your discussion topic uber clearly.
Mapme is built for just that. Mapme tackles content by segmenting location categories and themes, and creating personalized, “smart” maps in a very simple way.
How it’s Done:
a. Think of a map idea that would up your blog post’s engagement factor
b. Sign up for map creation on Mapme.
c. Begin the 3-stage process:
- Create a map
- Choose the borders of your map (the default zoom of your map)
- Choose categories that describe your different places. Label them with a name, icon, and color, all of which you can go back and change whenever.
d. Embed the map on your blog, or wherever you want to engage people.
Other cool features that users can choose to take on:
-Opt to make the map content crowdsourced, so that those interested can directly and add location to your map. You can moderate the locations before they’re added.
-Make reviews available for your map locations, to make your map into a community forum and not only a knowledge base/guide.
-Choose which information fields you want to hide or display with each place: URL, phone number, logos, e-mail, etc.
Don’t forget to share your maps!
Wanna learn how to make more money with your website? Check the Online Profits training program!
from Daily Blog Tips http://ift.tt/1IfqiHE
via IFTTT
No comments:
Post a Comment