SIGNALS
Buying AI visibility

Can you do AEO if another agency controls your website?

The short version

You can run AEO when another agency controls your website, and the work splits into three piles rather than two. Page edits need whoever holds the content management system, and those wait in a queue you do not control. Crawler access and snippet eligibility are usually set at the CDN and in the DNS record, which is often a different vendor again, and a refusal there outranks every page change you could make. Everything off your own domain needs nobody's permission, and the largest published studies put more of the citation outcome there than on your pages. Start by finding out which vendor holds which of the three, because the answer decides what your first ninety days can contain.

Can you do AEO if another agency controls your website?

Yes, you can do AEO while another agency controls your website, and the part that needs their cooperation is smaller than the part that does not. Three things decide whether an answer engine can use you: whether its crawler is allowed to fetch your pages, what the pages say when it does, and what other sites say about you. Only the middle one sits inside the content management system somebody else is holding.

The split matters because of where the measured effect sits. The largest study to separate page properties from retrieval found that which pages the engine's own search returns for its rewritten sub-queries explains about 32% of the variation in citations between pages, while properties of the page itself explain about 2.8%, according to Mahe Chen and Nick Koudas in "What Drives AI Citations? Content, Retrieval and Model Knowledge in Generative Engine Optimization" (arXiv 2610.15033, submitted 10 October 2026). Their sample was 158,099 answers and 468,037 citations across two 90-day collections.

Read against a blocked CMS, that finding is unusually good news. The work with the larger measured effect is retrieval and presence elsewhere, and neither needs a login to your website. The work that needs the login is real and worth doing, and it is the part you should expect to go slowly.

What does change is sequencing. A programme written for a client who can ship a page edit on Tuesday makes no sense when the same edit takes six weeks, so the order of work has to be rebuilt around the queue rather than against it. The rest of this page is that reordering.

Which AEO changes actually need the agency that controls your website?

The changes that need the agency holding your website are the ones that alter HTML, templates or server responses. Everything else belongs to somebody else, and knowing which vendor holds which lever is the first hour of work on an engagement like this.

What needs changing Who usually holds it How to get it done
Page copy, headings, answer paragraphs The agency holding the CMS A written change request per page, with the exact text
Templates, heading order, server rendering The agency's developers A scoped ticket, usually a separate quote
robots.txt, redirects, status codes Whoever deploys the site One-line change, often fastest of the lot
Crawler and bot rules The CDN account holder A settings change, no deployment needed
Domain and DNS records Sometimes the agency, sometimes you Check the registrar before anything else
Review profiles, directories, listicle entries You, directly No permission needed from anybody
Press, analyst and community presence You, or your PR function No permission needed from anybody

Two rows in that table surprise people. The CDN row is not part of the website in any sense a marketing team recognises, and it can decide whether an engine ever sees the page. The registrar row matters because an agency that bought the domain on its own account owns it until a contract says otherwise, which turns a routine request into a negotiation at exactly the wrong moment.

Our guide to what access an AEO agency needs to your website covers the permissions question from the other direction, including which requests to refuse outright.

What can you fix without touching the website at all?

Without touching the website you can change almost everything that sits off your own domain, and that is where most of what engines quote actually lives. Muck Rack analysed more than 25,000,000 links cited by ChatGPT, Claude and Gemini and found that about 84% of citations came from earned sources, counting journalism, academic research, government and non-profit sites, encyclopedic references, social platforms and third-party corporate content, with owned and paid content together accounting for about 16%, in its report "What is AI Reading?" (May 2026, read 19 November 2026).

Four jobs are available to you immediately. Correct and complete the profiles you already control on review platforms and directories, since those are your pages in every sense except the domain. Get into the comparison and best-of pages that cover your category, which is a pitching exercise rather than a publishing one. Give the trade press something specific enough to quote. Answer questions in the communities where your buyers argue, under a real name and with the affiliation stated.

None of that is a substitute for a site that can be read. A page nobody can fetch is still a page nobody can fetch. The point is narrower and more useful: the queue you are stuck in blocks one of three levers, and the other two are open while you wait.

Our longer answer on the balance between the two sides sits in whether you need third-party mentions or fixing your own site is enough, which works through how to tell which side your problem is on before spending anything.

Why does your CDN setting matter more than your CMS here?

Your CDN setting matters more than your CMS because a CDN rule can refuse the fetch that a citation depends on, and no amount of page work survives that. Cloudflare's own changelog, "New options to manage AI traffic" dated 1 July 2026 and read 19 November 2026, describes three crawler categories, Search, Agent and Training, each of which can be allowed, blocked, or blocked only on pages that display ads. From 15 September 2026 new domains onboarding to Cloudflare receive defaults that block Training and Agent crawlers on pages that display ads, while Search remains allowed, and the same entry states that multi-purpose crawlers combining Search and Training are affected by the new default to block Training.

Read that against who holds the account. If your web agency set up the CDN, the setting that governs whether a chat assistant can fetch your page on a reader's behalf is in somebody else's dashboard, filed under security rather than marketing, and nobody in your reporting line has looked at it. A low visibility reading can be entirely explained by one toggle.

Check it before buying any page work. The check is cheap: ask the account holder to screenshot the AI crawler settings, and separately confirm that your robots.txt does not disallow the agents you want. Reasoning about engine access from robots.txt alone now reads the wrong file, because the control moved from the origin to the edge.

While you are there, resist the dev ticket for a list of AI-specific files. Google's documentation on AI features in Google Search, read 19 November 2026, states that there are no additional technical requirements beyond being indexed and eligible for a snippet, and that you do not need to create new machine readable files, AI text files or markup, with no special schema.org structured data required. A long technical wishlist is the easiest thing to get rejected and the least likely to change anything.

How do you get an AEO change through another agency's queue?

Getting an AEO change through another agency's queue is a drafting problem more than a political one. The requests that stall are the ones that ask somebody else to make an editorial judgement; the requests that ship are the ones that arrive as finished text with a named page, a named section and an acceptance test.

Five habits do most of the work. Send the exact replacement copy rather than a description of it, so the task is a paste. Batch requests on a fixed monthly date instead of trickling them, because a queue rewards a predictable sender. Name the one page per batch that matters most, since partial delivery is normal and you want to choose which part. State what you will check after it goes live, which turns a vague improvement into a verifiable change. Put the approval chain on your own side in writing, because the commonest cause of a slow first quarter is a review step nobody scoped.

Keep a change log yourself, by URL and date, whoever makes the edit. A movement three months from now is uninterpretable without it, and the vendor holding the CMS has no reason to keep one for your purposes. The log is also the thing that makes a later handover cheap.

If the queue is genuinely closed, say so early and reorder the programme around the other two levers rather than pretending. A free visibility assessment is one way to find out which of the three levers your problem actually sits behind, since it reads your public pages the way a crawler sees them and samples your buying questions across the engines. Knowing that the blocker is a CDN toggle rather than your copy changes what you ask the other agency for.

Is it worth moving your website away from the agency that holds it?

Moving your website away from the agency that holds it is rarely worth doing for AEO alone, and it is often worth doing for reasons AEO merely exposes. A migration costs a quarter of momentum and carries its own risk of losing what you already earn, so the case has to rest on more than a slow ticket queue.

Three findings do justify a move. If the agency owns your domain or your DNS and will not transfer them, that is a commercial exposure with nothing to do with search. If nobody can tell you what the server returns to a crawler, you have no way to diagnose the retrieval stage at all. If the platform cannot render content without JavaScript executing, the page may be empty to the readers that matter, which is a build problem rather than a setting.

Our write-up on why a page can return 200 and still look empty to AI crawlers covers how to test that last one in an afternoon, and which website platform is best for AI search visibility covers what to move to if the answer is bad enough to act on.

Where the relationship is workable, the cheaper path is to buy the access rather than the platform. Ask for a content editor role on your own site, scoped to the pages in the programme. Agencies refuse admin for sensible reasons and grant scoped editing routinely, and one editor seat removes most of the queue problem for a fraction of a migration. Our two anonymised early case studies on the results page record an audit score moving from 17 to 68 on one engagement and more than doubling on the other after implementation, and that page states plainly that the audit score is an input metric describing how well a site is structured for citation rather than the outcome.

What else do people ask about AEO when another agency runs your website?

Marketing teams whose website is run by another agency ask these five questions most often.

Do you need admin access to your CMS to do AEO?

No. A content editor role scoped to the pages in the programme covers almost all of the page work, and a serious agency will tell you that admin is more access than the job needs. What you cannot do with an editor seat is change templates, server rendering or status codes, so those stay with whoever deploys the site and should be scoped as separate tickets.

Can an AEO agency work directly with your web agency?

Yes, and it usually goes better than routing everything through you, provided one thing is agreed in advance: who decides when the two disagree. Put that in writing before the first ticket. Without it, a conflict about a heading becomes a conflict about scope, and the work stops while two vendors wait for you.

What do you do if your web agency refuses the changes?

Separate a refusal on principle from a refusal on capacity, because the remedies differ. Capacity is solved with a fixed monthly batch and finished copy. A refusal on principle, usually about design or brand, is solved by taking the disagreement to whoever owns the site commercially, and by proposing the smallest version of the change on one page as a test.

Does a page edit made by somebody else count for less?

No. An engine reads the page, not the account that saved it. What does suffer is the record: when a third party makes the edits, nobody keeps a change log by URL and date unless you keep it yourself, and without that log a later movement in citations cannot be attributed to anything.

Should you wait for a website redesign before starting AEO?

Usually not, because a redesign is a schedule you do not control and the off-site work is available now. The exception is a redesign already in build with a launch date inside the next quarter, where page edits made on the old templates get thrown away. In that case, start with retrieval checks and off-site work, and hold the page edits for the new build.

Related guides

The Assessment

Find out which lever your problem sits behind.

A free visibility assessment samples your buying questions across ChatGPT, Perplexity, Google AI Overviews and Claude, and reads your public pages the way a crawler sees them.

Request a free visibility assessment →
SIGNALS · A BlackSig Systems company