Practice Radar
Changelog

What has changed, week by week.

Every entry below is something that shipped, taken from the build history and written in the words a practice owner would use. Internal plumbing is left out. Weeks with nothing worth telling you about are left out too.

Week seven

Your whole area on the record: CQC, NHS contracts and who owns each practice

A new page, CQC, NHS and ownership insights, on every plan, built on the official registers' own APIs.

  • CQC inspections for every practice within your radius, on a map coloured by what CQC last reported, with the previous owner's report where a new owner has none yet.
  • Who is taking new NHS adults, children and urgent care, from the NHS's own directory.
  • NHS contracts near you: yearly value, price per unit of dental activity, how much of this year's target is delivered, and NHS patients seen.
  • Who owns each practice, the groups holding more than one, and every sale or change of control in the last two years, from Companies House.
  • Search to enquiry now shows the calls, website clicks and directions your Google listing brings each month, against the same month last year.
  • New maps: a cleaner light map, a proper dark map in dark mode, and zoom on the CQC map.
  • Approved website changes are now sent to IndexNow, so Bing and the other engines that take part read them again within days.
Week six

The first feature that does the work

Until now every screen ended at a recommendation. This week the copy audit's recommendations became changes you approve, and the product applies them.

  • The Practice Radar Connector: a small plugin, or a snippet for Code Snippets, that lets the product read your WordPress site's titles, descriptions, social previews and image alt text, through Yoast, Rank Math or SEOPress.
  • Website changes, a new tab on the copy audit: each suggestion beside the wording it would replace, editable, with approve and dismiss. Nothing is written without your click.
  • Every applied change is checked on the live page, logged with what it replaced, and can be put back with one click.
  • Alt text drafted for images that have none, and one block of structured data for a home page that declares none, both waiting for approval like everything else.
  • After each monthly audit the engine proposes what it would change and emails you that they are waiting.
  • An applied change shows the tracked search's position on the day it went live and the latest reading since.
  • A new Execution group in the sidebar holds the screens that do work rather than report it: Website changes, Ad negatives, Review replies and the Request kit.
  • Seven more kinds of website change, each proposed from a reading and applied through connector 0.3: a drafted local page for a search with no page, answers to the questions rivals answer, structured data for treatments and people, an internal link from a page that ranks, a broken link fixed and its dead address redirected, an oversized image compressed, and a duplicate heading reworded. The queue gained a kind filter, a diff card for content changes, a draft card for new pages and a before and after slider for images.
  • Ad negatives: the search terms that took budget without booking anyone are proposed as negative keywords. Approve one and it is added to the campaign it fired in through the Google Ads API, read back, and can be put back with one click.
  • Every proposed change now explains itself in three parts: why it is proposed, what it aims to do, and how you will know.
  • An install page walks through the plugin in three steps with screenshots.
Week five

A page built for ad clicks, and every dashboard made easier to read

Two halves. The first paid traffic pointed at the product, and a pass over the screens you read every week to make them sortable, filterable, printable and quicker to take in.

  • A landing page for Google Ads, written for somebody arriving from a search rather than from the rest of the site.
  • A signup from an advert is counted without a tracking pixel: the click reference travels in the link and is recorded with the signup, so nothing is stored in your browser.
  • The four plans now also sit in one table, line by line, and the monthly or annual choice drives the prices in it as well as on the cards.
  • Every table sorts by any column, three clicks back to the order it arrived in, and your own row keeps its tint and its marker wherever the sort moves it.
  • Moving across a chart, by pointer or by arrow key, reads out the month and what each line was worth. A month the engine did not read says so instead of showing a figure.
  • A setup checklist on the dashboard: which of your Google accounts are connected, when you want to be alerted, whether your report is shared. Steps tick off from what the server can see, not from you saying so.
  • The terms now say plainly where responsibility sits for review replies written for you, and recommend keeping replies as drafts until the tone is right.
  • Website changes: connect a WordPress site with the Practice Radar Connector and the copy audit's title and description suggestions become a queue you approve one by one. Each applied change is checked on the live page and can be put back with one click.
  • Alerts choose what to be emailed about, finding by finding, and the page no longer mentions channels that do not exist yet.
  • One bar splitting your town's search value between the practices in it, with your own share marked, on the dashboard, the market map and shared pages.
  • Rankings gained quick filters for what is in the pack and what moved up, down or in new, each with its real count, and a grid of every tracked search against every date it was read.
  • Any table can be downloaded as a spreadsheet or printed, and the printed sheet drops the navigation and repeats the column headings on every page.
  • The keyboard palette now switches market and runs actions as well as jumping to a page.
  • An agency can name which practice is its client in each market, so a figure written in the first person only ever reaches the practice it measures.
  • The guides index became a grid of cards, each with its date and a reading time counted from the words in that guide rather than typed in by hand.
  • The longest guide carries a contents rail that marks the section you are reading, and the features page's anchor row now sticks under the header and does the same.
  • A dismissible line under the header about founding rates, and this changelog.
  • The privacy notice now says where backups are kept, on which machines, and for how long.
Week four

Annual pricing, your own brand on shared pages, and every dashboard read end to end

The longest week of the build so far, and most of it went on the things you read rather than the things that fetch the data.

  • Pricing can now be paid monthly or annually, with the saving in pounds and what the free month is worth shown beside each plan.
  • Starting a plan while your free month is still running no longer shortens it.
  • Every dashboard compares itself with the week or month before, in plain words: links, ads, content gaps, the rank grid, search demand, performance, assistant answers, citations, the page crawl and your Google listing.
  • A page with nothing measured yet says what it is waiting for and offers the one action that fills it, instead of showing a blank.
  • Agency plans carry the agency's own brand: their logo in the dashboard and on every shared page, their colour on buttons, navigation and links.
  • A shared link can only ever carry public information, by design, and every deletion is written to an audit record.
  • The share chart now labels which months were estimated before tracking started and which were measured, and says so in the key rather than in a footnote.
  • On a phone the market map comes first, the filters fold into one toggle, wide tables stack, and every control is a real thumb size.
  • Sixty interface components were rebuilt from a public catalogue into the product's own styles: one header row on every page, tables in frames, a keyboard command palette, and the same shapes across the site and the dashboard.
Week three

Your own Google accounts, and a monitor that watches your town for new practices

The week the product stopped being only about public data and started reading what you already own, if you let it.

  • Search Console, Analytics, Google Ads and your Business Profile can each be connected, separately, and each one is revocable in your own Google account. Every connection has a page showing what it adds.
  • Assistant answers now cover four platforms rather than one.
  • A daily roster monitor: a practice that opens near you, or closes, is picked up rather than waiting for somebody to notice.
  • Actions you have taken are tracked, so the brief stops recommending something you have already done.
  • A structured data tab, so you can see what your site is telling Google about itself.
  • A nightly backup of the database and the market data, kept on the server for fourteen days.
  • The monthly brief now gives three different kinds of action rather than three versions of the same one.
  • Five markets had a practice wrongly excluded from their roster. Fixed, which means the share figures in those towns changed.
  • The signup copy tells the truth about how a map is built: automatically, and instantly with an email address at the practice's own domain. Every "within a week" claim is gone.
  • Labels across the whole product dropped letterspaced capitals for plain sentence case.
Week two

The rank grid on a real map, assistant answers, and the free month end to end

Week two turned the dashboards into something a practice could be handed rather than shown.

  • The rank grid: your position for any tracked search drawn on the map itself in red, amber and green, so proximity stops being invisible.
  • Assistant answers: whether an AI assistant names your practice when a patient asks, with its own page and a place in the monthly pull.
  • The market map opens fitted to your market, separates practices sitting on top of each other as you zoom, filters by distance, and reads live NHS status.
  • Each action in the monthly brief carries its steps, its likely impact and how often it matters.
  • The free month works end to end: signup, verification, your market resolving, the build narrated while it runs, and what happens when the month ends.
  • Every surface still waiting for data says when it arrives and what it will come from, rather than showing a blank figure.
  • Every figure about you is now checked against whether the person looking is the practice being measured. One shared market could show a figure to the wrong viewer; it cannot now.
  • The weekly digest got a schedule, and the trial emails got the product's own design.
  • An audit of every claim on the marketing site: twenty-six checked, fourteen corrected, one removed.
  • Real product screenshots and a seventeen-second film of the product replaced the abstract art, at a tenth of the page weight.
Week one

The first working build: one map of one town

Practice Radar started as a map of one town, built to answer a question about one practice. Week one is that map becoming a product.

  • The market map: every practice competing with yours drawn on the map, each with its own identity, its NHS status, its type, and a filter for every tracked search.
  • Rankings, pack watch, the reviews race, links and ads, each on its own dashboard.
  • The monthly brief, and the alerts behind it.
  • A national benchmark cohort of 112 towns and 1,287 practices, so a figure has something to be measured against, and the product states the sample it used.
  • The product took its name.

See what it does for your own town.

The log above is the product this month. The free month points it at your market: every practice competing with yours, sized by the share of local search each one holds, re-checked every week.

Run on our own practice first: ninth of the eighteen practices in its town in May, first in September, on UK-wide search value. Page-one keywords: 6 in May, 194 now.

Start your free month See every feature

Free first month · No card · Map builds within one working day · Nothing starts when the month ends