Digital Signal
The signals we look for
Digital Signal looks for patterns across your estate, your competitors and relevant exemplars from outside your sector, and interprets what those patterns may mean for the decision in front of you.
This page sets out the seven lenses we use, where the outside view stops, and how the readout turns what we find into prioritised recommendations.
How to read an observation
Observe, interpret and prioritise
A Digital Signal works from publicly observable evidence. Each finding states what we saw and what it may indicate. Where confirming it needs internal access, the readout ranks those questions, so your team investigates the few that matter and leaves the rest.
We can observe this
Evidence anyone could verify from the outside.
- Key product information on three brand sites is published only in PDFs
- Two competitors present the same information as structured, linked pages
It may indicate this
Interpretation, labelled as such.
- The information is harder for people and machines to find, compare and cite
- The content model may not have been designed for reuse
Worth confirming next
Ranked in the readout, with a recommendation.
- First: whether the content model or the platform is the constraint, before any platform decision
- Then: what restructuring the highest-value product content would cost
The seven lenses
What each lens examines
Choose a lens to see what we observe, why it matters, what it might imply, where the outside view stops, and the decision questions it raises.
Discoverability
Whether people and machines can find, understand and use your information, in conventional search and in AI-driven discovery.
- What we can observe
- Crawl paths, indexability signals and rendered HTML
- Whether important information exists as text, and where it lives only in images, PDFs or scripts
- Page titles, metadata and structured data, and whether they match what the page says
- Entity clarity: whether products, services and the organisation are named consistently
- Topic coverage compared with competitors, and internal linking between related content
- Where reliable tools allow, evidence of content being surfaced or cited by AI search features
- Why it matters
- Discovery increasingly happens before a visitor reaches your site, through search features and assistants that retrieve and summarise. Information that is hard to retrieve is absent from those answers.
- What it may indicate
- Weak discoverability usually comes from content structure, authority or publishing discipline. It can also reflect rendering choices in the front end.
- What we cannot know from the outside
- Your search traffic, the queries that bring people in, how AI systems rank or select sources internally, or the business value of any particular visibility change.
Decision questions it raises
- Which questions do our customers ask that our content answers poorly or nowhere?
- Is our most important information published in a form machines can use?
- Where are competitors more retrievable than us, and does it matter commercially?
Content and findability
How the estate is organised, and whether its content looks designed to be found, understood, maintained and reused.
- What we can observe
- Information architecture and navigation across sections, brands and markets
- Near-duplicate pages and competing routes to the same answer
- Content depth and currency on the pages that carry key journeys
- Taxonomy and labelling consistency
- Signs of structured, reusable content, and signs of one-off page building
- Why it matters
- Content structure decides how well an organisation can change what it says, personalise it, localise it and expose it to other channels. It is also where most migration effort hides.
- What it may indicate
- Repeated duplication or inconsistent structure is consistent with a content model built around pages, or with governance that has not kept pace with growth.
- What we cannot know from the outside
- Your content model, authoring workflow, the volume of content behind the public site, or why a structure was chosen.
Decision questions it raises
- Could we change a core product fact once and have it update everywhere?
- How much of our estate would a migration need to rework, and how much is worth keeping?
- Do our business units share a structure, or only a design?
Experience and accessibility
Whether key journeys are coherent, inclusive and consistent, across devices and across the estate.
- What we can observe
- The clarity of next actions on key journeys
- Consistency of patterns and components across sections and brands
- Visible accessibility issues: structure, contrast, keyboard use, alternatives for media
- Resilience on smaller screens and slower connections
- How competitors handle the same journeys
- Why it matters
- Experience inconsistency reaches customers directly, and accessibility is both a legal and a reach concern.
- What it may indicate
- Inconsistency across brands or sections may point to a design system that is not shared, several delivery teams working apart, or legacy templates still in service.
- What we cannot know from the outside
- Conversion rates, user research findings, how your teams are organised, or the results of any formal accessibility audit.
Decision questions it raises
- Which journeys matter most commercially, and are they our most coherent ones?
- Is accessibility built into how we deliver, or checked afterwards?
- Where do competitors make the same task easier, and why?
Performance and engineering
Front-end performance and implementation quality, and the constraints they can sometimes reveal.
- What we can observe
- Page performance on key templates and journeys, measured consistently against competitors
- Where slow experiences cluster: particular page types, components or third-party scripts
- Front-end implementation patterns and the weight of what pages load
- Signs of caching, rendering and delivery approach
- Why it matters
- Performance affects experience and search. Where problems cluster around specific patterns, they often reveal how the estate is built.
- What it may indicate
- Clustered problems can indicate engineering or platform friction, an accumulation of third-party tags, or front-end debt. Isolated problems usually indicate less.
- What we cannot know from the outside
- Your hosting, back-end architecture, CMS version or configuration, release process, or whether a fix is already planned.
Decision questions it raises
- Are our slowest experiences also our most valuable ones?
- Who owns performance once a page is live?
- Would a targeted technical investigation settle whether the platform is the constraint?
Data, personalisation and experimentation
Visible evidence of how the organisation uses data to shape and improve the experience.
- What we can observe
- Consent experience and its relationship to the tags a page loads
- Visible personalisation, recommendations or audience-specific content
- Signs of experimentation tooling, and signs that it is in use
- Forms, preference centres and the data they ask for
- Why it matters
- Many organisations have paid for personalisation and experimentation capability. The visible experience shows whether it is shaping what customers see.
- What it may indicate
- Capability that is present but hard to observe in use may indicate an audience strategy that has not been defined, content that cannot support variation, or an operating model without room to test.
- What we cannot know from the outside
- Your data, your audience definitions, test results, or personalisation that depends on signals we cannot reproduce.
Decision questions it raises
- Which audiences would benefit from a different experience, and do we have the content for them?
- What have we learned from experiments in the last year, and what changed as a result?
- Is our consent approach helping or hindering what we are trying to measure?
Content operations and orchestration
Patterns that suggest how effectively the organisation creates, governs, localises and updates content.
- What we can observe
- Localisation lag between markets and inconsistencies in translated content
- Stale content on pages that should change often
- Campaign microsites and disconnected experiences that accumulate
- Structural inconsistency that suggests several ways of working
- Machine readability, which matters more as agents enter content workflows
- Why it matters
- Operating models show up in the public experience as consequences. As AI agents join content work, weak structure and unclear ownership become harder constraints.
- What it may indicate
- These patterns can generate strong hypotheses about workflow, ownership and tooling, and point to where a closer look is worthwhile.
- What we cannot know from the outside
- Approval queues, team structure, tooling in use, workload, or organisational politics. From outside, operations can only be inferred.
Decision questions it raises
- How long does it take us to get a change from decision to live, in every market?
- Who owns the accuracy of information once it is published?
- Is our content legible enough for people and agents to work on it reliably?
Platform and extensibility
Observable characteristics relevant to how the platform can evolve, integrate and support changing experiences.
- What we can observe
- Front-end architecture and delivery approach, where it can be identified
- Visible integrations: search, commerce, forms, personalisation, analytics
- Consistency of experience across channels that share content
- How quickly competitors appear to ship comparable capability
- Why it matters
- Platform decisions are expensive and slow to reverse. External evidence helps decide whether the platform deserves investigation at all, and which part.
- What it may indicate
- Patterns can support three different conclusions: the platform is broadly capable and the problem is elsewhere; it can evolve but specific constraints merit investigation; or structural constraint justifies a deeper platform strategy.
- What we cannot know from the outside
- Licensing, customisation, technical debt in the codebase, integration contracts or total cost of ownership.
Decision questions it raises
- Are we deciding about a platform, or about the way we use it?
- What would need to be true before we commit to a migration?
- Which constraint, if removed, would change the most?
The unit of value
Reading patterns across lenses
One slow page or an untidy heading structure is a fix. Decisions come from patterns that repeat across lenses and against competitors.
A pattern also changes meaning with context. An issue every competitor shares is the norm in your sector. An issue nobody has solved is an opportunity. An issue one competitor has clearly escaped is a risk.
Example pattern · Content, discoverability, operations
Information built for pages
- What we can observe
- The same product details appear in different wording on product pages, comparison tables and support articles, and competitors expose them as consistent, structured information.
- Why it matters
- Customers and AI systems meet conflicting versions of the same fact, and every change has to be made several times.
- What it may indicate
- It is consistent with a content model organised around pages, and it raises the question of how much a migration would have to restructure.
- What we cannot know from the outside
- Whether a structured model already exists internally and is simply not used on the public site.
Example pattern · Data, experience, platform
Paid-for capability with no visible effect
- What we can observe
- Experimentation and personalisation scripts load across the estate, while key journeys look the same to every visitor and have not visibly changed over time.
- Why it matters
- Paid-for capability may not be shaping what customers see, and a platform decision may be about to buy more of it.
- What it may indicate
- It may indicate an operating-model or content constraint.
- What we cannot know from the outside
- Whether tests are running in areas we cannot observe, or what they have found.
Why there is no score
A score invites a comparison between numbers that were never measuring the same thing, and it hides the reasoning a leadership team most needs to challenge.
A Digital Signal gives you the evidence, the interpretation and its limits in words, so you can disagree with any step of it.
Explore Digital Signal
AI discovery and GEO
What makes your information understandable, retrievable and citable by AI search, and what the evidence does not support.
A sample Digital Signal
An anonymised extract from a real snapshot for a UK travel company, annotated to show where evidence ends and interpretation begins.
Related articles
SitecoreAI · 6 November 2026
SitecoreAI from idea to execution: how brief types, Agentic Studio, Page builder and MCP fit together
SitecoreAI now has a capability at most stages between a marketing intention and a measured result. Connecting them raises five organisational questions.
AI · 21 October 2026
GEO after the hype: what actually makes content visible in AI search?
GEO, AEO and AI search optimisation name one problem. Here is what the primary evidence supports, what is sensible practice, and what nobody can yet prove.
SitecoreAI · 7 October 2026
SitecoreAI Signals and Scrunch: closing the loop from AI visibility to content action
Signals, powered by Scrunch, puts AI-visibility monitoring and page-level recommendations inside SitecoreAI. What that changes for content teams, and the judgement it leaves with them.