Read About the latest SEO News and Updates

Friday, August 25, 2017

Phrase match is dead. Long live phrase match!

Reports of the demise of phrase match have been greatly exaggerated, finds contributor Steve Cameron. It turns out that there are certain situations in which it comes in pretty handy. 

When Google launched their broad match modified match type some years ago, some marketers hailed the demise of phrase match as something of a foregone conclusion.
Many, ourselves included, quickly shifted gears and rolled out new campaigns using a combination of broad match modified (BMM), exact match and negative match keywords. And others did not.
Let’s consider why we did this. First — and this should be writ large wherever AdWords advertisers congregate — no one likes broad match. No one except, perhaps, Google.
Using broad match is essentially lazy, the equivalent of holding out your hand with all your money it in and letting Google take what they want. They’re getting better — broad match is nowhere near as bad as it used to be — but it still allows Google a freedom you wouldn’t want your car mechanic or your electrician to have.
As a result, many advertisers instead opted for phrase match and exact match for their keywords, often having to develop hundreds of phrase match keywords to cover a multitude of possible search terms. For example, if we were trying to promote our blue widgets, we might start with “blue widgets” as a search term but soon have to add “widgets in blue,” “blue color widgets,” and so on.
With the introduction of BMM, advertisers were suddenly able to cover hundreds of possible search terms by simply using +blue +widgets. In our agency, we then monitor the Search Query Performance reports, pull out those search terms that deserve special attention and move them directly into exact match status, thus making the intermediate phrase match version redundant.
This streamlines the process and, with new build campaigns, seems to be the simplest way to get campaigns live and generating real data. We can then crunch this data faster to get to the kernels of optimization that will drive ongoing success.

Phrase match is still holding its own

We reached out to other marketers to discover how phrase match fits into their account management approach and found that reports of phrase match’s demise may be a little premature.
As Mark Kennedy from SEOM Interactive comments:
“While the changes to match types over the last few months have leant towards the demise of phrase match, it still has its place. I won’t remove it from older accounts where phrase match KWs have good history and conversion value (although I will prune those with no value). And if they are in accounts where ad groups are broken out by match type, I tend to keep them as well — again, especially where there is historical data. The other time I use them is when I am mining search query reports for converting phrases that I want to test. So I’ll use different match types on these new terms (including phrase match) to see what performs well. So while phrase match isn’t ‘necessary’ anymore we haven’t taken it totally out of the utility belt.”
Kennedy’s comments about historical value are particularly significant. Google loves historical data — especially when it comes to Quality Score, for example, and it could take a new BMM keyword some time to achieve a high QS already enjoyed by a long-term phrase match keyword that has consistently performed well.
While others echo these sentiments, Julie Friedman Bacchini of Neptune Moon feels that keyword matching is becoming increasingly fuzzier. She cites the changes in the keyword planner where match types are no longer segmented as an indication of the way Google sees match types. Coupled with the ending of the close variant opt out, the battle lines between marketers and the search engines are blurring. Interestingly, she concludes:
“It’s a little ironic, really, because it seems like now more than ever true phrase match would be helpful to advertisers. With matching getting fuzzier, the ability to zero in on a particular phrase or way of expressing a search term without having to sculpt it with negatives would be welcomed by many, I suspect!”
James Svoboda, partner at WebRanking, also agrees that the close variant rollout last year essentially made phrase match and Broad Match Modified the same with one significant exception: word order.
He explains:
“Since we typically see similar results for search terms containing the same words, but in different word order, such as PPC Agency Minneapolis and Minneapolis PPC Agency, both of which can be targeted using one BMM Keyword: +Minneapolis +PPC +Agency, we’ve opted to simplify our account structure by using BMM instead of phrase match for most keywords. There are a few case-by-case situations that may arise where word order has a significant impact on performance, such “Used Cars” and “Cars Used” where the first one typically will be used by searchers with queries for preowned vehicles and the second one by searchers looking for cars used for specific tasks such as: cars used for off-roading. Even in these cases, we can use Negative Keywords to shape the queries that we are targeting through BMM Keywords.”
As a result, they have effectively removed phrase match from their arsenal and are looking forward to the day when both Google and Bing follow suit.
Whether that day will ever come is debatable. There are, perhaps, too many accounts that have been built and optimized over the years around a solid core of well-performing phrase match keywords. And, since phrase match isn’t broken, there may be no reason to try to fix it.
And for some of us, like Gil Hong from Seer, phrase match may simply be a habit that is hard to shake:
“I still use phrase match! Partly out of habit of how I build campaigns in Excel, and in some instances, phrase match still has a place for specific keyword intent.”
The consensus, therefore, seems to be that there is some life in phrase match after all. Where a well-performing phrase match keyword with great historical data and a good Quality Score is present, it could take some time for a Broad Match Modified keyword to catch up — and indeed, it would be hard to imagine the performance ever quite being matched. But where there are well-performing phrase match keywords, there are Exact Match versions willing and eager to usurp them.

So poor phrase match is getting pressure from both sides, and while it might be able to hold its own for the time being based on past glories, going forward, its days are still probably numbered. But then, we said that a couple of years ago!

Tuesday, August 22, 2017

Load time, static site generators & SEO: How we lowered our own site’s load time by 74%

Google's upcoming transition to mobile-first indexing, combined with its raised expectation of mobile site performance, should convince site owners to consider static site generation. 


Google has raised the bar on site load times consistently over the last decade, and the upcoming transition to mobile-first indexing, combined with its rising expectations of mobile site performance, should be a clear warning sign to site owners.
Site owners generally, however, seem not to be listening.
Unfortunately, based on our analysis of 10,000+ mobile web domains, we found that most mobile sites don’t meet this bar: The average load time for mobile sites is 19 seconds over 3G connections.
DoubleClick research published in September 2016
At our company, we have been experimenting over the last year with static site generation. Our tests on our own site are aimed at allowing us to assess the challenges facing site owners, to understand the scope of opportunity and potential for performance improvement, and also to explore the practical limitations in content management — one of the key criticisms of static site generation.
Our site, QueryClick.com, was a small, fairly well-optimized B2B site, but it averaged ~6.99 second load time in the month prior to our deployment of static site generation (July 2016), dropping to ~1.8 seconds in the month following. That represented a load time reduction of 74.29 percent, despite some server response issues experienced during the period we were actively developing the site.

One month before and after switching to a static site generation infrastructure.
We performed further server optimization improvements over the year, reaching our sub-one-second mobile device target even while testing the impact of less efficient elements driven by JavaScript.

Yes, we know! We didn’t even use sprites, gzipping, or other such techniques — which highlights the impact of a platform-first approach to solving the page speed problem.

A platform-first approach to page speed

I’ve written before about the varying levels of importance of the different aspects of page speed on SEO and about how Google’s algorithm employs data about SERP bounce-backs (when users bounce back to its SERPs after losing patience with a slow-loading site). But it’s worth making the point again as we head to a mobile-first world: server response times and the critical render path event (the point at which everything in the initial device viewport is rendered) are key to delivering high-performance SEO, especially for enterprise-level sites.
Any developer worth their salt will look at the asset load requests in QueryClick’s site displayed in the above image and shake their head at all the unoptimized elements. But that is the point. High performance was achieved despite a lack of rigorous optimization in the code and asset deployment. It was driven by the platform and the high-level architecture decisions.

Google would like us to improve further — and we will, but real performance change has already been delivered.
So, what architecture did we use? As Python and Django evangelists, we write the copy in Markdown and push it to our staging server build via Github, where we can check to ensure it’s all OK. We then use Celery to set a time for the staging server copy to be pushed to the live Git repository. Then, Cactus regenerates the pages and, voila, the live server is populated with the static pages.
Of course, for your average content producer, this infrastructure is not as simple to create or maintain as a standard CMS without some technical know-how. That is the most common criticism of static site deployments, and many enterprise clients consider it a deal-breaker when they’re looking at static site solutions.
Certainly, if you manage product inventory that dynamically changes by tens of thousand in a day, which one of our clients does, then a robust management back end is essential.
That’s why anyone deploying a static site performance solution in the enterprise must leverage Oracle ATG or the like, which can easily generate and manipulate static web pages using its API. When you think about it, live dynamic site management requires significantly more hardware infrastructure than static.
If you need more convincing, take a look at the variety of static code bases already in flight. They use a variety of programming languages and many of them are fully capable of being fitted into an enterprise environment. When you also use a content delivery network (CDN) in production, you can offer a robust solution that delivers both blazing speed (for even poor 3G mobile connections) and total redundancy and elimination of server failure challenges.
Dynamic static asset provision and modern caching controls on static generators allow clean, live adjustment of content that is exactly comparable to dynamic site generation at a fraction of the hardware demand.
It may take years for the general web to catch up with Google’s pioneering push for modern, fast, easy-anywhere web experiences. But if you want to benefit your conversion rate and your brand experience, and enjoy a significant drive to SEO performance thanks to fast critical render performance and positive SERP bounce behavior, then you should have your development team investigate and find an architecture that works for your site today.

Source URL: http://searchengineland.com/load-time-static-site-generators-seo-280785

Wednesday, April 12, 2017

Website Uses it's name in URL on Google Search Results

While I was searching for a keywords "seo services in delhi ncr", I found a results with totally unique URL listed in Google search results. I was little surprised to see the listed URL structure. Here is the screenshot for that unique URL structure:


It was the 1st time when I found this type of URL in Google search results so I was excited to know how it can be done. So I have started researching on it and found that it was an older Google update which happened in 16th April 2015 named "Google Replaces A Site’s URL In Search Results & Uses Its Site Name & Breadcrumb Path".

I realized that there are many such minor updates which happens in between and we miss them as we always focus on the major updates like penguine, panda etc. I am sure if we have a close eye on each minor updates like this then we will become a leader in the industry. As there are very few people in SEO industry have close eyes on such minor updates so they never gets benefits of these changes happen to their clients websites.

And if we get such minor updates then we should also implement the websites accordingly to understand the way how to implement them for a website. It can be a attraction to the users and clients as well.

For today I think it's enough to write on blog. I am still in the implementation stage for this update and once I get anything different on Google then I will share my another blog post.

Thanks for reading my blog. Your comments with your questions will be appreciated.

Wednesday, March 11, 2015

SEO: Understanding Pandas, Penguins, and Pigeons

You probably didn’t realize that animals would affect your website and your business. The three Google search algorithms having the biggest impact in the past three years are a bear and two birds: Panda, Penguin, and Pigeon.
Google’s algorithms are designed to emphasize quality websites while pushing down, in search results, low-quality sites. Google’s efforts are admirable, especially since Google is the most-used search engine.
What is harder to deal with is that a small group of people — Google employees who manage search algorithms — often cause a lot of hardship. Changes to search algorithms can greatly reduce business revenue and increase expenses. Revenue is typically reduced when a website’s ranking (and, thus, traffic) is lowered. Expenses can increase when businesses spend money to make corrections, to address the algorithm changes.
Google’s algorithm changes are designed to emphasize quality websites while pushing down, in search results, low-quality sites.
We could spend a lot of time fretting about these changes or we can push forward. Accepting the changes and objectively making corrective decisions is a better use of time. Moreover, web marketing has no endpoint and change is inevitable.
Let’s take a look at each of Google’s pets — i.e., algorithms — to better understand them and their impact on your business. Note that for purposes of this article, I am defining “low rank” as a ranking position in search results of 10 and beyond.

Panda Algorithm

Google released Panda in February 2011. The algorithm was aimed to make low-quality or thin sites less visible in search results and rank them lower.
The Google Panda U.S. patent states there is a ratio with a website’s inbound links and search queries for the website’s brand, products, and services. The ratio is used to create a modification factor affecting the entire website, not just individual pages. If the page fails to meet a certain mathematical threshold, the modification factor is applied and the website would rank lower in the search engine results page.
When we talk about low-quality websites, there are a few important factors to keep in mind.
  • Duplicate content within your website is an important issue that is not only about meta tags, but the visible content as well. Having web pages with the same title tag and meta description will hurt your rankings.
  • The visible content has to be of value to the visitors. Keyword density percentages are important as well as the web page’s readability score. Flesch-Kincaid and Flesch Reading Ease are two methods of determining readability scores. The more the web page can cater to the general public, the more likely it will meet a quality level based on a mathematical equation.
  • Fresh content that is helping to build the overall density of pages of your website is important. This is where “thin websites” that do not have enough content or for that matter websites that do not have fresh pages are negatively impacted.
To meet these requirements, consider using Google’s Webmaster Tools. Unlike Google Analytics, Google Webmaster Tools identifies problems with your website, from Google’s perspective.
Another consideration is to secure the services of writers and or marketers who can interpret the findings and make changes to help your website’s quality. A technical website developer is not necessarily the right discipline you need in this case.
A material update to Panda occurred in May 2014, with Panda 4.0. This algorithm is here to stay and keeps getting updated.

Penguin Algorithm

Google’s Penguin algorithm addresses inbound link quality.
Google implemented Penguin in April 2012. It is aimed at websites that violate Google’s guidelines by using so-called black-hat techniques — artificially increasing the ranking of a web page by manipulating the number of links pointing to it.
To avoid getting caught in the Penguin algorithm trap, you have to know if the websites linking to you are of quality. This means someone has to know how to determine the quality of websites based on metrics such as Google Page Rank, Alexa Traffic Rank, volume of pages indexed, and volume of links on the web. Quality over quantity is the key, which means someone actually has to research the information.
Using Google’s Webmaster Tools you can find out what websites are linking to you. Once you have that information you will be able to research metrics of these websites using publicly available automation tools to provide you their Google PageRank (a weighted average value from 0 to 10; the higher the better) and other information pertinent to determining their value.
Once you know which websites are of low quality you have two options.
  • Send the website a message and ask it to remove the link to yours.
  • Use Google’s Disavow Tool in Google’s Webmaster Tools to ask Google to not put this website into consideration as a link to your website.
Neither option will likely help your rankings right away. They are both time consuming.
The Penguin algorithm will likely be materially updated by the end of 2014, with version 3.0.

Pigeon Algorithm

Search Engine Land, the online magazine, reportedly first used the name “pigeon” for this new algorithm, which was implemented in July 2014. It designed to provide more useful and accurate local search results. Google stated that this new algorithm improves its distance and location ranking parameters.
The changes are visible in the Google Maps and Google web search results. It impacts local businesses, which may notice an increase or decrease in web site referrals and leads from this change.
Unlike Panda and Penguin, the Pigeon algorithm does not impose penalties. Its purpose is provide more accurate and relevant local search results.
Local business owners should consider these three points.
  • So-called website authority is an issue now because of Google’s search ranking signals. Map listings (i.e., local business listings) are now tied to your website’s authority. This in turn goes back to how Panda and Penguin algorithms are affecting your website.
  • Local business listings should be pin-code verified, updated, and continually maintained. Adding photos and videos and responding to ratings and reviews is important. Positive, legitimate ratings and reviews can only help.
  • Citations are important, which means you need to pin-code verify your listing at other sites beyond Google (such as Bing, YellowPages.com, Yelp, and the like) and be sure they are updated exactly the way your listing is at Google. Use automation services to help get the word out to over 200 other websites, which helps with the citation-building process.

Source URL: http://webmarketingtoday.com/articles/113316-SEO-Understanding-Pandas-Penguins-and-Pigeons/

Monday, June 23, 2014

Google Sandbox and Penalty Check

Deindexed - When your domain is completely removed from Google. Also known as Banned.
Penalized - When your domain or page still exists but none of your pages can be found through very direct search queries.  This penalty can be automatic through the Google algorithm or manually applied by a Google Quality Engineer.
Sandboxed - Your domain or page wasn't Deindexed or Penalized, but the traffic you were getting from Google suddenly drops dramatically.


Some tools for checking goggle penalized sites are given below:
http://pixelgroove.com/serp/sandbox_checker/
http://feinternational.com/website-penalty-indicator/
http://toolbox.gabblet.com/google-penalty-checker-tool-check.aspx

Tuesday, May 20, 2014

Google Begins Rolling Out Panda 4.0 Now

Matt Cutts have announced that Google is rolling out Panda 4.0 update starting today on 21st May 2014.


Google’s Matt Cutts announced on Twitter that they have released version 4.0 of the Google Panda algorithm.
Google’s Panda algorithm is designed to prevent sites with poor quality content from working their way into Google’s top search results.
But didn’t Google stop updating us on Panda refreshes and updates since they are monthly rolling updates? Yes, but this is a bigger update.
Panda 4.0 must be a major update to the actual algorithm versus just a data refresh. Meaning, Google has made changes to how Panda identifies sites and has released a new version of the algorithm today.
Is this the softer and gentler Panda algorithm? From talking to Google, it sounds like this update will be gentler for some sites, and lay the groundwork for future changes in that direction.
Google told us that Panda 4.0 affects different languages to different degrees. In English for example, the impact is ~7.5% of queries that are affected to a degree that a regular user might notice.
Here are the previous confirmed Panda updates, note, that we named them by each refresh and update, but 4.0 is how Google named this specific update:
  1. Panda Update 1, Feb. 24, 2011 (11.8% of queries; announced; English in US only)
  2. Panda Update 2, April 11, 2011 (2% of queries; announced; rolled out in English internationally)
  3. Panda Update 3, May 10, 2011 (no change given; confirmed, not announced)
  4. Panda Update 4, June 16, 2011 (no change given; confirmed, not announced)
  5. Panda Update 5, July 23, 2011 (no change given; confirmed, not announced)
  6. Panda Update 6, Aug. 12, 2011 (6-9% of queries in many non-English languages; announced)
  7. Panda Update 7, Sept. 28, 2011 (no change given; confirmed, not announced)
  8. Panda Update 8, Oct. 19, 2011 (about 2% of queries; belatedly confirmed)
  9. Panda Update 9, Nov. 18, 2011: (less than 1% of queries; announced)
  10. Panda Update 10, Jan. 18, 2012 (no change given; confirmed, not announced)
  11. Panda Update 11, Feb. 27, 2012 (no change given; announced)
  12. Panda Update 12, March 23, 2012 (about 1.6% of queries impacted; announced)
  13. Panda Update 13, April 19, 2012 (no change given; belatedly revealed)
  14. Panda Update 14, April 27, 2012: (no change given; confirmed; first update within days of another)
  15. Panda Update 15, June 9, 2012: (1% of queries; belatedly announced)
  16. Panda Update 16, June 25, 2012: (about 1% of queries; announced)
  17. Panda Update 17, July 24, 2012:(about 1% of queries; announced)
  18. Panda Update 18, Aug. 20, 2012: (about 1% of queries; belatedly announced)
  19. Panda Update 19, Sept. 18, 2012: (less than 0.7% of queries; announced)
  20. Panda Update 20 , Sept. 27, 2012 (2.4% English queries, impacted, belatedly announced
  21. Panda Update 21, Nov. 5, 2012 (1.1% of English-language queries in US; 0.4% worldwide; confirmed, not announced)
  22. Panda Update 22, Nov. 21, 2012 (0.8% of English queries were affected; confirmed, not announced)
  23. Panda Update 23, Dec. 21, 2012 (1.3% of English queries were affected; confirmed, announced)
  24. Panda Update 24, Jan. 22, 2013 (1.2% of English queries were affected; confirmed, announced)
  25. Panda Update 25, March 15, 2013 (confirmed as coming; not confirmed as having happened)

Source URL: http://searchengineland.com/google-begins-rolling-panda-4-0-now-192043

Official: Google Payday Loan Algorithm 2.0 Launched: Targets “Very Spammy Queries”

Google has confirmed they have released a new algorithm update to their Payday Loan Algorithm update over this weekend.
This algorithm specifically targets “very spammy queries” and is unrelated to the Pandaor Penguin algorithms. A Google spokesperson told us:
Over the weekend we began rolling out a new algorithmic update. The update was neither Panda nor Penguin — it was the next generation of an algorithm that originally rolled out last summer for very spammy queries.
This comes with at no surprise to most SEOs and Webmasters who watch the space. There was a tremendous of rumors and signals of a major update over the weekend, intensifying over the past couple days as webmasters began to look at their analytics and the update has continued to roll out through Google.
The original Payday Loan Algorithm launched just about a year ago on June 11, 2013. Back then, Google’s Matt Cutts told us the algorithm impacted roughly 0.3% of the U.S. queries, but Matt said it went as high as 4% for Turkish queries were Web spam is typically higher.
Google told us this specific update is an international rollout and it affects different languages to different degrees, but this impacts English queries by about 0.2% to a noticeable degree. Here is a video back when Matt Cutts of Google announced the update was coming back in 2013: