Check whether your site responds, glance at its search performance, browse a few product launches, then start a focused work session. Four existing Kepo store plugins cover those jobs without requiring you to generate a custom widget first.
We build Kepo, a Mac app with a shortcut-accessible widget panel. This guide focuses on four plugins available in the store today, with their actual published previews and setup details. The screenshots illustrate the interfaces; their numbers and launch listings are examples from those previews, not current measurements.
1. Web Status: keep one website's recent checks in view
The Web Status widget monitors one URL and displays its current reachability alongside a short history of recent checks. It is useful when you want a quick indication that a page you maintain is responding.
Published Web Status preview, showing the wide layout and recent-check history.
Start with a specific page that matters to you: your product homepage, documentation homepage, or another public URL you manage. Set that URL in the widget and compare the first result with opening the page yourself.
The history adds context to a single status indicator. If the recent checks alternate between success and failure, you have a reason to investigate instead of treating one successful response as the whole story.
There are three practical details to remember:
- Checks are scheduled. This is not a continuous live probe.
- Changing the configured URL resets that widget's old history. Keep separate widgets if you need separate histories.
- An excessively short timeout can cause false failures. A slow response and a genuinely unreachable site are different problems.
Use this as a convenient status view. For a production service that requires dependable incident notification, keep your established monitoring and alerting process too.
2. Google Search Console: bring four search metrics into the panel
The Google Search Console widget displays performance numbers for one website property. It is aimed at the recurring check: “How is this site's search performance looking over the period I selected?”
Published Search Console preview. The displayed values are preview data, not a report of today's results.
The setup is short:
- Add the component to a Kepo panel.
- Open its settings and set Website to your domain, such as
example.com. - Choose the time range you want to inspect.
- Open the report once and sign in if Google requests it. Your account must have access to the relevant property.
Choose the layout based on the information you need. Small displays clicks and impressions. Wide and large also show click-through rate and average position.
For a practical example, suppose you maintain a product site and a documentation site. Configure a widget for the property you want to review, choose its reporting period, and compare the displayed figures with the same property and period in Search Console. This catches an incorrect domain or time-range selection before it becomes part of your daily routine.
The widget is a compact view of Search Console performance data. It does not turn that data into a live visitor counter. Open the underlying report when you need to examine queries, pages, or a change in more detail.
3. Product Hunt: a compact list for launch discovery
The Product Hunt feed widget shows recent launches from Kepo's hosted Product Hunt feed. It brings product names, descriptions, icons, and links into a small browsing surface.
Published Product Hunt preview. Products, dates, and counts reflect the preview rather than the current launch list.
For an indie developer, this can be a useful place to discover how other makers describe a problem, package a feature, or present a product. Scan the list, choose one relevant launch, and follow its link when you want the full context.
The feed can include richer details such as votes, comments, ranks, topics, and makers. The plugin documentation specifies that counts, ranks, makers, and icons are read from the official API when available. Do not assume every item will always have every field.
A good way to use this component is to put a time boundary around discovery. Give yourself a short browsing window, save one idea worth investigating, and return to your own work. A compact feed is most useful when it supports that habit.
4. Pomodoro Clock: start work after the checks
The Pomodoro Clock widget supports work sessions, breaks, and recent completion records. It gives the panel an action you can take after checking the other widgets: start the next task.
Published Pomodoro Clock preview. The wide layout includes recent completion records.
The defaults are 25 minutes of work and 5 minutes of break time. Both durations can be changed in the widget settings. Available actions include start, pause, resume, finish, and reset.
To try it, choose one concrete task—such as drafting a changelog or fixing a small bug—then start a work session. Pause if you need to interrupt it, resume when you return, and switch to a break when appropriate.
Completed work sessions are stored locally. The wide layout shows recent records, which makes it useful when you want to look back at completed sessions. The plugin requires no login and does not open a browser.
Those records belong to the local widget data. Clearing that data removes them, so they should not be your only record if you need durable time tracking.
Choose a small starting layout
You can find all four in the Kepo widget store. This is a suggested arrangement rather than a requirement to install everything:
| Component | What it helps you do | Useful layout choice | Key dependency |
|---|---|---|---|
| Web Status | Check one URL and its recent history | Wide for visible history | Valid URL and scheduled checks |
| Search Console | Review one property's search performance | Wide or large for four metrics | Google access and the selected reporting period |
| Product Hunt | Discover recent product launches | Large for more reading space | Kepo's hosted feed and available source fields |
| Pomodoro Clock | Run focus sessions and breaks | Wide for recent records | Local widget data |
Start with two components if that covers your routine. Add a third when you have a recurring reason to check it. Kepo's Mac desktop widgets overview explains how these components fit into a panel you can bring up with Option + Space.
Three questions before you install
Do these four plugins require AI generation? No. These are existing store plugins. Install the relevant plugin and configure the component you want to use.
Does every widget need an account? No. Pomodoro Clock requires no login. Search Console needs access to your Google property. Check each plugin's setup notes rather than assuming all components share the same requirements.
Are the screenshots showing live results? No. They are the actual preview images published with the store versions. Verify your own widget's configured source and results after installation.
Which would earn a place in your daily panel: website checks, search metrics, launch discovery, or a focus timer?
Top comments (0)