5 Ways To Improve Your Adsense Earnings

If webmasters want to monetize their websites, the great way to do it is through Adsense. There are lots of webmasters struggling hard to earn some good money a day through their sites. But then some of the ôgeniusesö of them are enjoying hundreds of dollars a day from Adsense ads on their websites. What makes these webmasters different from the other kind is that they are different and they think out of the box. Continue reading “5 Ways To Improve Your Adsense Earnings”

3 Reasons Why Adsense Is Essential For Content Sites

To know why Adsense is essential for your content sites is to know first how this works.

The concept is really simple, if you think about it. The publisher or the webmaster inserts a java script into a certain website. Each time the page is accessed, the java script will pull advertisements from the Adsense program. The ads that are targeted should therefore be related to the content that is contained on the web page serving the ad. If a visitor clicks on an advertisement, the webmaster serving the ad earns a portion of the money that the advertiser is paying the search engine for the click. Continue reading “3 Reasons Why Adsense Is Essential For Content Sites”

How to convert Easting and Northing points to Latitude and Longitude for coordinates calculation

The terms easting and northing are geographic Cartesian coordinates for a point. Easting refers to the eastward-measured distance (or the x-coordinate), while northing refers to the northward-measured distance (or the y-coordinate).

Easting and northing coordinates are commonly measured in metres from a horizontal datum. However, imperial units (e.g., survey feet) are also used. The coordinates are most commonly associated with the Universal Transverse Mercator coordinate system (UTM), which has unique zones that cover the Earth to provide detailed referencing.


Have a go at finding your own coordinates:
Have a go at finding your own coordinates: Civil Engineering Homework

Please note that the UDF below converts northings/eastings in OSGB36 (Ordnance Survey) projection to latitude/longitude in WGS84 projection so they can be used in Google Maps.

****** Object:  UserDefinedFunction [dbo].[NEtoLL]    Script Date: 09/06/2012 17:06:39 ******/



--Author: Sandy Motteram
--Date:   06 September 2012

--UDF adapted from javascript at http://www.bdcc.co.uk/LatLngToOSGB.js
--found on page http://mapki.com/wiki/Tools:Snippets

--Latitude and Longitude are calculated based on BOTH the easting and northing values from the OSGB36
--This UDF takes both easting and northing values in OSGB36 projection and you must specify if a latitude or longitude co-ordinate should be returned.
--IT first converts E/N values to lat and long in OSGB36 projection, then converts those values to lat/lng in WGS84 projection

--Sample values below
--DECLARE @East INT, @North INT, @LatOrLng VARCHAR(3)
--SELECT @East = 529000, @North = 183650 --that combo should be the corner of Camden High St and Delancey St

    DECLARE @Pi              FLOAT
          , @K0              FLOAT
          , @OriginLat       FLOAT
          , @OriginLong      FLOAT
          , @OriginX         FLOAT
          , @OriginY         FLOAT
          , @a               FLOAT
          , @b               FLOAT
          , @e2              FLOAT
          , @ex              FLOAT
          , @n1              FLOAT
          , @n2              FLOAT
          , @n3              FLOAT
          , @OriginNorthings FLOAT
          , @lat             FLOAT
          , @lon             FLOAT
          , @Northing        FLOAT
          , @Easting         FLOAT

    SELECT  @Pi = 3.14159265358979323846
          , @K0 = 0.9996012717 -- grid scale factor on central meridean
          , @OriginLat  = 49.0
          , @OriginLong = -2.0
          , @OriginX =  400000 -- 400 kM
          , @OriginY = -100000 -- 100 kM
          , @a = 6377563.396   -- Airy Spheroid
          , @b = 6356256.910
    /*    , @e2
          , @ex
          , @n1
          , @n2
          , @n3
          , @OriginNorthings*/

    -- compute interim values
    SELECT  @a = @a * @K0
          , @b = @b * @K0

    SET     @n1 = (@a - @b) / (@a + @b)
    SET     @n2 = @n1 * @n1
    SET     @n3 = @n2 * @n1

    SET     @lat = @OriginLat * @Pi / 180.0 -- to radians

    SELECT  @e2 = (@a * @a - @b * @b) / (@a * @a) -- first eccentricity
          , @ex = (@a * @a - @b * @b) / (@b * @b) -- second eccentricity

    SET     @OriginNorthings = @b * @lat + @b * (@n1 * (1.0 + 5.0 * @n1 * (1.0 + @n1) / 4.0) * @lat
          - 3.0 * @n1 * (1.0 + @n1 * (1.0 + 7.0 * @n1 / 8.0)) * SIN(@lat) * COS(@lat)
          + (15.0 * @n1 * (@n1 + @n2) / 8.0) * SIN(2.0 * @lat) * COS(2.0 * @lat)
          - (35.0 * @n3 / 24.0) * SIN(3.0 * @lat) * COS(3.0 * @lat))

    SELECT  @northing = @north - @OriginY
         ,  @easting  = @east  - @OriginX

    DECLARE @nu       FLOAT
          , @phid     FLOAT
          , @phid2    FLOAT
          , @t2       FLOAT
          , @t        FLOAT
          , @q2       FLOAT
          , @c        FLOAT
          , @s        FLOAT
          , @nphid    FLOAT
          , @dnphid   FLOAT
          , @nu2      FLOAT
          , @nudivrho FLOAT
          , @invnurho FLOAT
          , @rho      FLOAT
          , @eta2     FLOAT

    /* Evaluate M term: latitude of the northing on the centre meridian */

    SET     @northing = @northing + @OriginNorthings

    SET     @phid  = @northing / (@b*(1.0 + @n1 + 5.0 * (@n2 + @n3) / 4.0)) - 1.0
    SET     @phid2 = @phid + 1.0

    WHILE (ABS(@phid2 - @phid) > 0.000001)
        SET @phid = @phid2;
        SET @nphid = @b * @phid + @b * (@n1 * (1.0 + 5.0 * @n1 * (1.0 + @n1) / 4.0) * @phid
                   - 3.0 * @n1 * (1.0 + @n1 * (1.0 + 7.0 * @n1 / 8.0)) * SIN(@phid) * COS(@phid)
                   + (15.0 * @n1 * (@n1 + @n2) / 8.0) * SIN(2.0 * @phid) * COS(2.0 * @phid)
                   - (35.0 * @n3 / 24.0) * SIN(3.0 * @phid) * COS(3.0 * @phid))

        SET @dnphid = @b * ((1.0 + @n1 + 5.0 * (@n2 + @n3) / 4.0) - 3.0 * (@n1 + @n2 + 7.0 * @n3 / 8.0) * COS(2.0 * @phid)
                    + (15.0 * (@n2 + @n3) / 4.0) * COS(4 * @phid) - (35.0 * @n3 / 8.0) * COS(6.0 * @phid))

        SET @phid2 = @phid - (@nphid - @northing) / @dnphid

    SELECT @c = COS(@phid)
         , @s = SIN(@phid)
         , @t = TAN(@phid)
    SELECT @t2 = @t * @t
         , @q2 = @easting * @easting

    SET    @nu2 = (@a * @a) / (1.0 - @e2 * @s * @s)
    SET    @nu = SQRT(@nu2)

    SET    @nudivrho = @a * @a * @c * @c / (@b * @b) - @c * @c + 1.0
    SET    @eta2 = @nudivrho - 1
    SET    @rho = @nu / @nudivrho;

    SET    @invnurho = ((1.0 - @e2 * @s * @s) * (1.0 - @e2 * @s * @s)) / (@a * @a * (1.0 - @e2))

    SET    @lat = @phid - @t * @q2 * @invnurho / 2.0 + (@q2 * @q2 * (@t / (24 * @rho * @nu2 * @nu) * (5 + (3 * @t2) + @eta2 - (9 * @t2 * @eta2))))
    SET    @lon = (@easting / (@c * @nu))
                - (@easting * @q2 * ((@nudivrho + 2.0 * @t2) / (6.0 * @nu2)) / (@c * @nu))
                + (@q2 * @q2 * @easting * (5 + (28 * @t2) + (24 * @t2 * @t2)) / (120 * @nu2 * @nu2 * @nu * @c))

    SELECT @lat = @lat * 180.0 / @Pi
         , @lon = @lon * 180.0 / @Pi + @OriginLong

--Now convert the lat and long from OSGB36 to WGS84

          , @OGlon  FLOAT
          , @height FLOAT

    SELECT  @OGlat  = @lat
          , @OGlon  = @lon
          , @height = 24 --London's mean height above sea level is 24 metres. Adjust for other locations.

    DECLARE @deg2rad  FLOAT
          , @rad2deg  FLOAT
          , @radOGlat FLOAT
          , @radOGlon FLOAT

    SELECT  @deg2rad = @Pi / 180
          , @rad2deg = 180 / @Pi

    --first off convert to radians
    SELECT  @radOGlat = @OGlat * @deg2rad
          , @radOGlon = @OGlon * @deg2rad
    --these are the values for WGS84(GRS80) to OSGB36(Airy) 

    DECLARE @a2       FLOAT
          , @h        FLOAT
          , @xp       FLOAT
          , @yp       FLOAT
          , @zp       FLOAT
          , @xr       FLOAT
          , @yr       FLOAT
          , @zr       FLOAT
          , @sf       FLOAT
          , @e        FLOAT
          , @v        FLOAT
          , @x        FLOAT
          , @y        FLOAT
          , @z        FLOAT
          , @xrot     FLOAT
          , @yrot     FLOAT
          , @zrot     FLOAT
          , @hx       FLOAT
          , @hy       FLOAT
          , @hz       FLOAT
          , @newLon   FLOAT
          , @newLat   FLOAT
          , @p        FLOAT
          , @errvalue FLOAT
          , @lat0     FLOAT

    SELECT  @a2 = 6378137             -- WGS84_AXIS
          , @e2 = 0.00669438037928458 -- WGS84_ECCENTRIC
          , @h  = @height             -- height above datum (from $GPGGA sentence)
          , @a  = 6377563.396         -- OSGB_AXIS
          , @e  = 0.0066705397616     -- OSGB_ECCENTRIC
          , @xp = 446.448
          , @yp = -125.157
          , @zp = 542.06
          , @xr = 0.1502
          , @yr = 0.247
          , @zr = 0.8421
          , @s  = -20.4894

    -- convert to cartesian; lat, lon are in radians
    SET @sf = @s * 0.000001
    SET @v = @a / (sqrt(1 - (@e * (SIN(@radOGlat) * SIN(@radOGlat)))))
    SET @x = (@v + @h) * COS(@radOGlat) * COS(@radOGlon)
    SET @y = (@v + @h) * COS(@radOGlat) * SIN(@radOGlon)
    SET @z = ((1 - @e) * @v + @h) * SIN(@radOGlat)

    -- transform cartesian
    SET @xrot = (@xr / 3600) * @deg2rad
    SET @yrot = (@yr / 3600) * @deg2rad
    SET @zrot = (@zr / 3600) * @deg2rad
    SET @hx = @x + (@x * @sf) - (@y * @zrot) + (@z * @yrot) + @xp
    SET @hy = (@x * @zrot) + @y + (@y * @sf) - (@z * @xrot) + @yp
    SET @hz = (-1 * @x * @yrot) + (@y * @xrot) + @z + (@z * @sf) + @zp

    -- Convert back to lat, lon
    SET @newLon = ATAN(@hy / @hx)
    SET @p = SQRT((@hx * @hx) + (@hy * @hy))
    SET @newLat = ATAN(@hz / (@p * (1 - @e2)))
    SET @v = @a2 / (SQRT(1 - @e2 * (SIN(@newLat) * SIN(@newLat))))
    SET @errvalue = 1.0;
    SET @lat0 = 0
    WHILE (@errvalue > 0.001)
        SET @lat0 = ATAN((@hz + @e2 * @v * SIN(@newLat)) / @p)
        SET @errvalue = ABS(@lat0 - @newLat)
        SET @newLat = @lat0

    --convert back to degrees
    SET @newLat = @newLat * @rad2deg
    SET @newLon = @newLon * @rad2deg

    SET @ReturnMe = 0

    IF @LatOrLng = 'Lat'
        SET @ReturnMe = @newLat
    IF @LatOrLng = 'Lng'
        SET @ReturnMe = @newLon

    RETURN @ReturnMe

Calculate the distance between two coordinates in SQL Server

google-distance-calculator-1390807649If you ever had to quickly retrieve a distance between two points (identified with a latitude and longitude each), you might have had to rely on the Google geocoding service / distance calculator.

For a lot of points, this might prove difficult, so we have found a good function that will do all the processing instantly inside SQL.

    @Latitude1  float,
    @Longitude1 float,
    @Latitude2  float,
    @Longitude2 float
returns float as
    declare @radius float

    declare @lon1  float
    declare @lon2  float
    declare @lat1  float
    declare @lat2  float

    declare @a float
    declare @distance float

    -- Sets average radius of Earth in Miles
    set @radius = 6366.7

    -- Convert degrees to radians
    set @lon1 = radians( @Longitude1 )
    set @lon2 = radians( @Longitude2 )
    set @lat1 = radians( @Latitude1 )
    set @lat2 = radians( @Latitude2 )

    set @a = sqrt(square(sin((@lat2-@lat1)/2.0E)) + (cos(@lat1) * cos(@lat2) * square(sin((@lon2-@lon1)/2.0E))) )
    set @distance = @radius * ( 2.0E *asin(case when 1.0E < @a then 1.0E else @a end ))

    return @distance

To use this function, call it with a pair of coordinates.

Example: Chicago 41.8819° N, 87.6278° W
New York 40.7127° N, 74.0059° W

Result: 1,143.38 km

print dbo.[F_GREAT_CIRCLE_DISTANCE] (41.8819, 87.6278, 40.7127, 74.0059)


If you would like to see the distance in miles rather than kilometers, change
set @radius = 6366.7
set @radius = 3956

The above result will be 710miles.

Google Adverts for Video

Is there anything that video can’t do? It surprises us, teaches us, even makes us giggle at work. Every day, the world watches more. And now with Google AdWords for video, you can put the power of video to work for you.

With Google AdWords for video, you can:

  • Reach the right viewer at the right price
  • Pay only when they choose to watch your ad
  • Manage campaigns with ease

Make more money with DoubleClick for Publishers (DFP) Video

  • Earn more from video ad sales
  • Simplify your ad operations and streamline your video workflow
  • Take control of how viewers view your ads
  • Handle complex syndication agreements easily
  • Reach new audiences on all devices

SEO Tips and Tricks for Higher Page Rank (6)

6. Traffic Analysisgoogle_webmaster_traffic

Google will look at the traffic that a document gets and changes to that traffic over time. It will also consider seasonal, daily or other timely changes to see if a document receives more traffic at these times and is therefore more relevant at these times. Any significant drop in traffic may indicate that a document is stale. Google may also consider ‘advertising traffic’ separately.
Is your primary goal in a search engine promotion campaign to increase overall traffic or to increase sales? The determination of your success will depend on your goals.

You will need to have the following statistics or metrics available to analyze your success:

  • How many unique visitors you get each week
  • The specific search engines that are sending you traffic
  • How many hits each search engine is sending you
  • The keywords people use to find your site
  • What your ranks are for certain keyword phrases
  • Sales per week

In order to get the above information you will need a traffic analyzer that will report your site statistics. We recommend the free Google Analytics.

You will also need to be able to integrate your site statistics with your sales/week. You can use Microsoft Excel for this purpose. You can transfer some of the information from Advanced Logger into an Excel file that also contains your average sales/day over a week. This will give you some revealing statistics about the relationships between search engines, visitors, and sales.

Over a period of time, you will be able to see the emerging relationships between keywords, search engines and sales. Analyzing these relationships will show you where you need to improve your site.

Track visitors with a traffic analyzer

A unique visitor is a person that visits your site for the first time. Some statistical reporting programs will tell you unique visitors per 24 hour period. This means, if the visitor returns the next day, they are counted again as a unique visitor, even if they have already been to your site.

When you start to analyze the data, you will be exposed to a lot of numbers. Make sure that you know the difference between the unique visitor and total hits on your site. Total hits can be anything from hits on every page to hits on every page and every graphic (total accesses).
You will need to know the number of unique visitors in order to track your sales success.

Simple site statistics usually provided by your host will tell you how many unique visitors your site is

Track Search Engines with a traffic analyzer

Depending on your site statistics program, you may also be able to see which search engines are referring traffic to your site. Google Analytics will provide graphical charts to represent site traffic.

Don’t expect to get every page ranked in every engine. Some search engines just naturally pick up more pages than others. Search engines are always in a competition for who has the biggest database of web pages. You may find that one search engine may be picking up and ranking almost every page of your site, while another engine only likes your home page. It is also dependent on the popularity of the specific search engine.

We’ve dealt with the statistics for many web sites over many years. We believe that Google sends the most traffic. But that doesn’t mean that Google always sends the most quality traffic. Quality traffic (traffic that produces sales) can vary by search engine. One important variable would be the product.
For instance, traffic from MSN may bring many sales for your product, whereas traffic from Google may yield you less sales per unique visitor.

You will need to look at your statistics over many months to determine which engines are bringing you sales and which keywords are producing traffic and sales for your specific product.
Track keywords with a traffic analyzer and a ranking report
Again, an advanced program will be very useful to help you accurately track the ranks of specific keyword phrases in the engines. You’ll need to get the free version of WebCEO which will provide you with plenty more analytical tools as well.

When you start getting a good amount of traffic (at least 500 unique visitors per week) you will start to understand that the keyword phrases people use are wide and varied. You will notice that you’re getting traffic from search engines on phrases that you never thought of. The essence of a good search engine promotion campaign is that you see a nice spread of traffic from ALL engines and a
nice spread of keyword phrases.

Some equations that may help you analyze traffic

Percent Increase of Unique Visitors:

  • UVB = unique visitors before a promotion campaign. They should be over a specific period of time, like 4 weeks.
  • UVA = unique visitors after or during a promotion campaign. This should be over the same period of time as UVB – 4 weeks.
  • UVA – UVB = difference
  • Difference/UVA = percent of visitor increase

Percent Increase of Hits from Search Engine(s):

  • HB = hits from search engine(s) before a campaign over specific time
  • HA = hits from search engines after a campaign over same time period as HB
  • HA – HB = difference
  • Difference/HA = percent increase of hits from search engine(s)

Percent increase in sales:

Sales/Unique Visitors = percent of sales/visitors

On the same day of each week (or month) you should calculate your sales/unique visitor ratio. This will tell you if your promotion campaigns are increasing sales, not just visitors. (We’ll venture to say that 1% is a good ratio. That is one sale per 100 visitors. If you see anything over 1%, you should examine the campaign and try to replicate it in any way possible.)

Google Deleted 100 Million Search Results in 2013

Since the beginning of the current year rights owners have asked the search giant to remove over 100 million links to “pirate” websites. This figure is already double the number Google processed for the whole last year. Google is currently processing an average of 15 million “pirate” links per month. Although this number is leveling off, the rights owners aren’t satisfied yet.

Trying to steer prospective customers away from illegal websites, rights owners keep sending the search engine millions of DMCA takedown requests. Google, on its side, is trying to give the public insight into the scope and nature of this process – this is why it started publishing details of all takedown requests in its Transparency Report. It turned out that since last year the number of URLs the company is being asked to remove has exploded.

Thus far, Google has been required to delete more than 105,300,000 links to infringing websites, and most of them don’t appear in search results anymore.


As for the websites for which the company received the most takedown notices, the file-hosting search engine FilesTube tops the rankings with almost 6,000,000 URLs. Another “rogue” website is Torrentz.eu with over 2,500,000 URLs, followed by Rapidgator.net with more than 2,000,000 links. The surprising fact is that infamous The Pirate Bay didn’t show up in the top 20. Maybe this is because it changed domain names, or maybe because it hosts just 2,000,000 magnet links on the website.

Talking about the reporting groups, we can see that the Recording Industry Association of America is one of the most active senders of DMCA takedown requests. The anti-piracy outfit has sent takedown requests for over 26 million URLs within the last year and half. Despite the fact that Google responds swiftly, the entertainment industry doesn’t believe the takedowns are efficient. This is why it now asks the search giant to ban entire domains from its search results.

On the one side, the company is satisfied with the way things are going, saying that it has faith in the general workings of the DMCA takedown procedure. The only problem with the massive number of takedowns is that thousands of links are taken down in error – for example, Microsoft recently asked to remove its very own website from the search results.

In the meantime, the industry experts note that it would be interesting to see how the tension between the search engine and the rights owners develops over time.