Beginner's guide to Search Engine Optimization (SEO) - SEO Technics and Technical Recommendations

SEO stands for "Search Engine Optimization",  SEO is the process of taking steps to help a website or content rank higher on search engines. It means the process of improving your website to increase its visibility/interaction when people search for products, articles or services related to your requested in Google, Bing, Yahoo and other search engines. The better visibility your pages have in search results.

Search engines provide results for any user requested content or query when enters. So they check and understand the vast network of websites that make up the web. They run a sophisticated algorithm that determines what results to display for each search query.

Below are the SEO Recommendations and start working on Technical SEO

• Find and Fix Broken Images
• Find and Fix Broken Links
• Find and Fix Duplicate H1 Heading
• Find and Fix CSS Error
• Find and Fix JavaScript Error
• Find and Fix HTML Error
• Find and Fix Theme UI/UX
• Find and Fix Mobile Friendly Error
• Use Schema
• Set Sitemap
• Set Robots.txt
• Set Analytics
• Set Google Search Console
• Set Canonical Tag
• Index Issue
• Find and Fix 404 Pages
• Set Redirect Pages
• Set Metadata Box
• Set Site Menu
• Set Site Structure
• Set Permalinks
• Find and Fix Orphan Pages
• Find and Fix thin Content Pages
• Speed Up Your Website
• Use Twitter Card
• Use OG Tag
• Images ALT tags

Onpage SEO

• Use Keywords In The Right Places
• Keep Users On Your Site Longer
• Find "Suggest" Keywords
• Delete Zombie Pages
• Do An Industry Study
• Add Related Keywords to Your Content
• Add Text to Infographics, Podcasts, and Videos
• Update Old Pages
• Keep Users On Your Site Longer
• Create Content Around Shoulder Niches
• Rank In The Featured Snippets
• Improve Your Organic CTR
• Focus on Onpage Content
• Find Long Till Keywords
• Use LSI Keywords
• Create Branded Keywords
• Writing Clickable Post Title
• Writing Readable Meta Title
• Writing compelling Meta descriptions
• Use Internal Link and External Link
• Find Rank Pages for Internal link
• Add “What is X” Definitions to Blog Content
• Use FAQs at the end of Content
• Create a Strategy That Supports Your Business Goals
• Competitor analysis
• Write Content for Home Page, Category Pages, Sub Category Pages, City Pages, Sub City pages, Areas Pages
• If you needed then Write Products Details Descriptions

Off-page SEO

• Get Backlinks From Your Visual Assets
• Find More Outreach Websites
• Getting Content backlinks and inbound links
• Use Sponsor Guest Post
• Social Bookmarking
• Business Profile Links
• Blog Comments
• Question and Ans Websites
• Web 2.o
• Niche Editing
• Create Social Media Profiles
• Update Social Platform
• Slide Share
• Infographic
• Press Release

Local SEO

• Verify Google My Business
• Optimize Google My Business
• Up-to-date Google My Business
• Post content on Google my Business
• Post Products on Google Business
• Post on Business Directory
• Post Images
• Update Events
• Update Offers
• Update Videos

Hope this article is useful for you. If you like please share. If still you have any queries please comment below.

Thankyou

Continue Reading →

How to create simple vertical timeline using HTML and CSS

In this post, we will learn how to build a simple vertical timeline using HTML and CSS from scratch. First, we will create the basic structure with minimal markup and the power of CSS pseudo-elements. We implemented this example without using Javascript and jQuery etc. Please follow the steps to create a basic vertical timeline

Following are the steps to creating HTML and CSS code.

Step 1 : ( Create HTML )

<div class="timeline-wrapper"> 

<ul class="StepProgress">

        <li class="StepProgress-item is-done">

            <div class="bold time">10:00 Am</div> 

            <div class="bold">Step 1</div>

        </li>

        <li class="StepProgress-item is-done">

            <div class="bold time">11:00 Am</div> 

            <div class="bold">Step 2</div>

            <div>Post a contest</div>

        </li>

        <li class="StepProgress-item current">

            <div class="bold time">12:00 Pm</div> 

            <div class="bold">Step 3</div>

        </li>

        <li class="StepProgress-item">

            <div class="bold time">01:00 Pm</div> 

            <div class="bold">Step 4</div>

        </li>

        <li class="StepProgress-item">

            <div class="bold time">02:00 Pm</div> 

            <div class="bold">Step 5</div>

        </li>

    </ul>

</div>

Step 2 : ( Apply CSS Styles to HTML )

<style> 

.bold{font-weight:bold;}

.time{position:absolute; left:-110px;}

.timeline-wrapper {

padding-left:80px;

min-width: 400px;

font-family: 'Helvetica';

font-size: 14px;

/*border: 1px solid #CCC;*/

}

.StepProgress {

position: relative;

padding-left: 45px;

list-style: none;

}

.StepProgress::before {

display: inline-block;

content: '';

position: absolute;

top: 0;

left: 15px;

width: 10px;

height: 100%;

border-left: 2px solid #CCC;

}

.StepProgress-item {

position: relative;

counter-increment: list;

}

.StepProgress-item:not(:last-child) {

padding-bottom: 20px;

}

.StepProgress-item::before {

display: inline-block;

content: '';

position: absolute;

left: -30px;

height: 100%;

width: 10px;

}

.StepProgress-item::after {

content: '';

display: inline-block;

position: absolute;

top: 0;

left: -37px;

width: 12px;

height: 12px;

border: 2px solid #CCC;

border-radius: 50%;

background-color: #FFF;

}

.StepProgress-item.is-done::before {

border-left: 2px solid green;

}

.StepProgress-item.is-done::after {

/*content: "?";*/

font-size: 10px;

color: #FFF;

text-align: center;

border: 2px solid green;

background-color: green;

}

/*.StepProgress-item.current::before { 

border-left: 2px solid green;

}

.StepProgress-item.current::after {

content: counter(list);

padding-top: 1px;

width: 19px;

height: 18px;

top: -4px;

left: -40px;

font-size: 14px;

text-align: center;

color: green;

border: 2px solid green;

background-color: white;

}*/

.StepProgress strong {

display: block;

}

</style>

I hope you like this article very much & Please don't forget to share.

Thank you.

Continue Reading →

How to display thumbnail preview link on whatsapp

Hai Folks,

In this article i will explain how to display thumbnail preview link on whatsapp with simple steps. and i ll add example screens in soon. In previous article How to share content on whatsapp using jQuery ( Title, Link,  Thumbnail etc.. ) we can see how to share content like Title, Description, Any links etc using whatsapp.

For this there is a concept meta tags in html. By using this meta tags we can easily add title, thumb, description, site name etc. you need to add these meta tags in side of <head> </head> section. After you have changed your meta tags, you might need to wait a while for possible caches to update.

The following meta tags are used for solve the problem:

<meta property="og:site_name" content="Site-Name-Here">
<meta property="og:title" content="Site-Title-Here" />

<meta property="og:description" content="Site-Description-Here" />
<meta property="og:image" itemprop="image" content="Image_url here">
<meta property="og:type" content="website" />
<meta property="og:updated_time" content="1440432930" />

The meta tag property og:image is enough for getting thumbnail.

If you still facing problem after adding above tags you can add following two kind of code in your page.

First, Add meta tag og:image inside of <head> </head> section.

<meta property="og:image" content="url_image">

Second, Thumbnail schema from schema.org inside <body> section

<link itemprop="thumbnailUrl" href="Image_url here"> 

<span itemprop="thumbnail" itemscope itemtype="http://schema.org/ImageObject"> 
      <link itemprop="url" href="Image_url here"> 
</span>

I hope you like this article very much & Please don't forget to share.

Thankyou.

Continue Reading →

How to create email template ? (or) Email template design techniques

HTML Email Tips for Web Designers

how do I get started designing HTML email? Any tips for the more advanced user?

If you're a web designer, and you know your stuff,  and give you a quick, no-nonsense "Quick Start Guide" to HTML Email...

HTML Design and Coding Tips:

• HTML Email should be sent in "multipart-alternative" format. That means the email is embedded with both the plain-text version, and the HTML version, of the message. When people can't (or won't) view HTML email, the plain-text version displays instead. That's the main reason to use a system like MailChimp, Constant Contact, GotMarketing, etc.
• You can try to code your own script to send multipart-alternative email. Use Google to research how. Then, after you've pulled out all your hair, yelled at your mom, and kicked your dog out of frustration, use one of the tools we listed above. Because even if you figure out how to deliver in multipart, you still need open, click, and bounce handling scripts, plus an email server that sends authenticated messages.
• Image files don't get sent along with HTML email as attachments. You host images on your server, then code the HTML in your email to point to them with absolute paths. In other words, you code something like this: <img src="http://www.yourserver.com/images/image.gif"> instead of like this: <img src="../images/image.gif">
• Design for the preview pane of email applications. That means you've got about 500, 600 pixels tops for your email designs. If you think recipients will actually double click an email to view your message in full screen "to appreciate all its glory," send us whatever you're smokin.
• You know how with web pages, you can use CSS to position things, and "separate content from appearance" and all that? Yeah, that won't work in email applications. Think back to the old days of the browser wars. When Netscape and Microsoft were duking it out. There was no Flash plugin. It was only shockwave. Put away your DIVs and DHTML. Dust off those tables, shim.gifs, and font tags, because you're gonna need 'em. Fancy CSS (especially DIVs and positioning) won't work reliably.
• When you code a web page, you test it in IE, Firefox, and Safari, right? And you kind of learned to "leave a little wiggle room" so that your designs work across all browsers. Well, when you code an HTML email, you have to test it in Lotus Notes, Outlook 2003, Outlook 2000, Outlook Express, Apple Mail, Apple Entourage, Eudora, Mozilla Thunderbird, AOL, Yahoo!Mail, Yahoo!Mail Beta, Google's Gmail, Hotmail, Earthlink, Comcast, etc (here's a bare-minimum checklist for ya). And yeah, they all display HTML email a little different. When we say, "Keep your HTML email simple," we really mean it. Update: If you'd like to test your email design and code in one easy click, check out our new Inbox Inspector tool.
• You can use a little CSS, such as for basic fonts and colors. But use it sparingly, and design things to fail gracefully.
• Use inline CSS, not linked files. Unlike images, linking to a server-hosted CSS file isn't that reliable.
• When you embed your CSS, embed it below the BODY tag because browser-based email applications (like Gmail, Hotmail, Yahoo!Mail, etc) strip out your HTML, HEAD, and BODY tags so they won't interfere with their own web page.
• Don't ever let any lines in your email or HTML code begin with a period. Some email servers interpret lines that begin with periods as the, "end of message" command, so your email will get stripped anywhere below that line (example). So be extra careful in your embedded CSS. Add spaces before any lines of your CSS that start with a period.
• JavaScript, ActiveX, Flash, and embedded movie files won't work. Don't shoot the messenger---we're just telling you the truth. The reason they won't work reliably is just about everybody has anti-virus applications that block that stuff from running.
• Background colors. Remember how we said that most browser based email applications (like HotMail) strip out your BODY tag? That's why assigning background colors to your BODY won't always work. The most reliable way of giving a background color to your email is to wrap it all inside a big, 100% wide table, and give the table cell a bgcolor. We warned you, HTML email is "old school."
• Don't forget your plain-text version. When web designers create HTML email, they often neglect the plain-text versions (they treat it like image ALT text, or META tags---always a pesky afterthought). But plain-text emails are very important. If you neglect them, some spam filters will even think you're a sloppy coder, and throw your mail into the junk folder.
• Tips for plain-text emails? You get absolutely no formatting. This is super old school. Hard wrap them at about 60 or 70 characters. Use a plain-text editor (not Microsoft Word), and type a letter (I like the letter "W") across the top of the document about 60 times. That's your ruler. When you type your message and get to the end of the ruler, hit return (more tips). 

About Spam Filters

• You need a good balance of "graphics vs. text." Otherwise, spam filters will get you. Don't send one ginourmous graphic. Balance it out with some copy, especially your company contact information and unsubscribe link. If you send one ginormous image as your HTML email, it can get you blacklisted.
• Don't write like a spammer. Watch those exclamation points, and FOR THE LOVE OF GOD, DON'T YELL in your email (learn how spam filters think).
• Don't get sloppy with your code, because spammers are sloppy with their code. Close those table cells and font tags.
• Don't use spammy looking colors, like HUGE SALE! and CLICK NOW!.
• Web designers will like this one: some spam filters will punish you for using FrontPage (or other WYSIWYG tools) to code your HTML email. So strip out any of that useless META stuff that those applications produce (more funny spam assassin criteria).
• Sending test emails to your client? If it's a fairly large corporation, their IT group probably has a spam firewall in place, and your test campaigns might get blocked. You may have to ask their IT geeks (politely) to whitelist your email service provider. Many of them throttle emails from new/unknown sending servers if they receive more than 2 or 3 messages at once. 
• When you code a web page, you probably use "lorem ipsum" dummy text, right? If you do that with email, some Bayesian spam filters might block you (example). Same thing happens when you just paste a bunch of placeholder text over and over in your email. Go grab real copy from somewhere instead. Avoid the word "test."

Every Email Campaign Should Have...

• An instantly recognizable from-name and reply-to address. Use your company name, for instance. Then, don't change it, because recipients might have whitelisted you.
• A good, descriptive subject line that's not spammy. You've got a split second to convince recipients that your message isn't junk.
• A one-click unsubscribe link. Consider placing it at the top of your email, not the bottom.
• Your "offline" contact information, including your physical mailing address, phone number, etc. It will help people remember who you are (subscribers forget you in 6 months) and they might trust your unsubscribe link more, instead of reporting your email as spam.

Continue Reading →