AI Gives You The Vocabulary. It Doesn’t Give You The Expertise via @sejournal, @DuaneForrester

Hiring managers are watching something uncomfortable happen in interview rooms right now. Candidates arrive with the right credentials, the right vocabulary, the right tool stack on their résumés, and then someone asks them to reason through a problem out loud, and the room goes quiet in the wrong way. Not in the thoughtful kind of way, but the empty kind that tells you the person across the table has never actually had to think through a hard problem on their own. And research is converging on the same conclusion. Microsoft, the Swiss Business School, and TestGorilla have all documented the same pattern independently: Heavy AI reliance correlates directly with declining critical thinking, and the effect is strongest in younger, less experienced practitioners.

This isn’t a technology story so much as a cognition story, and the SEO industry is living a version of it in slow motion. What none of those studies name is the specific mechanism: the three-layer architecture of expertise where AI commands the retrieval layer completely, and the judgment layers underneath it are more exposed than they’ve ever been. That architecture is what this piece is about.

The Debate Is Framed On The Wrong Axis

Every conversation about AI and critical thinking eventually lands in the same place: humans versus machines, organic thinking versus generated output, authentic expertise versus artificial fluency. It’s a compelling frame and also the wrong one.

The real fracture line isn’t human versus AI. It’s retrieval versus judgment, and those are not the same cognitive act, even though AI has made them feel interchangeable in ways that should concern anyone serious about their craft.

Retrieval is access. It’s the ability to surface relevant information, synthesize patterns across a body of knowledge, and produce fluent output that maps to the shape of expertise. Large language models are extraordinary at this, genuinely and structurally superior to any individual human at the retrieval layer, and getting better at speed. Fighting that reality is not a strategy.

Judgment, however, is different. Judgment is knowing which question is actually the right question given this specific context, the ability to recognize when something that looks correct is wrong for this situation in ways that aren’t in any training data, the accumulated weight of having been wrong in consequential situations, learning why, and recalibrating. You cannot retrieve your way to judgment. You build it through deliberate practice under real conditions, over time, with skin in the game that a model structurally cannot have.

The problem isn’t that AI handles retrieval well. The problem is that retrieval output now sounds so much like judgment output that the gap between them has become nearly invisible, especially to people who haven’t yet built enough judgment to know the difference.

The Judgment Stack

Think about expertise as a stack, not a spectrum.

Layer 1 is retrieval – synthesis, pattern vocabulary, volume processing, surface recognition. This is AI territory, and handing work in this area over to an AI is not weakness but correct resource allocation. The practitioner who uses an LLM to compress a competitive analysis that would have taken three hours into 40 minutes isn’t cutting corners; they’re buying back time to do the work that actually compounds.

Layer 2 is the interface layer – hypothesis formation, question quality, contextual filtering, knowing which output to trust and which to interrogate. This is where the leverage actually lives, and it’s fundamentally human-plus-AI territory. Your prompt quality is a direct proxy for your judgment quality. Two practitioners can feed the same LLM the same general problem and get outputs that are miles apart in usefulness, because one of them knows what a good answer looks like before they ask the question, and that foreknowledge doesn’t come from the model but from Layer 3 working backward.

Layer 3 is consequence and context – the ability to recognize when a pattern that has always worked is about to break, to assess novel situations that don’t map cleanly to anything in the training data, to hold strategic framing steady under pressure when the data is ambiguous. This is human territory, not because AI couldn’t theoretically develop something like it, but because it requires something a deployed model structurally cannot have: skin in the game, real consequence, the accumulated scar tissue of being wrong when it mattered and having to carry that forward.

The critical thinking crisis everyone is diagnosing right now is not, at its root, an AI problem but a Layer 2 collapse. People skip directly from Layer 1 retrieval to Layer 3 claims, bypassing the judgment infrastructure entirely. Layer 1 output is fluent, confident, and often correct enough to pass casual scrutiny, which keeps the gap invisible right up until someone asks a follow-up the model didn’t anticipate, and the person has no independent footing to stand on.

What SEO Is Actually Revealing

SEO is a useful diagnostic here because the industry has always been an early signal for how the broader marketing world processes technological disruption. We were the first to chase algorithmic shortcuts at scale. We were the first to industrialize content in ways that traded quality for volume. And right now we are watching two distinct practitioner populations diverge in real time, with the gap between them widening faster than most people have noticed.

The first population is using LLMs as answer machines: feed the problem in, take the output out, ship it. Ask the model what’s wrong with a site’s rankings. Ask it to write the content strategy. Ask it to explain why traffic dropped. This isn’t entirely without value, since Layer 1 retrieval has genuine utility even here, but the practitioners operating purely at this layer are making a trade they may not fully understand yet. They are outsourcing the only part of the job that compounds in value over time. Every hard problem they hand off to a model without first attempting to reason through it themselves is a training repetition they didn’t take, a weight they didn’t lift, and those repetitions are how Layer 3 gets built. You want the muscle? You have to do the work.

The second population is using LLMs as reasoning partners. They come to the model with a hypothesis already formed, a question already sharpened by their own thinking, and they use the output to pressure-test their reasoning, surface considerations they may have missed, and accelerate the parts of the work that don’t require their hard-won judgment, which frees them to apply that judgment more deliberately where it matters. These practitioners are getting faster and better simultaneously, because the model is amplifying something that already exists.

The difference between these two groups has nothing to do with tool access, since they are using the same tools, and everything to do with what each practitioner brings to the model before they open it.

The Leveling Lie

The argument for AI as a leveling tool is not wrong; it’s just incomplete, and that incompleteness is where the damage happens.

A junior practitioner today has access to a compression of the field’s knowledge that would have been unimaginable five years ago. Ask an LLM about crawl budget allocation, entity relationships, structured data implementation, or the mechanics of how retrieval-augmented systems weight freshness signals, and you will get a coherent, usually accurate answer in seconds. That is a genuine democratization of Layer 1, and dismissing it as illusory is its own form of gatekeeping.

But Layer 1 access is not expertise. It is the vocabulary of expertise, and there is a specific kind of danger in having the vocabulary before you have the understanding, because fluency masks the gap. You can discuss the concepts. You can deploy the terminology correctly. You can produce output that looks like the work of someone with deep experience, and you can do all of that while having no independent capacity to evaluate whether what you just produced is actually right for the situation in front of you.

This is not a character flaw but a metacognitive failure, the condition of not knowing what you don’t yet know. The junior practitioner using an LLM to accelerate their access to field knowledge isn’t being lazy. In many cases, they are working hard and genuinely trying to develop. The problem is that Layer 1 fluency generates a confidence signal that isn’t calibrated to actual capability. The model doesn’t tell you when you’ve hit the edge of what it knows. It doesn’t flag the situations where the standard answer breaks down. It doesn’t know what it doesn’t know either, and neither do you yet, and that combination is where well-intentioned work quietly goes wrong.

The leveling effect is real, but the ceiling on it is lower than most people assume. What gets leveled is access to the knowledge layer. What doesn’t get leveled (what cannot be compressed or transferred through any tool) is the judgment architecture that determines what you do with that knowledge when the situation doesn’t follow the pattern.

The practitioners who understand this distinction will use AI to accelerate their development. The ones who don’t will use it to feel further along than they are, right up until the moment a genuinely novel problem requires something they haven’t built yet.

Where The Abdication Actually Happens

Let’s be precise about this, because the accusation of abdication usually gets thrown around in ways that are more emotional than useful.

Using AI at Layer 1 is not abdication. Letting a model handle competitive analysis synthesis, first-draft content frameworks, technical audit pattern recognition, or structured data generation is correct delegation, since these are retrievable tasks and doing them manually when a better tool exists isn’t intellectual virtue but inefficiency pretending to be rigor.

Abdication happens at a specific and different point. It happens when you stop taking the problems that would have built your Layer 3 judgment and start routing them directly to a model instead: not because the model’s output isn’t useful, but because the attempt itself was the point. The struggle to formulate an answer to a hard problem, even an incomplete or wrong answer, is the mechanism by which judgment gets built. Hand that struggle off consistently, and you are not saving time but spending something you may not realize you’re spending until it’s gone.

This is the part of the conversation that doesn’t get said clearly enough: The low-consequence training repetitions are how you prepare for the high-consequence moments. A practitioner who has reasoned through hundreds of traffic anomalies, content decay patterns, and crawl architecture decisions (even inefficiently, even wrongly at first) has built something that cannot be replicated by having asked an LLM to reason through those same problems on their behalf, because the model’s reasoning is not your reasoning, just as watching someone else lift the weight does not build your muscle.

The senior practitioners who feel their position eroding right now are often misdiagnosing the threat. The threat isn’t that AI makes their knowledge less valuable, since genuine Layer 3 judgment is actually more valuable in an AI-saturated environment, not less, precisely because it becomes rarer as more people mistake Layer 1 fluency for the whole stack. The real threat is that the market hasn’t developed clean signals yet for distinguishing Layer 3 capability from Layer 1 fluency dressed up convincingly. It’s a signal problem that is temporary and will resolve itself in the most public and consequential ways possible – in front of clients, in front of leadership, in front of the situations where someone needs to make a call the model can’t make.

The answer for experienced practitioners is not to resist AI but to use it in ways that continue building Layer 3 rather than substituting for it. Use the model to go faster on Layer 1, and use the time that buys you to take on harder problems at Layer 2 and 3 than you could have reached before. The ceiling on your development just got higher, and whether you use that is a choice.

The answer for junior practitioners is harder but more important: Understand that the shortcut doesn’t shorten the path but changes the surface underfoot. You can move across the terrain faster with better tools, but the terrain still has to be crossed, and there is no prompt that builds the judgment architecture for you. Only doing the work, being wrong in situations that matter, and carrying that forward builds that.

The Prerequisite

Critical thinking is not the alternative to AI use. Instead, it is the prerequisite for AI use that compounds.

Without it, you are operating entirely at Layer 1, fluent and fast and increasingly indistinguishable from everyone else who has access to the same tools you do, and everyone has access to the same tools you do. The tools are not the differentiator and never were, serving instead as a floor, and that floor is rising under everyone’s feet simultaneously.

What compounds is judgment. The accumulated capacity to ask better questions than the person next to you, to recognize the moment when the standard pattern breaks, to hold a strategic position steady when the data is ambiguous and the pressure is real. That capacity doesn’t live in the model but in the practitioner, built over time through deliberate practice under real conditions, and it is the only thing in The Judgment Stack that gets more valuable as the tools get better.

The interview rooms where qualified candidates go quiet when asked to reason out loud are not showing us a technology problem. They are showing us what happens when a generation of practitioners optimizes for Layer 1 output without building the infrastructure underneath it, accumulating the vocabulary without the architecture, and the fluency without the foundation.

The practitioners who will matter in three years are building that foundation right now, using every tool available to go faster at Layer 1 and using the time that buys them to go deeper at Layer 3 than was previously possible. They are not choosing between AI and thinking but using AI to think harder than they could before, and that is not a leveling effect but a compounding one … and compounding, as anyone who has spent serious time in this industry understands, is an advantage worth building.

More Resources:

This post was originally published on Duane Forrester Decodes.

Featured Image: Summit Art Creations/Shutterstock; Paulo Bobita/Search Engine Journal

Earn AI Citations: What Your Content Needs To Look Like [A 4-Article Playbook] via @sejournal, @AirOpsHQ

TL;DR

The best companies aren’t panicking. Carta, Ramp, and Webflow are proving that visibility in AI search comes from connected systems where originality, speed, and credibility compound.

• Search is now an answer engine. Visibility depends on being cited, not ranked.
• Freshness fuels authority. 70% of AI-cited pages were updated within the past year.
• Originality wins. LLMs reward information gain—new data, unique insights, and first-party context.
• Humans set the standard. The best teams automate structure, not voice or judgment.
• Authority lives off-site. 85% of brand mentions in AI search come from third-party sources, not your own.
• Speed compounds trust. Teams that refresh content 3× faster dominate both Google and AI visibility.

‍

The way people get information has changed more in the past year than in the previous twenty.

Search is no longer a list of links. Instead of typing a question into Google and scrolling through ten blue links, billions of people are now getting direct answers from AI assistants like ChatGPT, Claude and Gemini.

That single behavioral change is rewriting how brands are discovered. When your customers stop clicking through, traditional SEO and content strategies stop working. The playbook that defined a generation of growth is collapsing — and with it, the visibility companies have long relied on to reach their audiences.

From learning to decision-making, each answer is powered by content that meets new quality and freshness standards. The brands that show up will win. The ones that don’t will disappear. The best companies are adapting to this reality, not panicking. They’ve built connected systems where visibility, content, and performance feed each other in a continuous loop.

We’ve assembled this guide so you can see exactly what’s working for the leading brands like Carta, Rampa and Webflow across AI search today.

Use this playbook to stay visible, move faster, and turn intelligent systems into lasting growth.

What’s Actually Working Today

The “slop” era is over. High-volume filler stopped working because audiences lost trust and leaders lost patience. Visibility in AI search now depends on credibility that begins on your website, but extends far beyond it.

The rules are still emerging, but that’s the opportunity. With fewer incumbents, the fastest-moving teams are winning by mastering three things: originality, human judgment, and speed.

Based on ~15 million data points across AI answers, queries, citations and brand mentions, a pattern is clear: freshness and speed is the competitive edge. Seventy percent of the pages cited by AI models were updated within the past year, and content less than three months old is three times more likely to be referenced.

Our analysis shows the same pattern across every high-performing team.

1. Create information-gain content

LLMs reward novelty, not noise. The web is saturated with repetition, and large models filter for sources that add something new. Winning teams compete on information gain. They publish proprietary data, internal insights, and distinct points of view that expands the model’s knowledge, not restate it.

• Carta and Ramp turn internal datasets, customer calls and insights from subject-matter experts into content to generate net-new content that audiences trust and LLMs notice.
• Webflow saw a 6× higher conversion rate from AI-sourced traffic after focusing on original, structured, and authoritative material competitors couldn’t copy.

Takeaway: Authoritative and unique content is now the most defensible moat in AI search.

AI agents are now the reader

Another new question has emerged alongside staying visible in AI search: how do we stay visible when AI agents are doing the searching on someone’s behalf?

Agentic AI — tools that browse, retrieve, and act autonomously — is changing the retrieval layer of search. Users will soon (if they haven’t already) connect AI assistants to live data sources, delegating research tasks to agents, and relying on automated workflows to surface what’s relevant. When an agent browses for your category, it retrieves the most structured, authoritative, and current information it can find.

This is where Model Context Protocol (MCP) comes in. MCP is the emerging standard that allows AI assistants like Claude to connect directly to external tools and data sources in real time. For content teams, it means two things:

1. Your content needs to be retrievable by machines, not just readable by humans. Structured formatting, clear hierarchy, and explicit answers aren’t just citation best practices — they’re the architecture agents depend on to extract and act on information.
2. Your own AI workflows can connect to live performance data. AirOps now offers an MCP integration that lets teams surface citation insights, brand visibility data, and content performance directly inside Claude.

2. Keep humans in the loop

AI enhances creativity but never replaces it. Top teams use AI to accelerate research and structure while keeping humans in charge of voice, accuracy, and tone. They’ve built workflows where writers, strategists, and systems designers collaborate in real time.

• Teams increasingly invest and upskill around content engineering, a hybrid role that blends editing, systems design, and quality control.
• At Klaviyo, this role orchestrates content systems that merge brand context, data, and human quality together.

Takeaway: Automation works best when it’s guided by judgment. Human oversight is the safeguard that keeps AI-driven content credible.

3. Move at high velocity

Freshness is the new authority signal. AI models overwhelmingly cite content that’s recent and actively maintained. Pages updated within three months are three times more likely to be cited, and >60% of commercial pages cited by ChatGPT were updated in the past six months.

Given the increased requirements in refresh frequency, teams are building systems to not only keep up, but make this their advantage.

Chime had over 700 blog posts and a refresh process that was capping the team at around 50 posts per quarter. After implementing AirOps, each refresh dropped from 45 minutes to under 5 minutes — an 89% time reduction — with refresh velocity increasing 70%. Within four weeks, AI citations on priority questions tripled.

Docebo turned content refresh into a competitive system. When traffic on a page dropped more than 20%, it automatically triggered an update cycle . The result: a 25% share of voice lead in their category, plus double the publishing velocity without adding headcount.

What makes Docebo’s approach worth studying isn’t just the numbers. It’s the shift from reactive to proactive. Rather than responding to visibility loss after the fact, they built a system that catches it early and acts before the drop compounds. They’re now expanding that same logic into internal linking audits, sitemap reviews, and full AI search optimization. Their content operations are a core part of their infrastructure.

Takeaway: The fastest teams don’t just publish more. They build systems that detect decay and respond automatically.

Information gain + human judgment + speed = durable growth.

AI rewards marketers who think like builders, not publishers.

Now that we’ve covered what works, the next step is building a system that makes those results repeatable. The following framework shows how leading teams plan, execute, and measure visibility in AI search.

The New System of Action

Crafting content that meets the demands of AI search now depends on a repeatable process that connects strategy, creation, measurement, and trust. This is the new system of action for modern content and marketing teams.

It’s a practical framework any organization can use. The goal is to make visibility measurable and repeatable, using tools and systems that fit your workflow and ignite your team’s creativity.

1. Know exactly what to do next

Use data to know where to focus before you create anything. Visibility grows faster when you prioritize the queries that matter most.

• Dive deep into the topics, prompts, and pages driving visibility and performance.
• Surface opportunities on your site, external sites, and even Reddit threads on a regular cadence
• Prioritize topics based on potential impact and effort, then align your team around the next best moves.

Result: A short list of high-impact topics that tells your team exactly where to invest next.

2. Create and refresh with precision

Keep your content system active and relevant. AI search rewards teams that update often and publish with the right structure to be found and cited.

• Combine human expertise with precise AI to bring your brand’s stories to life with workflows for creation and refresh across both owned and earned channels.
• Automate triggers for updates every 60–90 days, or when traffic or citations drop.
• Design templates and review cycles that maintain accuracy, speed, and brand context.
• Centralize where you collaborate with your team to accelerate approvals and stay aligned.

Result: A steady flow of content that stays visible, trusted, and aligned with how humans and AI search.

3. Measure your ROI and impact

The way we measure content performance has changed. Traffic and rankings once defined success, guided by impressions, clicks, and keyword positions. Now, visibility is measured by how often your brand is cited, mentioned, and trusted inside AI answers.

The best teams are shifting to a holistic approach that looks beyond search rankings to understand how the brand shows up across all discovery channels.

In AI search, visibility depends on appearing in trusted, authoritative answers on the topics that matter most.

To do this, don’t chase keyword volume and traffic. Instead, map out your most important topics, the queries that matter most, and where you want your brand to be seen as credible and useful.

What’s the ROI of your content? How has it performed over time? And where does your brand stand today?

What to measure:

The 2026 State of AI Search, developed with growth strategist Kevin Indig, confirmed many of these metrics. Pages that go more than three months without an update are 3× more likely to lose visibility. Annual updates are the minimum bar, with 70% of AI-cited pages updated within the past year. For SaaS, finance, and news, the window is tighter still.

One new signal worth adding to your dashboard: McKinsey research shows that 50% of Google searches already surface AI summaries, a number projected to hit 75% by 2028. Strong SEO and strong AEO aren’t parallel strategies. They’re the same investment.

Don’t wait for a traffic drop to trigger a refresh audit. The teams with the highest compounding visibility run standing weekly reviews of citation rate, share of voice, and pages aging out of the freshness window. They act before the decay starts.

• Brand Visibility: How often your company appears in AI-generated answers.
• Citation Rate: How frequently your pages are used as trusted sources.
• Share of Voice: How your visibility compares to competitors across AI search.
• Sentiment: Whether mentions are positive, neutral, or negative.

Result: A clear view of what’s driving growth and where to focus next.

4. Build a system of record for trust

In a world where AI generates endless variations of your message, the real differentiator is consistency. Consistency builds credibility, and credibility fuels authority. A system of record becomes the single source of truth that keeps every workflow, prompt, and piece of content aligned, factual, and unmistakably yours.

It should include:

• Product knowledge: Core features, differentiators, and pricing context.
• Brand voice: Tone, phrasing examples, and common pitfalls to avoid.
• Positioning and messaging: Approved narratives and target personas.
• Data sources: Verified research your team can cite confidently.
• Governance rules: Who owns updates, how changes are approved, and where they’re tracked.

This structure turns scattered information into reusable, trustworthy context that every workflow can draw from.

Each component should stay in sync with your existing systems. Store this information in a knowledge base that grounds every prompt and output. It keeps your context organized, prevents drift, and reduces friction between teams. As your product, positioning, or tone evolves, your outputs evolve too. Your content always reflects who you are now, not who you were six months ago.

Result: A reliable foundation that keeps every message on-brand, factual, and trusted across all channels.

How to Turn the System Into Visibility

The system of action gives teams a repeatable way to plan, create, measure, and maintain trust. To turn that system into real visibility, you need consistent action. The following four plays show how leading teams do it.

1. Create: Originality and structure win visibility

Originality is the moat in AI search. Models reward content that introduces new information, but it also must follow a clear structure they can easily interpret and trust.

Across more than 12,000 pages analyzed, every structural element tested appeared more frequently in ChatGPT-cited content often by margins of 20 to 40 percentage points compared to Google’s top results.

• Pages with FAQs show a 40% higher likelihood of being cited in AI search.
• Pages with three or more schema types are 13% more likely to earn AI citations.
• A clear heading hierarchy (H1 to H2 to H3) increases citation odds 2.8×.
• Organized lists and tables appear in nearly 80% of ChatGPT citations, compared to 29% in Google’s top results.

At Carta, this approach turned into results fast. By embedding structured authoring and proprietary data into every post, the team achieved a 7× increase in AI citations and a 75% citation rate on newly published pages without adding headcount.

2. Refresh: Updated content builds trust

Freshness is now one of the strongest signals of trust in AI search. Models consistently favor pages that are recent, accurate, and actively maintained especially for commercial queries tied to purchase decisions.

• 70% of cited pages were updated within the past year on ChatGPT.
• Pages refreshed within 3 months are 3× more likely to be cited.
• Companies in fast-moving industries like SaaS, finance and news sites only have a 3 month window before their content is out of date.

Webflow automated refresh workflows across its content library using AirOps, integrating directly with their CMS so updates could publish without manual staging. The results came fast: a 5× increase in content refresh velocity, a 40% traffic uplift within days of publication, and ChatGPT-attributed sign-ups growing from 2% to nearly 10% — with AI-sourced traffic converting at 6× the rate of traditional organic search.

3. Third-Party: Offsite signals add validation

Visibility doesn’t stop at your own domain. When AI models surface brands during early-stage commercial discovery, they look for external validation, not what the brand says about itself. In our research analyzing more than 21,000 brands, 85% of brand mentions are sourced from third-party content, not the brand’s own site. This shows that authority now lives across the web, not just on your homepage.

• Brands are 6.5× more likely to be cited through third-party sources than from their own domains, making external validation the dominant driver of visibility in AI search.
• 68% of brand mentions are unique to a single AI model–brands need consistent coverage across external sources to maintain visibility.
• Nearly 90% of all third-party citations come from listicles, comparisons and review sites and 80% of cited brands show up within the first three positions. AI relies on these ranked formats to understand which brands define a category.

The data is specific. Our research found that nearly 90% of all third-party citations come from listicles, comparison pages, and review sites — and 80% of cited brands appear within the first three positions of those formats. If you’re not in the top three on a key comparison page, you’re effectively invisible in that AI answer.

Where to focus your offsite effort:

• Reddit appears as a cited source in roughly 22% of AI-generated answers. Authentic peer discussion signals real-world credibility. The play isn’t brand promotion; it’s genuine participation in conversations your buyers are already having.
• YouTube is an underrated citation source, particularly for non-branded “how-to” queries. 75% of YouTube citations in AI answers occur in exploratory searches
• Listicles and comparisons are the highest-leverage surface to influence. If a publication in your category publishes a “best [your category] tools” list and you’re not on it (or in the top 3) that’s the first place to focus offsite outreach.

One more principle worth reinforcing: content must be quotable. Vague positioning and category-level claims give AI platforms nothing concrete to extract. The brands that earn the most offsite citations write in clear, specific, factual language that a model can lift and trust. Credibility is built in the specifics, not the superlatives.

As TrustRadius CMO Allyson Havener notes, “The most powerful influence happens where attribution can’t see: visibility in AI answers, peer referrals, and third-party proof. Credibility is the lever.”

4. Social Engagement: Community creates credibility

Community platforms have become the new trust layer of search. AI models now prioritize authentic participation and peer validation over brand promotion.

Our analysis of 5.5M answers found that user-generated citations cluster across four main types of platforms.

• Community Q&A spaces like Reddit and YouTube reward direct expertise and real discussion.
• Social platforms such as LinkedIn and X surface professional commentary and peer validation.
• Community editorial sites like Wikipedia and Medium build authority through collective editing and consensus.
• Review and rating platforms such as G2 and Trustpilot reinforce credibility through user feedback and proof points.

Visibility and awareness happen in real conversations across Reddit, LinkedIn, and YouTube, where the freshest and most authentic insights are shared. These platforms are increasingly cited in AI answers because they reflect what people are actually saying and searching for in real time, not static pages frozen in the past.

• 48% of AI citations come from Reddit, LinkedIn and YouTube.
• Reddit appears as a cited source in about 22% of generated answers.
• 75% of YouTube citations occur in non-branded “how-to” queries where users are exploring, not searching for a specific brand.

LegalZoom focuses on high-impact Reddit discussions that align with its brand. Using AirOps workflows, the team identifies opportunities and drafts responses reviewed for compliance and accuracy reducing their response times from 48 hours to under 30 minutes.

The Compounding Loop

These actions strengthen each other over time. Original ideas create content worth refreshing. Fresh content earns new mentions across trusted sources. Those mentions spark conversations in communities that feed the next wave of ideas. This is how enduring visibility is built: a continuous loop of creation, refresh, validation, and engagement. Teams that keep the loop in motion build authority faster and sustain it longer.

Organize the Team That Powers the System

Content engineering is now a job title people are actively hiring for.

AirOps University offers certification in content engineering, and the AirOps Cohort, a two-week live training program, has produced a growing community of certified practitioners across enterprise marketing teams, agencies, and in-house SEO functions. There’s a dedicated job board and an expert marketplace. The role has moved from concept to profession.

The bar for standing up a content-led growth system has dropped significantly as a result. You don’t need to build this capability from scratch or spend months defining what the role looks like internally. There’s a growing talent pool, a shared curriculum, and a community of practitioners who have already solved the problems your team will face.

The four-role structure, Context Librarian, Content Engineering team, Strategy Lead, and Executive Sponsor, gives each function a clearer hiring path, a set of shared tools and workflows, and external peers to learn from. It’s no longer a model you have to build from first principles.

Learn more about the evolution of the 10x content engineer.

Context Management: Govern brand truth

Content only moves fast when everyone trusts the foundation. This role owns the single source of truth for product definitions, tone, and positioning, built from the inputs of product marketing, legal, and other key teams. By aggregating what matters most across functions, the Context Manager maintains a “context library” that keeps every workflow aligned, accurate, and ready to move with speed.

Result: Every project starts from an approved, reliable context that speeds up collaboration and reduces review cycles.

Content Engineering: Build systems that scale quality

The content engineer designs the workflows that power the entire system. They connect research, briefs, and refreshes into one repeatable process and integrate AI tools without losing human oversight. Their work turns creative ideas into structured, scalable operations.

Result: Higher output, greater precision, and a consistent standard of quality across every channel.

Strategy Lead: Turn data into smart bets

The strategy lead translates visibility and performance data into clear priorities. They identify which topics or formats are compounding results and which need to be retired or refreshed. Their goal is to shorten feedback loops so the team learns faster and focuses on what moves the needle.

Result: Every decision ties back to measurable ROI and the system gets smarter with each cycle.

Executive Sponsor: Clear the path and set the mandate

AI search has become a leadership priority. The executive sponsor provides top-down alignment across marketing, product, and legal. They remove obstacles, secure budgets, and make it clear that speed and experimentation are not optional—they’re expected.

Result: A unified mandate that empowers the team to move fast, make decisions confidently, and scale with support from the top.

Together, these roles form a loop of clarity, execution, and learning. Context librarians define the truth. Content engineers operationalize it. Strategy leads turn insight into action. Executive sponsors keep the path clear.

This structure turns a content team from a production line into a growth engine that’s built for speed, trust, and adaptability.

What to Do Next

This is not the time to slow down. The rules of visibility are changing every quarter, and the advantage now belongs to teams that move with structure. The best teams measure visibility weekly, refresh content quarterly, and keep human and AI systems learning together in one loop.

The shift ahead is bigger than technology alone. Visibility now depends on how well your systems, workflows, and people operate as one connected engine. High-performing teams already think of this as a core operating principle, not a campaign.

If you are ready to see where your brand stands and what it will take to compete, our team can help. AirOps works with marketing and growth leaders to evaluate visibility, identify winning strategies, and design systems of action that match each organization’s goals and structure.

Book a demo if you’re a brand ready to take control of your AI search visibility and stop flying blind.

Get started immediately with this exclusive free trial.

SEO Is Filed Under Marketing — That’s The Whole Problem via @sejournal, @pedrodias

Every technical SEO has a version of this meeting.

The migration shipped on Friday. The redirects went in. Someone on Monday noticed organic traffic had fallen off a cliff, and someone else remembered there was, in fact, an SEO on the team somewhere, and perhaps they should take a look.

This isn’t the meeting anyone puts on the LinkedIn headline. It’s the forensic cleanup. The polite explanation of why a decision you weren’t consulted on is now producing consequences you would have flagged if anyone had thought to tell you it was happening. The quiet realization that your job, not for the first time, is to do archaeology on an outcome that was predictable the moment the roadmap got drafted without you in the room.

Welcome to SEO. The dark art. The mysterious discipline. The thing executives describe in tones usually reserved for alternative medicine and aggressive tax planning, and the profession The Verge once called “the people who ruined the internet.”

The industry has spent years worrying about this reputation. There are conference talks. There are working groups. There are, I assume, strategic initiatives. The prescribed fix never changes: SEOs need to communicate better. Get a seat at the table. Build executive presence. Translate technical concepts into business value. Develop soft skills. Take an MBA. Learn storytelling. The recommendations multiply every year, nobody moves, and everyone agrees there’s a problem.

Here is the part nobody at the working group seems willing to say: The reputation is earned. Not because SEO is actually mystical. It isn’t. The reputation is earned because the profession has been filed under marketing for 20 years, and a discipline responsible for outcomes it has no authority to produce behaves, from the outside, exactly like dark magic.

SEO is in the wrong part of the organizational chart. Everything called a perception problem flows from that one structural mistake. The rest of this post is what the mistake has produced, why it’s about to get materially worse, and why the people with the authority to fix it aren’t going to.

Responsibility Without Authority

Here’s the list of things SEO is expected to produce outcomes on.

URL structure. Rendering behavior. Canonical signals. Internal linking architecture. Schema and structured data. Content modeling. Information architecture. Pagination. Faceted navigation. Crawl efficiency. Indexability logic. Status codes. Redirect chains. Site performance. Mobile parity. Image and media handling. Hreflang. The sitemaps. The robots directives. The rendering pipeline that decides whether any of the above reaches a crawler in the first place.

Here’s the list of those things marketing owns.

None of them.

Every item on the list is owned by product or engineering. Some of them are owned so deep inside engineering that getting them changed requires a ticket, a sprint, a roadmap slot, and a PM willing to argue for prioritizing work they don’t personally benefit from shipping. That’s fine if you’re inside the org that owns the thing. It’s a problem if you’re a marketing function being asked to influence it.

This is the diagnosis. It has a name in every discipline that’s had to deal with it: responsibility without authority. Someone is accountable for an outcome they can’t unilaterally produce. It’s a known failure mode in organizational design, which is a polite way of saying every other discipline figured this out decades ago. In SEO, we’ve normalized it so thoroughly that practitioners build whole careers around being good at it.

The skill the industry calls “stakeholder management” is the skill of working around this problem. Translate. Influence. Build relationships. Earn trust. Tell the story. Take the executive to lunch. All of it is the language of a function that has to beg for every deliverable, because it can’t ship any of them itself.

Let’s be clear about what begging produces. When SEO needs a canonical fix, it asks engineering. When it needs a URL structure change, it asks engineering. When it needs schema implemented, it asks engineering. When it needs pagination logic redesigned, it asks engineering. When it needs the rendering pipeline adjusted so that the content actually reaches crawlers, it asks engineering very politely, ideally with a deck. None of those requests are guaranteed to be honored. The function making the request doesn’t own the backlog, doesn’t set priorities, and doesn’t report into a leadership chain that can force the issue.

What does the function own? Content. Specifically, the content it can produce without asking anyone. That’s the one lever it can pull cleanly. We’ll come back to what that does to the profession’s theory of the world.

The genuinely embarrassing part is that everyone involved agrees the arrangement is dysfunctional. Marketing leaders complain that SEO can’t deliver. SEOs complain that they have no authority. Engineering complains that SEO requests arrive late and without context. Product complains that nobody told them. Everyone’s right. They’re all looking at the same structural error from different sides of it.

The fix isn’t better stakeholder management. The fix is moving the function to the part of the org that owns the surface area it’s responsible for. Not a title change. Not a dotted line. Not a cross-functional working group that meets on Thursdays. Actual reporting into the org that owns the work, with the authority, budget, and priority access that comes with it.

This isn’t a radical proposal. Every other technical function figured it out decades ago. Security used to be treated as a side concern of IT, was consistently marginalized, and now lives under its own leadership because the failure mode was too expensive to ignore. Site Reliability Engineering was invented specifically because treating reliability as someone’s part-time concern produced predictable outages at scale. Both disciplines moved when it became clear the work couldn’t be done from where it had been filed.

SEO is the last major technical discipline still filed under the function that doesn’t own any of the work.

Campaign Time Vs. Infrastructure Time

Marketing operates on campaign time. Quarterly planning. Monthly reporting. Weekly standups where someone asks what has moved since last week. It’s a rhythm optimized for activity you can start, finish, and measure inside a budget cycle. That rhythm is load-bearing for a lot of what marketing actually does. Campaigns have start dates and end dates. Launches have moments. Brand work compounds, but most of the artifacts a chief marketing officer is evaluated on are discrete, time-boxed, and attributable to a quarter.

SEO doesn’t operate on campaign time. It operates on infrastructure time.

The work that produces durable search presence is the work of getting architectural decisions right and then leaving them alone for years. A URL structure that survives three migrations is worth more than a content campaign that trends for a week. An information architecture that scales with the business is worth more than any individual piece of content that lives inside it. The compounding is in the foundations, not the surface. Practitioners know this. It’s in every conference talk about technical debt, every post-mortem on a botched migration, every hushed conversation about a client who redesigned their site without telling anyone.

Try explaining infrastructure time to a function measured on quarterly pipeline contribution.

The function can’t hear it. Not because the people in it are stupid. They aren’t. It can’t hear it because the evaluation framework can’t process it. A CMO who invests this quarter’s budget in work that won’t produce visible returns for eighteen months is a CMO who won’t be at the company in 18 months to see the returns. The incentive structure of the role forecloses the investment. You can’t ask someone to spend their political capital on outcomes that will land after they’ve been replaced. They will, rationally, spend it on outcomes that land before the next board review.

So the work gets compressed. The infrastructure conversation becomes a content conversation, because content can be produced inside a quarter. The migration becomes a launch, because launches have dates. The site architecture becomes a “content strategy refresh,” because that’s the vocabulary the budget line expects. Every part of SEO that doesn’t fit inside the campaign calendar either gets deprioritized, rebranded as something that does fit, or quietly declared out of scope.

This is why SEO audits sit on shelves. The audit correctly identifies 47 architectural issues that will take 18 months of engineering time to resolve. The function responsible for acting on the audit has to report results next quarter. The maths doesn’t work. The audit gets filed, the function ships a content campaign, and the 47 issues stay on the shelf until the next agency writes the next audit identifying the same 47 issues, phrased slightly differently. Sometimes the new agency charges more for identifying them a second time. It’s a growth industry.

You can spot a site that’s been through this cycle a few times. It has a lot of content. It has very little that works.

The point isn’t that campaign time is wrong. It’s that campaign time and infrastructure time are different timescales, and you can’t get infrastructure outcomes by running infrastructure work on a campaign cadence. It’s the operational equivalent of asking someone to build a foundation during a sprint. You’ll get something poured, and it will not hold.

Product orgs already understand this. Roadmaps are measured in quarters but planned in years. Architectural decisions get scoped against multi-year consequences as a matter of routine. The entire discipline of engineering management exists to reconcile the short-term delivery pressure with the long-term integrity of the system. It’s not perfect. Product orgs have their own pathologies, and anyone who’s watched a feature factory run itself into the ground can list them. But the conceptual vocabulary for treating some work as infrastructural is there. The meetings exist. The rituals exist. The career paths exist for people whose job is to protect long-horizon work from short-horizon pressure.

None of that vocabulary exists in marketing. It was never supposed to. Marketing’s job isn’t infrastructure. That’s the point. Putting SEO in marketing isn’t just a filing error. It’s filing infrastructure work inside the one function in the org explicitly structured not to do infrastructure work.

When Content Is Your Only Lever

Here is the thing about being trapped in responsibility without authority on campaign time: it shapes what you believe.

A function can only develop expertise in the problems it’s allowed to solve. When the only lever a profession can pull without asking permission is content, the profession slowly, over years, over careers, over decades, develops a theory of the world in which content is the answer to most problems. Not because anyone sat down and decided that. Because the feedback loops that produce professional instincts only have one surface to operate on.

You ship content. You measure content. You get promoted for content. You train juniors on content. You write conference talks about content. You consult on content. Eventually, you believe, in the genuine, felt-in-your-bones way that professional instinct works, that content is what SEO is. Not because you’ve reasoned your way there. Because it’s the only thing the structure around you has ever let you ship.

Google hasn’t exactly helped. For 20 years, the headline advice out of Mountain View has been “create great content.” Never “build a valuable product.” Never “get your architecture right.” Never “think about whether the thing you’re publishing should exist.” The technical guidance is in the docs, buried where most of the profession doesn’t read, written for engineers who aren’t the ones being asked to act on it. The loud advice, the one that became the industry’s shared vocabulary, the one repeated in every Search Central video and quoted in every agency pitch, was always about content. Practitioners followed the loudest signal available. That’s what professionals do. The signal pointed at content for two decades, and the profession dutifully pointed itself in the same direction.

None of this absolves the industry. It does explain why the dysfunction has been so stable for so long. When the structure you work inside can only fund content, and the authority figure you’re trying to please only talks about content, developing a non-content theory of the work requires actively ignoring two reinforcing signals at once. Most people don’t. Most people shouldn’t have to.

This is how the industry ends up with GEO positioned as “optimize your content for LLMs.” It’s how “E-E-A-T” got absorbed as a content-quality checklist rather than what it actually describes. It’s how every major architectural shift in search and retrieval over the last five years has been immediately translated into a content prescription, regardless of whether the underlying change had anything to do with content.

AI Overviews arrive. The industry response: Write content that gets cited.

RAG pipelines become load-bearing for half the AI assistants on the internet. The industry response: write content that chunks well.

Agent browsers start navigating sites on behalf of users. The industry response, presumably arriving next quarter: write content for agents.

None of these responses are wrong, exactly. Content does play a role. The response is incomplete in a consistent, predictable direction, and the direction is the direction of the only tool the profession has ever been allowed to use. When all you have is a content calendar, everything looks like a content gap.

The architectural work that actually governs whether any of this succeeds (rendering pipelines, data models, URL design, schema, crawl surfaces, API exposure, the question of whether your application even produces stable, parseable HTML for a non-human client) sits outside the function making the prescription. So the prescription routes around it. It has to. The function doesn’t have the authority to ship the architectural work, so the architectural work exits the recommendation.

What the client receives is a content strategy. What the client needed was an architecture review. The consultant isn’t being dishonest. They’re producing the output their seat in the org allows them to produce.

This is the dysfunction loop. Marketing placement produces a content-only toolkit. The content-only toolkit produces a content-only theory of the work. The content-only theory produces prescriptions that ignore architecture. Sites spend a decade following those prescriptions. The architectural debt compounds. Eventually, something important breaks, a migration, a rendering change, a platform shift, and someone wonders why all that content didn’t save them.

It couldn’t have. The content was never the load-bearing layer. The industry just lost the vocabulary to describe what was.

Four Retrieval Contexts, One Architecture Problem

For most of SEO’s existence, there was one retrieval system that mattered. Googlebot crawled, Google’s index stored, Google’s ranking algorithms ordered, and whatever Google shipped defined the work. The profession developed against a single target. That target’s requirements were stable enough, for long enough, that “SEO” and “Google SEO” became synonymous to the point where nobody noticed the conflation.

That era is over. The target has multiplied, and the new targets don’t share requirements.

My read is that most sites now need to be correctly interpreted by not one retrieval system but at least four, each with materially different architectural needs. Classic search crawlers still do what they’ve always done, fetch, render, index, rank, and still care about rendered HTML, canonical signals, internal linking, and crawl efficiency. That work hasn’t disappeared. It’s just no longer the only work.

Alongside it sit three classes of retrieval that have arrived, are arriving, or are about to arrive at scale. Retrieval-augmented generation pipelines, where content gets chunked, embedded, and surfaced in response to queries that may never touch a traditional search results page. Agent browsers, where software acts on behalf of a user, filling forms, completing purchases, extracting information, and need the site’s interactive surface to be stable, parseable, and actionable. Training crawlers, whose presence on your site determines whether your content is even available to the models that power everything upstream of it.

Each of these has different requirements, or at least that’s what the behavior I’ve seen suggests. RAG pipelines appear to reward content that survives chunking: semantic boundaries that align with how retrieval windows get constructed, prose dense enough to carry meaning when it’s separated from its surroundings, metadata that persists through tokenization. Agent browsers appear to reward interactive affordances that hold up to automation: stable selectors, predictable navigation, structured data that describes what can be done on a page, and not just what it says. Classic crawlers reward what they’ve always rewarded, and the requirements occasionally conflict with the others. Content optimized for chunking may render poorly when the crawler expects traditional page structure, and sites that expose rich agent-friendly surfaces may produce indexing decisions that weren’t obvious a year ago.

I’d stake the general shape of this on the table: multiple retrieval contexts with overlapping but non-identical requirements. The specifics will keep moving.

None of this is a content problem. All of it is an architecture problem.

Deciding how your site serves four classes of non-human client with partially conflicting requirements is a product decision. It touches the rendering pipeline, the data model, the API surface, the URL structure, the caching strategy, the authentication boundaries, the robots directives. It requires trade-offs that can only be made by someone with the authority to ship across engineering and content at the same time. It requires someone to look at the four retrieval contexts, understand which ones matter for this specific business, and accept that you probably can’t optimize for all of them simultaneously.

That person is not in the marketing meeting. That person is in the architecture meeting, which is a meeting SEO generally isn’t invited to.

So what’s happening instead is predictable and, at this point, depressing to watch. The industry is translating each new retrieval context into a content prescription, because that’s the translation its org chart permits. RAG arrives, and the advice is “structure your content for retrieval.” Agent browsers arrive, and the advice will be, within a quarter or two, “write content agents can parse.” The architectural half of the work, the half that determines whether any of the content prescriptions can even be executed at the infrastructure level, goes unsaid, because the people producing the advice don’t have authority over it.

Meanwhile, the product teams making the actual architectural decisions aren’t making them with any of this in mind. They’re not malicious. They’re not negligent. They’re just not briefed, because the function that should be briefing them is in a different part of the org, producing a content strategy instead.

This is how sites go dark. Not in a single dramatic event. In a compounding sequence of architectural decisions, each individually defensible, made without anyone in the room whose job is to notice what happens at the retrieval layer when you ship them all together. The site doesn’t disappear. Its presence across four retrieval systems gets quietly, progressively worse, and by the time it shows up in a dashboard, it’s already eighteen months of decisions too late to fix cleanly.

The function that could have prevented this was downstairs, writing a blog post about E-E-A-T.

Decisions In Rooms SEO Isn’t In

Ask any technical SEO with a decade of scar tissue to describe the worst projects of their career. You’ll get a specific kind of story.

Someone decided to migrate the CMS. Someone decided to rebuild the frontend in a framework that rendered client-side by default. Someone decided a new URL structure was cleaner. Someone decided the old blog wasn’t worth porting. Someone decided the redirect logic could be simplified. Someone decided canonical tags were “technical debt.” Someone decided that consolidating three subdomains into one would be straightforward. Someone decided product pages didn’t need structured data because the new design handled it visually.

The word “someone” is doing a lot of work in those sentences. The someone is never an SEO. The SEO arrives after the decision has shipped, gets asked to “help with the SEO implications,” and spends the next six to eighteen months producing a recovery plan for a catastrophe that was entirely predictable at the point the decision got made.

This is not an accident of scheduling. It’s a structural consequence of where the function sits. Architectural decisions get made in meetings that belong to product and engineering. Those meetings have invite lists. The invite lists reflect who owns the work and who has the authority to block it. SEO, filed under marketing, is on neither list. Sometimes a senior SEO in a mature org has cultivated enough relationships to hear about decisions informally, early enough to influence them. That’s an individual achievement won in spite of the structure, not a property of the structure itself. The default state, the thing that happens when nobody has engineered around the problem, is that the architectural decisions get made and SEO finds out afterward.

“Get SEO a seat at the table” is the industry’s perennial rallying cry for this problem. Twenty years of conference talks have urged practitioners to be more strategic, more influential, more business-aligned, more whatever it takes to get invited to the meeting. It hasn’t worked. It can’t work. The meeting isn’t a table you get invited to. It’s a meeting for the org that owns the system being decided on. You’re either in that org, or you’re not, and no amount of storytelling improves the address on your org chart.

The practitioners who have, genuinely, managed to get into the room did it the hard way. They built enough credibility with product and engineering leadership that they became de facto members of decisions they had no de jure claim on. That’s a real achievement. It’s also not reproducible at scale. A profession can’t be built on the assumption that every practitioner will, through force of personality and political skill, overcome the structural arrangement of the function. Most won’t. Most shouldn’t have to.

The fix is to change the arrangement, not to keep demanding that individual practitioners heroically overcome it.

The Field Isn’t What It Looks Like From The Outside

There’s a second-order problem here that the “move SEO to product” argument has to confront honestly. Even if the org chart changed tomorrow, the supply of practitioners who could do the work the new placement demands is thinner than the industry is willing to admit.

SEO has the lowest barrier to entry of any technical discipline in the digital field. No certification actually means anything. No degree is required. No apprenticeship is standardized. People arrive from copywriting, from PPC, from affiliate marketing, from blogging, from whatever adjacent role they were doing when someone at a meeting said, “We should probably do some SEO,” and they were the nearest person available. The field absorbed all of them. Then it labeled them all “SEOs” and treated the label as if it meant something consistent.

It doesn’t. Two people with “Senior Technical SEO” on their LinkedIn can have knowledge bases that barely overlap. One of them spent ten years running log file analyses and arguing with engineers about rendering pipelines. The other spent 10 years optimizing meta descriptions and building internal linking strategies in a CMS. Both are senior. Both are technical. The word means different things to each of them, and the industry has never insisted it should mean anything in particular.

For a long time, this didn’t matter much because the bar the field had to clear was low enough that the distribution of capability still produced acceptable outcomes on average. Sites got published. Content got indexed. Rankings happened. The weaker end of the distribution didn’t cause obvious catastrophes because the systems being optimized for were forgiving. Google was doing most of the heavy lifting, and the profession could ride on top of that.

The bar has moved. The work the piece has been describing (making architectural trade-offs across four retrieval contexts, sitting in product meetings with the authority to influence infrastructure, understanding what happens at the retrieval layer when engineering ships the quarterly roadmap) requires a specific profile. Deep technical literacy. Fluency in how web systems actually work, not just how they’re supposed to work. The capacity to read a rendering pipeline and know what it’s going to do to indexability. The capacity to sit in a conversation about caching strategy and understand which decisions will quietly delete the site from retrieval systems that don’t forgive as much as Google did.

That profile exists. It’s a minority of the field. It’s been a minority of the field for a long time, because the structure of the profession has been selecting against it. When the work that gets funded is content, the people who get promoted, hired, trained, and retained are the ones good at content. Twenty years of that selection pressure produces exactly the distribution you’d expect. The profile the industry needs most for the work emerging now is the profile the industry has been filtering out for a generation.

This isn’t a character judgment on individual practitioners. It’s an observation about what happens when a field has no barrier to entry, no standard of practice, and a structural incentive pointing everyone in the same narrow direction. You get a very large population, labeled uniformly, with wildly uneven actual capability, over-indexed on the parts of the work the structure rewards.

And the industry’s own self-descriptions make this worse. Every agency pitches “full-service SEO” as if it were one thing. Every job description asks for the same generic list of responsibilities. Every conference talk is titled as if it’s addressed to a profession with a shared baseline. None of that is true. The field is a patchwork, and the patches don’t know how different they are from each other until one of them is asked to do work the other couldn’t.

The Matching Failure

So there’s a rare profile, scattered across a field that doesn’t know it’s rare. There are organizations that urgently need it, without knowing what it looks like. And there’s a labor market connecting them that’s been trained to produce and consume the wrong match.

Practitioners who could do the product-driven work often don’t know they could. They’ve spent their careers inside marketing org charts, performing the work marketing funded, being evaluated against marketing metrics. Nothing in their day-to-day has ever mirrored back to them that their actual capability is architectural. They think they’re marketers who happen to be good with technical detail, because that’s the only identity the structure around them has offered. Some of them would be transformative hires in a product org. They’re not applying because “senior SEO” job listings aren’t framed in a way that tells them they should.

Hirers are worse off still. An organization that genuinely needs a product-embedded technical SEO, someone who can sit in architecture reviews, argue retrieval trade-offs with engineering leads, and prevent the next migration from quietly removing half the site from indexing, will write a job description that asks for none of those things. Not out of malice. Out of not knowing. The hiring manager copied the last SEO job description the company used, which was written by a marketing director who copied one from their previous employer, which was copied from an agency template, which was a descendant of a 2015 list of generic SEO responsibilities. The job listing asks for keyword research, content strategy, and “familiarity with technical SEO best practices.”

Then, having asked for the wrong things, they evaluate candidates against the wrong instrument.

The CV gets scanned for tools. Ahrefs. Semrush. Screaming Frog. Sistrix. Botify. DeepCrawl. Ahrefs again, because it was listed in a different section. The logic, such as it is, is that knowing the tools means knowing the work. It doesn’t. Tool proficiency is the thing you pick up on the first day of a new job. It’s genuinely the least interesting information on an SEO’s CV, and HR treats it as the most. A candidate who can name 12 SEO suites gets prioritized over a candidate who can explain why the rendering pipeline is quietly deindexing a third of the site, because the first CV is legible to the evaluation framework and the second isn’t. The second candidate probably also knows the tools. They just didn’t think listing them was the point. They were wrong about what the point was. Not in reality, but in the system they were applying through.

The person the company actually needs reads the job listing, doesn’t recognize themselves in it, and doesn’t apply. The person who does recognize themselves in it applies, lists 14 tools, and gets hired. The organization believes it has conducted a search. What it has conducted is a filter, and the filter was calibrated to exclude exactly the person it was supposed to find.

The market can’t execute the match even when both sides of it exist. The vocabulary that would let them find each other was never produced, because the function that should have produced it has been too busy defending its own legitimacy inside marketing to define what it actually is.

Meanwhile, HR departments, which are not the villains of this story but can only hire against the descriptions given to them, run searches optimized for the profile the field has always produced. They find candidates. The candidates are hired. The hires are placed in marketing, where the next cycle of the same pattern begins. The people who could have broken the loop are somewhere else, unreachable through the channels the organization knows how to use.

This is the deepest layer of the dysfunction. Placement produced the wrong selection pressure. The selection pressure produced a skewed professional population. The skewed population produced self-descriptions that encoded the placement. The self-descriptions produced hiring frameworks that reproduced the placement. Every turn of the loop made the next turn more certain. Nobody designed this. It’s just what happens when a structural error is allowed to run for twenty years without anyone senior enough to fix it noticing that it was the structure, not the people, that needed fixing.

The Room Stays The Same

This isn’t a respect problem. Respect doesn’t move the role. The profession could earn the respect of every CMO on earth by next Tuesday, and the work would still be happening in the wrong room, because the work was never a marketing problem to begin with.

The decisions that determine whether a site exists to search engines, RAG pipelines, agent browsers, and training crawlers are product decisions. They always were. We’ve just been staffing them with marketing hires and acting surprised when marketing instincts produce marketing outputs.

The people who could make those decisions at the level the work now requires do exist. There aren’t many, because the field has spent twenty years selecting for a different profile. There will be fewer of them in five years, because the pipeline that produced them is being automated away. And the organizations that most need them won’t find them, because the job descriptions are being written by someone who read exactly one SEO blog in 2019.

For what it’s worth, I’ve been working this way under the banner of SEO Product Management since before the term had traction. I didn’t invent the model. I just refused to pretend the marketing placement was working.

So the industry does what it always does when it can’t change the room: It changes the vocabulary. GEO. AEO. Whatever the next Sand Hill Road newsletter proposes. None of it gets anyone into the meeting. It just makes the exclusion sound current.

The dark art reputation is going to stay intact for a while longer. It’s an impressive illusion: making a product function look mystical by never letting it into the room where the decisions get made. Magicians have been running versions of this trick for centuries. It works best when the audience doesn’t know what they’re not seeing.

More Resources:

This post was originally published on The Inference.

Featured Image: Anton Vierietin/Shutterstock