Skip to main content
AEO Buying Guide

What should an AEO agency service agreement include?

Learn what to put in an AEO service agreement, from the scope and monthly reports to content rights, service issues, data access and a clear exit plan.

Published
2026-11-18
Updated
2026-11-18
Read
12 min

Put the work in writing

What this guide shows

A clear agreement gives both teams a shared way to make decisions and resolve issues.

ScopeDefined work

Name each handoff and its owner.

ReportingClear limits

Keep platform data and business outcomes distinct.

RightsWritten terms

Ask counsel to review content rights.

ExitPlanned handoff

Know how access and files return to your team.

Short answer

The Answer

An AEO service agreement should state what is delivered and when, what is reported each month, who owns the content and accounts, how either side can end the deal, and how problems are raised and fixed. Leave out promised rankings or citations. Our founder handles AEO agency buying questions like this one, and his own real estate team closed over $100,000 in commission in July 2026 and credits AI search for it.

AEO means making your business easier for AI tools to find, trust and name. Use these questions to review the deal with your team and counsel.

In July 2026, the founder closed over $100,000 in commission, which he credits to AI search work on his own sites. We did it for our own business. Book a 30-minute call to find out how we can help yours

What work and deadlines should the agreement name?

A service agreement should let both sides tell when a piece of work is ready for review. Name each item, its scope, the owner and the date or schedule. State whether the work covers a single site, a group of brands, or a set of markets. List what is outside the scope too. A vague promise to improve AI visibility leaves too much room for each side to picture a different job.

For content, describe the expected format, topic approval, fact review and delivery point. Say whether delivery means a draft, an approved page or a live page. Those are different events. If your team controls the site, a draft can be complete while the page still waits for your review. Set a clear handoff so that neither side has to guess where the work stands.

Name the person who can approve work and the route for feedback. Agree on how many review rounds are included and what happens when a new request changes the scope. The agreement can call for a written change to the work, timing or fee before the new work begins. Ask how an urgent request will be handled when it competes with work already agreed.

For service-area pages, list each area, the page type and the person who checks local facts. Say who approves the draft and who can publish it. If a new area is added, agree on the change in writing before work begins.

Ask for a sample deliverable before signing. It helps you judge whether the level of detail fits your team. A list of tasks alone may not show what you will receive. Also ask what the agency needs from you, such as access, source material or a subject expert. Set out how a late handoff affects the schedule and how the parties will agree on a new date.

Do not sign a list of broad activities as if it were a list of finished work. Ask the agency to show what a completed item looks like and where your team will receive it. If the item needs your approval, name the person who can give it and the place where feedback will be collected. This gives each side a clear point for the next handoff.

For each deadline, ask what must happen first. A delivery date may depend on access to your site or a review by your team. Put those dependencies beside the date, along with the person responsible for each one. If a dependency is late, agree on the revised date in writing. The result should be a scope list with an owner, handoff and due date beside each item.

What should the monthly report show?

Put the report date, recipient, review meeting and action owners in the agreement. For the measures and their limits, see the monthly report guide; a sample is a view of what was seen, not a count of every answer given to every buyer. Keep the existing source records with the report, and ask for the question list and a named owner and due date beside each action.

Want a starting point for the questions in your report? Does ChatGPT name you?

Who should own the content and accounts?

Put ownership and access in writing before work starts. Name the content, source files, reports and other work covered by the deal. Ask when your rights begin, what happens if a bill is disputed and whether you can edit or reuse the work after the deal ends.

Do not assume that paying for a draft makes it a work made for hire. The U.S. Copyright Office describes specific conditions for that status. The U.S. Copyright Office said in January 2025 that AI output is protected only where a person contributed enough of the expression, and that prompts alone are not enough. If AI helps create a draft, ask how much of the page is human-written and edited. Put your planned use, rights and any transfer in the agreement.

Keep business accounts under your control where practical. List the site, analytics and search accounts the agency needs, along with the level of access and the person who can grant it. Ask for named users rather than a shared login. State who keeps access to reports and files, and how access will be removed when the work ends.

If you want to update a page after the agency leaves, the agreement should say whether you can edit it and use the related files. Check the rights before signing.

Also ask about material the agency brings to the job. A license for a photo, font or other asset may have terms that differ from those for the page text. Have the agreement identify any limits and who pays to keep a license active. If a source file cannot be handed over, ask what you will receive instead. Record where approved files live so the next team can find them without relying on a single person.

Account control deserves its own line in the deal. List the accounts your team owns and the access the agency needs to do the work. Name the person who can approve access and the person who will remove it. Ask where the finished files will be kept and how your team can retrieve them during the engagement as well as at the end.

Check the handoff against how your team plans to use the work. If another agency or an in-house writer may edit a page later, raise that use before the terms are signed. Ask for any limits on reuse to be written beside the relevant asset. Keep the approved rights and file locations with the agreement.

See the story behind our founder’s own result. Read the case study

How should problems be raised and fixed?

A service level agreement, or SLA, sets out the service you can expect and how problems are handled. In an AEO deal it can cover response and handoff times for work the agency controls. It should define the issue, the contact, the expected reply and the path to a person with authority if the issue remains open. A reply is not the same as a fix, so ask the agreement to make that distinction.

Use separate paths for routine edits and urgent problems. An incorrect service fact on a live page may need faster attention than a request for a new topic. Agree on how to report each kind of issue, what details to include and when the clock starts. State the business hours and time zone used for any response target. Ask what happens on a holiday or when your own team must approve a fix.

When your team spots a wrong claim on a live page, it needs a clear route to the person who can receive the alert. Name the contact at each firm, the person who can approve a change and the next contact if the issue remains open.

Ask for a record of the issue, the owner, the steps agreed and the date it was closed. If the agency misses a service target, state the review or remedy the parties have agreed to and its limits. Do not accept a promise that an outside platform will display a certain answer by a set date.

A steady review helps prevent a small delay from becoming a dispute. Agree on who attends, how open items are tracked and when the plan is revised. Ask how the agency will tell you about a risk to a due date before the date passes. Your team should also name a backup contact, so a request does not stall when its usual reviewer is away.

Write the response target so both sides can tell when it applies. Identify the channel for the notice and the information your team should send with it. A message that says a page is wrong may need a link and a description of the issue before the owner can assess it. Put those details in the notice process so an urgent request reaches the right person.

A first reply should tell you who owns the issue and what happens next. Ask how the agency will set a target for the fix, how it will report a delay and who can approve the proposed change. If your team must review the fix, name its reviewer and backup. Track the reply and the fix as separate steps.

For an open issue, agree on when it moves to a person with authority. That person should be able to review the record and agree on a next step with your team. Ask for the escalation contacts in the agreement itself, along with the route to update them if staff change. Keep the issue, owner and next update together in the record.

What data and security terms should you review?

List the data and systems the agency needs, the approved access, the notice route for an issue and the return or deletion handoff. NIST recommends addressing supplier cyber risks in agreements and planning for the end of the relationship. Use the vendor security questions guide for the wider review, and record the approved access and response contact in the agreement.

Have a question about the work you need? Email our team

How should the agreement end or change?

Check the start date, term, renewal and notice rules. Ask whether the deal renews on its own and how either side gives notice. Name the person at your firm who tracks the notice date and where to send it. List any fee or duty that continues after the work ends.

Agree on a handoff before it is needed. List the final files, reports, open work and account access your team should receive. Name the format and the person who will receive each item. State when access ends and how work in review will be handled. A good exit plan lets your team keep serving buyers while the next owner takes over.

If you bring the work in-house at the end of the term, the handoff list should name approved pages, source files and open edits. Check that your team can reach the materials before agency access is removed.

Ask how either side can request a change during the term. A new market, a site move or a change in the work may affect the plan. Put the new scope, fee and dates in a written change both sides accept. Keep the old and new terms together so your teams know which version governs the work.

Before signing, compare the agreement with the sales proposal and the report sample. Resolve gaps while the people who made the promises are still part of the discussion. This guide gives you buying questions, not legal advice. Give counsel the full set of documents for review and put agreed changes in writing.

Ask what happens to work that has been started but is still in review when the term ends. The agreement should identify what will be delivered, who will collect feedback and how the parties will handle any remaining approval. Do the same for a page that has been approved but is waiting to go live. Your team needs to know which items are ready to use and which still need a decision.

A handoff list is useful only if someone checks it. Name the person who sends each file or report and the person who receives it. Agree on a place for the materials and a way to flag missing items. Include the status of open issues so the next owner knows what has been raised and what remains to be done.

Review the access list against the handoff list. Your team should be able to reach its accounts and retrieve the agreed files as the agency leaves. Record which agency users need access removed and who is responsible for that step. Keep the final list with the written notice and the accepted changes to the agreement.

Do not leave renewal terms in a sales email while the contract says something else. Put the notice route and any agreed change in the documents that govern the deal. Before you sign, give the person tracking renewal a copy of the terms, the notice date and the address for sending notice.

What should you check before you sign?

  • A clear list of work, owners and handoffs
  • A report schedule with data sources and limits
  • Written rights to content, files and accounts
  • A contact and escalation path for service issues
  • Data access, security duties and a response contact
  • Renewal, notice and an agreed exit handoff

Frequently Asked Questions

Can an agency promise a top ranking?

You can ask for clear work and reporting, but leave a promised ranking out of the deal. Google says no one can guarantee a top Google ranking. Ask what the agency will deliver, how it will measure progress and how it will explain changes in the results.

Is a citation the same as a sale?

No. A citation is a link or named source in an AI answer. A sale is a later business outcome. Ask for the source and date of each measure, and keep the two separate. A report should explain what the available records can support.

Do you own every page you pay for?

Do not assume that payment alone settles ownership. The U.S. Copyright Office describes specific conditions for a work made for hire. Put the rights and any transfer in the agreement, including what happens to source files and licensed assets when the deal ends.

What if the agency misses a deadline?

The agreement should say how a delay is reported, who reviews it and how a new date is set. Define any agreed remedy and what happens if your team has not supplied an approval or source material needed for the work.

What happens to account access when the contract ends?

Agree on the handoff and access removal before signing. List the accounts, files and open work your team needs, and name who will receive them. Your security team can review the exit plan. NIST includes the end of a supplier relationship in its risk guidance.

Should your legal team review the agreement?

Yes. Give counsel the proposal, the agreement and any data terms together. Explain what the agency will access and how your firm plans to use the work. Record the changes agreed before signing. Include the report sample and any written changes to the scope so the review covers the full deal.

Explore the space your business wants to reach. Is your city or industry still open?

Sources

  1. Do you need an SEO?Google Search Central
  2. AI features and your websiteGoogle Search Central
  3. Default channel groupGoogle Analytics Help
  4. The NIST Cybersecurity Framework 2.0National Institute of Standards and Technology

About the author

Justin Borges

Founder & AEO Strategist

Justin leads The Answer Engine and helps businesses understand their place in AI search.

Next step

Find out what your business needs

We did this for ourselves. See how it could help your business.

Get your free Answer Engine audit

Free audit

See where answer engines miss your business

Get a clear view of how ChatGPT, Claude, Perplexity, and Google answer questions about your category today.

Run the free audit

Talk to the team.

Call us
(213) 444-2229
Email
support@theanswerengine.ai
Business hours
MON-FRI 0900-1800 PT

Audit requests reviewed by our team. Now accepting new clients.