Tag: Stakeholder Management

How I Build a Powerful SEO Budget Case My CFO Can’t Ignore
If I walk into a budget meeting armed only with rankings, traffic, and keyword reports, I know I am making the wrong case. CFOs do not approve SEO budgets because channel metrics look encouraging. They approve investments that reduce business risk, improve commercial outcomes, and justify the way capital is allocated.

As AI reshapes search economics and customer acquisition costs continue to climb, I believe translating SEO into business risk is becoming as important as the search strategy itself. This is how I prepare for that conversation before I enter the room.

Why I see SEO budget conversations break down

A global enterprise software company recently shared a revealing example with us, and I keep returning to it because it captures the problem so clearly.

One of the company’s core product lines generated 291 inbound demo requests during a single month in 2008. In the corresponding month of 2026, it generated only 274. Nearly two decades later, and despite a digital marketing budget roughly eight times larger, the business was producing fewer qualified opportunities.

I do not see that as a simple search strategy problem. I see it as a structural problem—and the CFO had already noticed it.

The head of search entered the budget review with a 24-slide deck. Slide 3 documented ranking improvements. Slide 7 highlighted year-over-year organic traffic growth. Slide 12 outlined keyword opportunities.

Every number was accurate, but none of them answered the question that mattered to the CFO: Why was the company spending more each year to generate roughly the same number of qualified opportunities?

The CFO let the presentation continue. Then, at slide 19, she put down her pen and said, “This is all interesting. But I can’t see the connection to pipeline.”

The head of search began to explain. The CFO looked toward the CMO, and the meeting was effectively over.

The lesson I take from this is that many search leaders lose the CFO budget conversation before they enter the room. Their strategies may be sound, and their numbers may hold up, but they arrive speaking in sessions, rankings, and organic traffic share. That is not the language of financial decision-making.

When I prepare for this kind of meeting, I assume the CFO wants to discuss the P&L, risk, payback periods, and opportunity cost.

If I open with “organic traffic grew 23% year over year,” I risk telling the CFO, unintentionally, that I cannot connect my work to revenue. If the CFO has already seen cost per opportunity moving in the wrong direction, that disconnect does more than create skepticism. It creates a reason to cut the budget.

The structural shift I diagnose first

I start with the diagnosis before I discuss tactics. Without a clear diagnosis, everything else becomes a more polished way to lose the same argument.

In 2008, paid search behaved like an undersupplied monopoly channel: high intent, limited competition, and relatively linear returns. A dollar invested could produce a reasonably predictable return. There was no AI layer absorbing clicks before they happened, no army of comparison aggregators siphoning away high-intent traffic, and no group of competitors with 18 years to build organic authority in the category.

That environment is gone.

Today, I operate in a search landscape where organic authority is fiercely contested. AI Overviews can intercept high-intent queries before users reach paid ads, while attribution models designed for the old environment are still being used to defend budgets in the new one.

The message I bring to a CFO is not simply, “I need more budget,” or, “Our rankings are improving.” I explain that the structural conditions that once made search efficient have changed, show how those changes affect commercial performance, and present my plan for adapting.

Why I do not lead with channel metrics

I understand the temptation to showcase channel performance. After spending months building organic authority, improving rankings, and growing traffic, I naturally want that work to be visible. The problem is that presenting it without a commercial connection can undermine the very case I am trying to make.

CFOs have been burned by marketing attribution models before. They have seen enough ranking charts and organic traffic reports to know that neither metric connects directly to the P&L without additional evidence.

When I lead with channel metrics, I invite two immediate questions: “According to which model?” and “What does this mean for revenue?” Every slide that raises those questions before I have framed the argument spends some of my credibility.

How I handle the counterfactual problem

The deeper issue is the question I expect every CFO to bring into the room: “Would this revenue have happened anyway?”

I consider that the hardest question in marketing attribution, yet many budget presentations never answer it. They treat the connection between organic performance and commercial outcomes as self-evident. It is not. A CFO who has watched the marketing budget expand for a decade while blended customer acquisition cost drifts upward is right to challenge that assumption.

If I am asked, “How do we know those customers would not have found us anyway?” and I do not have a prepared answer, I have lost the thread. That is why I do not build my budget case on an attribution model I cannot defend under pressure. I build it around something much harder to dismiss: measurable business risk.

Dig deeper: Stop paying for traffic: The enterprise CMO’s guide to ROI-driven SEO

How I frame SEO as business risk

I think of CFOs primarily as risk managers, not channel optimizers. Their job is to protect the business from downside scenarios, allocate capital efficiently, and prevent unpleasant surprises in the P&L.

If I enter the room talking only about upside—what a larger budget might achieve—I am appealing to the wrong instinct.

Instead, I lead with downside and focus on three risks that a CFO can price, model, and act on.

1. Competitive displacement risk

I never treat organic search positions as permanent assets. They are contested positions in a live market. If I reduce investment, competitors do not pause and reduce theirs to match. They usually accelerate.

I also avoid saying only, “We will lose rankings.” Rankings are still a channel metric. I frame the risk in commercial terms:
- “A 30% budget reduction will not create a simple 30% reduction in output. I expect it to trigger a compounding decline over the next three to 18 months as competitor content accumulates, our positions erode, and the cost of recovering those positions exceeds the cost of maintaining them.”
I am presenting a deferred-liability argument, not merely a channel-performance argument. It gives the CFO a risk that can be modeled. For example, I can calculate how much a 20% decline in organic share of voice would add to CAC over 12 months if paid search had to compensate for the lost visibility.

When I show that calculation, I can move the conversation from “Can we afford this investment?” to “Can we afford the cost of withdrawing it?”

2. AI visibility risk

I see AI visibility as the newest and least understood risk in many boardrooms. That gives me an opportunity if I can explain it clearly and connect it to financial outcomes.

As AI Overviews and LLM citations become a primary discovery layer for high-intent queries, I no longer think of organic authority solely in terms of rankings. I also ask whether our brand appears in the AI-generated answer.

A paid campaign can often be restarted next quarter by adding budget. AI citation share is different. It depends on content depth, structured data, brand signals, and domain authority built over months or years. I cannot rebuild that visibility with a quick media buy; I need a content and authority program measured in quarters rather than weeks.

The commercial connection is crucial. If I lose AI visibility, I do not just lose traffic. The business may have to buy back those same high-intent users through paid search, often at CPCs inflated by competitors that continued investing and preserved their citation share.

I do not treat this as a distant concern. For many organizations, declining AI visibility can be the trigger for a broader CAC blowout, so I price the risk explicitly.

The framing I use with the CFO:
- “We currently hold strong AI citation share across our 10 most important commercial queries. I do not expect that position to maintain itself. Here is what it cost us to build, what I estimate it would cost to recover if we lost it, and the quarterly investment I recommend to defend it.”
Dig deeper: The bureaucracy tax: How disruptors are winning AI search visibility

3. CAC blowout risk

I find that this risk lands hardest because it is already materializing in many enterprise organizations.

As AI reshapes search, every glowing path to discovery carries commercial value—turning SEO investment into a conversation about pipeline, risk, and customer acquisition costs.

When I return to the enterprise software example, the year-over-year picture is even more revealing than the 18-year comparison:
- April 2025: Roughly $420,000 in Google spend, 681 inbound demo requests, and approximately $617 per opportunity.
- April 2026: Roughly $310,000 in Google spend, 418 inbound demo requests, and approximately $741 per opportunity.
Spend fell by 26%, qualified opportunities fell by 39%, and cost per opportunity increased by 20% in one year. The deterioration happened not simply despite the budget reduction, but partly because of it.

I expect a CFO to test a simpler explanation: Perhaps performance was already declining and the budget was cut in response. That is a reasonable hypothesis, but it does not fully fit the data. Cost per opportunity had started rising before the reduction. The cut did not create the original efficiency problem; it exposed a structural problem that already existed.

The search environment had changed, but the budget strategy had not. AI Overviews were absorbing high-intent category and solution queries before many of those searches became clicks.

At the same time, the organic authority that took years to build was generating fewer visits as zero-click search expanded. When paid spend fell, the organic foundation was not strong enough to carry the load. Together, the two effects caused more damage than either would have caused independently.

This is how I explain the CAC blowout mechanism: When organic visibility weakens and paid media has to compensate, blended CAC rises. If paid investment is then reduced before the organic gap is repaired, CAC can rise even further.

The CFO sees a negative trend and may conclude that search no longer works. I see a different problem: The structural relationship between paid and organic was never actively managed.

I do not consider this unique to enterprise software. It is a predictable outcome when paid and organic search are managed as separate budget lines with separate accountability, as they still are in many enterprise organizations.

The framing I use with the CFO: I show the relationship between organic share of voice and blended CAC across the previous 18 to 24 months. If organic visibility declined while paid CPCs rose, I have direct evidence of the risk.

If I have completed a cannibalization audit and redirected spend away from terms where paid ads competed with strong organic coverage, I also present that work. Moving the budget toward genuine demand gaps gives me a concrete example of the structural fix in action.

Why I brief the CMO before the meeting

One of the most valuable preparation steps I can take is briefing the CMO before I enter the budget meeting. I do this not simply to seek approval, but to stress-test my argument.

The CMO has usually participated in more CFO conversations than I have. They know which objections carry the most weight, which risks currently concern the CFO, and which parts of my case are likely to receive the greatest scrutiny. I cannot gain that perspective if I build the deck in isolation.

A CMO who has already challenged and strengthened my argument becomes an ally in the room. A CMO who hears the case for the first time alongside the CFO can become a liability. If the CMO hesitates over a number or qualifies a claim I presented with confidence, the CFO will notice.

That is why I brief the CMO and enter the meeting aligned. In my experience, much of the budget conversation is won or lost before anyone sits down.

How I prepare for three inevitable questions

Before I prepare the answers, I plan my opening move.

I do not spend the first 60 seconds summarizing last quarter’s performance, and I do not jump into risk without establishing common ground. Instead, I begin with the structural diagnosis.

I might say:
- “Before I walk through the data, I want to explain why we are having this conversation. The search environment has changed materially over the past three years. I want to show how that change is affecting our cost per opportunity and what I recommend we do about it.”
From there, I present the evidence, explain the risks, and prepare for the questions. These questions are not hypothetical. Search leaders hear them repeatedly, so I want my answers ready before I enter the room.

“What happens if we cut this by 30%?”

I do not respond by declaring the cut unacceptable or catastrophic. A CFO asking this question may be testing how well I understand the program’s efficiency curve rather than announcing an actual reduction. If I become defensive, I signal that I have not modeled the scenario.

I prepare a specific answer in advance:
- “A 30% reduction applied evenly across the program would cost us approximately [X] in organic traffic within six months. At our current organic conversion rate, that represents [Y] in pipeline impact. If we need to remove 30%, I would make these specific cuts to minimize commercial damage. This is the threshold below which I believe the program becomes structurally unsustainable and the cost of recovery exceeds the savings.”
With that answer, I demonstrate P&L literacy, anticipate the follow-up questions, and shift the meeting from budget defense to business problem-solving. I am not protecting a line item; I am helping the CFO make a better capital allocation decision.

“How do we know these conversions would not have happened anyway?”

I do not try to defend an attribution model as if it were indisputable. I am unlikely to win that argument, and fighting it can damage the credibility of everything else I have presented.

Instead, I acknowledge the attribution problem and pivot to incrementality:
- “I agree that last-click attribution overstates organic search’s contribution, so I do not use it as my primary evidence. Instead, I track periods when organic visibility declined across our most important commercial queries and paid CAC increased as paid search compensated. I consider that our most defensible proxy for organic search’s incremental contribution, and I have deliberately kept the estimate conservative.”
I find that intellectual honesty about attribution limitations builds credibility with a financially trained audience. CFOs have seen too many models that appear designed to prove whatever the presenter wants to prove.

By acknowledging the limitation first and offering a conservative proxy, I can earn more trust than I would by making an aggressive ROI claim.

“What is the payback period?”

I avoid answering with a broad argument about long-term brand equity or compounding authority. CFOs working within quarterly reporting cycles are unlikely to approve capital based only on a three-year organic growth narrative. If I lead with that answer, I suggest that I do not understand how the allocation decision is being made.

I separate the investment into two components with different payback profiles.

Maintenance spend covers the work required to preserve existing positions, keep content current, and maintain technical health. I frame its payback as immediate because it protects value the business has already created. The relevant comparison is the future cost of recovering the positions if they are lost.

Growth spend covers new content, category expansion, and authority building. For content aimed at existing demand with known search volume, I model the payback across six to 12 months. I make the assumptions visible, including query volume, conversion rate, and revenue per conversion.

I show my work. If the CFO stress-tests my assumptions and challenges specific numbers, I consider that constructive engagement with the model. It is a better outcome than polite agreement followed by a budget cut because my methodology failed to inspire confidence.

The data I leave behind—and the data I bring

Before I build the deck, I decide what to remove. Most search budget presentations do not fail because they lack useful data. They fail because the valuable evidence is buried beneath metrics that erode credibility before the important numbers appear.

What I leave behind
- Keyword rankings in isolation: Unless I can connect a specific ranking movement to pipeline impact, I treat it as another channel metric that invites the counterfactual question.
- Organic sessions without market context: If my traffic grew by 15% while the market grew by 40%, I lost ground. Without an external benchmark, year-over-year traffic growth gives the CFO little basis for evaluation.
- Metrics that require a glossary: If I have to explain what a metric means before I can explain why it matters, I leave it out of the meeting. Every definition delays the commercial argument.
- Long-term brand equity arguments: I do not reject these arguments, but I recognize that they are difficult to act on within a quarterly budget cycle. Leading with them creates a mismatch between my timeline and the CFO’s.
What I bring

Before I finish the deck, I decide what deserves the most important slide. I do not choose a generic traffic graph or ranking summary. I begin with a commercially meaningful statement such as:
- “I estimate that organic search offset $[X] in paid-search dependency this quarter.”
I lead with the money the program saved the business, expressed in language the CFO already uses. The supporting evidence follows:
- Blended CAC across the previous 18 to 24 months, segmented by channel. I use this chart to expose the relationship between paid and organic performance and connect search investment to the P&L.
- Organic share of voice compared with the three leading competitors over time. I use this to make competitive displacement measurable. If a competitor gained ground while our investment remained flat, I show it.
- Pipeline contribution by channel under a conservative, clearly labeled attribution model. I state whether the model is last-touch, position-based, or something else. I find that transparent disclosure builds more credibility than an optimistic number that invites a methodological dispute.
- A pre-modeled 30% reduction scenario with specific commercial consequences. I consider this the most powerful analysis I can bring because it answers the likely budget question before it is asked.
- AI Overview citation share across the 10 most important commercial queries. I use our own data to ground the AI visibility argument. It demonstrates that I understand the changing discovery landscape without relying on vague industry generalizations.
How I turn the meeting into a capital allocation conversation

I do not consider the enterprise software company in this example an outlier. I see the same pattern across enterprise search: budgets rise, efficiency declines, and CFO skepticism grows as AI Overviews absorb intent, paid and organic remain disconnected, and reporting continues to reward channel metrics instead of commercial outcomes.

I have learned that winning this conversation does not depend only on having the best search strategy. It depends on translating SEO into business risk in language a CFO can evaluate and act on.

Before I enter the room, I brief the CMO, model the commercial effect of a budget cut, prepare a conservative answer to the attribution question, and separate maintenance investment from growth investment. That preparation is within my control, even though the structural shift in search—and the CFO’s skepticism—are not.

Ultimately, I choose which conversation I am ready to have. I can defend a collection of channel metrics, or I can help the CFO make a capital allocation decision. Only one of those approaches gives my SEO budget a compelling business case.

Inspired by this post on Search Engine Land.
July 10, 2026
Use Google Documentation to Win SEO Buy-In With Proof
Let me be blunt: SEO advice can sound completely made up to people who do not live in search every day.

When I say things like “change this canonical,” “don’t block that resource,” or “we need this content exposed in the rendered HTML,” I understand why someone outside SEO might hear it and wonder whether I am inventing rules on the spot.

That is one reason SEO still gets treated like black magic inside many organizations.

I have been pushing the idea of “un-nerding SEO” for years, but this is about something very practical: I use Google’s own documentation to earn approval, build trust, and help SEO work get prioritized.

Not because Google tells us everything. Not because every sentence in its documentation should be treated as gospel. I use it because documented evidence is much harder to dismiss than personal opinion.

When I need buy-in, the strongest argument is rarely “trust me.”

It is usually something closer to: “Google has already documented how this should be approached.”

The buy-in problem is usually not the recommendation itself

In my experience, most SEO recommendations do not die because they are wrong. They die because they are competing with everything else happening inside the business.

Dev sprints, product timelines, CMS limitations, legal concerns, brand standards, executive assumptions, and the classic “we’ve always done it this way” all have a seat at the table. SEO is rarely the only priority in the room, even when the recommendation is technically correct.

That is why I do not rely on “best practice says” or “from an SEO perspective” when I am trying to move work forward. Those phrases sound optional, especially to teams already balancing risk, deadlines, and competing requests.

But “Google has official documentation that supports this recommendation” lands differently.

It may not automatically win the argument, and it definitely does not mean the work will be prioritized tomorrow. But it changes the conversation from “the SEO person said so” to “we have official Google documentation explaining why this matters.”

Google documentation is not gospel

I know the objection already: “Are we really pretending Google tells us the full truth about how search works?”

Absolutely not.

Google’s documentation is not the complete truth of search. It has omissions. It simplifies complex systems. Sometimes it explains how Google wants site owners to behave, not every technical factor that influences organic visibility.

Google also writes for a broad audience, which means nuance gets smoothed out, edge cases get skipped, and the answer can be technically true without being the entire story.

So no, I am not treating every Google statement as if it were carved into stone and carried down from Mountain View.

But that does not make the documentation useless.

It makes it a starting point. A receipt. An official reference point.

It moves the discussion away from “I think this matters” and toward “Google has explicitly documented why this matters.” That distinction matters when I am asking someone else to approve and prioritize the work.

Documentation is especially useful with developers

This is where Google documentation often earns its keep the fastest. SEOs need developers, and I have learned that the quickest way to lose developer support is to treat every recommendation like a command instead of a requirement that needs to be implemented thoughtfully.

And yes, just in case it ever works, I still wish I could run this:

google.exe /disable-ai-overviews /please

Bummer. No dice.

Developers are not wrong just because they disagree with an SEO recommendation. Most of the time, they are optimizing for completely valid priorities: performance, code quality, technical debt, security, and avoiding the kind of production mistake that can take a whole site down.

But sometimes developers are wrong about how Google discovers, crawls, renders, indexes, or interprets content.

And telling a developer “you’re wrong” is a great way to make sure my ticket never sees the light of day.

This is where documentation helps. It removes some of the subjectivity and shifts the discussion toward how to implement the requirement inside the existing technical environment.
The point is never “SEO wins and dev loses.”

The point is that I now have an external source of truth to discuss. That is a much better conversation than two teams arguing from preference.

Documentation is also a client management tool

For client-facing SEO work, documentation helps me separate serious recommendations from “trust me, bro, I have a contact at Google” consulting.

Rows of illuminated data cabinets and paper files stretch into the distance, capturing the pressure on marketers to turn fragmented customer data into a smarter performance engine.

That matters even more when a client has been burned by bad SEO advice before.

Instead of saying, “We need to change this because it’s better for SEO,” I can frame the recommendation with evidence.

“Here’s what Google documents. Here’s where your current setup conflicts with that. Here’s the risk. Here’s the recommendation. Here is the estimated reward.”

That framing builds trust because it shows the recommendation is not relying on blind faith.

It also makes the SEO look less like a magician and more like an interpreter.

That is how I see the real role of SEO: translating Google’s documented needs into business and technical decisions that a team can actually act on.

Less black magic, more receipts

SEO has a reputation problem, and some of it is earned.

Too much SEO work is still explained with vague phrases and shaky confidence. I hear people say things like “Google likes this” or “this needs to exist for the bots” when the stronger version is: “Google documents this behavior here, and here is how it applies to our situation.”

That does not mean documentation alone creates buy-in.

Dropping a Google link into a ticket or Slack thread is not a strategy. I still have to translate what it means, explain the risk, connect it to business outcomes, and help the team understand why the recommendation deserves attention.

Google documentation will never replace experience, testing, or judgment. It will not tell me everything, and I should not treat it like the final answer to every SEO debate.

But it can make SEO easier to defend, easier to prioritize, and much harder for leaders to dismiss.

The best SEOs are not just the ones who know what to recommend. They are the ones who can prove why the recommendation deserves to be taken seriously.

Less black magic. More receipts. More results.

Google documentation may not be the whole truth, but I would rather show up to a buy-in conversation with official references than with “my buddy from Google told me.” Suuuure they did.

This post first appeared on the author’s website and is republished here with permission.

Inspired by this post on Search Engine Land.
July 9, 2026
How I Safely Roll Out High-Impact Technical SEO Changes

When I work on technical SEO, I know the right changes can dramatically improve how search engines crawl, understand, and evaluate a website.

I also know that the recommendations with the biggest upside usually carry the biggest implementation risk. URL changes, canonical updates, robots.txt edits, internal linking improvements, and site migrations can all strengthen organic performance, but one mistake can damage crawling, indexing, and search visibility.

That is why I do not treat technical SEO as a simple list of fixes. I treat it as a process: evaluate the impact, weigh the effort and risk, align the right teams, and test everything before and after launch.

From audit to implementation to prioritization

For me, the work is not finished when the SEO audit is delivered.

Prioritization is where the real judgment begins. I look at how severe the issue is, what outcome I expect, how many pages are affected, how much development effort is required, and what could go wrong if the change is implemented poorly.

The recommendations with the greatest potential impact often need buy-in from developers, content teams, product owners, and stakeholders because they require more resources and carry more risk. A clear recommendation, a practical test plan, and early alignment make implementation much easier to move forward.

Understanding the issue and potential outcome

I do not assume every technical SEO issue found in an audit needs immediate action. Before I prioritize a recommendation, I validate it manually and consider the broader context of the site, including priority sections, platform limitations, and business goals.

For example, missing meta descriptions on low-priority pages or title tags that fall outside recommended lengths may appear in an audit because they are easy for tools to measure, not because they will meaningfully affect performance.

Crawling tools and automated reports are valuable because they help me find issues at scale. But they do not always tell me whether an issue matters to the business.

A warning may point to a real problem, an intentional setup, a platform constraint, or something with little to no measurable impact. I need that context before I decide what deserves attention.

Evaluating impact, risk, and effort

Once I validate an issue, I decide how to address it and whether it is worth recommending for implementation.

When I am prioritizing technical SEO recommendations for a development queue, I consider the number of affected pages, the expected outcome, the resources required, and the potential risks.

Updating a few title tags may be low risk. Changing URL structures or modifying robots.txt directives can affect thousands of pages and influence crawling, indexing, and discoverability.

By understanding both the upside and the downside, I can make better decisions, allocate resources more responsibly, and plan changes in a way that reduces risk while still pursuing meaningful gains.

High-impact technical changes that require extra caution

The following technical SEO initiatives can meaningfully affect site performance. I do not avoid them because they are risky. I approach them carefully because their implications, benefits, and failure points need to be understood before implementation.

1. URL updates and changes

I often recommend URL updates when a site needs a clearer folder structure, content consolidation, rebrand support, or stronger information architecture.

For example, a business may move service pages from the root domain into a subfolder so the content is easier to organize and the site is easier to navigate.

URL changes can provide real benefits, but I need to make sure those benefits outweigh the risks and that a proper redirect strategy is ready before anything goes live.

Search engines treat a changed URL as a new URL, so redirects are essential for preserving rankings, traffic, backlinks, and other signals tied to the original page. Missing redirects, bad mappings, redirect chains, outdated internal links, and stale XML sitemaps can all hurt crawling, indexing, and discoverability.

Before I move forward with URL changes, I create a redirect mapping plan. Ideally, I validate and test redirects in a development environment before launch, then check them again after launch and update the XML sitemap.

I also include internal link updates and performance monitoring in the launch plan. Careful planning helps preserve existing SEO equity while supporting the larger goals of the site.

2. Canonical updates

Canonical tags help search engines understand which version of a page should be treated as the preferred version when duplicate or similar content exists. I use them to consolidate ranking signals, avoid internal competition, improve crawl efficiency, and clarify which URLs should be prioritized for indexing.

For example, an ecommerce site may use canonical tags to consolidate parameter-based URLs or faceted navigation pages to a primary product or category page. But if a canonical tag is applied to the wrong template, it could unintentionally tell search engines to consolidate an entire group of important pages elsewhere.

Canonical updates may look simple, but mistakes can be difficult to spot once they are deployed across a site. I take time to review canonical targets and validate the implementation so I do not send conflicting signals that cause important pages to lose visibility or fall out of the index.

3. Robots.txt file changes

The robots.txt file controls how search engines and other crawlers access content on a website. I usually recommend robots.txt changes to improve crawl efficiency, prevent low-value content from being crawled, or limit access to specific site sections.

For example, I may recommend blocking filtered URLs, internal search results, or other pages that consume unnecessary crawl resources. When implemented correctly, these updates help focus crawl activity on more important content.

The risk comes from rules that are too broad, misplaced, or copied from the wrong environment. A single directive can block important sections of a site from being crawled. Accidentally deploying a staging robots.txt file to production can also disrupt how crawlers access live content.

Because robots.txt changes can affect large parts of a site, I test rules carefully, review the proposed changes against the intended URL patterns, and verify the implementation after launch. Even a small robots.txt edit can have sitewide consequences.

4. Internal linking changes

Internal linking helps search engines discover content, supports priority pages, connects related topics, and guides users through a website. My recommendations may include updating navigation, adding contextual links, consolidating content hubs, or improving pathways to key pages.

As websites evolve, internal linking often needs cleanup. Removing important links, creating orphaned pages, linking to staging environments, or accidentally pointing users and crawlers to non-public URLs can all hurt discovery. Large navigation updates can also change how easily search engines reach important content.

That is why I always look closely at scope. A navigation update may touch thousands of pages, making it far riskier than adding a few contextual links to a small group of priority pages.

5. Site migrations

At some point, every SEO team deals with a site migration. It may happen because of a rebrand, a domain change, a redesign, or a move to a new CMS. When planned well, migrations can improve user experience, support long-term SEO performance, and benefit the business.

They are also inherently risky because they often combine several technical SEO changes at once. Redirects, URL restructures, canonical tags, indexing directives, content updates, and internal linking changes may all happen during the same launch. With that many moving parts, even a small oversight can affect crawling, indexing, and visibility.

Even a well-planned migration can run into problems if changes are not documented, tested, reviewed, and validated throughout the process. I rely on pre-launch QA, post-launch testing, and ongoing monitoring to catch issues before they have a lasting effect on performance.

Working across teams to ensure success

Technical SEO updates often require multiple teams to work together. I may need input from content teams, in-house developers, external agencies, product managers, and analytics teams before a change is ready to launch.

Clear communication is essential. I make recommendations straightforward, build testing and QA into the process, and define success criteria before launch. I also want a plan for quickly identifying and resolving issues if something goes wrong.

Communicating recommendations effectively

Whether I am discussing a recommendation directly with developers or documenting it in a structured ticket, I make sure the issue is clearly defined, examples are included, and the required changes are easy to understand.

Clear documentation helps me set expectations, explain scope, identify affected URLs, and define the expected outcome. It also gives teams a place to ask questions, raise concerns, and flag limitations before implementation begins.

Testing in development environments

Whenever a site change is made, I want it tested thoroughly before launch. A development environment gives me a place to validate the implementation, ask questions, and provide feedback while there is still time to adjust the work.

Post-launch testing and monitoring

Sometimes a change that works perfectly in development behaves differently after launch.

That is why I am ready to validate the implementation as soon as changes go live. Post-launch checks help me identify issues quickly, begin troubleshooting immediately, and monitor the impact before small problems become larger ones.

Balancing opportunity and risk

Most technical SEO recommendations are designed to improve crawling, indexing, or site architecture. When I implement them correctly, they can significantly improve how search engines access, understand, and evaluate a website.

But implementation usually depends on multiple teams working toward the same goal. As a recommendation moves from audit to production, misunderstandings, assumptions, and overlooked details can create unintended consequences.

That is why I see technical SEO as more than finding opportunities. I need to understand the issue, evaluate the potential impact, weigh the development effort, and manage the risk of implementation.

No technical SEO change is completely risk-free. But with thoughtful planning, clear communication, thorough testing, and ongoing monitoring, I can catch issues earlier, reduce their impact, and roll out high-impact changes with the caution they deserve.

Inspired by this post on Search Engine Land.

July 3, 2026
Strengthen Stakeholder Support for Technical SEO Success

As someone deeply involved in technical SEO, I’ve realized that our projects thrive when I effectively communicate their value to both executives and developers.

What sets a great SEO professional apart from the rest is their knack for managing stakeholders. This skill is crucial in technical SEO, where projects often involve numerous teams, making it challenging to convey the importance of our work.

At the core of stakeholder management is the perceived value of our work. In technical SEO, this can be especially tricky. People outside the SEO realm might not immediately grasp the significance of optimizing a site’s internal linking or implementing schema markup.

The most successful technical SEO projects aren’t merely seen as SEO enhancements; they are viewed as vital to business outcomes like revenue growth, better conversion rates, and operational efficiency. By strengthening this connection, I find it easier to gain stakeholder support and showcase long-term value.

Why Aligning Technical SEO Work with Business Impact Is Essential

For most executives and development teams, technical SEO isn’t at the forefront. That’s why I ensure our technical SEO recommendations are directly linked to measurable business goals.

Take, for instance, a scenario where a company modifies its website’s CMS. The SEO implications of such a change are often overlooked on a project manager’s long list of priorities. It’s not until I clearly demonstrate the risks and their potential impact that SEO is properly emphasized.

Technical SEO initiatives can be inherently complex. They require a strong grasp of the company’s systems and teams, coupled with excellent communication and management skills.

Even though I might see this work as pivotal to the site’s SEO health, others might not appreciate its value if I’m talking in terms of crawl budget or index management. Drawing parallels to core business goals helps make our work more comprehensible and valuable.

Aligning technical SEO initiatives with business performance and goals is the best way for me to secure buy-in and highlight their impact.

Business Outcomes That Drive SEO Buy-In

Understanding the metrics and business goals is crucial for demonstrating how technical SEO can impact performance. Most organizations set corporate goals like expanding reach, boosting revenue, or entering new markets.

Revenue

For many businesses, whether a charity or a multinational, the bottom line is revenue. Connecting technical SEO efforts to revenue growth is a surefire way for me to secure support and illustrate its value.

Conversion

I can also show the value of technical SEO by linking it to conversion optimization. Studies indicate that a one-second delay in page load speeds can slash conversions by up to 7%.

Looking at core web vitals scores is important, but framing it as potential conversion loss grabs more attention from stakeholders.

Cost Reduction

I often notice that the potential for cost reduction is overlooked in SEO. Website visits incur hosting, infrastructure, and security costs that add up quickly with large sites.

Highlighting how technical SEO can reduce unnecessary expenses is key.

Dig deeper: How to prioritize technical SEO fixes by business impact

How to Strengthen Buy-In for Technical SEO Work

These four strategies help stakeholders better understand, support, and prioritize technical SEO projects.

1. Determine the Value of the Work

I never assume an SEO activity is worthwhile just because it’s a “best practice.” Every task I undertake ties directly to a business benefit and a core KPI.

Even if the immediate result is not new revenue, the activity should support revenue growth, conversion enhancements, or cost efficiency.

When I review and optimize internal site structures, I aim for improved rankings and increased organic traffic, translating to more conversions and revenue.

2. Identify How the Work Will Impact Company Goals

Once I understand the value of my technical SEO tasks, I align them with broader company or project goals to gain stakeholder approval.

For instance, if my goal is increased profitability in a certain region, and the task involves optimizing hreflang tags, I focus on how this supports the company’s goals, rather than technical specifics.

3. Communicate Effectively

Communicating SEO work’s impact is challenging, but breaking it down into ‘who, what, where, why, when, and how’ makes it understandable for stakeholders at all levels.

My goal is to make even the most technical aspects digestible by linking tasks back to business metrics everyone understands and values.

4. Prove the Impact Over Time

By consistently showing the positive results of technical SEO, I align our efforts with business objectives and make future conversations with stakeholders simpler.

After completing a project, I regularly review the outcomes to understand the impact, allowing for better future planning and adjustments.

Business Impact Matters More Than Technical Best Practices

Assumptions of what might enhance performance can sometimes miss the mark. Without revisiting previous implementations, I might not know what actually worked.

Just because something is hailed as “best practice” doesn’t confirm it will fit my site. Continually evaluating technical SEO outcomes helps reaffirm their business value.

Dig deeper: Advanced technical SEO tips: 14 technical SEO issues you’re missing

Inspired by this post on Search Engine Land.

May 18, 2026
Lessons Learned from a Costly PPC Decision

Amy Hebdon shares lessons from early mistakes in her career, emphasizing the importance of managing relationships alongside campaigns.

I recently had the opportunity to interview Amy Hebdon, an international expert in paid search and the founder of Paid Search Magic, on episode 337 of PPC Live The Podcast. We talked about real-life experiences behind paid media initiatives, focusing on the challenges and insights rather than just techniques. Amy’s vast industry experience makes her perspectives invaluable for anyone steering through complex digital marketing campaigns.

Early career mistakes and learning experiences

Amy recounted an eye-opening experience from her early career while managing a fitness client’s creative assets that didn’t align with Google Ads guidelines. Despite her efforts to safeguard the account, her tactless approach during a high-stakes meeting with leadership caused friction with the creative team. Reflecting on it, Amy realized that while her decisions were valid, better communication could have preserved vital working relationships for future collaboration.

Accountability and oversight in campaign management

I also learned about another incident early in Amy’s career, where she took sole charge of a low-touch account that went inactive due to an expired insertion order. This experience underscored the importance of personal accountability, regular check-ins, and structured processes—even when managing less significant campaigns. Amy pointed out that both her oversight and the client’s lack of internal checks contributed to this oversight.

Stakeholder management and communication

Amy often emphasizes the critical nature of understanding stakeholders’ perspectives and nurturing relationships diligently. She reflects on how decisions that might seem tactical can have relational impacts, highlighting the need for empathy, strategic communication, and objectivity in managing conflicts or escalations.

Lessons on team support and leadership

Another key lesson from Amy is the value of a supportive team and managers who prioritize shared objectives over placing blame. Effective leadership, she believes, involves fostering collaboration, redistributing workload when necessary, and cultivating an environment where mistakes can be openly addressed without fear. For managers, promoting accountability and transparency within teams bolsters both performance and professional growth.

Strategic focus over tactics

Amy stresses that achieving success in paid media demands a strategic approach over purely tactical execution. Merely focusing on bid settings or platform features often overlooks the broader goal of conversion optimization and audience alignment. Amy warns that even technically perfect campaigns can falter if they aren’t aligned with overall business objectives, urging a strategic evaluation over rushing the tactical details.

Navigating AI and automation in PPC

With AI gaining importance in digital marketing, Amy highlights the risks of over-relying on automated outputs. Although AI may produce results that seem right, they often lack accuracy. Marketers need a robust foundational knowledge to critically assess these results. Strategy, judgment, and expertise are crucial in differentiating meaningful insights from the noise generated by automation.

Reflections and career philosophy

In conclusion, Amy reflects on how inevitable mistakes are a valuable part of any career in PPC. With time, marketers can understand these errors in context, learn from them, and avoid letting them define their careers. She describes her career as “practical magic,” blending technical precision with strategic insights to achieve results, knowing that true success comes from both patience and meticulous planning.

Inspired by this post on Search Engine Land.

January 16, 2026