The IT Line of Death in Enterprise SEO

I recently spoke with an SEO who, along with their entire team, had just been made redundant. From the business side, organic traffic had been falling and frustration was building because it looked like nothing was improving. From the SEO team’s perspective, that wasn’t true at all.

Over the previous 18 months, they had raised more than 1,400 tickets documenting issues, recommending fixes, and explaining impact. The work was structured, detailed, and continuous. But almost none of it ever made it into production.

Engineering capacity was constantly pulled towards other priorities—product launches, leadership requests, and CEO-led initiatives that always took precedence. So while the SEO team saw a growing list of actions, the business only saw declining performance. Eventually, the team was cut.

A backlog is not progress. It is only intent that has not been delivered.

This is where many SEO programmes quietly fail. Submitting tickets is not the job. Implementation is. If changes never reach production, they don’t exist in any meaningful sense. They do not influence rankings, traffic, or visibility. And as search evolves quickly, that gap between “work done” and “work shipped” becomes increasingly costly.

Work only matters when it is prioritised

In many organisations, SEO work only moves when it fits the current business narrative.

The same technical fixes that sit untouched for months can suddenly become urgent when rebranded as “AI readiness”, “platform improvement”, or “customer experience upgrades”. The underlying work doesn’t change, but the framing does—and that determines whether it gets prioritised.

I experienced this first-hand while working at IBM. Several SEO recommendations struggled to get traction internally. Later, when similar issues were flagged as problems affecting our own site search performance, they were prioritised immediately. The work was essentially identical, but the context made it valuable.

The lesson is simple: work is not prioritised because it is correct. It is prioritised because it aligns with what leadership currently cares about.

The invisible constraint in every organisation

After selling my agency, I worked with a company that was performing well in organic search. Then the rise of paid search changed how budgets were allocated, and suddenly the pressure to dominate the market increased significantly.

I presented a roadmap for growth, expecting alignment. Instead, the CTO drew a faint line on a whiteboard.

Everything above that line could be delivered within the financial year. Everything below it would not be touched.

There was no negotiation. Every initiative had to compete for limited engineering capacity, and anything already above the line had been prioritised for a reason—revenue, compliance, technical debt, or internal influence.

That moment revealed a hidden reality in most organisations: there is always a limit to what can be delivered, and it is rarely visible to those outside engineering.

This is what I call the “IT line of death”. SEO work only gets delivered if it either sits above that line or replaces something that already does.

From task lists to real business value

Most SEO recommendations fail not because they are incorrect, but because they are not competitive within the organisation’s prioritisation system.

Engineering teams don’t assess SEO in isolation. They compare it against everything else demanding attention: product features, security updates, infrastructure work, and executive requests. SEO often arrives as a list of fixes without clear trade-offs, ownership, or measurable business value.

That makes it easy to deprioritise.

To succeed, SEO work must be reframed. It is not enough to identify issues—you must justify why they deserve to replace something else already scheduled. That means translating recommendations into effort, impact, and opportunity cost.

Backlogs and audits describe activity, but organisations fund outcomes, not activity.

This is where many SEO strategies stall: they generate insight but fail to compete in prioritisation.

Fixing systems instead of symptoms

Once you understand the existence of the IT line, the focus shifts from “how do I get this done?” to “how do I make this part of something already getting done?”

The fastest path to implementation is often alignment, not new requests.

Engineering teams are constantly working on larger initiatives such as platform migrations, template updates, or system refactoring. These already sit above the line. When SEO requirements are embedded into those projects, they inherit priority.

This is how the most impactful SEO improvements tend to happen—not as standalone tickets, but as part of broader engineering work.

Scale also matters. Fixing a single page rarely justifies prioritisation, but fixing a template or CMS logic can affect thousands of pages at once. That shift in scale is often what moves work above the line.

When symptoms are mistaken for causes

A common issue in enterprise SEO is focusing on visible errors rather than the system that creates them.

Large volumes of 404s, redirects, or duplicate pages often trigger urgent fixes, but these are frequently just symptoms.

For example, I once worked with a site that generated product URLs based on a changing attribute from a feed. Every time that attribute changed, a new URL was created. The result was constant churn: broken pages, indexing issues, and escalating Search Console errors.

Fixing the errors would have been endless. The real solution was to fix the URL logic itself. Once the system was corrected, the errors stopped appearing altogether.

That is the difference between treating symptoms and addressing the underlying structure.

Why most SEO work never crosses the line

Across organisations, industries, and levels of maturity, the pattern is consistent: work that cannot justify itself against competing priorities does not get delivered.

Engineering capacity, product strategy, compliance requirements, and leadership focus all compete for the same finite resources. SEO is just one of many voices in that system.

The challenge is not producing more recommendations. It is ensuring those recommendations are framed in a way that makes them viable within the organisation’s constraints.

Once you understand that, the role of SEO changes. It stops being about identifying problems and starts being about influencing decisions—what gets built, why it matters now, and what it replaces.

Because in the end, nothing gets implemented simply because it is best practice. It gets implemented because it is worth more than everything else competing for the same space.