What is Digital Presence Score (DPS) and how does it work?

The problem DPS solves

For twenty years, local businesses have been measured by numbers that measure something but not what an owner cares about. “Impressions” measures a search page you never see. “Click-through rate” measures a decision a buyer makes about a title tag. “Domain authority” measures a page-rank proxy invented by an SEO tool. “Review count” measures volume without measuring whether anyone answered. Each is correct about what it measures. None of them answers the question an owner actually asks: am I showing up or not?

DPS answers that question with one number from 0 to 100. Say your DPS is 42: your digital presence is in rough shape. Say it is 78: you are in strong shape for your category. Say it moves from 51 to 61 in a quarter: something you did worked. Say it moves from 51 to 44: something broke. A citation went inconsistent, a review streak snapped, a page lost its schema. The point of one number is compression. The point of compression is that you can act on it.

How DPS is constructed

DPS is built from two sides. One side measures what you control directly: your website, your profiles, your structured data, your crawler access, your business-information consistency. The other side measures how the open web has reacted to you: reviews, citations, press mentions, and whether language models name you when someone asks for a recommendation in your category and city.

The first side moves fast. Fix your Google Business Profile category today and the first-side score moves this week. Ship an llms.txt tomorrow and it moves. Add schema to five pages and it moves. The signal is responsive because the surfaces are yours.

The second side moves slow. Reviews accumulate. Citations get crawled on their own cadence. Models refresh. A mention in a trade publication might not show up in DPS for a month, because the LLM-crawl layer has not picked it up. That is not a bug. It is an honest measure of how long outside validation takes to show up. The second-side score lags, and if you shortcut it, you are measuring theatre, not presence.

The composite is a weighted blend, and the weight is tuned by category. A roofing company gets more second-side weight, because reviews drive the call. A specialty trades contractor gets more first-side weight, because reviews are sparse and profiles and citations do the heavy lifting. The weighting is published alongside the score, not hidden. If you cannot explain the weighting, the number is theatre.

What DPS measures, concretely

Six signal clusters feed DPS:

1. Business-information consistency. Name, address, phone, hours, categories, services, matched across your website, GBP, and the top citation sources. Mismatches drag the score. Matches lift it.
2. Google Business Profile completeness and activity. Categories chosen correctly, service area set, photos recent, products or services populated, posts in the last 30 days, Q&A monitored, review response rate above 70%.
3. Review profile. Volume, recency, response rate, response quality (specific, not boilerplate), and position against the top three competitors in your category and city.
4. Technical crawlability for language models. Does robots.txt allow the LLM crawlers (GPTBot, ClaudeBot, PerplexityBot, Google-Extended, Applebot-Extended)? Is there a well-formed llms.txt? Is schema present and parseable on the pages a model would land on first?
5. Pillar and FAQ coverage. Is there a page that defines the thing you want to be known for, in a way a model can quote? Is there an FAQ an answer engine can lift verbatim?
6. LLM mention rate. Across a battery of queries for your category and location, how often do ChatGPT, Claude, and Perplexity mention you when a buyer asks for a recommendation? Are you named first, named third, mentioned in passing, or misdescribed? This signal lags by weeks, and it is the one that tracks most directly with inbound.

Why one number

Dashboards fail because owners do not open them. A dashboard with 14 widgets gets reviewed in January and ignored until October. One number on a page gets glanced at every Monday. Compression is the feature. The score does not replace the breakdown. The breakdown is one click away, and the breakdown is where the work happens. But the score is what gets looked at, and the score is what gets reported when an owner tells a partner, an accountant, or a spouse whether the website is working.

One number also forces discipline on the people measuring it. Every signal in DPS has to justify its weight. Every signal that drifts without explanation gets investigated. There is no hiding behind “impressions were down this month” when the composite went up. The composite is the truth. Either your work moved it or it did not.

How often DPS updates

Weekly. Every Monday morning the harness runs: crawl of controlled surfaces, pull of review and citation data, LLM mention sweep across three models and the current query battery. The score updates, the breakdown updates, and anything that moved more than two points in either direction gets flagged for inspection.

Monthly, the harness recalibrates: new queries in, dead queries out, weights adjusted on cohort data. The score definition does not drift. The measurement around it stays current.

What moves DPS fastest

In rough order of leverage per hour spent:

1. Fix robots.txt so LLM crawlers can read your site. If GPTBot is blocked, you have been uncitable to ChatGPT for as long as it has been blocked. One line of configuration.
2. Clean up citation inconsistencies. The three or four variants of your business name floating across directories. Low glamour, high lift.
3. Ship an llms.txt pointing models at your three best pages. One Markdown file at the root of your domain.
4. Respond to every review from the last 90 days. By name. Specifically. This is the single strongest signal of a healthy local business, and the score weights it accordingly.
5. Write one pillar page that defines the thing you want to be known for. Not twelve. One.
6. Add schema to that pillar page, your homepage, and your top-three service pages. JSON-LD, not microdata.

Everything else matters, but these six account for most first-quarter movement for a business below 50.

See a real DPS

The best way to understand DPS is to see one live. NoCode Labs publishes its own at nocodelabs.io/our-score: the actual composite, the actual breakdown, moving as the underlying surfaces change.

Here is the part most score sellers will not do: we show you ours. A score you will not publish is a score you do not trust. Go look at it. Then ask why nobody else in your category will show you theirs.

Frequently asked questions