When we came up with the concept for Little Warden, we planned that each person would add the Root URL and maybe a few subdomains and so we planned the backend and frontend to match this.
Well, it turns out there is a reason that all the startup books tell you to interview your customer base before you start to build stuff.
Turns out that Little Warden users like tracking pages as well as root domains and some of them like tracking 5000 or more pages on a single domain.
This has proved… interesting from a product perspective and whilst we’ve managed to make the product ‘work’ with this many URLs.. it wasn’t a great experience and certainly doesn’t fit in with the four keys that we try and run the company by.
Well, today I’d like to announce that we’ve launched the refresh of our internal system which means that URLs are grouped by domain or subdomain and you can quickly modify the checks and settings on a mass scale!
Today we’ve pushed out a small tweak to how we import URLs from Search Console.
The change comes down to how Google views ‘sites’ in Search Console for example;
These URLs would all be considered separate sites with GSC (or WMT as all the cool kids call it) and if we import 4 sites for the same URL then that just becomes a pain in the arse for everyone involved.
As far as Little Warden is concerned.. if you added the https:// version which renders, we check all the other URLs by default so there is no need to add them.
So from now on, we don’t import them automatically we just pick the one which renders and import that one (you can force these to be importing by switching auto sync to manual checks).
Over the past few weeks, as well as eating cake and sponsoring conferences, we’ve been working on some backend changes to our system to enable things like hourly checking.
BUT it’s been a while since we launched anything VISUAL so I’d like to present to your our latest update – Recent Changes is now colour coded and in a timeline.
I hear you ask
This is just a Balsamiq mockup of the feature and not a screenshot of the application in situ
A very good point.
Well, If I wanted a screenshot of the website I’d either have to redact some customer data OR spend a few hours mocking up some fake changes on some generic websites and to be honest, not enough people read this blog to make it worthwhile and the mockup looks pretty close to the final feature
Well that makes total sense, thank you for your reasonable answer, I shall go and look at that feature now
So head on over to https://littlewarden.com/change-history and see whats happening. This report will also update your daily changelog to make it a bit easier to see and understand.