Nightwatch Review

Updated September 2026 · Written and maintained by the Progression Agency strategy team

Nightwatch is a rank tracker built around fine-grained location tracking, competitor monitoring and agency reporting. This overview is compiled from published documentation and pricing rather than hands-on testing, and it is organized around the thing that decides whether the tool is worth it: whether you will ever act on the difference between one place and another.

Scope of this page

What follows is assembled from the vendor’s published documentation, feature list and pricing structure, together with how location-granular rank tracking works as a category. It is not a hands-on test, no score is awarded, and no claim is made about living with the product over time.

Stating that is not a disclaimer for its own sake. A page that reads like experience but was written from a features page is worse than useless, because it is confidently wrong in ways the reader cannot detect.

The granularity question, in five parts — Fine-grained tracking is the feature people buy and the reason the bill surprises them. Both facts come from the same arithmetic.

Why a national position is often the least useful number you have

A service business asks a rank tracker one real question: where are we weak? A single national or country-level position cannot answer it, because it is an average of places and therefore describes none of them.

How much a national average position hides — The single national number is the one figure in the set that describes nowhere. For a business with service areas, it is close to useless.

The average hides exactly what you would act on

The suburbs where you already rank well need nothing. The areas where you sit outside the first page are where the next customer is. Averaging the two produces a middling number that moves slowly, tells you nothing about cause, and reliably provokes the wrong decision.

Proximity makes local results genuinely different

Local search results depend heavily on where the searcher is standing, and that is not something you can edit. Two people three miles apart see different results for the same query. Any tracker reporting one position for a whole country is flattening that away by design.

National — describes nowhere. An average of places, matching none of them.

City — the usable minimum. Matches what a customer in that city sees.

Postcode — for dense areas. Where a mile changes the result.

Grid — for map pack work. A matrix of points around a location.

Device — a separate axis. Local search skews heavily mobile.

Competitors — vary by area. The rival in one suburb is not the rival in the next.

What granularity actually buys you

What each level of tracking granularity can answer — Granularity buys you the ‘where’ question. If you never act on location, you are paying for an answer you will not use.

It converts monitoring into direction

Country-level tracking answers ‘is it improving?’. Area-level tracking answers ‘where should we work next?’, which is the question that changes what anyone does on Monday. That shift from monitoring to direction is the entire argument for paying more.

It is only worth it if you would act on it

A national ecommerce brand with one warehouse and no service areas gains almost nothing from postcode-level positions, because there is no location-specific action available. The feature is not better or worse in the abstract; it is a service-area feature.

Grids are sampling, not omniscience

Map-grid tools place a matrix of points around a location and check each one. That is a sample of a continuous surface, which is a good approximation and not the same as knowing every address. Read grid output as a pattern, not a census.

Noise — expect it. Local results move more than national ones.

Personalization — unavoidable. No tracker sees an individual's exact result.

Sampling — how grids work. Points on a map, not every address.

Volatility — higher locally. Small result sets swing more.

Trend — the only honest read. Direction across weeks, per area.

Verify — occasionally. Check one area manually each month.

The arithmetic that decides your bill

Location tracking is priced the way it is because it multiplies. This catches nearly everybody once.

How a keyword count grows
Setup	Terms	Areas	Devices	Tracked total
Single-location shop	20	1	1	20
Same shop, mobile and desktop	20	1	2	40
Service business, five towns	20	5	1	100
Same, both devices	20	5	2	200
Trimmed to real intent terms	8	5	1	40
Agency, ten clients, five towns each	8	50	1	400
Franchise, forty locations	6	40	1	240

Trim terms, keep areas

The instinct when the bill arrives is to cut locations, which removes exactly the insight you paid for. Cut term variants instead. ‘Emergency plumber’, ’emergency plumber near me’ and ’24 hour plumber’ usually rank almost identically and tracking all three triples the cost for no additional decision.

Mobile-only is defensible for local

Local service searches skew heavily to mobile. Tracking mobile alone halves the count and loses little for that use case, which is a much better economy than dropping service areas.

Terms x areas — the real count. This is the number your bill is based on.

Trim terms — not areas. Areas carry the insight; term variants rarely do.

Mobile only — for local. Defensible, and halves the count.

Weekly refresh — often enough. Daily rarely changes a decision.

Two rivals — per area. Not fifteen across the account.

Review monthly — not daily. The data is slow by nature.

Design the schema before you import anything

Designing a tracking schema before you import anything — Almost every complaint about tracking cost or noise is really a complaint about a schema nobody designed.

Write down the service areas you would genuinely send someone to
Pick one keyword per commercial intent, not per phrasing
Multiply terms by areas and look at the number before you commit
Decide the device policy deliberately rather than accepting the default
Choose two real competitors per area, not a long list across the account
Group everything by area so reports segment cleanly later
Set a monthly review cadence and stick to it
Write the schema down somewhere outside the tool, so a migration is possible

Almost every complaint is a schema problem

Too expensive, too noisy, too many charts nobody reads — these are usually symptoms of a keyword set that was imported rather than designed. Twenty minutes of planning at the start prevents most of it.

The agency case

Trackers by location granularity and reporting depth — Granularity and reporting depth are separate axes. Agencies usually need both, which is why they end up in the more expensive corner.

Reporting is the feature agencies actually pay for

White-label reports, scheduled sends and client-facing dashboards remove a recurring monthly task across every client at once. For an agency that is not a nice-to-have — it is the difference between reporting being an afternoon and reporting being automatic.

API access is where it stops being a dashboard

Rank data becomes considerably more useful when it sits alongside analytics, call tracking and conversion data in one place. That requires an API and usually a higher tier, so price that tier at the start if you intend to build anything.

Annotations are underrated

A chart showing a rise means nothing without a note saying what changed that week. Recording ‘new page published’, ‘site migration’, ‘competitor relaunched’ against the timeline is what makes rank reporting explainable rather than decorative.

Scheduled sends — save real hours. The report that arrives without being asked for.

API access — for pipelines. Where rank data joins the rest of your reporting.

Dashboards — for clients. Live beats a monthly PDF, when clients will look.

Segments — by area. One client, several stories, told separately.

Annotations — underrated. Marking what changed is what makes charts explainable.

Granularity levels, compared

Choosing the right level of location precision
Level	Best for	Typical cost impact	Main limitation
Country	National brands and publishers	Lowest	Describes nowhere in particular
State or region	Broad regional coverage	Low	Still averages across many markets
City	Most service businesses	Moderate	Misses variation inside large cities
Postcode	Dense urban service areas	High	Only worth it where a mile changes the result
Coordinates	Precise single-point checks	High	Easy to over-specify and over-pay
Map grid	Map pack visibility mapping	Highest	A sample of points, not every address

City level is the honest default

It matches what a customer in that city actually sees, it is affordable, and it answers the ‘where should we work’ question for the overwhelming majority of service businesses. Go finer only where you can name a reason — usually a dense metro where two neighborhoods genuinely behave differently.

Over-specifying is the expensive mistake

Coordinate-level tracking across thirty points when six towns would have told the same story is the most common way to turn a useful subscription into an expensive one. Precision you cannot act on is cost, not insight.

Who it fits

Who genuinely needs fine-grained tracking — Location granularity is a service-area feature. Outside that context it is cost without a corresponding decision.

A month of local rank data, read properly — The point of location tracking is not more numbers. It is knowing which place to work on next, which takes about a month to see.

Strong fit

Multi-location service businesses, franchise networks, and agencies reporting to local clients. In all three, the difference between one area and another is the actual subject of the work, and reporting is a recurring cost that automation genuinely reduces.

Weak fit

National ecommerce, publishers and anyone whose ranking is not location-dependent. They are paying for an axis of data with no corresponding lever.

The single-location case is genuinely mixed

One shop with one catchment sometimes still benefits, because a catchment is not uniform and the edges of it are where growth usually is. But the gain is smaller and a cheaper tracker with city-level tracking often covers it.

Agencies — the core buyer. Many clients, many areas, one reporting burden.

Multi-location — the obvious case. Each branch is its own competitive situation.

Single location — sometimes. One catchment can still hide big differences.

National brands — rarely. Location granularity answers a question they do not have.

Publishers — no. Nothing about the model applies.

What local rank tracking cannot tell you

It measures one signal well and is silent on several things that decide local performance.

It cannot tell you why an area is weak — only that it is
It does not measure the map pack and organic results as one thing; they are separate races
It cannot see the effect of proximity, which is the strongest local factor and not editable
It says nothing about review volume or velocity, which genuinely move local rankings
It does not audit your business profile, where most local problems actually live
It cannot distinguish a ranking that produces calls from one that produces nothing
It samples locations rather than covering every address
It cannot see the personalized result an individual searcher gets

The business profile usually matters more than the tracking

Categories, service areas, hours, photos and questions on a business profile decide more local outcomes than most on-site work does. A tracker that shows a weak area is useful precisely because it sends you to look at those things for that area.

Both volume and how recently they arrived matter. An area with thin, old reviews will underperform one with steady recent ones, and no amount of tracking changes that until somebody asks customers for reviews.

Map pack — a different result. Organic position and local pack are separate races.

Proximity — dominates local. The searcher's distance is a ranking factor you cannot edit.

Reviews — move local rank. Velocity and volume both matter.

Citations — supporting, not decisive. Consistency matters more than count.

Reading the data honestly

How to interpret local rank movement
What you see	Most likely cause	Sensible response
One area moves, others do not	Genuine local change or local competitor activity	Look at that area specifically
Every area moves together	Algorithm update or a site-wide change	Check the site and the date, not the areas
Constant small swings in one area	Small local result set, high volatility	Ignore; read the monthly trend
Strong organic rank, no calls	Map pack is winning the query	Work the business profile, not the page
Grid shows a hot center, cold edges	Proximity working as expected	Target content and profile signals at the edges
Good positions, poor conversions	Wrong intent or a weak landing experience	Fix the page, not the ranking
A new area starts strong	Low competition, not brilliance	Verify it is a real market before celebrating

Report outcomes, not positions

For a local service business the unit that matters is calls and bookings by area. Rank is the leading indicator; the call log is the result. A report showing both is far harder to argue with than one showing green arrows.

Verify one area manually each month

Pick a service area, check two or three terms from that location, and confirm the tool agrees. It takes ten minutes and it is the only way to know the data underneath the reporting is still sound.

Search Console — by page, not place. It will not answer the 'where' question.

Analytics — behavior after arrival. Location tracking ends at the click.

Call tracking — closes local loops. For service businesses, calls are the conversion.

Together — the real picture. No single source covers local performance.

Report outcomes — not positions. Calls and bookings, by area.

Comparing local visibility sources

What each source can and cannot answer about local performance
Source	Answers	Cannot answer	Cost
Local rank tracker	Where you rank, by area, over time	Why, or whether it produced anything	Subscription, scales with areas
Google Search Console	Real impressions and clicks, by query and page	Anything by geography beyond country	Free
Google Business Profile insights	Calls, direction requests, profile views	Organic web positions	Free
Analytics	What visitors did after arriving	Where the search happened	Free
Call tracking	Which area and campaign produced calls	Search positions	Paid, usually modest
Manual checks	Ground truth for one place, one moment	Any trend at all	Free, but time
Review monitoring	Volume and recency of reviews by location	Rank directly, though it influences it	Free to modest

No single source covers local performance

The tracker knows where you rank and nothing about outcomes. The business profile knows about calls and nothing about organic positions. Search Console knows real clicks and almost nothing about geography. A local reporting setup is these three read together, which is why the API matters to anyone building it properly.

Start free, then add the paid piece you actually need

Search Console, business profile insights and analytics cost nothing and answer a surprising amount. The specific gap they leave — where you rank, by area, against named competitors, over time — is precisely the gap a local tracker fills, and knowing that keeps the purchase honest.

What only a trial will tell you

Documentation establishes scope and price. It cannot establish whether the location granularity is precise enough for your particular geography, how the reports look to a client who is not you, or whether support answers quickly when something breaks mid-month.

Set up one real client or one real service area, not a demo
Verify positions manually from inside that area
Generate a white-label report and look at it as the client would
Test whether the granularity distinguishes two neighborhoods you know differ
Check the API on your intended tier if integration matters
Export everything once, to confirm you could leave
Ask support a real question and time the reply

Judge the report, not the dashboard

Dashboards are for you; reports are for the client. If the exported report needs editing before you would send it, that editing is a recurring monthly cost, and it belongs in the comparison.

SEO for small businesses — Google Search Central. Where local tracking fits a service business.

Analyzing performance on Google Search — Google Search Central. Grounding rank data in first-party reporting.

Do you still need a website in 2026? — Google Search Central. Context for local visibility work.

Questions about Nightwatch and local rank tracking

Want local visibility reported by area?

We track the service areas that matter, tie positions to calls and bookings, and tell you which neighborhood to work on next.

Talk to us about local SEO

Getting found in search

AI, AEO and what is changing

Paid media and lead generation

Websites and design

Choosing and working with an agency

Social, content and brand

By industry and by situation

Frequently asked questions

What is Nightwatch?

A rank tracker built around fine-grained location tracking, competitor monitoring and agency reporting, including white-label reports and API access.

Is this a hands-on review?

No. It is an overview compiled from published documentation and pricing, set against how location-granular rank tracking works as a category. No score is awarded and no testing is claimed.

Why does location granularity matter?

Because a national average position is an average of places and therefore describes none of them. For a service business the useful question is which area is weak, and only area-level tracking answers it.

Do I need postcode-level tracking?

Only if a mile changes the result where you operate, which is true in dense urban areas and less true in sparse ones. City-level is the usable minimum for most service businesses.

Why did my tracked keyword count explode?

Because locations multiply. Twenty terms across five towns on two devices is two hundred tracked keywords, not twenty. This is the arithmetic that decides the bill.

How do I reduce cost without losing insight?

Trim term variants, not areas. Three phrasings of the same query usually rank almost identically. Areas carry the insight; phrasings rarely do.

Should I track mobile and desktop for local searches?

Mobile alone is defensible for local service queries and halves your count. That is a far better economy than dropping service areas.

What is a map grid?

A matrix of sample points placed around a location, each checked separately, producing a heat map of local visibility. It is a sample of a continuous surface, so read it as a pattern rather than a census.

Does it track the map pack as well as organic results?

Local pack and organic are separate races and should be tracked as such. A strong organic position with no calls usually means the map pack is winning the query.

Why can I not fix proximity?

Because it is the searcher’s distance from the business, not a property of your site. It is the strongest local ranking factor and the one you have no control over, which is why service-area strategy matters more than on-page tweaks for local work.

What actually moves local rankings?

The business profile — categories, service areas, hours, photos, questions — plus review volume and how recently reviews arrived, plus relevance of the landing page. Tracking tells you where to apply those; it does not apply them.

Who is this kind of tool for?

Multi-location service businesses, franchise networks, and agencies reporting to local clients. In all three, the difference between areas is the subject of the work.

Who should not buy it?

National ecommerce brands, publishers, and anyone whose ranking is not location-dependent. They would be paying for an axis of data with no matching lever.

Is it worth it for a single location?

Sometimes. A catchment is not uniform and its edges are usually where growth is. But the gain is smaller, and a cheaper tracker with city-level granularity often covers it.

What makes it an agency tool?

White-label reporting, scheduled sends, client dashboards and an API. Those remove a recurring monthly task across every client at once, which is where the money is saved.

Do I need the API?

Only if you intend to combine rank data with analytics, call tracking or conversion data in one place. If you do, price that tier from the start because it is usually a higher one.

How should I design my keyword set?

Real service areas, one term per commercial intent, a deliberate device policy, two competitors per area, everything grouped by area, and the whole schema written down outside the tool.

How often should I review the data?

Monthly. Local results are more volatile than national ones, so weekly reading produces reaction rather than decision.

What should I report to a client?

Calls and bookings by area alongside position trends. Rank is the leading indicator; the call log is the result, and a report showing both is much harder to argue with.

Why does one area swing constantly?

Small local result sets are inherently volatile — fewer competing businesses means larger apparent movement. Read the monthly trend for that area and ignore the daily figure.

How do I verify the tool is accurate?

Pick one service area each month, check two or three terms from that location, and confirm the tool agrees. Ten minutes, and it is the only check that matters.

What should I do during a trial?

Set up one real service area, verify positions manually from inside it, generate a white-label report and read it as a client would, test whether it distinguishes two neighborhoods you know differ, and export everything once.

Sources and further reading

Get a free marketing proposal

Tell us what you are trying to grow and we will come back with a plan, not a pitch deck. Same-day reply on weekdays.