This article tells you about my personal experience with the using of PlanoTse for web search automation. Specifically, it is for general job search and not tied to any particular job search engine.
Sure, the PlanoTse Handbook for Job Search Automation has all the guidance you need but it is so thick that it is hard to wrap your mind around all the concepts therein. This article should provide the full context for your first attempt at using PlanoTse for web search automation.
Text Me When Done
Yes, PlanoTse can automatically do the web search all night long while you sleep. And if you want to get up as soon as the web search automation is over, you can ask PlanoTse to text your phone at the end of its mission. Don’t forget to pump up the volume such that the text message, as shown below, can actually wake you up. The following image sums up one of the most beautiful features of PlanoTse as a personal tool for mining global data. Here is a picture of my iPhone getting a text from PlanoTse:

I’m a QTP Automation Consultant. That means I use QuickTest Professional (QTP) and program in VBScript. I want PlanoTse to automatically search for the newest opportunities in QTP every night. In this way, I can always catch the best possible project opportunities for me and yet at the earliest possible time. This is how PlanoTse can help me to ensure that the time I spend in between contracts would be less and less.
Web Search Automation Wizard
I tell PlanoTse what to do by using a web search scripting language called PlanoTseScript. Since I do not remember so many different keywords in PlanoTseScript, I call for assistance from its Web Search Automation (WSA) wizard, a.k.a. automation wizard. The wizard is used before the start of automation. While automated web search is in progress, the automation wizard is not involved at all.
When you supply a search string for Google to find something, it comes back with several search engine results pages (SERP), each with up to ten document links. You click around until you decide to supply another search string. From the start of executing a search string until the time you try another search string is called a web search iteration. In PlanoTse, an automation iteration includes all activities related to a single search string.
To bring up the automation wizard, I select the menu [Automation >> Web Search]. Right on the first page of the wizard, I specify Factor Count to be 3 and set Factors to be: “major, minor, city”. This would make the next three pages to be Major Factor Page, Minor Factor Page and City Factor Page. I used two keywords for Major factor: “automated, automation”. I used two keywords for Minor factor: “QA, Test”. I do not worry too much about upper and lower cases as the search engine will automatically consider both for me. For the search factor City, I use 9 city names. These are of the cities along a freeway near home. From the 2 major, 2 minor and 9 city keywords, or phrases, the wizard will generate 36 different search strings, shown below, for 36 different search iterations in the same WSA session.

The above specification is not exactly what I want to do every night. I do not know that yet. This is only a start, to explore available possibilities. I will become more and more precise later, as explained further down in this article.
In PlanoTse, a run is a shorthand for a halfway decent HTTP response. A broken link, for example, is not counted as a run. You can declare a maximum number of runs per iteration as 20 in one of the following ways:
- Use the following PlanoTseScript instruction: { aw set maxruns 20; }. For more syntax, see this page.
- On page 1 of the automation wizard, set Maximum Runs to be 20.
I used 20 at first because I only want to have a foretaste and see if it is really necessary to use all 9 city names. After reviewing 20 responses from each of the 36 iterations, I will decide to keep all 9 city names, or not. If most the jobs I want are available in City1 and none are available in City2, I would not include City2 in my city list. This would save me from going through a lot of results from a set of useless automated search iterations for City2.
The group of all settings declared together by the automation wizard is called a configuration for web search automation, or simply, WSA config. I pressed NEXT again and again until the last page then I press GO to associate this config with the Go command on the main menu. To start the WSA session, I close the wizard then select the menu Go.
Web Search Scripting Language
A round of automation, also known as an automation iteration, is the duration between the start of the first iteration and the end of the last iteration. After the first round, I saw that I was getting many job listings. I hate that. I want to look at job offers, not job listings. To resolve this issue, I use a page filter consisting of instructions as listed below in PlanoTseScript syntax:
- must avoid hardware, Hardware;
- repeat maximum 4 more;
- repeat maximum 4 detail;
- must have Automation, automation;
- must have Consultant, consultant, Profesional, professional, Analyst, analyst, Tester, tester;
- must have QA, Test, test, testing;
- must have QTP;
- must have Job Description, Job description;
- must have Minimum, Required, minimum, required; must have Compensation, Pay, Rate, Salary;
- must have excellent, strong;
- must have ability, skills;
- must have process, plan;
What you see here is a foretaste of a web search scripting language. The above instructions make up a web search script. Web search scripting is much more precise than search string specification. The search engine rarely does exactly what you specify in the search string. In web search scripting, you must be case sensitive and very precise in defining your page filter. I can make this web search script longer and longer until most unwanted documents are filtered out. Only actual job descriptions would meet the exact criteria I spell out in a web search script with so many instructions.
For those who are new to PlanoTseScript, all must-avoid phrases must not be present in the document highlighted as an excellent search result. In contrast, only a single must-have phrase per filtering instruction must be present in the document.
The repeat-maximum filter is saying that, the document may not have more than so many times of a certain phrase or character string. This last feature is a way to fight against appearances of too many unwanted listing. Most listings have something repeated again and again on every row, for example, More or Detail, at end of each row briefing. The repeat-maximum should detect such a listing as forewarned by the user in their web search script.
WSA Configuration File
At this time, I realize that I’ve done a lot of work. Most of the work has been in figuring out what settings to declare for my automation. On the wizard menu, I select [File >> Save Config As...] to save my settings in a configuration file. For safekeeping, I copy the WSA config file to my thumb drive. When I’m at another computer, I can always download PlanoTse but I need to have this WSA config file to avoid starting from scratch in the development of my automation strategy.