Microsoft Power Virtual Agents –

Microsoft Power Virtual Agents – an offering that enables anyone to create powerful chatbots using a guided, no-code graphical interface, without the need for data scientists or developers.

To build a chatbot, go to

Watch this overview video, which highlights some of the new capabilities included in the latest update to Microsoft Power Virtual Agents that will help you plan and prepare for the upcoming updates with confidence.

Here are some relevant links to get you started:


Posted in Conversation AI new features

On-demand by new and existing customers Easy2Pay has released the following new features on 23rd August 2014. Find out more by going to

  1. Easy2Pay subscribers can now add surcharge to the payments they receive from their clients.

    Easy2Pay Enable Surcharge Screen

    Easy2Pay Enable Surcharge Screen

  2. Easy2Pay subscribers can now receive an email after every successful payment by their clients without any extra cost.

    Easy2Pay Receive Admin Email Screen

    Easy2Pay Receive Admin Email Screen

  3.  Easy2Pay subscribers can now send an email after every successful payment by their clients without any extra cost.

    Easy2Pay Send Client Email Screen

    Easy2Pay Send Client Email Screen

Posted in Easy2Pay

How to improve SEO for a SPA which is using .NET back-end?

When Google and other search engines index websites, they don’t execute JavaScript. This seems to put Single Page Application (SPA) — many of which rely on JavaScript — at a tremendous disadvantage compared to a traditional website.

If you’re running a SPA with content that you’d like to appear in search results of Google and other search engines websites, then you have to index your content. Historically, AJAX applications have been difficult for search engines to process because AJAX content is produced dynamically by the browser and thus not visible to crawlers because they cannot execute JavaScript. The browsers can run JavaScript and create content on the fly – the search crawler cannot. To make the crawler see what a user sees, the server needs to give a crawler an HTML snapshot, the result of executing the JavaScript on your page. HTML snapshot allows the web server to return to the crawler this HTML created from static content pieces as well as by executing JavaScript for the application’s pages.


Here is an image made by Google depicting the setup of how a crawler index AJAX crawling scheme enable application using HTML snapshot and improve Search Engine Optimization (SEO).

Ajax Crawler Diagram (Graphic by Katharina Probst)

Ajax Crawler Diagram (Graphic by Katharina Probst)

In your SPA replaces the hash fragments (e.g. #myForm) to hashbang (e.g. #!myForm).

For example, replace

to!myForm (which could be available to both crawlers and users.) 

How do we create different hash bang for various contents in the same URL of a SPA?

If you are using KnockoutJS, you might use SammyJS or PagerJS to support hash fragments. See for how to use it.

If you are using AngularJS, the ngRoute module is available in the framework itself. See for how to use it.

When the crawler see the hashbang (#!), it knows that the site supports AJAX crawling scheme on its web server. You have to provide the crawler with an HTML snapshot of this URL so that the crawler sees the content. How will your server know when to return an HTML snapshot instead of a regular page? The answer is the URL that is requested by the crawler: the crawler will modify each AJAX URL such as!myForm


There are two critical reasons why hash bang is necessary:

  • Hash fragments are never (by specification) sent to the server as part of an HTTP request. In other words, the crawler needs some way to let your server know that it wants the content for the URL!myForm (as opposed to simply
  • Your server, on the other hand, needs to know that it has to return an HTML snapshot, rather than the standard page sent to the browser. An HTML snapshot is all the content that appears on the page after the JavaScript has been executed. Your web server returns the HTML snapshot for!myForm (that is, the original URL!) to the crawler.

When the crawler sees the hash bang it to replace it with the “_escaped_fragment_” before making the request to the web server to index that page. For example

The web server sees the “_escaped_fragment_” in the URL it knows that the request is from a crawler. The web server will then redirect the request to the headless browser to serve HTML snapshot from the server.

How to create HTML snapshots on the web server?

If you are a .NET developers you could use ASP.NET MVC with PhantomJS. Create an [AjaxCrawlableAttribute] which will redirect all request with “_escaped_fragment_” in the query string to the HtmlSnapshotController. The HtmlSnapshotController will load the PhantomJS.exe to create HTML snapshot. You can get the PhantomJSexe in the Nuget gallery. Please see this article for detail implementation steps

If you do not want these headache of creating, maintaining & scaling HTML snapshot on your web server check out the following online SaaS,

  1. Brombone is using nodejs, PhantomJS, Amazon AWS SQS, AWS EC2, and AWS S3. BromBone supports sites that use HTML5 pushState URLs instead of hashbang URLs. They do not offer a free trial plan, but they offer a no questions ask money back guarantee.  If you have any question contact Chad DeShon (Founder of Brombone) on Check them on out
  2. AjaxSnapshots has multiple snapshotting servers on Amazon AWS, which has a Java based dispatcher that sends requests on to one of the PhantomJS based headless servers. They use Amazon AWS SQS, AWS EC2, AWS ELB for load balancing and AWS S3. They got a free trial plan. They also claim that PhantomJS script that they run benefits from many modifications they have made to deal with corner cases that trip up naive implementations. If you have any question contact Robert Dunne (Founder of AjaxSnapshots) on Robert also wrote a helpful summary of which search and social bots are aware Check them out on

How to test headless browser content?

It’s highly recommended that you try out your HTML snapshot mechanism. It’s important to make sure that the headless browser indeed renders the content of your application’s state correctly. Surely you’ll want to know what the crawler will see, right? To do this, you can write a small test application and see the output, or you can use a tool such as Fetch as Googlebot. A .NET developers could use NHtmlUnit. NHtmlUnit is a .NET wrapper of HtmlUnit; a “GUI-less browser for Java programs”. It allows you to write code to test web applications with a headless, automated browser.

Google put the following steps to make your SPA crawling,

  1. Indicate to the crawler that your site supports the AJAX crawling scheme.
  2. Set up your server to handle requests for URLs that contain
  3. Handle pages without hash fragments
  4. Consider updating your Sitemap to list the new AJAX URLs

To see the details implementation of the above steps click Guide to AJAX crawling for webmasters and developers. You might find Making AJAX Applications Crawlable useful too.


In summary, starting with a stateful URL such as , it could be available to both crawlers and users as!myForm which could be crawled as Using modern headless browsers, we can easily return the fully rendered content per request by redirecting bots on web servers. 


In 2009, Google released the idea of escaped fragments. Services


Special thanks to Chad DeShon (Founder of Brombone) and Robert Dunne (Founder of AjaxSnapshots) for reviewing this blog.

Posted in Javascript, Single Page Application