The Integrity Graph: The Missing Layer In Your AI Visibility Audit via @sejournal, @billhunt

A recent announcement from Common Crawl introduced an AI Visibility Audit designed to help organizations determine whether AI systems can discover and access their content. The premise is straightforward and difficult to dispute. Before an AI system can retrieve, summarize, cite, recommend, or act upon information, it must first be able to find it.

For years, visibility has been the foundation of search. If Google could not crawl a page, it could not rank it. If an AI system cannot access information, it cannot incorporate that information into responses, recommendations, or decisions.

Yet as I read through the announcement, I found myself thinking about a different problem entirely.

Common Crawl is not a search engine, nor is it an AI platform. It is one of the largest open repositories of web crawl data and has become an important source of training and research data for the broader AI ecosystem. Whether or not a particular AI model uses Common Crawl directly, the project has become a useful proxy for a larger question: Can machines discover and access the information organizations publish online?

That is precisely why the AI Visibility Audit caught my attention.

What happens after the content is discovered?

That question came into focus while reviewing schema implementations across several banking websites. On the surface, most appeared reasonably mature. The sites contained Organization markup, BankOrCreditUnion entities, branch information, product schema, service schema, and many of the components one would expect to see at large financial institutions.

However, when I stopped looking at individual pages and started looking at the relationships between entities, a very different picture emerged. I found most banks had a fundamental schema, but very few had built out a knowledge graph.

The Difference Between Describing A Page And Describing A Business

One recurring theme in the SEO industry is the importance of schema completeness. We audit whether required properties are present. We validate markup against Google’s tools. We look for missing fields and opportunities to expand coverage.

The problem is that most of these exercises evaluate pages in isolation.  A branch page is reviewed as such. A product page is reviewed as a product page. A service page is reviewed as such. What often gets overlooked is whether those entities are meaningfully connected.

In the banking examples I reviewed, it was common to find a branch location, a checking account, a mortgage offering, and a corporate organization all marked up separately. What was frequently missing was the connective tissue that explained how those entities related to one another.

• Which legal entity owned the consumer-facing brand?
• Which products were offered through which services?
• Which services were available at which branches?
• Which offerings were available only in specific markets or jurisdictions?
• Which products belonged to a larger family of financial solutions?

The markup described the individual pieces, but it rarely described the business itself.

That distinction may seem subtle, but it becomes increasingly important as search engines and AI systems move beyond page-level understanding toward entity-level understanding.

The Validator Problem

Part of the issue may stem from how we evaluate structured data. Most validation tools perform a single-page review. They determine whether a page contains the expected properties for a given schema type and whether those properties conform to accepted standards.

This approach works reasonably well when the objective is to generate a rich result or to validate a standalone entity. It becomes less effective when the objective is building a connected knowledge graph.

One of the more frustrating aspects of implementing sophisticated schema architectures is that the very mechanisms designed to create entity relationships often appear incomplete when viewed through page-level validation tools.

The contradiction becomes particularly apparent when organizations attempt to implement graph-based architectures as Google recommends. A branch page may reference its parent organization through an @id relationship that points to the organization’s primary entity definition on the homepage. The organization’s address, legal information, social profiles, and other core attributes are stored in the graph, but not necessarily on the page being tested.

Ironically, some of the same implementations Google recommends for entity alignment can generate warnings in page-level testing tools because the information is intentionally referenced elsewhere rather than duplicated. In effect, organizations are encouraged to build graphs while still being evaluated as though every page were an island.

That distinction may have mattered little during the rich snippet era, when the primary objective was determining whether a single page contained enough information to qualify for a search feature. It becomes increasingly important as search engines, knowledge systems, and AI platforms seek to understand how entities relate to one another across an entire organization.

Google’s Evolution Reveals The Real Direction

Today, many of Google’s most significant investments appear focused on relationships and context. Product Graph, Merchant Center feeds, compatibility data, variant relationships, entity reconciliation, and Conversational Attributes all point in a similar direction. Collectively, these initiatives suggest that understanding relationships between entities has become increasingly important, particularly when those relationships are difficult to infer consistently from content alone.

Google’s actions suggest that relationship inference remains challenging even for one of the world’s most sophisticated information retrieval systems. Otherwise, there would be little reason to continue expanding the mechanisms through which organizations can explicitly provide contextual information about products, services, brands, and audiences.

Common Crawl Measures Visibility. Relationships Determine Understanding

This brings us back to Common Crawl.

The AI Visibility Audit addresses an important challenge. Organizations should absolutely understand whether AI systems can access their content. Content that cannot be discovered cannot influence search results, AI-generated answers, or recommendation systems.

Visibility matters. However, visibility and understanding are not the same thing. In many ways, Common Crawl is asking the same question SEO teams have asked for decades: Can machines reach the content?

The emerging AI challenge is what happens after machines gain access to the content. A crawler can successfully discover every page on a website and still struggle to understand how the underlying entities connect. Historically, search engines attempted to infer those relationships from content, links, user behavior, and countless other signals. In many cases, they became remarkably good at it. Yet Google’s recent investments suggest that inference has limits.

Consider the recent introduction of Conversational Attributes in Merchant Center. Rather than relying solely on AI systems to determine which products solve similar problems, which products are alternatives, or which attributes matter in specific situations, Google is increasingly asking merchants to provide that context directly.

Google clearly possesses the resources, data, and AI capabilities to make educated guesses about product relationships. Nevertheless, it continues to seek information directly from the organizations that manufacture, sell, and support those products.

The reason is simple. Inference can be powerful, but first-party knowledge is often more accurate.

A manufacturer knows which products are compatible. A retailer knows which products are commonly purchased together. A bank knows which services are available at which branches. A global company knows which product variations apply in specific markets.

While AI systems can attempt to reconstruct those relationships from content, organizations already possess the answers. The question, therefore, is not whether AI can infer relationships. The more important question is whether the organizations that own those relationships can and would provide a reliable way for machines to understand them.

That distinction becomes increasingly important as AI systems move beyond retrieving information and begin synthesizing, recommending, and acting upon it. The information may already exist somewhere on the website, but the contextual relationships that give it meaning are often left for machines to discover on their own.

Are We Ready For The Agentic Hype Machine?

Over the past year, the industry has become increasingly focused on concepts such as MCP, WebMCP, agent skills, agent cards, API catalogs, A2A protocols, and llms.txt files. Much of the discussion assumes that the web is rapidly evolving toward an agent-first ecosystem.

Recent Agentic Readiness research by Bastian Grimm offers a useful reality check. After benchmarking highly visible websites across the United States, the United Kingdom, and Germany, he found that adoption of these agent-oriented standards remains remarkably limited. The overwhelming majority of sites exposed none of the agent-discovery mechanisms currently being promoted by the industry.

That finding does not suggest the agent-ready web is unimportant, but suggests we may be getting ahead of ourselves. More importantly, even if every major website deployed llms.txt, WebMCP manifests, and API catalogs tomorrow, the same underlying challenge would remain.

What information are those systems exposing?

A machine-readable doorway is valuable only if it leads to accurate, connected, and contextually complete information. If the underlying relationships between products, brands, locations, services, and markets are poorly modeled, agentic access simply makes incomplete information easier to retrieve.

The access layer is not the hard part. The relationship layer is.

Beyond Entity Graphs: Introducing The Integrity Graph

Most discussions around structured data focus on building an Entity Graph to help machines understand the company, product, location, and how they are connected to each other. Those capabilities are important. However, AI systems face a more difficult challenge. They must determine which facts apply within which contexts. This is where I believe organizations need to begin thinking about what I call an Integrity Graph.

An Integrity Graph extends beyond entity identification to preserve contextual truth.

It helps establish which legal entity owns a brand, which products belong to a product family, which services are available in specific markets, which branches offer particular services, which regulations apply in particular jurisdictions, and which information is globally applicable versus locally relevant.

Simply identifying entities is no longer enough. Organizations must preserve the integrity of their relationships.

What Organizations Should Audit Next

The growing number of AI readiness audits highlights how quickly the conversation is evolving. Common Crawl’s AI Visibility Audit focuses on discoverability and accessibility. Bastian Grimm’s benchmark for agent-ready technologies assesses whether websites provide machine-readable interfaces that agents can discover and interact with. Dixon Jones and the team at Waikay approach the challenge from yet another angle, Brand AI Visibility Audit, evaluating whether AI systems can recognize brands, understand entities, and accurately associate an organization with the topics, products, and concepts it seeks to own.

Viewed collectively, these emerging audit frameworks reveal that the industry is evaluating several distinct layers of machine understanding.

Common Crawl focuses on visibility and accessibility by asking whether machines can discover and access the content.

Agentic readiness frameworks examine whether agents can discover capabilities and interact with systems.

Entity visibility assessments assess whether AI systems can correctly identify brands, organizations, and the concepts associated with them.

Relationship integrity focuses on a different question entirely: whether machines understand how the organization itself operates.

Each layer builds upon the one before it. Content must be discoverable before it can be accessed. It must be accessible before it can be associated with an entity. It must be associated with an entity before machines can accurately understand the relationships that give the information meaning.

Why This Matters For Global Organizations

The importance of relationship integrity becomes even more obvious when viewed through an international lens.

A multinational company may have content available in twenty markets. Common Crawl can successfully discover all of it. AI systems can retrieve it. Search engines can index it. The visibility problem is solved.

For years, international SEO focused on helping search engines show the correct page to the correct user. AI systems introduce a different challenge. Now we must help machines understand the correct facts for the correct audience, market, and context.

We must ensure clarity on which product information applies in Germany, which regulations apply in Japan, and which services are available in Canada. Often, an equally complex challenge is which local brand names map to the same global product, and which facts are globally true and which are market-specific? These are not crawling and retrievability problems but data integrity problems.

In many ways, the next generation of international SEO may resemble hreflang at the knowledge level rather than at the URL level. The challenge is no longer simply routing users to the correct page. The challenge is ensuring machines understand the correct version of the truth.

The Next Competitive Advantage

The banking analysis that inspired this article illustrates the issue well. Most of the institutions had no shortage of schema. Their websites contained thousands of lines of structured data and numerous schema types. What they lacked was a coherent representation of how the business itself operated. That focus makes sense because discoverability remains a prerequisite for participation. However, discoverability alone will not be enough.

The organizations that thrive in the next phase of search may not be those with the most schema markup, the most pages, or the most AI-ready endpoints. They may be the organizations that provide the clearest, most complete, and most trustworthy representation of how their entities, products, services, locations, brands, and markets relate to one another. The next challenge is determining whether machines understand how the business actually works.

That shift may ultimately prove more important than any individual schema property, API endpoint, or AI optimization tactic. As search engines and AI systems become increasingly capable of retrieving information, the competitive advantage will move toward organizations that can provide context, preserve relationships, and maintain the integrity of their knowledge.

Understanding an entity is only the beginning. Understanding how that entity relates to everything around it is where the real value lies.

More Resources:

Featured Image: Roman Samborskyi/Shutterstock

Why Enterprise SEO Recommendations Fail – It’s Psychological, Not Technical via @sejournal, @billhunt

A few years ago, I was working on a large-scale global digital transformation initiative. After weeks of analysis, stakeholder interviews, audits, and performance reviews, I assembled the first draft of the executive readout presentation. The findings were direct and intentionally candid. I had sections labeled “Challenges,” “Problems,” “Risks,” and “Organizational Gaps.” To me, those labels seemed perfectly reasonable. The data was solid, the recommendations were practical, and the roadmap was achievable.

The response from the executive sponsor came back surprisingly fast. “We need all references to problems and challenges changed to opportunities.”

At first, I dismissed it as classic corporate language gymnastics. A problem is still a problem regardless of what you call it. Changing the label does not suddenly improve the situation. But over time, I realized the executive understood something that I did not yet fully appreciate. Organizations rarely resist recommendations because the recommendations are wrong. They resist them because the recommendations feel like criticism instead of evolution.

That realization fundamentally changed how I approach enterprise consulting, governance, and organizational change. Not because the facts changed, but because I finally understood that organizational psychology is often more important than analytical accuracy when it comes to getting things implemented.

Why Most Organizations Don’t Actually Want “Problem Solvers”

Early in my consulting career, I proudly positioned myself as a “problem solver.” It sounded logical. Companies hire consultants because something is not working correctly. They need someone who can identify the root cause, navigate complexity, and help fix the issue. But over time, I realized that most organizations do not actually want “problem solvers” as consultants imagine them. The phrase itself unintentionally creates tension because admitting there is a problem also implies that someone failed to recognize it, allowed it to happen, or was unable to solve it internally.

Once ownership enters the conversation, politics follows.

This is especially true in enterprise SEO, as it is uniquely effective at exposing organizational friction that companies often prefer to ignore. A technical audit rarely uncovers just technical problems. It uncovers fragmented governance, disconnected teams, conflicting KPIs, duplicated ownership, inconsistent workflows, and years of accumulated operational debt. What starts as a discussion about crawling or indexing quickly turns into a conversation about who owns decisions, whose priorities matter, and which teams create friction for others.

To the strategist, these are operational realities. To the organization, they can feel deeply personal.

Looking back, some of the projects that took the most time to implement or achieve expected success had very little to do with capabilities or even strategic disagreement. In many cases, the resistance emerged because my framing unintentionally forced executives and teams into a defensive posture. The recommendations themselves were often correct, but the language surrounding them implied organizational failure rather than operational evolution. Instead of hearing, “Here is how we improve,” stakeholders heard, “Here is what you did wrong.”

That distinction matters far more than most consultants realize.

When Failure Becomes A Lesson Instead Of A Threat

One of the best managers I ever worked with understood this instinctively. He encouraged experimentation constantly and was willing to try almost anything if there was enough logic behind it. What made him different, however, was how he evaluated outcomes.

Every project wrap-up followed the same structure: objective, goals, approach, and lessons. Not failures. Lessons.

That subtle distinction shaped the team’s culture in profound ways. If an initiative did not produce the expected outcome, it was still considered valuable if we learned something meaningful from it. We may have discovered a limitation that prevented future wasted investment. Maybe we uncovered a better direction. Maybe we ruled out an approach that looked promising in theory but collapsed under real-world conditions. In his mind, the only true failure was walking away unchanged and repeating the same mistake later.

That mindset stayed with me because it reframed failure as part of organizational evolution rather than evidence of incompetence. Teams became more willing to experiment because they were not terrified of blame. Discussions became more honest because people no longer felt the need to constantly protect themselves. Most importantly, the organization evolved faster because learning was rewarded instead of punished.

Years later, I realized the same principle applies directly to enterprise SEO governance and digital transformation. Organizations become defensive when recommendations feel like criticism, but collaborative when framed as evolution. Over time, I started calling this “evolutionary framing.”

Evolutionary Framing In The GEO And AI Search Era

This idea matters far more today because organizations are now being forced to confront structural weaknesses that traditional SEO often allowed them to ignore. For years, many companies compensated for fragmented systems by resorting to brute-force publishing, paid amplification, aggressive content production, or sheer domain authority. But AI-driven search systems are exposing weaknesses that were previously hidden beneath rankings and traffic reports.

AI retrieval and synthesis systems are much less forgiving than traditional search. They expose inconsistent governance, fragmented content ecosystems, disconnected entity relationships, weak attribution signals, poor taxonomy alignment, and years of accumulated operational shortcuts. Many organizations are discovering that their websites were never truly designed as coherent knowledge systems. They were designed as disconnected publishing environments optimized around campaigns, silos, and departmental priorities.

The problem is that many executives interpret these findings as criticism of past decisions rather than evidence that the environment itself has fundamentally changed.

That distinction is critical.

Telling an organization, “Your content strategy is failing in AI search,” immediately creates defensiveness. It implies that leadership made poor investments, teams executed poorly, or the existing strategy is obsolete. But framing the same issue as “The shift toward AI retrieval and synthesis requires a more structured and interconnected content ecosystem” creates a completely different conversation. The first statement feels like blame. The second feels like evolution.

The facts themselves do not change. The organizational willingness to act on them does.

This is where many SEO and GEO transformation efforts quietly break down. Consultants often assume resistance happens because stakeholders do not understand the recommendations. In reality, stakeholders frequently understand the implications perfectly. Recommendations tied to AI search transformation often expose uncomfortable organizational realities: fragmented ownership, disconnected systems, inconsistent governance, weak content operations, poor taxonomy alignment, or technical debt that accumulated over years of decentralized decision-making.

Those findings do not simply threaten workflows. They can threaten reputations, political influence, organizational authority, and long-standing narratives about what the company believed it was doing well.

That is why evolutionary framing matters so much in the GEO era. The goal is not to hide problems or soften reality. The goal is to position recommendations as a necessary adaptation to a changing ecosystem rather than as a retroactive condemnation of prior decisions.

Because in truth, most organizations are not failing because they ignored SEO. They are struggling because the environment evolved faster than their operating models did.

And organizations are far more willing to embrace evolution than admit failure.

The “Ugly Baby” Problem Inside Enterprise Organizations

I once worked with a company whose digital ecosystem had accumulated years of technical debt, fragmented international architecture, duplicated content, and inconsistent governance. From a strategic standpoint, the issues were obvious almost immediately. But from the perspective of the executive team, that platform represented years of investment, effort, political negotiation, and personal ownership.

In simple terms, I was telling them their baby was ugly. People rarely respond well to that.

The initial meetings became defensive almost immediately. Teams justified their decisions. Stakeholders debated terminology instead of discussing solutions. Conversations drifted toward explaining why things happened instead of whether they should evolve. Nothing moved forward because the organization interpreted the recommendations as criticism rather than an opportunity.

The breakthrough only happened once the framing changed. Instead of emphasizing what was broken, the conversation shifted toward operational maturity, modernization, scalability, and reducing friction that was limiting future growth. The recommendations themselves barely changed at all. What changed was the organization’s emotional relationship to them.

That experience forced me to confront something uncomfortable about consulting and leadership in general. Being right is not enough.

You can have the correct diagnosis, the correct data, the correct roadmap, and still fail completely if the organization interprets your recommendations as an attack on competence rather than a path toward evolution.

The “I Already Know That” Manager Problem

There is another layer of resistance that rarely gets discussed openly in enterprise organizations: the manager who believes acknowledging a recommendation somehow diminishes their expertise.

Most experienced consultants have encountered this dynamic. You present a finding or recommendation, and the immediate response is: “We already knew that.”

Sometimes that statement is true. Often, it is partially true. But many times it is less about the accuracy of the statement and more about protecting status.

Because if an outside consultant identifies something important that internal leadership failed to prioritize, the recommendation can unintentionally create embarrassment. Admitting the issue exists may raise uncomfortable questions. Why was this not addressed earlier? Why did nobody escalate it? Why was the organization investing heavily in one direction while foundational issues remained unresolved?

That creates a subtle but important dynamic. Managers who feel threatened by recommendations often shift the conversation away from the problem itself and toward ownership of the idea. The goal becomes preserving credibility rather than solving the issue.

Ironically, this behavior slows down the very evolution organizations claim to want.

The strongest leaders I have worked with never felt the need to pretend they already knew everything. They were comfortable acknowledging gaps, adapting quickly, and treating new information as a strategic advantage rather than a reputational risk. Those organizations almost always moved faster because they spent less time defending the past and more time adapting to the future.

This is another reason evolutionary framing matters. Recommendations framed as organizational evolution allow leaders to engage without feeling personally diminished. The conversation becomes less about who missed something and more about how the organization adapts to changing realities.

That shift may sound subtle, but in enterprise environments it often determines whether change gains momentum or quietly dies in committee meetings.

Why This Problem Is Becoming More Dangerous In The AI Era

This challenge becomes even more dangerous in the AI era because AI systems are compressing the time organizations have to adapt. Traditional SEO often allowed companies to recover slowly. Rankings fluctuated gradually. Traffic patterns evolved over time. Teams could defer structural improvements for months or even years while still maintaining acceptable performance.

AI-driven discovery systems are accelerating the consequences of organizational fragmentation. Weak governance, disconnected content systems, poor entity alignment, and inconsistent operational structures are no longer isolated technical concerns. They directly impact whether organizations become visible, understandable, and retrievable within AI ecosystems.

Many companies still approach GEO as though it is another layer of tactical optimization that can be delegated to a small team. But the underlying issues are usually much broader than metadata, prompts, or AI content generation. The organizations struggling most with AI visibility often have deeper operational problems that existed long before AI search became mainstream.

The difference now is that those weaknesses are becoming impossible to hide.

That is why framing matters so much. If AI transformation conversations become framed as criticism of prior leadership, organizations instinctively defend themselves. Teams protect budgets, authority, workflows, and ownership models. But when transformation is framed as a necessary adaptation to a rapidly changing ecosystem, organizations become far more willing to collaborate.

In many ways, the biggest challenge in enterprise SEO today is no longer technical education. It is organizational acceptance.

The Real Work Isn’t Finding Problems; It’s Helping Organizations Evolve

One of the hardest lessons for technically-minded strategists to accept is that analytical accuracy alone does not create organizational change. The real work is not simply identifying what is wrong. The real work is helping organizations evolve without triggering the defensive instincts that prevent evolution in the first place.

That does not mean hiding reality. It does not mean avoiding accountability. And it certainly does not mean watering down difficult conversations.

It means understanding that enterprise transformation is as much psychological as it is operational.

The companies that evolve fastest are rarely the ones with the fewest problems. They are usually the ones best able to discuss those problems without turning them into identity threats.

That is ultimately why evolutionary framing matters. Not because it sounds softer.

Because it creates the psychological conditions necessary for organizations to adapt, modernize, and evolve before market forces force them to do so the hard way.

More Resources:

Featured Image: KitohodkA/Shutterstock

Why Your SEO Work Isn’t Getting Implemented (The IT Line Of Death) via @sejournal, @billhunt

I recently spoke with an SEO who, along with his entire team, had just been laid off. The company was rapidly losing organic traffic, leadership was frustrated, and from their perspective, nothing was being done to fix it. The SEO saw it very differently. They had submitted more than 1,400 tickets over the previous 18 months, each documenting an issue and outlining the importance of what needed to be done. The backlog was extensive, detailed, and, in their mind, proof that the SEO team was working hard to reverse the decline. The problem was that none of the requested actions had been implemented. Engineering time had been consistently redirected to CEO initiatives, product launches, and other internal priorities that always seemed to matter more. From the SEO’s point of view, the work existed. From the business’s point of view, nothing had changed. Traffic declined, visibility dropped, and eventually a decision was made to eliminate this underperforming team.

A backlog is not progress. It is an unimplemented intent.

This is the uncomfortable reality many practitioners struggle to accept. Submitting tickets is not the job. Getting them implemented is. If your recommendations never make it into production, they do not exist in any meaningful way. They do not drive traffic, they do not improve visibility, and they do not protect the business as Google continues to evolve. And right now, that evolution is accelerating, which makes the gap between activity and impact even more dangerous.

Align With What Already Matters

You can see how organizations are frantically responding to the pressure to perform in AI Search, albeit subtly. Work that sat untouched for months as “SEO improvements” suddenly gets prioritized when it is reframed as AI readiness, Generative Engine Optimization, or content structuring for AI discovery. Nothing about the underlying work changes, but the framing does, because it aligns with what leadership believes matters in that moment. It may feel frustrating, even cynical, but it reveals a deeper truth.

At IBM, we struggled to get many SEO initiatives prioritized. A report later flagged our site search experience as poor and negatively impacting sales of our own search product. The required improvements were largely the same as those we had been recommending for external SEO. By relabeling them as “site search fixes” under this new mandate, we were able to accelerate implementation and improve both internal and external search performance. Work is not prioritized because it is the right thing to do. It is prioritized because it aligns with the current narrative of impact and executive priorities. To understand why so much SEO work fails to cross that threshold, you have to look at where decisions are actually made.

The Line You Don’t See Until It Stops You

After selling my agency, I took on a project for a company that was already performing well in organic search. Then Google launched paid search, and everything shifted. Large advertisers began reallocating their budgets because buying search traffic directly from Google suddenly looked more efficient than advertising on websites that simply arbitrage organic traffic to generate the ad impressions they had purchased.  The board’s response was immediate and direct. They wanted to dominate every aspect of their category and be in the top three across the board, and they were willing to provide me with whatever resources were necessary to make that happen.

So I went to engineering with my plan and list of activities for total domination, expecting complete alignment and momentum. Instead, the CTO walked me to a whiteboard and pointed to a faint dotted line. Anything above that line, he explained, might get implemented this fiscal year. Anything below it would not. There was no debate or negotiation. Every idea, no matter how strategically sound, had to either fit above that line or displace something already there. It was a simple constraint of available resources, and it made one thing clear: what was already there mattered. He told me that those initiatives were also blessed by the same executives who greenlit mine. These existing initiatives were tied directly to revenue, others to compliance or security, and some were simply protected by stakeholders with enough influence to keep them in place.

That was the moment the reality became clear. This line, invisible in every audit and absent from every SEO tool, determines what actually gets built. I call it the “IT line of death.” Your mission, as an SEO or GEO manager, is to find creative ways to get your activities into or to replace one of those above-the-line projects.

From Tasks To Contribution Value

Most SEO recommendations do not fail because they are wrong. They fail because they are not competitive within that resource allocation system. This means everything is a trade-off. Engineering does not evaluate your recommendation in isolation; they evaluate it against everything else competing for their time and resources. Revenue-driving features, compliance requirements, infrastructure improvements, and existing commitments all carry weight. And so does the requester. When SEO shows up as a collection of disconnected fixes, it struggles to compete because it lacks a clearly articulated cost, ownership, and relative impact.

That realization forces a shift in how SEO needs to be approached. It is no longer enough to identify issues. You have to justify why they deserve to exist above the line and are as important as or more important than another activity. That means translating work into effort, impact, and trade-offs. It means moving from tasks to contribution value. Audits, tickets, and backlogs describe activity, but engineering teams do not fund activity. They fund outcomes. If you cannot explain why your recommendation is worth more than another team’s request, it will not get done.

This is where many SEO programs stall. They are rich in insight but weak in prioritization, and that gap becomes even more visible when you look at how work actually gets implemented. It is often difficult to tie SEO activities directly to revenue or basket size, but that does not remove the responsibility to try.

Fix The Systems, Not The Symptoms

Once you understand your organization’s IT line of death, the question becomes practical. How do you get work implemented in an environment where everything is competing? The answer is not to push harder, but to work differently within the system. In most organizations, the fastest path to implementation is not to create new work but to align with work already in motion. Engineering teams are constantly updating templates, redesigning page structures, migrating platforms, or refactoring components. Those initiatives already sit above the line. They already have a budget, attention, and momentum. When SEO is introduced as a separate request, it has to fight for priority. When it is embedded into an existing initiative, it inherits that priority. Some of the most impactful SEO changes are implemented this way, folded into broader projects rather than introduced as standalone efforts.

This becomes even more effective when you focus on scale. Isolated fixes rarely justify prioritization, but changes that act as force multipliers do. Updating a template rather than a single page can affect thousands of URLs. Adjusting CMS logic can eliminate entire categories of issues. Fixing navigation or internal linking can reshape how the entire site is understood and crawled. These are the types of changes that connect relatively small effort to large-scale impact, which makes them far more competitive at the line.

Even then, success depends on understanding the problem at its source. One of the most common failure points in SEO is diagnosing symptoms instead of causes. Large numbers create urgency, but they can also mislead. Thousands of redirects, tens of thousands of 404 errors, and duplicate pages across a site often trigger large remediation efforts, yet they are frequently just the visible output of a much smaller issue.

I worked with a company that generated pages from a product feed daily, with URLs based on the product name and its first attribute. It seemed logical, but the attribute was not stable. Every time it changed, the URL changed with it. That single design decision created a cascade of problems. New pages were constantly being created, old URLs turned into 404s, and the site effectively churned its own index. The Search Console error log reflected this chaos, filled with tens of thousands of issues that needed fixing. But none of those issues was the real problem. The solution was not to clean up the errors; it was to stop creating them. By realigning the URL structure to a stable identifier such as a SKU, the entire system stabilized. The errors disappeared because the mechanism producing them was removed. One change replaced thousands of remediation tasks.

This is the difference between work that stays below the line and work that crosses it. The former treats symptoms, the latter resolves the system that generates them. This dynamic is not unique to a single company or a single moment in time. It shows up consistently across organizations, industries, and levels of Search maturity. Whether the constraint is engineering bandwidth, compliance requirements, or competing product priorities, the outcome is the same. Work that cannot justify itself at the line does not happen. We explored this further in a podcast episode, breaking down how this pattern repeats and why so many well-intentioned initiatives stall before they ever reach production. The conclusion was consistent. Most SEO work does not fail because it is wrong; it fails because it is not framed in a way the organization can act on.

Once you understand that, the role of SEO changes. You are no longer just identifying issues; you are shaping decisions. You are defining what is worth doing, why it matters now, and what impact it will have relative to everything else competing for attention. That is what moves work from backlog to implementation.

In the end, nothing gets done because it is best practice. It gets done because it is worth doing.

More Resources:

Featured Image: Roman Samborskyi/Shutterstock

The Modern SEO Center Of Excellence: Governance, Not Guidelines via @sejournal, @billhunt

Most enterprise SEO Centers of Excellence (CoE) fail for a surprisingly simple reason. They were built to advise, not to govern.

On paper, the idea of an SEO CoE is appealing. Centralized expertise. Shared standards. Training and enablement. Documentation that can be reused across markets. In theory, it should bring order to complexity.

In practice, it rarely does.

Most SEO CoEs operate without any real authority over the systems that determine search performance. They publish recommendations that teams are free to ignore. A CoE without governance power becomes a spectator to the very failures it was meant to prevent. This weakness stayed hidden for years because traditional search was forgiving.

Inconsistencies could be corrected downstream. Signals recalibrated. Rankings recovered. But modern search, especially AI-driven discovery, is far less tolerant. Visibility is now shaped by structure, consistency, and machine clarity across the entire digital ecosystem.

Those outcomes cannot be achieved by advisory groups alone. They require operational governance embedded into how digital assets are designed, built, and deployed.

The future of SEO Centers of Excellence isn’t about sharing knowledge more efficiently. It’s about controlling the standards that shape digital assets before they exist.

What We Mean By A Modern SEO Center Of Excellence

A Center of Excellence, in its simplest form, is meant to centralize expertise and standardize how work is done across a complex organization. In theory, it exists to reduce duplication, improve quality, and create consistency at scale.

A modern SEO CoE functions as a governance body. Its responsibility is to define, enforce, and audit the standards that determine how digital assets are designed, built, and deployed across the enterprise.

This distinction matters more than most organizations realize. A CoE is not effective because teams agree with it or appreciate its expertise. It is effective because compliance with its standards is required.

When organizations confuse documentation with governance, they end up with extensive guidelines and minimal change. Standards exist, but adherence is optional. Exceptions multiply quietly. Leadership assumes SEO is being handled because materials have been produced.

Governance is what closes that gap. It transforms SEO from advice into infrastructure.

The Legacy CoE Problem

Traditional SEO Centers of Excellence were designed for a very different operating reality. SEO was treated as a marketing discipline, and visibility was shaped largely by page-level tactics that could be reviewed and corrected after launch. In that environment, guidance, training, and periodic audits were often sufficient to produce incremental gains.

As a result, most legacy CoEs were built around education rather than enforcement. They created playbooks, audited markets, trained local teams, and advised on fixes. What they did not have was authority over the systems that actually determined outcomes – development standards, templates, structured data policies, or product requirements. SEO success depended on persuasion rather than process.

Over time, the CoE became a library of best practices instead of an operating body. The problem was never a lack of knowledge. It was a lack of authority.

That distinction has been understood for decades. Nearly 20 years ago, Search Marketing, Inc., co-authored with Mike Moran, laid out the operating requirements for enterprise-scale search programs, including centralized standards, cross-functional integration, executive sponsorship, and accountability beyond marketing. The model assumed – correctly – that search performance at scale required structural ownership, not optional recommendations.

Where enterprises struggled was not in understanding that model, but in implementing it inside organizations unwilling to centralize control over digital standards. Many adopted the language of a Center of Excellence without adopting the authority required to make it effective.

Why Governance Is Now Mandatory

Search no longer evaluates isolated pages. It evaluates whether an organization presents itself as a coherent system.

As search engines and AI-driven discovery layers have evolved, they’ve shifted from asking “Which page is most relevant?” to “Which sources can be consistently understood and trusted?” That determination isn’t made at the page level. It emerges from how information is structured, reused, governed, and reinforced across an enterprise.

This is where most organizations begin to struggle. In the absence of centralized governance, decisions that affect search performance are made independently across markets, platforms, and teams. Templates evolve to meet local needs. Content adapts to brand or legal constraints. Structured data is implemented differently depending on tooling or vendor preference. None of these choices are irrational on their own. But taken together, they fragment the system’s signal.

Modern search systems respond poorly to fragmentation. When entity definitions vary, taxonomy drifts, or structural rules aren’t consistently enforced, machines can no longer form a stable representation of the brand. The result isn’t a gradual decline that can be corrected with optimization. It’s exclusion. AI-driven systems simply route around sources they cannot reliably interpret and default to alternatives that appear more coherent.

This is the inflection point that makes governance mandatory rather than optional. Best practices and guidelines assume voluntary compliance. They work only when teams are aligned, incentives are shared, and deviations are rare. Enterprise environments rarely meet those conditions. Without enforcement, standards erode quietly, exceptions multiply, and inconsistencies become embedded before anyone notices the impact externally.

Governance is what closes that gap. It ensures that the structural decisions shaping discoverability are made intentionally, enforced consistently, and reviewed before they harden into production. In modern SEO, that level of control is no longer a nice-to-have. It’s the prerequisite for visibility.

What A Real SEO CoE Must Control

A modern SEO Center of Excellence cannot remain advisory. To function as governance, it must have authority across a small number of clearly defined domains where search performance is created or destroyed at scale.

These are not tactical responsibilities. They are control points across five critical areas.

1. Platform & Template Standards

At scale, templates, not individual pages, determine crawlability, eligibility, and consistency. When SEO has no authority over templates, every market, product line, or release becomes a new risk surface, and structural mistakes are replicated faster than they can be corrected.

Governance here does not replace engineering judgment. It defines the non-negotiable requirements that engineering solutions must satisfy before they reach production. In practice, this means the CoE governs standards for:

• Page templates and rendering rules.
• Technical accessibility requirements.
• Metadata and URL frameworks.
• Structured data deployment patterns.

2. Entity & Structured Data Governance

In AI-driven search, entity clarity determines whether a brand is understood or ignored. Fragmented schema does not merely weaken signals; it fractures identity.

A governing CoE must own how the organization defines itself to machines, ensuring consistency across properties, platforms, and markets. This is not about marking up more fields. It is about protecting signal integrity.

That responsibility includes control over:

• Entity definitions and relationships.
• Schema standards and implementation rules.
• Canonical brand representation.
• Cross-property and cross-market consistency.
• Alignment between legal constraints and brand expression.

Without centralized ownership, entity signals drift – and visibility follows.

3. Content Commissioning Standards

One of the most important shifts in modern SEO is where governance occurs in the content lifecycle. A governing CoE does not review content after publication. It defines what qualifies for creation in the first place. By setting structural and intent-based requirements upstream, it eliminates downstream debate and rework.

This means governing:

• Content structure and format requirements.
• Intent mapping and coverage frameworks.
• Depth and completeness expectations.
• Internal linking rules.
• Topic and market rollout models.

When these standards are enforced before content is commissioned, SEO stops negotiating outcomes and starts shaping inputs.

4. Cross-Market Consistency

Global organizations need flexibility, but flexibility without oversight quickly turns into fragmentation. A governing CoE ensures that deviations from global standards are visible, intentional, and accountable. It does not eliminate local autonomy; it prevents unintentional conflict.

This requires authority over:

• Global standard adoption.
• Local deviation review and approval.
• Hreflang governance.
• Language-versus-market resolution.
• Canonical ownership rules.

Without centralized oversight, local teams often send conflicting signals that quietly erode global visibility.

5. Measurement & Accountability Integration

Finally, governance fails if it cannot be measured and enforced. A real SEO CoE controls not just reporting, but accountability. If search performance represents systemic risk, it must be monitored and escalated like one.

That includes ownership of:

• SEO performance standards.
• Reporting frameworks.
• Shared key performance indicators across departments.
• Compliance monitoring.
• Escalation authority and executive visibility.

SEO must be measured as infrastructure, not as a marketing channel. When failures carry organizational consequences, governance becomes real.

Control Vs. Influence: The Critical Difference

Most SEO Centers of Excellence operate through influence. They publish best practices, provide training, and offer guidance in the hope that teams will comply. When alignment exists and incentives are shared, this approach can work.

Enterprise environments rarely meet those conditions.

Influence depends on cooperation. It assumes teams will voluntarily prioritize SEO standards alongside their own objectives. When deadlines tighten or tradeoffs arise, influence is the first thing to give way. What remains are local decisions optimized for speed, risk avoidance, or revenue, not for long-term discoverability.

Governance operates differently.

A governing SEO CoE does not dictate how teams build solutions, but it does define the non-negotiable requirements those solutions must satisfy. It establishes mandatory operating standards for templates, structured data, entity representation, and market compliance, and it embeds those standards into workflows before assets are released.

This distinction is often misunderstood as “SEO trying to control everything.” In reality, governance is about oversight, not micromanagement. Engineering still engineers. Product still prioritizes. Markets still localize. But all of them operate within enforced constraints that protect search visibility as a shared enterprise asset.

That difference becomes visible in where authority actually exists. Advisory CoEs can recommend standards, but they cannot enforce template compliance, approve deviations, require pre-launch checks, or escalate violations. Governing CoEs can. Enterprise SEO only scales under that model. Not because teams agree with SEO, but because the organization has decided that discoverability is important enough to be protected by enforceable standards.

Organizational Impact Of A Governing CoE

When SEO governance is institutionalized, the effects extend well beyond search metrics.

Structural errors begin to decline, not because teams are fixing issues faster, but because many of those issues never make it to production. Standards enforced upstream prevent the same mistakes from being replicated across templates, markets, and releases. SEO shifts from remediation to prevention.

Visibility improves for the same reason. When signals are consistent and scalable, search systems can form a stable understanding of the brand. That consistency compounds over time, reinforcing eligibility rather than constantly resetting it.

Markets also begin to align more naturally. Governance doesn’t eliminate local flexibility, but it requires that deviations be explicit, reviewed, and justified. Instead of fragmentation happening quietly, exceptions become visible and accountable. Global coherence stops being accidental.

In AI-driven discovery, this coherence becomes even more valuable. Eligibility improves not through tactical optimization, but because entities, content, and relationships are structured in ways machines can reliably interpret. Brands stop competing on individual pages and start competing as systems.

Perhaps most noticeably, internal friction drops. When SEO standards are embedded into workflows, teams stop renegotiating fundamentals on every launch. The same conversations don’t have to happen repeatedly, and escalation becomes the exception rather than the norm.

Counterintuitively, this increases speed. When governance defines the rules of the road, execution accelerates because teams can focus on building within known constraints instead of debating them after the fact.

The Final Reality

Enterprise SEO rarely fails because teams aren’t trying hard enough. It fails because governance is missing.

Over the years, I’ve helped design and implement Search and Web Effectiveness Centers of Excellence inside large organizations. The ones that worked best all shared a common trait: They had real authority to guide and enforce compliance. Not heavy-handed control, but clear standards backed by the ability to say no when those standards were ignored.

What’s often misunderstood is that these governing CoEs were also the most collaborative. Because authority was clear, teams didn’t have to renegotiate fundamentals on every project. Everyone understood the shared goals and the mutual benefits of operating as a coordinated system rather than as isolated functions. Governance removed friction instead of creating it.

Those CoEs succeeded by treating search visibility as a team sport. Cross-department initiatives weren’t exceptions; they were the operating norm. Development, content, product, and marketing aligned around enterprise objectives because the value of doing so was explicit and reinforced through process, not persuasion.

By contrast, CoEs built solely to advise rarely achieved that alignment. Without enforcement, standards became optional, exceptions multiplied, and collaboration depended on goodwill rather than structure.

Modern search leaves little room for that model. Organizations that want to maintain control over how they are discovered, understood, and recommended must move beyond documentation and consensus-building alone. Governance is what makes collaboration durable. It turns good intentions into repeatable outcomes.

In an AI-driven search environment, that shift is no longer aspirational. It is the difference between being represented accurately and being replaced quietly by sources that are.

More Resources:

Featured Image: Masha_art/Shutterstock

How To Build An SEO Commissioning Workflow: From Tickets To Requirements via @sejournal, @billhunt

Enterprise SEO doesn’t fail because teams lack knowledge. It fails because they’re invited too late.

In most large organizations, SEO still operates in a reactive posture. Teams review pages after launch, run audits, document issues, file tickets, and then wait, often for months, for other teams to implement changes. Modern search visibility is no longer shaped by tweaks. It is shaped by what gets built upstream.

High-performing organizations have responded by changing SEO’s role entirely. Instead of treating SEO as a cleanup function, they’ve repositioned it as a commissioning function, one that defines the exact requirements digital assets must meet before they are ever created. This article explains how enterprises can formalize that shift by building an SEO commissioning workflow: a structured, repeatable process that embeds search requirements into digital creation at the moment decisions are made.

The Problem With Ticket-Based SEO

In the traditional enterprise model, SEO is integrated into the workflow after launch. In the traditional cycle, content is created or revised without input from SEO, and the resulting changes often harm search performance. The SEO team investigates the decline to identify new or updated content or templates and creates tickets to adapt them to recover what was lost, or, in the case of new content, what was not gained.  Those tickets are then placed into development queues alongside revenue initiatives, product launches, and executive priorities.

What follows is predictable. Fixes are delayed. Implementation is partial. Some issues are addressed, others are deferred, and many recur in the next release because the underlying cause was never addressed. This model creates three chronic failures.

• First, SEO is perpetually behind. It is reacting to outcomes rather than shaping them.
• Second, SEO relies on persuasion rather than process.
• Third, structural mistakes multiply faster than they can be fixed. Every new page, template, or market rollout becomes another opportunity to replicate the same issues at scale.

When SEO lives downstream, every asset is a potential liability. The organization becomes very good at discovering problems and very bad at preventing them. Progress depends on relationships and goodwill rather than enforceable requirements. Commissioning exists to flip that dynamic.

What SEO Commissioning Actually Means

Instead of reviewing pages after they are launched, leading organizations have begun moving SEO to the moment digital assets are conceived.

At that stage, the question is no longer whether a page can be optimized later. The question becomes whether the asset is designed so that search systems can understand it from the start. Content structure, template behavior, entity representation, internal linking roles, and market alignment are all determined before production begins. When those decisions are made upstream, discoverability becomes a property of the system rather than a series of corrections applied after launch.

A useful analogy comes from high-rise construction. On complex projects, builders often assign a dedicated commissioning agent whose job is not to install anything directly but to ensure that all the independent systems going into the building, including HVAC, elevators, electrical systems, glass, fire controls, and dozens of other components, work together as a coherent whole. Without that coordination, the building may be technically complete yet fail to function as a system.

SEO plays a similar role in digital environments. Instead of diagnosing problems after launch, SEO helps define the requirements that must be satisfied before assets move forward. Those requirements shape how content is commissioned, how templates behave, how entities are represented, and how information is structured so that search engines and AI systems can interpret it correctly.

When SEO participates at the design stage, teams stop asking, “How do we fix this later?” and start asking a more useful question: What must be true before this asset should exist at all?  In that environment, SEO stops behaving like a repair function and becomes part of the design discipline that ensures digital systems work as intended from the beginning.

The SEO Commissioning Lifecycle

Organizations that operationalize SEO commissioning tend to follow the same lifecycle, even if they don’t label it explicitly. The difference is that high-performing teams make these stages intentional, documented, and enforceable.

1. Define Intent Before Creation

Every asset should begin with clarity about why it should exist from a search perspective.

At this stage, SEO identifies how users actually search for the topic or product, how intent is distributed across informational, commercial, and navigational needs, and what search systems typically surface for eligibility. This prevents a common enterprise failure mode: Well-written content that is structurally misaligned with how demand expresses itself.

Commissioning forces an uncomfortable but necessary question early in the process: Why would a search engine or AI system ever select this asset?

If that question cannot be answered clearly, the asset should not move forward.

2. Define Eligibility Signals

Before development or content production begins, SEO specifies the signals that must exist for eligibility.

This includes decisions about schema usage, page classification, metadata structures, heading hierarchies, internal linking roles, entity associations, media requirements, and – when relevant – market and language signals. The key distinction is timing. These decisions are not retrofitted later. They are defined before work begins, ensuring assets are born eligible rather than hoping eligibility can be added after the fact.

Eligibility becomes a prerequisite, not a gamble.

3. Define Structural Requirements

Commissioning also applies to platforms and templates, not just content.

This is where SEO moves closest to product and engineering teams, shaping the structures that determine discoverability at scale. URL rules, template architecture, rendering accessibility, navigation placement, internal linking frameworks, and content modules for depth are all defined here. These are not tactical SEO opinions. They are structural requirements that influence how thousands of pages will be interpreted by machines over time.

When SEO is incorporated at this stage, discoverability becomes a property of the system rather than the result of manual intervention.

4. Pre-Launch Validation (Search QA)

Before release, SEO validates that commissioning requirements were actually implemented.

This includes confirming crawlability, indexability, structured data integrity, entity consistency, internal linking alignment, market targeting, and content completeness relative to intent. This step is often misunderstood as “SEO QA,” but it is fundamentally different from traditional bug fixing. The purpose is not to discover surprises. It is to confirm compliance with requirements already agreed upon.

When commissioning is done correctly, this stage is fast and predictable.

5. Post-Launch Monitoring & Feedback

Commissioning does not end at launch.

SEO monitors performance relative to expectations, including visibility patterns, SERP feature capture, AI citation presence, market alignment, and template behavior at scale. Real-world query data then feeds back into future commissioning rules. This creates a virtuous cycle. SEO evolves from a reactive repair function into a continuous upstream optimization system that improves with each release.

Where Commissioning Lives In The Enterprise Workflow

For commissioning to work, it must live where decisions are made.

That means being embedded into product requirement documents, content briefs, CMS template design, sprint planning, market rollout processes, and governance checkpoints. SEO becomes a required approval step before assets move forward, not an optional reviewer afterward.

This is the difference between SEO as a service and SEO as infrastructure.

Why This Model Changes Everything

Ticket-based SEO creates backlogs and dependencies and commissioning-based SEO creates leverage and prevention. The benefits compound quickly.

Assets launch search-ready the first time, increasing speed rather than slowing it. Structural failures decline because mistakes are prevented upstream. Compliance scales automatically across thousands of pages. Content and entities are structured for machine retrieval from day one. And SEO stops fighting for attention because it is embedded directly into how work gets done.

Most importantly, commissioning aligns incentives. SEO success is no longer dependent on favors, persuasion, or heroics. It becomes a predictable outcome of a well-designed system.

The Hard Truth

Most enterprise SEO pain is self-inflicted. Organizations built workflows where SEO arrives late, lacks authority, fixes rather than defines, and is measured by outcomes shaped by others. Commissioning removes those structural handicaps.

It moves SEO to the point where search success is actually created: the moment decisions are made.

Coming Next

Commissioning solves timing; it does not solve ownership. In the next article, we’ll examine why SEO still fails without clear cross-functional accountability and how enterprises must redefine ownership if commissioning is going to scale.

More Resources:

Featured Image: Summit Art Creations/Shutterstock

Enterprise SEO Operating Models That Scale In 2026 And Beyond via @sejournal, @billhunt

Most enterprises are still treating SEO as a marketing activity. That decision, whether intentional or accidental, is now a material business risk.

In the years ahead, SEO performance will not be determined by better tactics, better tools, or even better talent. It will be determined by whether leadership understands what SEO has become and restructures the organization accordingly. SEO is no longer simply a channel but an infrastructure, and infrastructure decisions are leadership decisions.

The Old SEO Question Is No Longer Relevant

For years, executives asked a familiar question: Are we doing SEO well? Or even more simply, are we ranking well in Google? 

That question assumed SEO was something you did, summed up as a collection of optimizations, audits, and campaigns applied after the fact. It made sense when search primarily ranked pages and rewarded incremental improvements. The more relevant question today is different: Is our organization structurally capable of being discovered, understood, and selected by modern search systems?

That is no longer a marketing question. It is an operating model question because AI optimization must become a team sport.

Search engines, and increasingly AI-driven systems, do not reward isolated optimizations. They reward coherence, structure, intent alignment, and machine-readable clarity across an entire digital ecosystem. Those outcomes are not created downstream. They are created by how an organization builds, governs, and scales its digital assets.

What Has Fundamentally Changed

To understand why enterprise SEO operating models must evolve, leadership first needs to understand what actually changed in search.

1. Search Systems Now Interpret Intent Before Retrieval

Modern search systems no longer treat queries as literal requests. They reinterpret ambiguous intent, expand queries through fan-out, explore multiple intent paths simultaneously, and retrieve information across formats and sources. Content no longer competes page-to-page. It competes concept-to-concept.

If an organization lacks clear intent modeling, structured topical coverage, and consistent entity representation, its content may never enter the retrieval set at all, regardless of how optimized individual pages appear.

2. Eligibility Now Precedes Ranking

This shift also changed the sequence of how visibility is earned. Ranking still matters, particularly for enterprises where much of the traffic still flows through traditional results. But ranking now occurs only after eligibility is established. As search experiences move toward synthesized answers and AI-driven surfaces, eligibility has become the prerequisite rather than the reward.

That eligibility is determined upstream by templates, data models, taxonomy, entity consistency, governance, and workflow design. These are not marketing decisions. They are organizational ones.

3. Enterprise SEO Has Crossed An Infrastructure Threshold

Enterprise SEO has always depended on infrastructure. What has changed is that modern search systems no longer compensate for structural shortcuts. In the past, rankings recovered, signals recalibrated, and messiness was often forgiven.

Today, AI-driven systems amplify inconsistency. Retrieval becomes selective, narratives persist, and structural debt compounds. Delivering results aligned to real searcher intent has shifted from a forgiving environment to a selective one, where visibility depends on how well the underlying system is designed. Taken together, these conditions define what a scalable enterprise SEO operating model actually looks like, not as a team or function, but as an organizational capability.

The Leadership Declaration: What Must Be True In 2026

Organizations that scale organic visibility in the coming years will share a small set of non-negotiable characteristics. These are not best practices. They are operating requirements.

Declaration #1: SEO Must Be Treated As Infrastructure

SEO must be treated as infrastructure. That means it moves from a downstream marketing function to a foundational digital capability. SEO requirements are embedded in platforms, standards are enforced through templates, and eligibility is designed before content is commissioned. When failures occur, they are treated like performance or security issues, not optional enhancements. If SEO depends on post-launch fixes, the operating model is already broken.

Declaration #2: SEO Must Live Upstream In Decision-Making

SEO must live upstream in decision-making. Search performance is created when decisions are made about site structure, content scope, taxonomy, product naming, localization strategy, data modeling, and internal linking frameworks. SEO cannot succeed if it only reviews outcomes; it must help shape inputs. This does not mean SEO dictates solutions. It means SEO defines non-negotiable discovery constraints, just as accessibility, performance, and security already do.

Declaration #3: SEO Requires Cross-Functional Accountability

SEO requires cross-functional accountability. Visibility depends on development, content, product, UX, legal, and localization teams working in concert, similar to a professional sports team. In most enterprises, SEO is measured on outcomes while other teams control the systems that produce them. That accountability gap must close. High-performing organizations define shared ownership of visibility, clear escalation paths, mandatory compliance standards, and executive sponsorship for search performance. Without this, SEO remains a negotiation rather than a capability.

Declaration #4: Governance Must Replace Guidelines

Governance must replace guidelines. Guidelines are optional; governance is enforceable. Scalable SEO requires mandatory standards, controlled templates, centralized entity definitions, enforced structured data policies, approved market deviations, and continuous compliance monitoring. This demands a Center of Excellence with authority, not just expertise. SEO cannot scale on influence alone.

Declaration #5: SEO Must Be Measured As A System

Finally, SEO must be measured as a system. Executives need to move beyond quarterly performance questions and instead assess structural eligibility across markets, intent coverage, entity coherence, template enforcement, and where visibility leaks and why. System-level measurement replaces page-level obsession.

This shift mirrors a broader issue I explored in a previous Search Engine Journal article on the questions CEOs should be asking about their websites, but rarely do. The core insight was that executive oversight often focuses on surface-level outcomes while missing systemic sources of risk, inefficiency, and value leakage.

SEO measurement suffers from the same blind spot. Asking how SEO “performed” this quarter obscures whether the organization is structurally capable of being discovered and represented accurately across modern search and AI-driven environments. The more meaningful questions are systemic: where visibility leaks, which teams own those failure points, and whether the underlying architecture enforces consistency at scale.

Measured this way, SEO stops being a reporting function and becomes an early warning system for digital effectiveness.

The Operating Model Divide

Enterprises will fall into two groups.

Some will remain tactical optimizers, where SEO lives in marketing, fixes happen after launch, paid media masks organic gaps, and AI visibility remains inconsistent. Others will become structural builders, embedding SEO into systems, defining requirements before creation, enforcing governance, and earning consistent retrieval and trust from AI-driven platforms.

The difference will not be effort. It will be organizational design.

The Clarifying Reality

Ranking still matters, particularly for enterprises where a significant share of traffic continues to flow through traditional results. What has changed is not its importance, but its position in the visibility chain. Before anything can rank, it must first be retrieved. Before it can be retrieved, it must be eligible. And eligibility is no longer determined by isolated optimizations, but by infrastructure – how content is structured, how entities are defined, and how consistently signals are enforced across systems.

Every enterprise already has an SEO operating model, whether it was designed intentionally or emerged by default. In the years ahead, that distinction will matter far more than most organizations expect.

SEO has become infrastructure. Infrastructure requires leadership because it shapes what the organization can reliably produce and how it is perceived at scale. The companies that win will not be the ones that optimize harder, but the ones that operate differently, by designing systems that search engines and AI-driven platforms can consistently discover, understand, and trust.

More Resources:

Featured Image: Anton Vierietin/Shutterstock

The Real SEO Skill No One Teaches: Problem Deduction via @sejournal, @billhunt

Most SEO failures are not optimization failures. They are reasoning failures that occur before optimization even begins.

In enterprise SEO escalations, the pattern is remarkably consistent. Teams jump straight to causes, debate theories, and assign blame before anyone clearly articulates the actual problem they are trying to understand.

Once blame enters the conversation, problem definition disappears. Teams shift into CYA mode, and without a shared understanding of the problem, every proposed fix becomes guesswork.

The Failure Pattern Everyone Recognizes

If you’ve worked in enterprise SEO long enough, you’ve seen this meeting.

A stakeholder raises an issue. Google is showing the wrong title or site name. Search visibility dropped. A location isn’t represented correctly. The room doesn’t go quiet. It fills with explanations.

Someone points to a lack of internal links. Another suggests Google rewrote the titles. Yet another CMS defect is mentioned. A recent Google update is blamed. Someone inevitably asks whether hreflang is broken.

Each explanation sounds plausible in isolation. Each reflects real experience. But none of them is grounded in a clearly stated problem.

Everyone is trying to be helpful. No one has actually said what outcome the system produced.

SEO discussions often collapse not because teams lack expertise, but because they skip the most important step: precisely describing the system outcome they are trying to explain.

Meeting Two: Activity Without Clarity

What usually follows is a second meeting. On the surface, it feels productive.

Teams arrive having done work. The CMS has been reviewed. A detailed technical SEO audit is complete. Google update trackers and industry forums have been checked for similar impacts, along with LinkedIn commentary. Multiple diagnostic tools have been run.

There is evidence of many man-hours of activity presented. There are screenshots of issues and non-issues, and it all looks like progress toward a resolution. In reality, it is often a misdirected effort.

If the original problem was vague or incorrectly framed, all of that analysis is aimed at the wrong target. Only later does the realization set in. While the audits detected issues, they are not related to this problem.

Time and attention were spent validating assumptions instead of diagnosing system behavior.

That’s not an execution failure. It’s a problem definition failure.

Why SEO Conversations Go Off The Rails

That failure isn’t accidental. It’s structural, and SEO is uniquely exposed to it.

I have often been critical, stating that the search industry lacks root cause analysis. That’s true, but it’s not because teams aren’t trying. There is no shortage of audits, checklists, or prescriptive processes when a traffic drop or SERP anomaly appears. The problem is that those tools narrow thinking rather than clarify it. They push teams toward doing something before anyone has agreed on what actually happened.

In many SEO conversations, signals are treated as probabilistic guesses rather than observed outcomes. Rankings fluctuate, a listing looks different, traffic dips, and the discussion quickly drifts toward familiar explanations. Google must have changed something. A ranking factor shifted. An update rolled out.

What gets missed is far more mundane and far more common. Control is spread across teams. Changes are made inside one department and are never communicated to another. Content, templates, navigation, schema, analytics, and infrastructure evolve independently. Cause and effect don’t move in straight lines, and no single team sees the whole system.

When no one clearly states the outcome the system produced, the group defaults to what feels responsible: activity.

Root cause analysis turns into a checklist exercise. Teams start debating causes before agreeing on the outcome itself. Meetings fill with effort, artifacts, and action items, but clarity never quite arrives.

Systems, however, don’t respond to effort. They respond to inputs.

The Missing Skill: Problem Deduction

The most important SEO skill isn’t keyword research, schema, technical audits, GEO, or any other optimization acronym that happens to be in fashion. Those are all processes and tools. Useful ones. But they only matter after the real work has been done. That work is problem deduction.

Problem deduction is the discipline of slowing the conversation down long enough to understand what the system actually produced, not what the team expected it to produce. It requires stepping outside of assumptions, resisting familiar explanations, and describing the outcome in neutral terms before trying to fix anything.

Only then does real analysis begin. Teams can reason backward through the signals that contributed to the outcome, distinguish between inputs they can change and constraints they inherited, and act without blame or superstition driving the discussion.

In practice, problem deduction means the ability to:

• Observe a system outcome without bias, focusing on what the system produced rather than what was intended.
• Describe that outcome precisely and neutrally, without embedding assumptions about cause.
• Reason backward through contributing signals, identifying which inputs could plausibly influence the result.
• Separate fixable inputs from historical constraints, so effort is spent where it can actually matter.
• Act without blame or superstition, keeping decisions grounded in evidence rather than instinct.

This doesn’t replace technical SEO or root cause analysis. It makes them possible.

Problem deduction is systems thinking applied to search. And almost no one teaches it.

A Real-World Enterprise Example

Recently, I reviewed an enterprise case where a client was frustrated that Google consistently displayed a specific location as the site name, regardless of the user’s location or query intent. The conversation followed a familiar arc. At first, explanations came quickly. Someone pointed to internal linking, noting that this location had accumulated more authority over time. Others suggested Google’s automatic title rewrites were to blame. The CMS came up, along with the possibility of injected or inconsistent code. SEO implementation gaps were also mentioned. Each explanation sounded reasonable. All of them were based on real experience. But none of them described the outcome. So we stopped the discussion and reset the conversation by stating the problem plainly:

Google selected a location, not the brand name, as the site name representing the brand in search results.

That single sentence changed the tone of the room. Once the outcome was clearly defined, the reasoning became straightforward. The discussion shifted from speculation to diagnosis, and the signals that led to that result became much easier to trace.

How Google Actually Made That Decision

Google wasn’t confused. It was responding to a consistent set of reinforcing signals.

Once the outcome was clearly defined, the explanation stopped being mysterious. Several independent signals all pointed to the same conclusion, and Google simply followed the strongest, most consistent path.

1. Misapplied WebSite Schema

One issue started at the structural level. Location pages had been marked up as if each were a separate website entity, rather than reinforcing the primary brand domain. Multiple pages effectively claimed to be “the website,” diluting canonical authority and causing the schema signal to cancel itself out through duplication. Google didn’t misunderstand the markup. It received conflicting declarations and discounted them logically.

2. Title Tag Dilution

At the same time, title tags failed to reinforce a clear hierarchy. The homepage HTML title tag attempted to carry too much information at once, referencing the marketing tagline first, then the brand and first location, and finally the other locations, separated by commas, into a single tag. Instead of clarifying the relationship between the brand and locations, the structure blurred it. Google responded by favoring the location that was most consistently reinforced across signals. Google favored the most consistently reinforced location, not arbitrarily, but logically.

3. External Corroboration Bias

External signals reinforced the same outcome. Inbound links, citations, and references disproportionately pointed to a single location. From Google’s perspective, the broader web corroborated what on-site signals already suggested. One location appeared to represent the brand more clearly than the others. This wasn’t favoritism. It was corroboration.

What Could Be Easily Fixed And What Couldn’t

Once the actual problem was clearly identified, the conversation changed. The issue wasn’t that Google was behaving unpredictably. It was that something in the system was consistently telling Google to treat a single location as the site name rather than the brand itself.

With the problem framed that way, analysis became practical. Instead of debating theories, we could examine the systems that contributed to that outcome and begin correcting them. Just as importantly, it allowed us to distinguish between changes that could be made immediately and those that would require sustained effort.

Some corrections were straightforward. Because the schema was generated programmatically, the WebSite markup could be adjusted immediately to reinforce the primary brand entity. The brand team also agreed to simplify the homepage title, focusing it on the brand and tagline, while allowing individual location pages to carry the weight of location-specific signals.

Other signals were less malleable. External corroboration, built up through years of links and citations pointing to a single location, couldn’t be reversed quickly. That work would take time and consistent reinforcement.

Problem deduction didn’t just tell us what to fix. It told us where to start, what to expect, and how much effort each correction would realistically require.

SEO teams waste enormous effort trying to “fix” things that can only change gradually. Problem deduction helps teams focus on directional correction rather than instant reversal.

Why Root Cause Analysis Often Fails In SEO

Root cause analysis breaks down when teams try to answer “why” before agreeing on “what.”

In enterprise SEO, that failure is amplified by how work is organized. Control is decentralized across content, engineering, analytics, brand, legal, localization, and platform teams. No single group owns the full system, yet everyone is accountable to their own KPIs. When an anomaly appears, the instinct isn’t to describe the outcome carefully. It’s to protect territory.

Conversations shift quickly. Causes are proposed before outcomes are defined. Responsibility is implied, then deflected. Each team points to the part of the system it doesn’t control. The discussion becomes less about understanding behavior and more about avoiding fault.

At the same time, the process itself narrows thinking. Root cause analysis turns into a checklist exercise. Teams reach for audits, tools, and familiar diagnostic steps, not because they are wrong, but because they are safe. Checklists create motion without requiring agreement, and activity becomes a substitute for clarity.

When internal explanations feel uncomfortable or politically risky, attention often shifts outward. Someone cites a recent Google update. Another references a post from a well-known SEO or a chart showing sector-wide volatility. External signals offer a kind of relief. If “everyone” is seeing impact, then no one internally has to explain their system.

But those signals are rarely diagnostic. Used too early, they short-circuit reasoning rather than support it.

The result is a familiar pattern. Meetings generate effort, artifacts, and action items, but the outcome itself remains vaguely defined. Teams stay busy. Nothing really changes.

Problem deduction interrupts that cycle. It forces agreement on what the system actually produced before explanations, defenses, or fixes enter the conversation. Once the outcome is clearly defined, decentralization becomes navigable, blame loses its power, and root cause analysis shifts from performance to purpose.

That’s when it starts working.

The Skill Enterprises Should Be Hiring For First

Not long ago, an advisory client asked me a deceptively simple question while defining a new enterprise search role.

“What is the single most important skill we should hire for?”

They were expecting a familiar answer. Something about technical SEO depth, AI search experience, schema expertise, or platform fluency. That’s usually how these conversations go.

I didn’t give them any of those. Instead, I said critical reasoning.

There was a pause.

Despite what many people in the search industry believe, technical skills are the easy part. Tools can be learned. Platforms change. Gaps get closed. Teams adapt. What’s far harder to teach is the ability to think clearly when the system doesn’t behave the way you expected it to.

Enterprise SEO is full of that kind of ambiguity. Signals conflict. Outcomes are indirect. Ownership is fragmented. And when things go wrong, pressure builds quickly.

In those moments, the people who struggle most aren’t the ones who lack tactical knowledge. They’re the ones who can’t slow the conversation down long enough to reason.

The skill that matters is the ability to observe what the system actually produced without bias, describe it precisely, separate symptoms from causes, reason backward through contributing signals, and resist the urge to jump to conclusions or assign blame.

In other words, problem deduction.

Specifically (as highlighted above), the ability to:

• Observe a system outcome without bias.
• Describe it precisely.
• Separate symptoms from causes.
• Reason backward through contributing signals.
• Resist jumping to conclusions or assigning blame.

I told them plainly: We can teach the mechanics of search. What’s nearly impossible to teach is how to reason critically if that muscle isn’t already there. People either have it or they don’t. Enterprise SEO punishes the absence of that skill more than almost any other digital discipline.

This Is Bigger Than SEO

Once you recognize the pattern, it becomes hard to unsee.

The same failure mode that derails root cause analysis also explains why SEO so often turns political. When outcomes aren’t clearly defined, teams fill the gap with narratives. Best practices harden into superstition. Google updates become a convenient external explanation for internal incoherence. Infrastructure issues quietly masquerade as ranking problems because they’re harder to confront directly.

None of this happens because teams are careless. It happens because modern digital systems are fragmented by design.

As described earlier, control is decentralized across content, engineering, analytics, brand, legal, localization, and platform teams. No one owns the entire system, yet everyone is accountable to their own KPIs. When something goes wrong, describing the outcome precisely feels risky. It invites scrutiny. It raises uncomfortable questions about ownership and handoffs.

So conversations drift. Causes are debated before outcomes are agreed upon. Responsibility is implied, then deflected. Checklists replace reasoning because they allow motion without alignment. And when internal explanations feel politically unsafe, attention shifts outward – to Google updates, industry chatter, or gurus diagnosing sector-wide volatility.

Those external signals provide relief, but not resolution. They describe correlation, not causation. They offer context, not clarity and allow organizations to stay busy without ever confronting how their own systems produced the result.

This is where SEO begins to overlap with something broader: findability.

Whether someone encounters a brand through Google, an AI assistant, a marketplace, or a vertical search engine, the underlying questions are the same. Are we present? Are we represented clearly and consistently? Does that representation invite deeper engagement, or does it confuse and fragment trust?

Those outcomes don’t depend on isolated optimizations. They depend on coherent systems that behave predictably across surfaces.

Problem deduction is what makes that coherence possible. By forcing agreement on what the system actually produced before explanations or fixes enter the room, it cuts through decentralization, neutralizes blame, and restores reasoning. Root cause analysis stops being performative and starts serving its purpose.

That’s when the conversation changes. And that’s when progress actually begins.

The Real Takeaway

Google didn’t choose the wrong site name. It chose the only version of the brand the system clearly defined.

The real SEO skill isn’t knowing what to change. It’s knowing what actually happened before you touch anything at all.

Until enterprises teach, hire for, and reward problem deduction, SEO conversations will continue to spin in circles, fixing symptoms while the system quietly reinforces the same outcomes.

And no amount of optimization can fix a problem that was never clearly defined in the first place.

More Resources:

Featured Image: KitohodkA/Shutterstock