Runtime params: Not required anymore. See ScrapeList in app.config.
ScrapeList: Multiple scrape lists can now be added in the latest version. You can add these settings in the app.config file, just make sure the key contains "Scrape". Some examples can be found in the app.config where the first parameter is the number of pages to scrape on that particular vehicle and the second parameter is the search URL.
Gumtree URLs: Gumtree can be weird when paging through a result set. For some reason, it doesn't like particular links, so when you try paging through the same articles will load regardless of the page you're on. On top of this, Gumtree doesn't seem to like links with encoded HTML entities either, so if your URL isn't "correctly formatted", you may end up with some very weird scrape results.
Luckily, I've found a link combination that'll always (hopefully) work, modify to your criteria:
Known issues:
DaysOld field not showing accurate age: Gumtree will sometimes show the "date posted" field (from which the DaysOld field is scraped) as null, this means that getting an accurate DaysOld value is very difficult. As a result, the only way to ensure this field is accurate is to allow a number of days scraping to occur. As each day passes, the scraper will automatically increment the DaysOld field relative to it's DateAdded date - this is the only work around for this issue at this moment in time.
Querying the database: If you copy a result link from your web browswer in order to do a search for it in your database, keep in mind that some browsers URL parsers encode/decode HTML entities, which may affect searching on article links if they don't match up properly.
Database structure:
