PeekabooICU is the public face of the Business Visibility Center (BVC) — a measurement system that checks whether real customers, search engines and AI systems can find your business, understand it, and trust it. This report is a complete, honest inventory of what the system can actually do today. It is written for business owners, not engineers. Every entry carries a status marker and an evidence level, so you can tell the difference between something that is proven in daily operation, something that is built and waiting for its first real use, something that is ready to connect to an outside service, and something that is still planned. Nothing in this report is aspirational marketing. If a capability is partial, disconnected or operator-only, it says so.
Only entries marked PROVEN are validated against the current certified BVC baseline. Nothing else is described as certified.
The core measurement: one canonical check of a real website across every visibility category we score.
Type your website address and get a full visibility check in about a minute — no account, no card, no salesperson.
Why it matters — You find out where you actually stand before spending a cent, using the same engine paying customers use.
A brand-new visitor can run three complete audits before being asked to create an account.
Why it matters — Enough room to check your own site and compare it to two competitors before committing to anything.
Every audit — free, paid, embedded, scheduled or run from a station — is produced by the exact same measurement engine.
Why it matters — A free result and a paid result are the same measurement. Nothing is held back to make an upgrade look better.
Your business is checked across search, AI understanding, local presence, trust and authority, business identity, online actions and code readiness.
Why it matters — Being findable is not one thing. A site can rank well and still be invisible to AI assistants, or trusted by people and unreadable by machines.
Newer categories are measured quietly and clearly labelled before they are allowed to affect your score.
Why it matters — Your score never moves because we were experimenting. A new measurement has to earn its place first.
Each category is built from many individual checks against your live site and public sources, each recording what it found.
Why it matters — Findings are traceable to something real, not to an opinion or a generic checklist.
When something genuinely cannot be checked, the result says so instead of scoring it as zero.
Why it matters — A missing measurement and a bad measurement are different facts. Treating them the same would mislead you.
Automatic protection stops the free audit from being abused, without getting in an ordinary visitor's way.
Why it matters — Keeps the free check fast and available for real business owners.
If a check fails because of a problem on our side, the attempt is given back to you rather than counted against your allowance.
Why it matters — Our reliability problem should never become your cost.
How the number is produced, and the guardrails that keep it comparable over time.
A single headline number summarising how visible your business is right now.
Why it matters — One number you can track, share with your team, and argue about productively.
A plain-language rating — Excellent, Good, Fair or Needs Work — attached to the number.
Why it matters — Tells you whether the number is good news without needing to know the scale.
Every result states how much evidence it was built from, from high confidence down to insufficient data.
Why it matters — A confident score and a thin score should not be treated as equally reliable.
Each category reports how much of it could actually be measured on your site.
Why it matters — Shows whether a weak category is genuinely weak or simply not visible to us yet.
A prioritised list of what to fix, ordered by severity, with the reason it matters and what to do.
Why it matters — Turns a score into a to-do list your web person can work through on Monday morning.
Every audit records the exact standard and scoring version used to produce it.
Why it matters — A score from March and a score from September can be compared honestly, because you can see whether the ruler changed.
The scoring engine is fingerprinted and locked. Any change to it is detected automatically and has to be a deliberate, versioned decision.
Why it matters — Your score cannot quietly drift because of an unrelated change somewhere else in the system.
Scoring calibration is managed and change-logged by our team, never adjusted per customer.
Why it matters — Nobody gets a flattering score. Every business is measured with the same ruler.
A fixed set of reference sites is re-scored to confirm the engine still behaves the way it did before.
Why it matters — Catches silent measurement drift before it ever reaches a customer's report.
Getting the result out of the screen and into a meeting, an inbox, or a client deliverable.
Every completed audit has its own page you can send to a colleague or supplier.
Why it matters — No screenshots, no exporting, no explaining — just send the link.
A clean, print-formatted version of the full report.
Why it matters — Works for a board pack or a client folder without any design work.
A generated PDF of the full report, produced on our side rather than by your browser.
Why it matters — A consistent, presentable document you can attach to an email or invoice.
The completed result is also available in a structured format that other software can read.
Why it matters — Lets a developer or agency feed results into their own dashboard or client reporting.
Known limitation — Only completed audits are exposed. Internal scoring mechanics are never included.
One place listing every finished report on your account, with links to view, download and verify each one.
Why it matters — Nothing gets lost between audits.
Professionals who deliver reports to clients get a monthly capacity of branded reports, tracked and shown as it is used.
Why it matters — You know exactly how much delivery capacity you have left in the month.
Known limitation — Purchasing additional capacity requires payment processing, which is not connected yet.
Finished reports and notifications can be delivered by email, with consent and unsubscribe handled properly.
Why it matters — The report reaches the person who needs it without anyone logging in.
A side-by-side comparison of audits, exported as a single document.
Why it matters — Shows a client or a boss exactly what changed, in one page.
Creating an account, keeping your work, and controlling who else can see it.
Create an account with an email address and keep every audit you run.
Why it matters — Your history becomes an asset instead of a series of one-off checks.
Audits you ran before signing up can be attached to your new account.
Why it matters — You do not lose the check that convinced you to sign up.
Your current position, recent activity and quick access to everything on your account.
Why it matters — One place to start, instead of hunting for the right page.
Your audits, reports and business data are only visible to you and the people you invite.
Why it matters — Especially important if you are an agency holding several clients' data in one place.
A result that belongs to an account is not publicly viewable unless you share it.
Why it matters — You decide who sees your weak spots.
Invite staff or colleagues into a shared organisation with a defined role, and remove them again.
Why it matters — Your marketing person can work without sharing your login.
Known limitation — Membership behaviour is enforced and change-logged, but has no dedicated automated test suite yet.
An agency account can be formally linked to a client account, and that link can be ended.
Why it matters — Handover is clean: when the relationship ends, the access ends with it.
Keeping the record, and being able to prove what it said at the time.
Every audit on your account, filterable by website and status.
Why it matters — Progress only means something if you can see where you started.
An audit stores what was found and how it was scored at that moment, not just the final number.
Why it matters — A result from six months ago still means exactly what it meant then.
Reconstructs an older audit exactly as it was scored, and flags where today's standards differ.
Why it matters — Settles the 'did my score drop, or did your rules change?' question with evidence.
Known limitation — Reachable by direct link rather than from a menu, and unavailable for audits that pre-date snapshotting.
Each audit keeps a record of what happened during the check.
Why it matters — When something looks wrong, there is a factual record to look at rather than guesswork.
Old operational records are cleaned up on a schedule rather than accumulating forever.
Why it matters — Keeps the system fast and keeps stored data proportionate.
Automatic re-checks so you find out about a problem before your customers do.
Put a website on a weekly or monthly schedule and it is re-audited automatically.
Why it matters — Visibility decays quietly. Monitoring turns that into something you get told about.
Known limitation — Not included on the free tier.
Set how big a drop has to be before it is worth telling you about.
Why it matters — You hear about real problems, not normal week-to-week noise.
Raises an alert when your rating moves between bands, such as Good dropping to Fair.
Why it matters — A band change is the moment the outside world starts noticing.
Detects when a scheduled check could not complete — a site down, blocking us, or timing out.
Why it matters — A check that cannot run is itself important news about your site.
A suspected problem has to be confirmed across checks before it is treated as a real incident.
Why it matters — One bad moment on the internet is not an emergency. A sustained one is.
A single list of every alert raised on your monitored sites.
Why it matters — Nothing important is buried in an inbox.
Alerts can be delivered by email as well as shown in the app.
Why it matters — You find out when you are not logged in — which is most of the time.
A background watchdog checks that monitoring itself is still running on time.
Why it matters — Silence should mean 'nothing wrong', not 'monitoring quietly stopped'.
Seeing movement — against your past self, or against someone else.
Compare two or three completed audits directly against each other.
Why it matters — Proves whether the work you paid for actually moved anything.
Known limitation — No dedicated automated test suite covers the comparison view yet.
Run the same check on a competitor's public website and compare the results.
Why it matters — Turns an abstract score into a concrete competitive position.
Your score history per website, shown over time.
Why it matters — Shows direction of travel, which matters more than any single number.
When a comparison spans a change in our standards, the difference is called out.
Why it matters — Prevents a rule change being mistaken for a real decline.
For businesses that are not one website at one address.
Organise what you own as businesses, the locations under them, and the websites under those.
Why it matters — A franchise or multi-branch business finally matches how it really works.
Each location keeps its own record of identity details and findings.
Why it matters — Local visibility is won or lost per location, not per company.
Reassign a website to a different location without losing its history.
Why it matters — Reorganisations happen. Your data should survive them.
The system refuses to attach a location or website to the wrong owner.
Why it matters — Stops one client's data from ever landing under another client.
A physical, scannable presence placed at a real business that delivers a real audit to whoever scans it.
A named station tied to a host business, with its own permanent scannable code.
Why it matters — Turns a counter, a window or a table at an event into a working lead instrument.
Each station has a permanent web address and a downloadable code image for printing.
Why it matters — Print once. The code never has to change, even if what it shows does.
Scanning a station opens a phone-first free audit screen that names the host business.
Why it matters — A visitor gets real value in under a minute, standing at the counter.
A station can be drafted, activated, paused, reactivated and retired.
Why it matters — A host that leaves, or a printed code that goes astray, can be switched off immediately.
A station code only works on our own site. Copying it onto another website does not work.
Why it matters — The code cannot be lifted and used to run someone else's front door.
Find any station by name, host, location or code, filter by state or remaining capacity, and sort by activity.
Why it matters — A network of a hundred stations stays manageable by one person.
Scans, refused visits, completed audits, accounts and last activity date, per station.
Why it matters — Shows which placements are working and which are just decoration.
Knowing exactly which physical placement produced which visitor, audit, account and sale.
Every scan of a station is recorded with its outcome — served, or refused and why.
Why it matters — You can tell the difference between a placement nobody scans and one that is being turned away.
Station to visit, visit to audit, audit to account, account to eventual purchase — all linked on our side.
Why it matters — The single hardest thing about physical marketing is proving it worked. This proves it.
Attribution is decided on our side and re-checked against a real recorded visit, never taken on trust from the browser.
Why it matters — Credit cannot be faked by editing a link.
A station's activity only counts as qualified when an audit actually finishes successfully.
Why it matters — A curious tap is not the same as a delivered result, and is not counted as one.
Visit records keep only a coarse device class and a non-reversible network signal. No personal data is collected at the scan.
Why it matters — You get the operational insight without collecting anything a visitor would object to.
When a payment succeeds, it is traced back to the station that originally produced the account.
Why it matters — Revenue per placement — the number that decides where the next station goes.
Known limitation — Built and tested, but cannot run end to end until payment processing is connected.
Controlling how much free value each individual placement gives away.
Set how many completed free checks a particular station will provide. Leave it blank for unlimited.
Why it matters — A trade show stand and a long-term host partnership need very different generosity.
The limit is applied at the exact moment a check finishes, with the station locked, so two people finishing simultaneously can never push it over.
Why it matters — Your cost ceiling per location is a real ceiling, not an approximation.
A station that has reached its limit stops serving new checks politely, and the visit is still recorded.
Why it matters — You still learn that demand existed, even after you stopped paying for it.
Reducing a station's limit below what it has already used stops further use but changes nothing that already happened.
Why it matters — Past results stay true. Records are never retroactively altered.
A paid entitlement comes first, then the station's own allowance, then the standard three free checks.
Why it matters — A paying customer is never blocked by a station's generosity setting.
The internal console our team uses. Listed here for completeness — none of it is customer-facing.
A single console covering customers, audits, reports, communications, deployments, stations, commercial products and system health.
Why it matters — One trained person can run the whole platform without touching the database.
Operator permission is granted from one authoritative list and checked on the server for every privileged action.
Why it matters — There is no second, forgotten way to become an administrator.
Our team can look up a customer, see their activity, and record notes and interactions against the account.
Why it matters — Support conversations start with context instead of questions.
Our team can re-run a failed audit, retry a report that did not generate, and resend a report that did not arrive.
Why it matters — A failure becomes a five-minute fix instead of a lost customer.
Message history, consent, unsubscribe handling and delivery outcomes, managed in one place.
Why it matters — Nobody is contacted who asked not to be, and we can prove it.
Support issues are tracked as cases with an append-only history.
Why it matters — The record of what was promised cannot be quietly edited later.
Privileged actions are recorded.
Why it matters — Accountability for anything done on a customer's behalf.
The operating procedures live inside the console itself.
Why it matters — The platform can be run by someone who did not build it.
What a customer is entitled to, how it is decided, and how it degrades safely.
Plans, prices, descriptions, badges and button labels are managed data, not fixed page text.
Why it matters — Pricing can change without a code release, and the public page can never disagree with the real catalogue.
Business owners and professionals who deliver reports to clients see offers built for them.
Why it matters — A single price list cannot serve both without confusing one of them.
What your account can do is resolved from your plan, your account's current standing, and any time-boxed exceptions.
Why it matters — One consistent answer to 'am I allowed to do this?', everywhere in the product.
If an account falls behind, capability steps down through defined stages rather than collapsing without warning.
Why it matters — A billing hiccup should not instantly destroy your access.
Consumption such as branded report capacity is metered and visible.
Why it matters — No surprise overage, because you can see the meter.
Anything unusual in billing is registered as an exception with a permanent trail.
Why it matters — Money problems are never resolved quietly and invisibly.
A limited-time offer slot that shows nothing at all when no offer is live.
Why it matters — Promotions can run without leaving stale text behind when they end.
Deliberately not connected. Everything around it is finished and waiting.
Card and account payment processing is intentionally not connected at this time.
Why it matters — Stated plainly so nobody assumes checkout works. It does not.
Because payments are not connected, nothing pretends to be purchasable. No button dead-ends into a broken checkout.
Why it matters — Better to say 'talk to us' than to take someone to a page that cannot take their money.
Incoming payment notifications are verified and recorded so the same event can never be applied twice.
Why it matters — Nobody gets double-charged or double-credited by a retried message.
The retry-and-grace timetable for failed payments has no default. Until it is formally approved, automatic progression refuses to run.
Why it matters — Nobody is downgraded or suspended by a timetable nobody agreed to.
Machinery to compare our records against the payment provider's and report differences.
Why it matters — Quiet discrepancies get found instead of accumulating.
Putting a working audit unit on somebody else's website, safely.
A guided path from adding a domain, proving you own it, configuring and previewing, to going live.
Why it matters — A partner site can be live and verified the same day, with no developer call.
A domain must prove it belongs to you before anything will run on it.
Why it matters — Nobody can install your audit unit on a site they do not control.
A set of automatic checks, plus a real browser self-test, before an installation is certified.
Why it matters — 'It's installed' is confirmed by evidence rather than assumed.
A passing installation is certified and recorded, and a copied snippet on an unauthorised site is refused.
Why it matters — You know which installations are genuine and which are not.
A deployment's configuration can be rolled back to a previous known-good version.
Why it matters — A bad change is a one-click problem rather than an emergency.
Live installations report whether they are actually working on the host site.
Why it matters — You find out a partner's site broke the unit before the partner does.
Running the same engine under someone else's brand, or inside someone else's software.
The same free audit unit, embedded on an approved outside website.
Why it matters — A partner's visitors get real value on the partner's own page.
An embedded unit only runs from a verified domain with a live authorisation. Anything else is refused.
Why it matters — The engine cannot be quietly resold by copying a snippet.
Colours, name and presentation can be set per installation, with a change history.
Why it matters — A reseller or association can present the service as their own.
The measurement engine carries no distributor branding. Branding is a layer on top.
Why it matters — The same certified engine can serve several brands without being forked.
Documented addresses for retrieving a completed result, a report document and platform health.
Why it matters — An agency can wire results into its own reporting without waiting for us.
Public endpoints declare caching rules deliberately, and anything account-specific is never cacheable.
Why it matters — One customer's data can never be served from a cache to another.
The system watching itself, and telling the truth about it publicly.
A public page showing current operating state, notices, upstream service health and recent reliability results.
Why it matters — When something is wrong you can check, rather than wonder.
A machine-readable health summary for anyone monitoring the service.
Why it matters — A partner can watch our availability from their own tooling.
When something quietly fails internally, the system records the fact rather than swallowing it.
Why it matters — Silent failures become visible problems that can be fixed.
Refused visits and internal hiccups affecting stations are listed for our team to review.
Why it matters — A misprinted or copied code shows up as evidence instead of disappearing.
The outside data services we rely on are health-checked, with automatic backing-off when one is struggling.
Why it matters — One slow outside service does not take the whole audit down.
Failure conditions are deliberately rehearsed and the results recorded.
Why it matters — We know how the system behaves under failure because we have tried it, not because we hope.
Regular internal snapshots of overall platform condition.
Why it matters — Trends in platform health are visible, not just today's reading.
The permanent factual record underneath everything else.
Each audit records the steps it went through.
Why it matters — Support questions get answered with facts.
Plan, entitlement and billing changes are all recorded as events.
Why it matters — You can reconstruct exactly what an account was entitled to on any past date.
The path from first visit to finished audit to account creation is recorded as events.
Why it matters — Shows where people get value and where they give up.
Key records — billing exceptions, support cases, deployment events, relationship changes — cannot be deleted or edited after the fact.
Why it matters — History is evidence. Evidence you can rewrite is not evidence.
Who can see what, enforced at the data layer rather than by the screen.
Access rules live with the data itself, not in the page you are looking at.
Why it matters — Even a mistake in the interface cannot expose another customer's data.
Two real accounts are used in automated tests that actively try to read each other's data and must fail.
Why it matters — Isolation is proven by attack, not by assumption.
Once something belongs to an account, it cannot be moved to another one.
Why it matters — Removes an entire category of catastrophic mistake.
Every privileged action is authorised on the server. Hiding a button is never the control.
Why it matters — Security does not depend on what your browser chooses to show.
Automated endpoints require a shared operator secret, compared safely, and refuse to run if it is not configured.
Why it matters — Automation cannot be triggered by a stranger.
Contact consent and unsubscribe state are stored and honoured separately from account data.
Why it matters — Opting out of marketing never costs you a service message you need.
Verifiable codes — built, governed, and deliberately awaiting activation.
Every completed audit mints a verification record with its own lifecycle state.
Why it matters — The foundation for proving a report is genuine and current.
A public page where anyone can look up a verification reference and see its state.
Why it matters — A customer or a procurement officer can check a report independently.
Known limitation — The page and lifecycle are live; cryptographic verification is deliberately not activated yet.
A verification can be activated, revoked or expired.
Why it matters — A report that is no longer valid can be marked as such rather than living forever.
Verification activity is governed and can never alter a score, band or confidence level.
Why it matters — The badge can never influence the measurement.
Scannable codes are generated by the platform itself, with no outside code service involved.
Why it matters — No third party sits between your printed code and your customer.
Integration points exist for a governed external code registry.
Why it matters — Registered codes, reprint control and ownership records become possible without redesigning anything.
Your information, in forms you can actually use, kept for a sensible length of time.
Results are available both as a document to read and as structured data to process.
Why it matters — One for the client, one for the spreadsheet.
Audits and their supporting records are retained so history stays meaningful.
Why it matters — Year-on-year comparison is only possible if last year still exists.
A durable record of a business's identity details, kept separately from any one audit.
Why it matters — Your business facts persist even as individual audits come and go.
Results are published in a standard structured format that search engines and AI systems can read.
Why it matters — Your good result becomes something machines can actually understand and repeat.
The work that happens whether anyone is logged in or not.
Monitoring runs, background jobs, reliability checks and cleanup all run on a fixed schedule.
Why it matters — The service keeps working overnight, at weekends and over holidays.
Background work is queued, claimed once, and retried under a defined policy if it fails.
Why it matters — A transient failure does not silently lose your audit.
Two workers can never pick up the same piece of work.
Why it matters — You are never double-charged or double-audited by an internal race.
When an outside service starts failing, the system stops hammering it and recovers gracefully.
Why it matters — One bad dependency does not become a platform outage.
What you can do entirely on your own, without calling us.
Run an audit on your own site whenever you want.
Why it matters — Zero cost, zero friction, immediate answer.
The prioritised fix list is written to be actionable by a business owner or their existing web person.
Why it matters — Most of the value can be captured without hiring anyone new.
Add sites, choose the schedule and set the sensitivity yourself.
Why it matters — Ongoing protection without an ongoing service fee for someone to press buttons.
Invite, promote, demote and remove your own people.
Why it matters — Staff changes do not require a support ticket.
Download, print and share reports without asking anybody.
Why it matters — Client deliverables on your schedule, not ours.
Public explanations of the methodology, the categories and the terminology, including this report.
Why it matters — An informed customer buys less and gets more, on purpose.
What our team does for you when you would rather not.
We verify, configure, preflight, self-test and certify an installation on your site.
Why it matters — You get a certified working install without touching anything technical.
We create, configure, print-prepare, deploy and monitor visibility stations at host locations.
Why it matters — A physical lead channel without you running it.
We set up branding, assets and presentation for a reseller or partner brand.
Why it matters — Your brand, our engine, no build cost.
We re-run failed audits, regenerate reports, resend deliveries and resolve exceptions.
Why it matters — Someone is accountable for making it right.
A guided review of your results with a recommended action plan, offered as a service.
Why it matters — For owners who want the conclusion rather than the data.
Hands-on work to fix what the audit found, quoted case by case.
Why it matters — For owners with no internal web capability at all.
Groundwork that exists today for things not being offered today.
Stations are not tied to a fixed address, so a placement can move without breaking its record.
Why it matters — A code on a vehicle, a stand or a travelling display works the same way as one on a counter.
The engine, attribution and deployment layers are brand-neutral and reusable by other properties.
Why it matters — New products do not require a new engine.
Capturing visitor feedback at a station.
Why it matters — Would let a host see satisfaction, not just volume.
Structured connection points for additional outside data services.
Why it matters — Some checks currently inferred from your own site could become independently verified.
How we know any of the above is true.
A large automated test suite runs against every change, covering scoring doctrine, isolation, commercial rules, stations and operational safety.
Why it matters — A new feature cannot quietly break an old one.
The measurement engine has a recorded fingerprint that is verified on every build.
Why it matters — Your score is produced by the same certified engine today as it was last month.
The platform has been through documented full-system certification passes.
Why it matters — Readiness is a documented event, not a feeling.
This report separates proven, implemented, integration-ready and planned, and never labels the last three as certified.
Why it matters — You can trust the parts we claim, because we do not claim the parts we cannot.
The exact words this system uses, what each one means here, and why it should matter to you.
A complete check of how visible a business is.
In this system — One canonical run of the measurement engine against a live website, producing a score, category results, confidence, coverage and an Action Map.
Why you care — It is the unit everything else is built on — history, monitoring, reports and station activity are all counted in audits.
Used by Everyone
A single number summarising visibility.
In this system — A score built only from evidence we could actually measure, using the published standards and scoring version recorded on that audit.
Why you care — It is the number you track and the number you argue about with a supplier.
Used by Everyone
A word rating attached to the number.
In this system — Excellent, Good, Fair or Needs Work, fixed by published thresholds rather than judgement.
Why you care — Tells you whether to celebrate or act, without knowing the scale.
Used by Everyone
How much evidence the result is built on.
In this system — A stated level from High Confidence down to Insufficient Data, reported per result and per category.
Why you care — A low-confidence result is a reason to look closer, not a reason to panic.
Used by Everyone
How much of a category we could actually measure.
In this system — The share of applicable checks in a category that produced a real measurement.
Why you care — Separates 'you are weak here' from 'we could not see here'.
Used by Everyone
One individual check.
In this system — A single evidence-gathering check against your site or a public source. Many probes make one category.
Why you care — Findings trace back to specific checks rather than to opinion.
Used by Everyone
What one check found.
In this system — Measured, not measurable, or failed — recorded separately so a failure is never scored as a zero.
Why you care — It is why our results do not punish you for things we could not see.
Used by Everyone
The prioritised fix list.
In this system — Findings ordered by severity, each with the impact and a specific recommendation.
Why you care — This is the part you actually act on.
Used by Everyone
A measurement being trialled quietly.
In this system — A category that is measured and labelled but does not affect the production Visibility Score until it is calibrated.
Why you care — Your score never moves because we were experimenting.
Used by Everyone
Which edition of the rules produced this result.
In this system — A version identifier recorded on every audit alongside the scoring version.
Why you care — It lets you tell a real change from a rule change.
Used by Everyone
A physical scannable placement at a real business.
In this system — A named station with a permanent link and printable code that delivers a real free audit to whoever scans it.
Why you care — It turns a physical location into a measurable source of business.
Used by Hosts and operators
The business where a station is placed.
In this system — The named business a station belongs to, shown to the visitor when they scan it.
Why you care — The visitor knows who is offering them the check.
Used by Hosts and operators
Somebody opening a station's link or code.
In this system — A recorded visit to a station, with its outcome — served, or refused with a stated reason.
Why you care — It is the first measurable moment of interest at a placement.
Used by Operators
A visit that was turned away.
In this system — A scan that could not be served — the station is paused, retired, out of allowance, unknown, or the code was used somewhere it does not belong.
Why you care — Refused visits are evidence. A printed code that stopped working shows up here.
Used by Operators
A visit that turned into a finished result.
In this system — A station's activity counts as Qualified only when an audit started from it actually completes successfully. It is stamped once and never twice.
Why you care — It is the honest measure of what a placement delivered.
Used by Operators
The cap on qualified uses for one station.
In this system — An operator-set number of Qualified uses a station will provide. Blank means unlimited. It is enforced at the moment a check finishes, with the station locked.
Why you care — Your free-value cost per location is a hard ceiling, not an estimate.
Used by Operators
Knowing what produced what.
In this system — The recorded chain from station to visit to audit to account to eventual purchase, decided on our side rather than taken from the browser.
Why you care — It proves which physical placement generated real business.
Used by Operators
How much you are permitted to use.
In this system — A permitted count of something — free audits, branded reports, monitored sites — resolved from your plan and your account's standing.
Why you care — You can always see it, so you are never surprised by it.
Used by Everyone
The free checks you get without an account.
In this system — Three complete audits for a brand-new visitor, owned and counted on our side, never trusted to the browser.
Why you care — Enough to check yourself and two competitors before deciding anything.
Used by Everyone
What your account is allowed to do.
In this system — A resolved set of permissions and limits from your plan, your account's current standing, and any time-boxed exception.
Why you care — It is the single answer to 'can I do this?' everywhere in the product.
Used by Account holders
How your account currently stands.
In this system — Trialing, active, past due, in grace, restricted, suspended or cancelled — each with a defined ceiling on capability.
Why you care — Capability steps down predictably instead of vanishing without warning.
Used by Account holders
A report delivered under a professional's own brand.
In this system — A metered monthly capacity for people who deliver reports to clients, consumed and shown as it is used.
Why you care — You know your remaining delivery capacity at any moment.
Used by Professionals
Every audit you have run.
In this system — The filterable record of your audits with their scores, statuses and dates.
Why you care — Progress only exists if you kept the starting point.
Used by Account holders
Automatic re-checking on a schedule.
In this system — Weekly or monthly re-audits of a chosen site, with thresholds and alerting attached.
Why you care — You learn about decline from us rather than from lost customers.
Used by Paid plans
How big a change has to be to matter.
In this system — The score drop you set before an alert is raised.
Why you care — Keeps alerts meaningful instead of constant.
Used by Paid plans
A recorded notification.
In this system — A raised event such as a score drop, a band change or a failed check, listed in your alert centre and optionally emailed.
Why you care — It is the record that you were told, and when.
Used by Paid plans
Your number went down.
In this system — A monitored site's score falling by more than your configured threshold between scheduled checks.
Why you care — The earliest reliable warning that something on your site changed.
Used by Paid plans
Your rating moved.
In this system — A monitored site crossing from one band into another, such as Good into Fair.
Why you care — This is the point at which customers and search systems start to notice.
Used by Paid plans
The check could not be completed.
In this system — A scheduled check that could not finish — site unreachable, blocking us, or timing out — recorded as its own outcome.
Why you care — If we cannot reach your site, neither can some of your customers.
Used by Paid plans
A confirmed, sustained problem.
In this system — A suspected problem that has been confirmed across checks rather than treated as an emergency on first sight.
Why you care — You are alerted to real problems, not to one bad moment.
Used by Paid plans
Putting results side by side.
In this system — A direct comparison of two or three completed audits, viewable and exportable, with any change in standards called out.
Why you care — It is how you prove work was worth paying for.
Used by Everyone
More than one location or website.
In this system — A structure of businesses, the locations under them, and the websites under those, with integrity guards.
Why you care — Local visibility is won per location, so it has to be measured per location.
Used by Paid plans
A shared workspace for a team.
In this system — A group of people with defined roles sharing access to the same businesses and audits.
Why you care — Staff can work without sharing your login.
Used by Paid plans
An authorised member of our team.
In this system — An authorised person on a single operator list, whose permission is checked on the server for every privileged action.
Why you care — There is exactly one way to hold administrative authority here.
Used by Internal
An isolated customer space.
In this system — The boundary that owns your data. Nothing crosses it, and ownership cannot be reassigned afterwards.
Why you care — Your data and your competitor's data can never meet.
Used by Internal
An authorised installation on a website.
In this system — A verified domain with a configured, preflighted and certified audit unit running on it.
Why you care — It is how the engine legitimately appears somewhere other than here.
Used by Operators and partners
Switching an installation on.
In this system — The point at which a verified, preflighted deployment starts serving real visitors, recorded as an event.
Why you care — Going live is a deliberate, evidenced step.
Used by Operators and partners
The audit unit running inside another website.
In this system — The same measurement unit, served only to verified domains with live authorisation, refused everywhere else.
Why you care — Partners deliver real value without the engine being copied.
Used by Operators and partners
The service presented under another brand.
In this system — Per-installation branding and presentation with a change history, over a brand-neutral engine.
Why you care — A partner can offer it as their own without a separate build.
Used by Operators and partners
How the platform itself is doing.
In this system — Live operating state, notices, upstream service condition and reliability results, published publicly.
Why you care — When something looks wrong, you can check rather than guess.
Used by Everyone
A recorded internal hiccup.
In this system — A logged record of something that failed quietly inside the system — a refused code, a record that would not save, a count that could not be applied.
Why you care — Silent failures become visible, so they get fixed.
Used by Operators
Something wrong at a placement.
In this system — A diagnostic event tied to a station, listed for review — an unknown code, a copied code, a rate-limited visit, a lost record.
Why you care — A misprinted or stolen code shows up as evidence instead of disappearing.
Used by Operators
Background work.
In this system — A queued unit of work claimed once and retried under a defined policy.
Why you care — Work keeps happening when nobody is watching, and is never done twice.
Used by Internal
A step recorded during an audit.
In this system — An entry in the audit's own trail, used to answer questions about what happened.
Why you care — Support answers come from facts.
Used by Operators
A recorded change to money or entitlement.
In this system — An entry recording a plan, entitlement, invoice or payment change.
Why you care — You can reconstruct what an account was entitled to on any past date.
Used by Operators
The written output of an audit.
In this system — The full result presented for reading, printing, downloading or sending.
Why you care — It is what you actually hand to someone else.
Used by Everyone
Taking your results out.
In this system — A document version for people and a structured version for software.
Why you care — Your results are not trapped in our screens.
Used by Account holders
What was true at the time.
In this system — Stored snapshots that let an old audit be reconstructed exactly as it was scored then.
Why you care — It settles arguments about whether you declined or the rules changed.
Used by Account holders
The verified state of the measurement engine.
In this system — A recorded fingerprint of the engine, verified on every build, so protected measurement code cannot change unnoticed.
Why you care — Your scores stay comparable because the ruler is locked.
Used by Everyone
Run a free visibility check on your own website. It takes about a minute, needs no account, and gives you the same measurement every paying customer receives.
This report is maintained alongside the system it describes. Last updated 2026-09-14.