Who Should Own the AEO Budget? SEO, PR, Content, or Product

Ask four department heads who owns AEO and you will get four different answers, and all four will be partly right. SEO will say it belongs to them because schema markup and crawlability are technical SEO deliverables. PR will say entity building and third-party mentions are their lane. Content will point to the writing and structuring work. Product will shrug, because nobody filed a ticket. None of them is wrong. That is exactly the problem.

I get this question from nearly every client who has moved past “what is AEO” and into “okay, so who actually does this.” The honest answer is that AEO does not map cleanly onto a single department’s job description, because it was never designed as a department. It emerged from the overlap of four things that already existed: search optimization, public relations, content marketing, and the product or engineering team that controls the actual codebase. Assigning the budget means deciding who funds the overlap, not pretending one team can absorb it alone.

This is not an abstract org chart puzzle. It shows up as a real, recurring meeting problem. A CMO asks the SEO lead for an AI visibility update. The SEO lead reports schema coverage and crawler access, both genuinely improved, but cannot explain why ChatGPT still never mentions the brand. Nobody in that meeting owns the answer, because the missing piece, entity authority, was never assigned to anyone. The budget sits unspent or misallocated not because the company lacks resources, but because nobody has the mandate to spend it across department lines.

If you are a leader coming into this question cold, it helps to start one step above the budget line itself. Our executive’s guide to AEO covers what leadership actually needs to understand about AI visibility before getting into who pays for what. This article picks up from there and focuses specifically on the organizational and budget mechanics.

Why no single team owns AEO cleanly

Every function has a legitimate claim, and every function also has a blind spot. Understanding both halves of that statement is what makes budget assignment possible instead of political.

The case for SEO owning it

SEO teams already touch schema markup, site architecture, crawler access, and content structure. These are the exact technical foundations that determine whether an AI crawler can read your site at all. If your SEO team already manages robots.txt, sitemaps, and structured data, they are the closest thing to a natural home for the technical half of AEO.

The blind spot: entity authority. Most SEO teams were trained to think in keywords, rankings, and backlinks. Wikidata entries, Knowledge Panel claims, and third-party mention density live outside the traditional SEO scorecard. An SEO lead who has never thought about entity disambiguation will treat AEO as “SEO with extra schema,” which misses half the work.

The case for PR owning it

Entity authority, the pillar that measures whether your brand exists as a recognized thing across the web, looks a lot like earned media. Press mentions, industry publication features, podcast appearances, and third-party citations all build the same signal PR has always chased. A PR team that already tracks media mentions is well positioned to extend that tracking into AI citation monitoring.

The blind spot: PR rarely touches schema, crawler access, or content formatting. A press hit in a major trade publication helps your entity graph, but if your own site blocks GPTBot in robots.txt, the hit does not translate into citations. PR can build the outside signals and still miss the inside ones.

The case for content owning it

Content teams write the pages that get cited or ignored. Answer-first structure, comprehensiveness, FAQ sections, and definition boxes are writing and editing decisions. If your content team already owns the blog, the resource center, and the service pages, they are already producing the raw material AI models extract from.

The blind spot: content teams usually lack the technical access to verify whether their work is even reaching AI crawlers. A beautifully structured article sitting behind a JavaScript-rendered page that returns an empty shell to crawlers is invisible no matter how well it is written. Content can own the words and still have zero control over whether those words get seen.

The case for product owning it

Server-side rendering, page speed, Core Web Vitals, and the actual implementation of schema in the codebase are engineering decisions, not marketing ones. If your site is built on a JavaScript framework and nobody on the product team understands why AI crawlers need rendered HTML, every other team’s work gets capped by a technical ceiling they cannot see, let alone fix.

The blind spot: product teams rarely have AI visibility as a stated priority. Without a ticket, a deadline, and a business reason attached, AEO technical work loses every prioritization fight against feature requests and bug fixes. Product can fix the ceiling, but only if someone tells them it exists.

The case for nobody owning it, and why that is the default

There is a fifth option worth naming honestly, because it is the most common outcome by far: nobody owns it. Not out of malice or incompetence, but because every function listed above already has a full workload tied to metrics they are measured on. SEO is measured on rankings and organic traffic. PR is measured on media placements. Content is measured on publishing cadence. Product is measured on shipped features and uptime. AEO threads through all four without being the primary metric for any of them, so it loses every quarterly planning cycle to work that is directly tied to someone’s performance review.

The four-pillar split and who should own each

Rather than assigning AEO to one department, assign each pillar to the function best equipped to execute it, and name a single budget owner who coordinates the whole picture. Here is how the split typically works in practice.

Notice that two of the four pillars already require two functions working together. That overlap is the reason AEO budget conversations get stuck. If you try to fund it as a single line item owned by a single department, you end up funding three-quarters of the work and leaving the rest to chance. If you want the fuller breakdown of what each pillar actually measures, our AEO Maturity Model walks through all four in detail.

Who should hold the budget line

Executing the work across four functions does not mean the money has to be split four ways too. In most organizations, the cleanest model puts the budget under one accountable owner, usually the head of marketing, a VP of growth, or whoever already owns the SEO and content budget lines, and that person funds cross-functional work the way they already fund a rebrand or a product launch.

This person does not need to execute the technical work personally. They need three things: authority to pull resources from SEO, content, PR, and product; a shared scorecard everyone reports against; and a standing cadence to review progress across all four pillars together, not in four separate meetings that never compare notes.

Smaller organizations without a dedicated growth function often default to the SEO lead as budget owner, since SEO already touches three of the four pillars directly or indirectly. This works, provided the SEO lead has the standing to request PR and product time rather than simply hoping it shows up. Without that standing, entity authority work quietly never happens, because it belongs to nobody’s quota.

One pattern worth avoiding: splitting the budget evenly across four departments before any work has been scoped. This feels fair on paper and fails in practice, because the four pillars do not require equal investment. A brand with strong existing SEO might need 70 percent of new spend concentrated in entity authority, the pillar it has never touched. A brand with weak technical infrastructure might need the opposite. Scope the work first, see where the gaps concentrate, then size the budget to the gaps rather than to department headcount.

It also helps to separate the question of who approves the spend from who executes the work. A single budget owner approving a quarterly AEO allocation does not need to personally write schema or pitch journalists. Their job is closer to a portfolio manager than an individual contributor: they decide where the next dollar goes based on the scorecard, and they protect the cross-functional work from getting deprioritized when a department head needs to borrow those hours for something else.

Do you need new budget, or can you reallocate?

This is the question that actually determines whether this conversation becomes a fight. The honest answer is both, and the split depends on what you already have in place.

Work you can mostly fund from existing budget:

• Schema markup implementation. If your SEO team already manages technical SEO, extending that scope to Organization, Article, and FAQPage schema is incremental, not new spend.
• Content restructuring. Rewriting existing pages to lead with answers, add FAQ sections, and use tables is editorial work your content team already does. It is a reprioritization, not a new headcount.
• Robots.txt review. Checking and unblocking AI crawlers is a five-minute technical task well within existing SEO or product bandwidth.

Work that typically needs new budget:

• AI citation tracking. Manually querying ChatGPT, Perplexity, and Google AI Overviews across a fixed query set every week takes real hours, and most organizations do not have anyone already doing this.
• Entity building. Wikidata entries, directory consistency audits, and third-party mention campaigns are net-new work for most PR functions, since they were not chasing this signal before AI answer engines existed.
• Dedicated engineering time. If your site needs server-side rendering changes or a rebuild of how structured data gets generated, that is a product sprint, not a marketing line item.

For a small to mid-size business, a reasonable starting range is $1,500 to $3,000 per month covering content optimization, schema implementation, entity monitoring, and citation tracking, much of which overlaps with SEO spend you are likely already approving. For the fuller cost breakdown across company sizes and in-house versus agency models, see our guide on how much AEO actually costs.

The scorecard that keeps four teams from pointing fingers

Budget ownership breaks down fastest when each team reports its own activity metrics instead of a shared outcome. SEO reports schema pages shipped. PR reports press mentions earned. Content reports articles published. Product reports tickets closed. Every team can show progress on their own dashboard while the brand remains invisible to AI models, because none of those metrics measures the thing that actually matters: did an AI model cite you.

The fix is a single shared metric that every function reports against in the same meeting. Share of AI Voice, the percentage of AI-generated answers across a defined query set that cite your brand, works well for this because it is outcome-based and cannot be gamed by any one team’s activity. When SEO ships new schema and citations do not move, that is visible. When PR lands three press mentions and citations still do not move, that is visible too. A shared scorecard turns a four-way turf war into a shared problem.

Set the cadence monthly. Pull the same 20 to 50 queries every cycle, log every brand cited, and calculate your share against named competitors. Review it in one meeting with representatives from SEO, content, PR, and product present, not four separate check-ins. The teams that are dragging the score down become obvious fast, and the budget conversation shifts from “who deserves more money” to “where is the bottleneck actually sitting.”

One caution worth stating plainly: do not let the shared scorecard turn into a blame exercise. AI model outputs vary across runs, and a single flat month does not automatically mean a pillar failed. Look for trend direction across three or four cycles before reallocating budget away from a function. A single-month dip is noise. A quarter-long plateau while the rest of the scorecard moves is signal.

What the budget conversation looks like in practice

Abstract org charts are easy to agree with and hard to execute. Here is what a real quarterly budget conversation sounds like once the pillars and scorecard are in place.

The budget owner opens with the current Share of AI Voice number against the top three competitors, pulled from the most recent monthly audit. If the number moved up, the conversation shifts to which pillar drove the gain and whether that work should get more investment next quarter. If the number stalled or dropped, each function reports what changed on their side: did SEO ship the schema update on schedule, did PR land the press mentions it committed to, did product close the rendering ticket, did content publish the planned FAQ expansions. Gaps between committed work and completed work usually explain a stalled score faster than any external factor.

From there, the budget owner reallocates for the next quarter based on where the biggest gap sits, not based on which department asked loudest. If entity authority has been flat for two quarters while content and technical foundation both improved, the next quarter’s incremental budget goes toward entity work, even if that means a smaller allocation for a content team that is otherwise performing well. This is the part that requires actual authority beyond a title. A budget owner who cannot move money away from a well-performing team toward an underperforming pillar is not really the budget owner.

A practical ownership model by company size

The right structure depends heavily on how many people you have and whether those functions already exist as separate teams.

Small teams without dedicated SEO, PR, or product

If marketing is one or two people wearing every hat, do not try to simulate a four-department structure. Name yourself the budget owner, work through the pillars in order of impact (technical foundation first, since it unblocks everything else), and outsource the specialized pieces, like entity building or ongoing citation tracking, to an agency or freelancer rather than trying to build in-house expertise for a function you will touch quarterly.

Mid-size companies with separate SEO and content teams but no formal PR function

This is the most common setup we see. SEO and content can split three of the four pillars between them. Entity authority is the gap, since nobody owns press relationships or directory consistency work. Either assign entity authority to whoever currently handles public relations informally (often the founder or head of marketing), or bring in outside help specifically for that pillar rather than letting it default to nobody.

Larger organizations with SEO, content, PR, and product as distinct functions

Use the four-pillar split in the table above as a starting org chart. The main risk at this size is coordination failure, not missing capability. Each team has the skills; the budget owner’s real job is making sure the quarterly roadmap gets built together instead of in four separate planning cycles that happen to touch the same website.

At this scale, it is worth formalizing a lightweight cross-functional working group rather than relying on the budget owner to relay information between four department heads individually. One representative from each function, meeting monthly against the shared scorecard, catches the coordination failures (a schema change that breaks a page PR just secured a feature mention for, a content refresh that happens the same week product changes the rendering setup) before they turn into wasted work.

Agencies and outside help as a fifth option

None of the models above require every pillar to be staffed internally. Many organizations, regardless of size, choose to keep the budget owner and the scorecard internal while outsourcing one or two pillars entirely, most often entity authority and citation tracking, since these require specialized, ongoing attention that does not map neatly to an existing internal role. This is not a sign of an immature AEO program. It is often the fastest path to a working program, because it avoids the multi-quarter delay of hiring or retraining for a skill set that did not exist as a job title two years ago.

The budget owner’s job does not change when outside help is involved. They still hold the scorecard, still approve the quarterly roadmap, and still coordinate internal product and content resources that the outside team depends on to execute. An agency can run citation audits and entity building, but it cannot unblock a robots.txt file or ship a schema update without internal engineering cooperation. The ownership question does not disappear just because execution is outsourced.

What to put in the budget owner’s job description

Whoever ends up holding the AEO budget line needs a few specific responsibilities written down, not implied. Vague ownership produces the same result as no ownership.

1. Approve the quarterly roadmap across all four pillars, pulling priorities from SEO, content, PR, and product rather than letting each team submit an isolated wish list.
2. Run the monthly citation review using the shared scorecard, with all four functions represented in the same meeting.
3. Hold a defined SLA with product for technical AEO tickets, since this is the dependency most likely to stall silently without a deadline attached.
4. Decide where outside help fills gaps, particularly for entity building and citation tracking, two areas most internal teams are not already staffed to execute.
5. Report the shared metric up to leadership, framing AEO progress as a single number rather than four disconnected activity reports.

This is less about creating a new management layer and more about naming who is accountable when the question “are we getting cited by AI yet” comes up in a leadership meeting. Right now, in most organizations, that question has no owner, which means it has no answer.

The skills gap hiding inside the budget question

Part of why budget ownership is murky is that the skill set AEO requires does not map to any existing job title. A strong technical SEO might never have thought about entity disambiguation. A strong PR lead might never have opened a robots.txt file. Before locking in who owns the budget, it is worth an honest assessment of who on your existing team actually has the skills to execute each pillar, versus who simply has the closest job title.

We broke down the specific competencies AEO work requires, from schema implementation to AI citation auditing, in our guide to the skill set AEO actually demands. Reading it alongside your current team roster is often the fastest way to see where the real gaps sit, separate from which department feels like the obvious owner on paper.

What happens when ownership stays undecided

The default outcome of not deciding is not neutral. It is worse than any single imperfect owner. SEO assumes PR is handling entity mentions. PR assumes product is handling schema. Product assumes marketing owns all of it since it is “a marketing thing.” Content keeps publishing well-written articles that nobody checks for crawler accessibility. Every function is technically doing its job, and the brand remains a ghost to every AI model a prospective customer might ask.

This is the pattern we see most often in new client engagements: scattered, inconsistent signals that nobody owns end to end. Schema half-implemented on some pages. A Wikidata entry nobody remembers creating, sitting unverified for a year. A content team producing strong articles that live behind a rendering setup nobody flagged as a problem. None of these are hard problems individually. They persist because the question of who owns the fix never got a clear answer.

Where to start this week

You do not need a finalized org chart to make progress. Start with three moves that work regardless of which structure you eventually land on.

First, name an interim budget owner, even informally, for the next quarter. Second, run the citation audit now, before you have assigned anything, so you have a baseline number instead of a guess. Third, bring SEO, content, PR, and product into one room (or one shared document) to walk through the four-pillar table above and have each function claim or decline each piece honestly. The gaps that surface in that conversation are exactly where your next budget decision needs to go.

If you want an outside read on where your current ownership gaps sit before you lock in a structure internally, that is exactly the kind of assessment we run for clients navigating this exact question.