Up To Date SEO Information for Top Positions in Organic Search

Search Engine Optimization


Expert Tips
> 19 Years  Online Marketing Experience

A Vancouver Island Business since 1996

  Canada SEO Comox Valley » Home » SEO Information » SEO! The beginning of an interesting year

Log In |  Cart Contents  |  Checkout | 

          SEO Results.
   342 Search phrases
          74% in top 3
          100% page 1

SEO Options
box
'08 Client Report
Help Us Help You
SEO Clients
SEO Program Elements
SEO WebSite Audit (1)
Website Work (1)
Guaranteed Instruction (1)
Seo Fast Track Book (1)
Mentoring (2)
Testimonials
box
Articles
box
New Articles (0)
All Articles (33)
SEO Information (23)
Building a Website (1)
Business Intelligence (9)
box
Best Sellers
box
01.The Fast Track to SEO Success instructional plan
box
Specials
box
The Fast Track to SEO Success instructional plan
The Fast Track to SEO Success instructional plan
 $89.95  $39.95 
box
Information
box
Terms and Conditions
Privacy
Contact Us
box
Who's Online
box
There currently are 3 guests online.
box
SEO! The beginning of an interesting year by Reg Charie

Looking at Google's list of search changes for February.

  • More coverage for related searches. [launch codename “Fuzhou”] This launch brings in a new data source to help generate the “Searches related to” section, increasing coverage significantly so the feature will appear for more queries. This section contains search queries that can help you refine what you’re searching for.

You will find this in the left menu under "More".
The choices are now:

Images, Maps, Videos, News, Books, Places, Blogs, Discussions, Applications, Patents
 

  • Tweak to categorizer for expanded sitelinks. [launch codename “Snippy”, project codename “Megasitelinks”] This improvement adjusts a signal we use to try and identify duplicate snippets. We were applying a categorizer that wasn’t performing well for our expanded sitelinks, so we’ve stopped applying the categorizer in those cases. The result is more relevant sitelinks.

Less internal duplication by letting the internal linking flow naturally and not forcing a choice.

  • Less duplication in expanded sitelinks. [launch codename “thanksgiving”, project codename “Megasitelinks”] We’ve adjusted signals to reduce duplication in the snippets for expanded sitelinks. Now we generate relevant snippets based more on the page content and less on the query.

Attention SEOers.
Another relevance adjustment.

  • More consistent thumbnail sizes on results page. We’ve adjusted the thumbnail size for most image content appearing on the results page, providing a more consistent experience across result types, and also across mobile and tablet. The new sizes apply to rich snippet results for recipes and applications, movie posters, shopping results, book results, news results and more.

Read: "We tweaked our results page layout".

  • More locally relevant predictions in YouTube. [project codename “Suggest”] We’ve improved the ranking for predictions in YouTube to provide more locally relevant queries. For example, for the query [lady gaga in ] performed on the US version of YouTube, we might predict [lady gaga in times square], but for the same search performed on the Indian version of YouTube, we might predict [lady gaga in India].

"Local search is given a high factor"

  • More accurate detection of official pages. [launch codename “WRE”] We’ve made an adjustment to how we detect official pages to make more accurate identifications. The result is that many pages that were previously misidentified as official will no longer be.

Does this mean I will have to write "The OFFICIAL Reg Charie site on http://RegCharie.com

  • Refreshed per-URL country information. [Launch codename “longdew”, project codename “country-id data refresh”] We updated the country associations for URLs to use more recent data.

Again changes to local search.

  • Expand the size of our images index in Universal Search. [launch codename “terra”, project codename “Images Universal”] We launched a change to expand the corpus of results for which we show images in Universal Search. This is especially helpful to give more relevant images on a larger set of searches.

A bigger db is a good thing.

  • Minor tuning of autocomplete policy algorithms. [project codename “Suggest”] We have a narrow set of policies for autocomplete for offensive and inappropriate terms. This improvement continues to refine the algorithms we use to implement these policies.

Does "refine" mean the further narrowing of the already narrow policy set, or the widening of the amount of search terms caught in the filter?

  • “Site:” query update [launch codename “Semicolon”, project codename “Dice”] This change improves the ranking for queries using the “site:” operator by increasing the diversity of results.

This I just do not understand.
The operator "site:" returns the pages in the site. It should return ALL the pages in the site so how can this be made more diverse?

  • Improved detection for SafeSearch in Image Search. [launch codename "Michandro", project codename “SafeSearch”] This change improves our signals for detecting adult content in Image Search, aligning the signals more closely with the signals we use for our other search results.

Similar to "Suggest" but applied to results not suggestions.

  • Interval based history tracking for indexing. [project codename “Intervals”] This improvement changes the signals we use in document tracking algorithms. 

Keeping an eye on the freshness of things.

  • Improvements to foreign language synonyms. [launch codename “floating context synonyms”, project codename “Synonyms”] This change applies an improvement we previously launched for English to all other languages. The net impact is that you’ll more often find relevant pages that include synonyms for your query terms.

Attention LSI buffs. They are using some form of Latent Semantics.

  • Disabling two old fresh query classifiers. [launch codename “Mango”, project codename “Freshness”] As search evolves and new signals and classifiers are applied to rank search results, sometimes old algorithms get outdated. This improvement disables two old classifiers related to query freshness.

Not sure what this would be. New signals could be social metrics instead of something like press releases.

  • More organized search results for Google Korea. [launch codename “smoothieking”, project codename “Sokoban4”] This significant improvement to search in Korea better organizes the search results into sections for news, blogs and homepages.

I don't know if this would be a good idea.  I would like to see the sites gain top linking positions independently of sub classifications.

  • Fresher images. [launch codename “tumeric”] We’ve adjusted our signals for surfacing fresh images. Now we can more often surface fresh images when they appear on the web.

Faster imaging results - Applying "Caffeine" update factors to images.

  • Update to the Google bar. [project codename “Kennedy”] We continue to iterate in our efforts to deliver a beautifully simple experience across Google products, and as part of that this month we made further adjustments to the Google bar. The biggest change is that we’ve replaced the drop-down Google menu in the November redesign with a consistent and expanded set of links running across the top of the page.

Read: "We tweaked our results page layout". (Again)

  • Adding three new languages to classifier related to error pages. [launch codename "PNI", project codename "Soft404"] We have signals designed to detect crypto 404 pages (also known as “soft 404s”), pages that return valid text to a browser but the text only contain error messages, such as “Page not found.” It’s rare that a user will be looking for such a page, so it’s important we be able to detect them. This change extends a particular classifier to Portuguese, Dutch and Italian.

Internal Changes (non SEO related).

  • Improvements to travel-related searches. [launch codename “nesehorn”] We’ve made improvements to triggering for a variety of flight-related search queries. These changes improve the user experience for our Flight Search feature with users getting more accurate flight results.

Fresher Results?

  • Data refresh for related searches signal. [launch codename “Chicago”, project codename “Related Search”] One of the many signals we look at to generate the “Searches related to” section is the queries users type in succession. If users very often search for [apple] right after [banana], that’s a sign the two might be related. This update refreshes the model we use to generate these refinements, leading to more relevant queries to try.

Past searches influence current search? Does this apply to logged out also?

  • International launch of shopping rich snippets. [project codename “rich snippets”] Shopping rich snippets help you more quickly identify which sites are likely to have the most relevant product for your needs, highlighting product prices, availability, ratings and review counts. This month we expanded shopping rich snippets globally (they were previously only available in the US, Japan and Germany).

Good for shopping sites.

  • Improvements to Korean spelling. This launch improves spelling corrections when the user performs a Korean query in the wrong keyboard mode (also known as an "IME", or input method editor). Specifically, this change helps users who mistakenly enter Hangul queries in Latin mode or vice-versa.

Internal Changes (non SEO related).

  • Improvements to freshness. [launch codename “iotfreshweb”, project codename “Freshness”] We’ve applied new signals which help us surface fresh content in our results even more quickly than before.

Internal Changes to the Caffeine update mechanics.

  • Web History in 20 new countries. With Web History, you can browse and search over your search history and webpages you've visited. You will also get personalized search results that are more relevant to you, based on what you’ve searched for and which sites you’ve visited in the past. In order to deliver more relevant and personalized search results, we’ve launched Web History in Malaysia, Pakistan, Philippines, Morocco, Belarus, Kazakhstan, Estonia, Kuwait, Iraq, Sri Lanka, Tunisia, Nigeria, Lebanon, Luxembourg, Bosnia and Herzegowina, Azerbaijan, Jamaica, Trinidad and Tobago, Republic of Moldova, and Ghana. Web History is turned on only for people who have a Google Account and previously enabled Web History.

Is this really needed? We have a browser web history.

  • Improved snippets for video channels. Some search results are links to channels with many different videos, whether on mtv.com, Hulu or YouTube. We’ve had a feature for a while now that displays snippets for these results including direct links to the videos in the channel, and this improvement increases quality and expands coverage of these rich “decorated” snippets. We’ve also made some improvements to our backends used to generate the snippets.

Internal Changes (SEO related) for description displays.

  • Improvements to ranking for local search results. [launch codename “Venice”] This improvement improves the triggering of Local Universal results by relying more on the ranking of our main search results as a signal. 

Looks like they are joining local and general search more closely.

  • Improvements to English spell correction. [launch codename “Kamehameha”] This change improves spelling correction quality in English, especially for rare queries, by making one of our scoring functions more accurate.

Improved spelling corrections.

  • Improvements to coverage of News Universal. [launch codename “final destination”] We’ve fixed a bug that caused News Universal results not to appear in cases when our testing indicates they’d be very useful.

Internal Changes

  • Consolidation of signals for spiking topics. [launch codename “news deserving score”, project codename “Freshness”] We use a number of signals to detect when a new topic is spiking in popularity. This change consolidates some of the signals so we can rely on signals we can compute in realtime, rather than signals that need to be processed offline. This eliminates redundancy in our systems and helps to ensure we can continue to detect spiking topics as quickly as possible.

Freshness changes again. Faster more topical reults.

  • Better triggering for Turkish weather search feature. [launch codename “hava”] We’ve tuned the signals we use to decide when to present Turkish users with the weather search feature. The result is that we’re able to provide our users with the weather forecast right on the results page with more frequency and accuracy.

Turkish weather improvement.

Display changes in the admin.

  • Panda update. This launch refreshes data in the Panda system, making it more accurate and more sensitive to recent changes on the web.

How does "refreshing data" make it more accurate? I wish they would speak English. What data are they talking about?

  • Link evaluation. We often use characteristics of links to help us figure out the topic of a linked page. We have changed the way in which we evaluate links; in particular, we are turning off a method of link analysis that we used for several years. We often rearchitect or turn off parts of our scoring in order to keep our system maintainable, clean and understandable.

Finally! They are talking about changes made made in May 2010.
In the Mayday update they slipped a major change to the PR algos by most of us.
This update makes relevance the principal linking factor.
By using relevance they do not need to use the old metric of the page's mathematically calculated PR number.
Now, a link on a relevant PR0 page will assign more PR to the linked page than a link on a high PR non-relevant page. 

  • SafeSearch update. We have updated how we deal with adult content, making it more accurate and robust. Now, irrelevant adult content is less likely to show up for many queries.

A better search result for porn? Yippie!

  • Spam update. In the process of investigating some potential spam, we found and fixed some weaknesses in our spam protections.

** Tightening up of the non organic linking pattern filters?

  • Improved local results. We launched a new system to find results from a user’s city more reliably. Now we’re better able to detect when both queries and documents are local to the user.

Wonder what signals are being used to determine local results?

All in all it looks like the beginning of an interesting year.

This article was published on Thursday 01 March, 2012.
Plus +1 if you liked the article -

Current Reviews: 0
Write Review
Tell a friend
box
Tell a friend about this article:  
box



SEO Affiliate Program

SEO Affiliates
box
Affiliate Program FAQ
Affiliate Sign Up & Log In
box
Shopping Cart
box
0 items
box
Your Account
box
Your Email Address
Your Password
box

eXTReMe Tracker



Custom Programming from Open Source by DotCom-Productions.com