Let me share a quick exchange from a meeting that drove me up the wall and taught me a very specific lesson:
My director of marketing: “I want to land more AI overviews, rich snippets, and voice search results.”
Me: “Okay! We need answers based on original research, schema markup, and more conversationally phrased headings.”
Our SEO contractor: “Schema markup doesn’t really matter.”
Why Schema Markup Actually Mattered Here
I explained to him that we were selling courses and SaaS. We actually HAD to implement structured data to get a chance at some of the rich snippets our director wanted to land. He said they weren’t required and didn’t guarantee us a snippet. Well, of course it didn't guarantee us one. But without the required markup, we weren't even eligible for those results in the first place.
The Strategy vs. Execution Bottleneck
And that's where things got frustrating. I could develop the content strategy, explain exactly what we needed to do and why, but I couldn't implement the technical SEO myself. That was our SEO guy's job, and he didn't think it was worth doing. What did I do next? I sent the director a message with sources directly from Google explaining why my recommendations were necessary to even try to meet some of her goals.
What I wish I'd Done
What I didn't do was follow through with a specific request for action.
I gave my director the information she needed to understand the problem, but I left the next step entirely up to her. What I should have asked was, "Are we still pursuing these rich results? If we are, who is going to implement the markup, and when?" I could have proposed a small test. Picked a few eligible course and software pages, add the appropriate structured data, validate it, and monitor the results. If our SEO contractor didn't think it was worthwhile, he could explain why. Maybe he'd have had a perfectly reasonable argument. I'd have been happy to hear it. But somebody needed to make a decision.
Instead, I was stuck in a situation where I was responsible for developing a strategy to meet goals that depended partly on work another person didn't want to do.
What Happens When Your Campaign Depends on Somebody Else?
Content marketers run into this constantly.
You can write a fantastic article, but you can't make the developer fix the technical problem preventing Google from crawling it. You can build an email campaign, but you can't make someone configure the CRM correctly. You can develop a conversion strategy, but you can't personally approve every landing page change. And yet, when the campaign results come in, somebody is going to want to know why you didn't hit your targets.
This is where I think I missed the biggest opportunity.
I should have:
documented the dependencies as carefully as I documented the strategy. Not just "We should implement schema markup," but which search appearances we were targeting, which pages needed work, who was responsible for doing it, and what we'd be unable to measure or accomplish if that work wasn't completed.
asked my director to decide whether we were going to pursue those opportunities or revise the goals.
made sure our campaign reporting distinguished between the work we actually completed and the parts of the strategy we couldn't execute.
The Lesson I'm Taking With Me
I spent too much energy trying to establish that my recommendation was correct and not enough figuring out how to get a decision made. That's an easy mistake to make when you're working with someone who technically has authority over a piece of your strategy. I don’t want to step on anyone’s toes, but I care about business goals. I cared about my director too.
Next time, I'll bring the documentation, explain the dependency, recommend a course of action, and ask for an owner and a decision.