Showing posts with label how to. Show all posts
Showing posts with label how to. Show all posts

Monday, September 26, 2022

Advertising on Meta Business Suite Belonging to Facebook Social Media Networking Site

Introduction to Facebook 

With 2.93 billion monthly active users Facebook needs no introduction. FB has become a household name worldwide and is the leading social media networking site. It was started in the year 2004 by Mark Zuckerberg from the USA. 

Facebook is the number one site for social networking, and it nurtures virtual relationships between family and friends daily in cyberspace. To describe it as a living platform would be apt as the social site has become a virtual extension of our lives.     

Though entirely meant for personal networking FB today has become a major commercial entity and the FaceBook Pages facilitate advertisement on the platform.  Facebook is now Meta and advertisements on Meta in the year 2020 earned a revenue of 80 billion plus dollars. 

How to Advertise on Meta?

Meta Business Suite

(https://business.facebook.com/)

Meta Platforms now comprise FaceBook, Instagram & WhatsApp and enable advertisement using one common business suite known as Meta Business Suite. The suite allows the integration of FaceBook and Instagram messaging platforms for the purpose of online Ads in one place. Yes, the suite allows response to messages and notifications and the facility to post stories or content based on a content calendar. You can also manage ads using Meta Business Suite. 

Posting Ads on Meta Business Suite

You can make simple posts that could be shared on Facebook and Instagram Platforms after you have linked with each. There is an option to add links, videos, or photos to your post and stories. You can post immediately or use the content calendar to schedule posts, stories, and Ads. The business suite provides a calendar to meticulously post as desired based on suitable events, festivals, and weekends for example.  

You can place ads based on demographics, location, gender, and profession and limit them to a certain area where you wish your ads should be visible. 

But first, you must set the goal among the options given:

  • Get more messages
  • Get more calls
  • Get more leads
  • Get greater engagement
  • Get more traffic 
  • Automatic

Audience

Next, you must choose the audience type

  • Student
  • Local Residents 
  • People who like your page 
  • People who like your page and similar pages
  • People you choose to target
There are options to choose more audience types when you click on the create new button below you get a list of options based on interest, demographic, and behaviors whence you click on the browse button. For greater targeting options you can click on the Ads Manager for more options:
  • Create Custom Audience
  • Create Saved  Audience
  • Create Lookalike Audience 
Insights 

There is an option to use meta pixel as well to get a better idea of how your ad is performing. 

Ad Spend & Duration 

Here you can specify the ad spend and duration the amount of money you deposit with Facebook will limit your ad display.  Before your ads begin to show you must specify the mode of payment and deposit the required amount at the meta business suite.  

Pathway for Marketing Solutions

All ads utilize the same funnel for achieving the goal Meta offers many types of Ads that can be used suitably. Ads can be displayed across 15 platforms for wider coverage. The sales funnel works exactly like that used everywhere.

  • Attraction or Awareness
  • Engagement or Consideration 
  • Goal Conversion or Action   
Advertisers can use plain text with appealing headlines, photos, or videos. Unlike Google Ads Meta of Facebook ads is not shown in the search but nevertheless, the phenomenal user base is enough to make all advertisement campaigns a huge success.  Facebook's amazing targeting methodology, ads-related tools, and management capabilities are best suited to boost your business to reach incremental growth. 

Using the Facebook Audience Network you can reach the target audience on high profile promising mobile apps as well. The highly rated and secure network is visited by over one billion users every month.  Those businesses seeking higher reach must include Audience Network in the mix of placement on the Facebook or Meta Advertisement Platforms.  

===================
Uday works at Above The Fold Company based in Mumbai. The company provides marketing solutions for advertisements on social media. Uday works as SEO & Content Writer at ATF. 
He can be contacted at pateluday90@hotmail.com ...9755089323
Author

9755089323 

Tuesday, March 22, 2016

AMP HTML Specification

This article has been picked up for readers...due credit is given to the source linked below.  

AMP HTML is a subset of HTML for authoring content pages such as news articles in a way that guarantees certain baseline performance characteristics.

Being a subset of HTML, it puts some restrictions on the full set of tags and functionality available through HTML but it does not require the development of new rendering engines: Existing user agents can render AMP HTML just like all other HTML.

Also, AMP HTML documents can be uploaded to a web server and served just like any other HTML document; no special configuration for the server is necessary. However, they are also designed to be optionally served through specialized AMP serving systems that proxy AMP documents. These documents serve them from their own origin and are allowed to apply transformations to the document that provide additional performance benefits. An incomplete list of optimizations such a serving system might do is:
  • Replace image references with images sized to the viewer’s viewport.
  • Inline images that are visible above the fold.
  • Inline CSS variables.
  • Preload extended components.
  • Minify HTML and CSS.
AMP HTML uses a set of contributed but centrally managed and hosted custom elements to implement advanced functionality such as image galleries that might be found in an AMP HTML document. While it does allow styling the document using custom CSS, it does not allow author written JavaScript beyond what is provided through the custom elements to reach its performance goals.
By using the AMP format, content producers are making the content in AMP files available to be crawled (subject to robots.txt restrictions), cached, and displayed by third parties.

Performance

Predictable performance is a key design goal for AMP HTML. Primarily we are aiming at reducing the time until the content of a page can be consumed / used by the user. In concrete terms this means that:
  • HTTP requests necessary to render and fully layout the document should be minimized.
  • Resources such as images or ads should only be downloaded if they are likely to be seen by the user.
  • Browsers should be able to calculate the space needed by every resource on the page without fetching that resource.

The AMP HTML format

Sample document



<!doctype html>
<html >
  <head>
    <meta charset="utf-8">
    <title>Sample document</title>
    <link rel="canonical" href="./regular-html-version.html">
    <meta name="viewport" content="width=device-width,minimum-scale=1,initial-scale=1">
    <style amp-custom>
      h1 {color: red}
    </style>
    <script type="application/ld+json">
    {
      "@context": "http://schema.org",
      "@type": "NewsArticle",
      "headline": "Article headline",
      "image": [
        "thumbnail1.jpg"
      ],
      "datePublished": "2015-02-05T08:00:00+08:00"
    }
    </script>
    <script async custom-element="amp-carousel" src="https://cdn.ampproject.org/v0/amp-carousel-0.1.js"></script>
    <style amp-boilerplate>body{-webkit-animation:-amp-start 8s steps(1,end) 0s 1 normal both;-moz-animation:-amp-start 8s steps(1,end) 0s 1 normal both;-ms-animation:-amp-start 8s steps(1,end) 0s 1 normal both;animation:-amp-start 8s steps(1,end) 0s 1 normal both}@-webkit-keyframes -amp-start{from{visibility:hidden}to{visibility:visible}}@-moz-keyframes -amp-start{from{visibility:hidden}to{visibility:visible}}@-ms-keyframes -amp-start{from{visibility:hidden}to{visibility:visible}}@-o-keyframes -amp-start{from{visibility:hidden}to{visibility:visible}}@keyframes -amp-start{from{visibility:hidden}to{visibility:visible}}</style><noscript><style amp-boilerplate>body{-webkit-animation:none;-moz-animation:none;-ms-animation:none;animation:none}</style></noscript>
    <script async src="https://cdn.ampproject.org/v0.js"></script>
  </head>
  <body>
    <h1>Sample document</h1>
    <p>
      Some text
      <amp-img src=sample.jpg width=300 height=300></amp-img>
    </p>
    <amp-ad width=300 height=250
        type="a9"
        data-aax_size="300x250"
        data-aax_pubname="test123"
        data-aax_src="302">
    </amp-ad>
  </body>
</html>

Required markup

AMP HTML documents MUST
  • start with the doctype <!doctype html>. 🔗
  • contain a top-level <html > tag (<html amp> is accepted as well). 🔗
  • contain <head> and <body> tags (They are optional in HTML). 🔗
  • contain a <link rel="canonical" href="$SOME_URL" /> tag inside their head that points to the regular HTML version of the AMP HTML document or to itself if no such HTML version exists. 🔗
  • contain a <meta charset="utf-8"> tag as the first child of their head tag. 🔗
  • contain a <meta name="viewport" content="width=device-width,minimum-scale=1"> tag inside their head tag. It’s also recommend to include initial-scale=1 (1). 🔗
  • contain a <script async src="https://cdn.ampproject.org/v0.js"></script> tag inside their head tag. 🔗
  • contain the AMP boilerplate code in their head tag. 🔗
(1) width=device-width,minimum-scale=1 is required to ensure GPU rasterization is enabled.

Metadata

It is encouraged that AMP HTML documents are annotated with standardized metadata: Open Graph Protocol, Twitter Cards, etc.
We also recommend that AMP HTML documents are marked up with schema.org/CreativeWork or any of its more specific types such as schema.org/NewsArticle or schema.org/BlogPosting.

HTML Tags

HTML tags can be used unchanged in AMP HTML. Certain tags have equivalent custom tags (such as <img> and <amp-img>) and other tags are outright prohibited:
Tag Status in AMP HTML
script Prohibited unless the type is application/ld+json. (Other non-executable values may be added as needed.) Exception is the mandatory script tag to load the AMP runtime and the script tags to load extended components.
base Prohibited
img Replaced with amp-img.
video Replaced with amp-video.
audio Replaced with amp-audio.
iframe Replaced with amp-iframe.
frame Prohibited.
frameset Prohibited.
object Prohibited.
param Prohibited.
applet Prohibited.
embed Prohibited.
form Prohibited. Support coming in the future.
input elements Prohibited. Includes input, textarea, select, option. Notably, button element is allowed.
button Allowed.
style Required style tags for adjusting opacity. One additional style tag is allowed in head tag for the purpose of custom styling. This style tag must have the attribute amp-custom. [🔗](https://github.com/ampproject/amphtml/blob/master/spec/#cust)
link rel values registered on microformats.org are allowed. If a rel value is missing from our whitelist, please submit an issue. stylesheet and other values like preconnect, prerender and prefectch that has side effects in the browser are disallowed. There is a special case for fetching stylesheets from whitelisted font providers.
meta The http-equiv attribute is banned. Otherwise allowed.
a The href attribute value must not begin with javascript:. If set, the target attribute value must be _blank. Otherwise allowed. [🔗](https://github.com/ampproject/amphtml/blob/master/spec/#ancr)
svg Most SVG elements are allowed.
Validator implementations should use a whitelist based on the HTML5 specification with the above tags removed. See AMP Tag Addendum.

Comments

Conditional HTML comments are not allowed.

HTML attributes

Attribute names starting with on (such as onclick or onmouseover) are disallowed in AMP HTML. The attribute with the literal name on (no suffix) is allowed.
The style attribute must not be used.
XML-related attributes, such as xmlns, xml:lang, xml:base, and xml:space are disallowed in AMP HTML.
The javascript: schema is disallowed.

Stylesheets

Major semantic tags and the AMP custom elements come with default styles to make authoring a responsive document reasonably easy. An option to opt out of default styles may be added in the future.

@-rules

The following @-rules are allowed in stylesheets:
@font-face, @keyframes, @media, @supports.
@import will not be allowed. Others may be added in the future.

Author stylesheets

Authors may add custom styles to a document using a single <style amp-custom> tag in the head of the document.

Selectors

The following restrictions apply to selectors in author style sheets:
Universal selector
The universal selector * may not be used in author stylesheets. This is because it can have negative performance implications and could be used to circumvent the rules set out in the following paragraph.
not selector
:not() may not be used in selectors because it can be used to simulate the universal selector.
Pseudo-selectors, pseudo-classes and pseudo-elements
Pseudo-selectors, pseudo-classes and pseudo-elements are only allowed in selectors that contain tag names and those tag names must not start with amp-.
Example OK: a:hover, div:last-of-type
Example not OK: amp-img:hover, amp-img:last-of-type
Class and tag names
Class names, in author stylesheets, may not start with the string -amp-. These are reserved for internal use by the AMP runtime. It follows, that the user’s stylesheet may not reference CSS selectors for -amp- classes and i-amp tags. These classes and elements are not meant to be customized by authors. Authors, however, can override styles of amp- classes and tags for any CSS properties not explicitly forbidden by these components’ spec.
To prevent usage of attribute selectors to circumvent class name limitations it is generally not allowed for CSS selectors to contain tokens and strings starting with -amp- and i-amp.

Important

Usage of the !important qualifier is not allowed. This is a necessary requirement to enable AMP to enforce its element sizing invariants.

Properties

These CSS properties are permanently banned:
  • behavior
  • -moz-binding
The following properties are currently blacklisted due to performance concerns:
  • filter
AMP only allows transitions and animations of properties that can be GPU accelerated in common browsers. We currently whitelist: opacity, transform (also -vendorPrefix-transform).
In the following examples <property> needs to be in the whitelist above.
  • transition <property> (Also -vendorPrefix-transition)
  • @keyframes name { from: {<property>: value} to {<property: value>} } (also @-vendorPrefix-keyframes)
overflow (and overflow-y, overflow-x) may not be styled as “auto” or “scroll”. No user defined element in an AMP document may have a scrollbar.
Maximum size
It is a validation error if the author stylesheet is larger than 50,000 bytes.

Custom fonts

Authors may include stylesheets for custom fonts. The 2 supported methods are link tags pointing to whitelisted font providers and @font-face inclusion.
Example:


<link rel="stylesheet" href="https://fonts.googleapis.com/css?family=Tangerine">
Font providers can be whitelisted if they support CSS-only integrations and serve over HTTPS. The following origins are currently allowed for font serving via link tags:
  • https://fast.fonts.net
  • https://fonts.googleapis.com
IMPLEMENTERS NOTE: Adding to this list requires a change to the Google AMP Cache CSP rule.
Authors are free to include all custom fonts via a @font-face CSS instruction via their custom CSS. Fonts included via @font-face must be fetched via the HTTP or HTTPS scheme.

AMP runtime

The AMP runtime is a piece of JavaScript that runs inside every AMP document. It provides implementations for AMP custom elements, manages resource loading and prioritization and optionally includes a runtime validator for AMP HTML for use during development.
The AMP runtime is loaded via the mandatory <script src="https://cdn.ampproject.org/v0.js"></script> tag in the AMP document <head>.
The AMP runtime can be placed into a development mode for any page. Development mode will trigger AMP validation on the embedded page, which will emit the validation status and any errors to the javascript developer console. Development mode may be triggered by appending #development=1 to the URL of the page.

Resources

Resources such as images, videos, audio files or ads must be included into an AMP HTML file through custom elements such as <amp-img>. We call them managed resources because whether and when they will be loaded and displayed to the user is decided by the AMP runtime.
There are no particular guarantees as to the loading behavior of the AMP runtime, but it should generally strive to load resources quickly enough, so that they are loaded by the time the user would like to see them if possible. The runtime should prioritize resources currently in viewport and attempt to predict changes to the viewport and preload resources accordingly.
The AMP runtime may at any time decide to unload resources that are not currently in viewport or reuse the resource containers such as iframes to reduce overall RAM consumption.

AMP Components

AMP HTML uses custom elements called, “AMP components” to substitute built-in resource-loading tags such as <img> and <video> and to implement features with complex interactions such as image lightboxes or carousels.
See the AMP component spec for details about supported components.
There are 2 types of supported AMP components:
  1. Built-in
  2. Extended
Built-in components are always available in an AMP document and have a dedicated custom element such as <amp-img>. Extended components must be explicitly included into the document.

Common attributes

layout, width, height, media, placeholder, fallback

These attributes define the layout of an element. The key goal here is to ensure that the element can be displayed and its space can be properly reserved before any of the JavaScript or remote resources have been downloaded.
See the AMP Layout System for details about the layout system.

on

The on attribute is used to install event handlers on elements. The events that are supported depend on the element.
The value for the syntax is a simple domain specific language of the form:


eventName:targetId[.methodName[(arg1=value, arg2=value)]]
Example: on="tap:fooId.showLightbox"
If methodName is omitted the default method is executed if defined for the element. Example: on="tap:fooId"
Some actions, if documented, may accept arguments. The arguments defined in the parenthesis in the key=value notation. The accepted values are:
  • simple unquoted strings: simple-value;
  • quoted strings: "string value" or 'string value';
  • boolean values: true or false;
  • numbers: 11 or 1.1.

Extended components

Extended components are components that do not necessarily ship with the AMP runtime. Instead they must be explicitly included into the document.
Extended components are loaded by including a <script> tag in the head of the document like this:


<script async custom-element="amp-carousel" src="https://cdn.ampproject.org/v0/amp-carousel-0.1.js"></script>
The <script> tag must have an async attribute and must have a custom-element attribute referencing the name of the element.
Runtime implementations may use the name to render placeholders for these elements.
The script URL must start with “https://cdn.ampproject.org” and must follow a very strict pattern of /v\d+/[a-z-]+-(latest|\d+|\d+.\d+).js.
URL
The URL for extended components is of the form:


https://cdn.ampproject.org/$RUNTIME_VERSION/$ELEMENT_NAME-$ELEMENT_VERSION.js

Versioning
Extended components are versioned via semver. The version is referenced explicitly (See $ELEMENT_VERSION above) when loading the component in the URL. It may have the value “latest”. Changes to the PATCH version component (x in 1.1.x) must strictly maintain backward compatibility or fix urgent security issues.
AMP documents may only reference versions with one or two components. Version “1” states “I accept every version of this component with major version 1”. Version “1.1” states “I accept every PATCH level of 1.1”. It is now allowed to explicitly reference the PATCH level in the version string.

Extended templates

Templates render HTML content based on the language-specific template and provided JSON data.
See the AMP template spec for details about supported templates.
Extended templates are not shipped with the AMP runtime and have to be downloaded just as with extended elements. Extended components are loaded by including a <script> tag in the head of the document like this:


<script async custom-template="amp-mustache" src="https://cdn.ampproject.org/v0/amp-mustache-0.1.js"></script>
The <script> tag must have an async attribute and must have a custom-template attribute referencing the type of the template. The script URL must start with “https://cdn.ampproject.org” and must follow a very strict pattern of /v\d+/[a-z-]+-(latest|\d+|\d+.\d+).js.
The templates are declared in the document as following:


<template type="amp-mustache" id="template1">
  Hello !
</template>
The type attribute is required and must reference a declared custom-element script.
The id attribute is optional. Individual AMP elements discover their own templates. Typical scenario would involve an AMP element looking for a <template> either among its children or referenced by ID.
The syntax within the template element depends on the specific template language. However, the template language could be restricted within AMP. For instance, in accordance with the “template” element, all productions have to be over a valid well-formed DOM. All of the template outputs are also subject to sanitizing to ensure AMP-valid output.
See documentation for a specific extended template on the syntax and restrictions.
URL
The URL for extended components is of the form:


https://cdn.ampproject.org/$RUNTIME_VERSION/$TEMPLATE_TYPE-$TEMPLATE_VERSION.js

Versioning
See versioning of custom elements for more details.

Security

AMP HTML documents must not trigger errors when served with a Content Security Policy that does not include the keywords unsafe-inline and unsafe-eval.
The AMP HTML format is designed so that is always the case.
All AMP template elements must go through AMP security review before they can be submitted into AMP repository.

SVG

Currently, the following SVG elements are allowed:
  • basics: “svg”, “g”, “path”, “glyph”, “glyphRef”, “marker”, “view”
  • shapes: “circle”, “line”, “polygon”, “polyline”, “rect”
  • text: “text”, “textPath”, “tref”, “tspan”
  • rendering: “clipPath”, “filter”, “linearGradient”, “radialGradient”, “mask”, “pattern”, “vkern”, “hkern”
  • special: “defs” (all children above are allowed here), “symbol”, “use”
  • aria: “desc”, “title”
As well as these attributes:
  • “xlink:href”: only URIs starting with “#” are allowed
  • “style”

AMP document discovery

If AMP documents are alternative representations of a canonical document, then the canonical document should point to the AMP document via a link tag with the relation “amphtml”.
Example:


<link rel="amphtml" href="https://www.example.com/url/to/amp/document.html">
The AMP document itself is expected to point back with its canonical relation to a document that has the “amphtml” relation.
Note, that AMP document may also be linked to directly. The mechanism described here provides a standardized way for software to discover whether an AMP version exists for a canonical document.

Source: AMP HTML Specification 

Friday, August 14, 2015

Making a Mobile Friendly Website

There is a tremendous increase in mobile phone usage all over the World. This along with technology that allows website visibility on the phone more and more users are searching online. The design and development of websites differs whence the screening is concerned on mobiles.  


The mobile friendly features can be incorporated in a manner such that the friendliness relates to its screening on our desk top as well as on our handsets.


It is well known fact that search engine algorithms have difficulty assessing Java Scrips and Flash Pages. The latter also drags down the websites and slows their downloading speed. Hence these elements have to be avoided or restricted.


Fetch as Google is an ideal tool in webmaster to ascertain that the sites is being indexed properly. Another useful element is the robot.txt file which enable search engines to accept or neglect pages for indexing. In case robot txt file is not incorporated than that means no pages are restricted.  


Xml site map is another useful website element that help SE robots to find pages to index.  


Some other points of interest are:


Link are too close


Fonts  are not of proper size (Small or Too Large)


Viewport is not configured. 


Configuring viewports meta tag file


<meta name=viewport content="width=device-width, initial-scale=1">



View port also controls device pixels,hardware pixels and CSS pixels.



The content of your pages should fit within the size specified in the viewport.  




Sunday, February 9, 2014

Using The Disavow Tool

Link Building phenomenon shot sky high when in the initial stages of search engine proliferation on the Internet began. Sergey Mikhaylovich Brin & Larry Page created the algorithmic wonder that is Google. The information retrieval system simply fetches what you are seeking online or on the Internet. 

Since the phenomenal growth of search engine usage there is a constant effort to improve the information retrieval system. This has resulted in lot of updates, additions and changes in the evolutionary algorithms that are used for indexing and ranking by Google.  This very evolutionary impact has unnerved lot of webmasters or seo experts who are actually the people behind with an important role to play in the future of search practices on the Internet. The frequent updates have baffled many webmasters and have critically challenged their optimization skills time and time again. With every change the search engines force compliance to their guidelines some of which are penny pricking.    

The evolution of search engine began from Brin's data mining which eventually lead to Google. The earlier algorithm relied heavily on keywords on page as well as external links pointing to the site. Both factors created a revolution and are still relevant albeit diluted. The search engine look for greater signals now whence indexing and ranking websites and blogs as response to the user query or the search term.  The complexity of the metrics of this highly evolved system in recent times has made it difficult for many webmasters to overcome.   

The heavily relied upon link building campaigns have now become more difficult with links being classified by search engines as bad, weak, good and strong. A greater understanding of the web has been called to picture. The search engines since inception have created an industry around them with link building being the most popular. It takes little to realize that things will not always remain the same hence the industry has to follow the changing dynamics.  Webmasters with shallow knowledge base will go down the history lane. 

Inadvertently search engine optimization will always rely on external link building untill unless the search engines systems take over the ranking game totally and make organic search sterile.  The smart operators realize very well the role web masters play in popularity of their search engines. Those who do not will linger behind for every and keep their search offerings to themselves however good.      

Unlike earlier times link evaluation has become more critical and a bad link creation can pull your site down on the SERP on primary term. This means developing skills to evaluate the link building exercise as well as to evaluate the platform.  The number game has some importance left still but an equatable platform has been created for those who cannot indulge in massive link building campaigns like the big firms.

It is not only the link wheel or the keyword profile that counts the source counts as well. Association with relevant, unique content and editorial scrutiny is a must for a link to gain juice - as referred in seo parley.  

Sensible quality link building is the need of the hour. This does not mean all papers should have scholarly  impact. People are searching the Net for basic information relevant on day to day basis to quench their information need. A scholarly paper has less importance for average searcher who is more on the Net for curiosity sake "Net Gossip" as I call it.

Hence large link building campaigns have resulted in trash which after the release of Panda and Penguin have become internecine. The bad link profile earlier innocuous has now become short of auto immunity disease. Therefore it has become necessary to get rid of as many bad links as possible. In order to assist the webmasters Google has introduced the Disvow Tool.    

Using the Disavow tool webmasters or website owners can remove unwanted back links that are pulling their site down on SERPs.  For this purpose the links that have to be removed have to be uploaded is a text file to the disavow tool online. Removing bad links will also mean removal of oft repeated anchor texts which invite Google penalty as well.

As Matt Cutts the Google spokesperson says the removal has to be cautiously done after efforts to remove them manually has failed.  Judging a link will be the next part of the story...bye for now...     

Search Engine Optimization a shifting paradigm

Many of the sites with aggressive promotion or link building have taken a heavy toll on the serps. This has happened after the roll out of Panda Filter and Penguin algorithmic changes.  You may be surprised by the delay of my entries since the last one was on May 2012.

Well some of my sites experienced negative changes  while a couple with duplicate contents unknown to me suffered very badly. It is obvious that sites that have been hit have been aggressively promoted other than my own activities. 

The Aftermath

Clients 

Rule One: Of seo has emerged for client. Get one who does not have any idea of seo... but service them sincerely. 

Rule Two: Interfering clients and those with half backed knowledge of seo do not last long. They keeping moving from one aggressive link builder to another till the domain is exhausted and put out by the search engines for ever.     

Link Building

Rule Three: Rely very less on paid links. Go for topically relevant paid links only if strong referral generation is achieved.

Rule Four: Relevancy cannot be sacrificed. Search Engines are being influenced by many other mark ups and feeders. Hence be careful what you put on Google places, plus, classifieds etc.  

Rule Five: Try to get natural back links with unique informative content on board. This applies to internal or resource pages as well.

Rule Six: Get back links from sources with acclaimed editorial scrutiny. This means writing expert contents and staying away from quickfire postings on blogs, forums and resorting to minimal submissions elsewhere. 

Rule Seven: Number of back links count but those with approval ratings as mentioned above. Thresholds have to be kept in mind.Example one good article = ten bad articles.

Rule Eight: Keep searching for good emerging platforms. 

Rule Nine: Involve Social Media. 

Rule Ten:A good back link platform has a good page rank, relevant to the topic of your website, has less ads properly placed. Less number of links per page, all relevant links in the category. Submissions/publications go through editorial scrutiny. Certainly not made for unwarranted revenue generations. Use your experience to make out more about a good platform and inform me kindly. 

Rule eleven: Aim at long tailed/ secondary search terms for reaching the primary goal.  

On Page Optimization 


Rule Twelve: Begins with unique site contents. Sites with blemish in contents never reach anywhere on serps.

Rule Thirteen: Accurate content creation is a must for a successful websites. The Content Creation is important for achieving results on targeted terms.  

Rule Fourteen: User Friendly Architecture. All important information should be easily found from anywhere on site.  

Rule Fifteen: Use robot text file properly or add directions in meta for search engine to follow and index the page or avoid it.  

Rule Sixteen: Page Download Speed: Does the site load happily for you ..well that is the landmark.

Rule Seventeen: For Speed:  Reduce Http: requests, define images, optimize images, use server side includes,  keep the page length optimum.In all these matters consult an experienced web designer.

Rule Eighteen: Unique Title/Meta Desc for every page this is a must.

Rule Nineteen: Try Meta Data on home page that describes the ownership/service etc.

Rule Twenty: Optimize alt text.

Rule Twenty One: Place your internal links right. More useful on top.

Rule Twenty Two: Place ads according to SE guidelines. .

Rule Twenty Three: Properly Format text and make them easily readable.

Rule Twenty Four: Minimize Text Descriptive, do not use H1 tags for promotional purpose it should describe the page as well. Avoid bold, underline and tags etc. 

Rule Twenty Five: Keep keyword density 3 to 4 percent. Use keywords in contents natural or else avoid them.Write to describe the offerings and not for search engines. You contents should make the targeting of chosen search terms possible. 

Rule Twenty Six: Work up on LSI.

Rule Twenty Seven: Resort to Internal Linking if required.

There is more to come in time to come...keep on hanging 


Sunday, May 27, 2012

Penguin Update - How to Overcome?

Since April 24th for many website owner and web masters the World has com tumbling down. The cause is the Penguin Update that Google has implemented in order to cut down web spam. Earlier Panda Update was a major update many versions of which have been implemented. 

From time to time Google unleashes these changes in order to improve the quality of sites on the top for the users. Most of these changes have come about through the algorithms but the Penguin Update is not one of them. It is more like a filter which checks for the web spam and qualifies or disqualifies the site, or on some instances lowered ranking may be the outcome.       

Though the update has created lot of flutter especially from those who have been hit badly. But there have been lot of instances where good sites have been hit as well. Well this could be due to that one or the other element on their web page which may have been qualified as spam albeit it may have been in place unintentionally.   

The finger clearly points out at duplicate content and too much formatting. Some on page factors like excessive use of H1 tag, bold tag, and  yes keyword stuffing. Websites that do not pass through a good seo may contain lot of search terms, which most of the web designers add out of impulse or lack of knowledge. Many web designing companies do not have content writers, hence the site contents are usually palmed off from a similar site on the net. Improper contents arise due to bad quality and cheap content writers. 

The Solutions

Hence the cleaning process would involve removing duplicate content, H1, H2 tags if too many and excessive internal links. Changing anchor text of internal links to natural and such that similar anchor text is not repeatedly used. There are many finer points to writing contents but that is for experts. You can write simple meaningful contents yourself which should be original and readable.

Ads: This is another issue that has come up in recent times. Your advertisements should be placed as such that they do not obstruct the contents or distract visitors in any way. The focus should not be selling advertisements or affiliate links but on creating a good website first.   

After you have worked extensively on your website then wait for Penguin Refresh or the spiders to do their work and improve rankings. 

Sunday, January 15, 2012

How to Blog?

Blog is one of the most useful tool that has come in recent times. The weblog as the blog is called is a short of personal diary and is an account of one's experience. The blog do contain information articles and news items as well.

The blogsite is an interactive platform and is easy to use. For example you have to first create and account with the service provider. One such service provider is blogspot for which you need gmail to create and account. 
You can either type the url or search in google using keyword "blogspot".

The Url is http://www.blogger.com

Another way is to click on the right side of the Google search result page. There is sign in written on the top right click on sign in. Once you sign you can add blogger services to your account. Going through the URL is best for first timer. 

Once you are at the blogger interface look for options. Select the New Post option or Write a Post option to enter the platform. Here you can type in whatever you wish to write and from the options on the top you can add photographs and use the editor to format your text. You can also add a link to the sites which are relevant to your content and add information to it. You add too many links your blog will become a  spam blog hence be very careful. Write for the users.  Once your entry is complete you can click on the publish button to publish your entry. 

Other options: While you are writing an entry you can frequently use the save button to save your work. Your entry will be saved a draft. Once it is complete you can publish it. 

There is an option for adding keywords on the right side of the writing surface. You can add keywords that describe your contents. Similarly you can location search to add the position on which your write is based. These will help the search engines place your blog better on SERPs.

Preserve the user name and password that you have created to open and account with the blogger.