Dev.to WebDev πŸ›  Dev πŸ‘ 0 πŸ“– 6 min read

Do these three things before you ever start paying an AEO agency

This is a cross-post of Preferly's guide on what to do before hiring an AEO agency. Short answer: before you pay an AEO agency, get a complete audit of your current AI visibility, do the quick fixes yourself (this usual

This is a cross-post of Preferly's guide on what to do before hiring an AEO agency.

Short answer: before you pay an AEO agency, get a complete audit of your current AI visibility, do the quick fixes yourself (this usually takes a few hours), then wait 2-4 weeks and run the same audit again. That second baseline is what you take to the agency, so you can measure what they actually change.

A founder recently shared that their AEO agency was a complete fail. The milder version is common too: an agency bills for a month of work, visibility ticks up, and some of that jump would have happened anyway once the site could be read and the obvious errors were cleaned up. Skip the three steps below and you pay an agency to do things you could have done in an afternoon, and they take credit for the low-hanging fruit.

1. Get a complete audit of your current AI visibility

A useful audit is a snapshot you can repeat, not a slide deck. It should tell you, in writing, where you stand today on each of these.

The assistants your customers use. ChatGPT, Gemini, Google AI Overviews and AI Mode, Perplexity and Claude don't always name the same businesses. Check the ones your customers actually open.

The questions a customer would ask. Don't only search your own name. Ask category and problem questions without naming yourself ("best family dentist in South Tampa", "emergency plumber near Westchase open Sunday"), then ask about you by name. Repeat each question a few times in a private window, logged out. Answers vary from run to run, so one missing mention isn't a baseline.

Crawler access. If AI tools can't load your pages, they can't quote them. Check robots.txt for rules that block search crawlers such as OAI-SearchBot, Claude-SearchBot or PerplexityBot. Check whether a firewall or bot check turns identified crawlers away, which is common on Cloudflare and some hosts. Confirm the homepage loads over HTTPS with a valid certificate.

This is more common than it feels. In Preferly's study of 3,693 small and local business websites in 26 US cities, 14.4% (about 1 in 7) weren't fully open to AI crawlers, and most owners didn't choose that: 5.8% showed a bot check, 5.0% didn't load (mostly HTTPS failures), and 3.1% blocked some or all AI crawlers in robots.txt. Preferly's free AI crawler check runs the same two requests used in that study.

Listings and reviews. AI answers often lean on Google Business Profile, maps, review sites and directories. If those pages show old hours, the wrong category, a closed location, or a different name from your website, the audit should record it.

Schema and on-site content. Do your key facts (name, address, hours, services, area served) appear in the HTML, not only after JavaScript runs? Is there LocalBusiness structured data, and does it match the visible page?

You can gather a first pass with tools like Preferly's free check or others, or by hand in a few private chats. Write down the questions, the models, who was named, which URLs were cited, and any crawler or listing problems, so you can run the same audit again later.

2. Do all the quick fixes based on your audit

Most of what turns up is not a content strategy problem. It's a blocked crawler, a certificate warning, a stale listing, or a homepage that never states what you do in plain text. This shouldn't take more than a few hours.

Typical fixes, in the order they usually pay off:

  1. Let the search crawlers in. If robots.txt disallows OAI-SearchBot or the other search crawlers you care about, allow them. You can still block training crawlers such as GPTBot. This is often a few minutes.
  2. Relax the bot check for verified AI crawlers. If Cloudflare or your host shows a challenge page to identified crawlers, adjust the bot settings so search crawlers can load the page, and leave protection in place for everyone else. This is usually a short visit to the dashboard.
  3. Fix the HTTPS certificate if the homepage doesn't load. An AI crawler that hits a certificate error usually just moves on. Renewing or replacing a certificate is often quick; if the domain or DNS is wrong, it may take longer.
  4. Make your listings match your website. Hours, address, phone, name, category, and whether you're open. Start with Google Business Profile, then the directories the first audit cited. This can fill an afternoon if several listings are out of date.
  5. Put the facts in the HTML. Name, location, hours, services, and who you serve should be readable without JavaScript. Add or correct LocalBusiness schema so it matches what's on the page.
  6. Correct the pages AI already cites when they contradict your site, including third-party pages you can claim or update.

Save a copy of what you changed and when. You'll need that list when you read the second audit.

3. Wait 2-4 weeks, then do a second audit

Fixes don't show up in AI answers the same day. Crawlers have to revisit the pages, and some answers still come from older copies or from training data that only changes when a new model ships.

OpenAI says a robots.txt change can reach its search systems in about 24 hours, but being crawled and then cited can take longer. Listing and third-party updates often take longer than a site change. That's why we say wait 2-4 weeks: long enough for a re-crawl and for answers to refresh.

Then run the same audit again: same assistants, same questions, same method. Compare whether you're named more often on the customer questions, whether answers about you match your website, which sources are cited now, and whether crawlers can load the pages they couldn't before. That second snapshot is your new baseline. Everything after it is what an agency can fairly be judged on.

How to use the second baseline in an agency contract

Bring the two audits (before the fixes, and 2-4 weeks after) to the first serious conversation. Ask the agency to treat the second one as day zero.

Measure the same questions, on the same assistants, on a fixed schedule. Agree in writing what "improvement" means: how often you're named on a set of customer questions, whether the facts about you stay accurate, and which sources those answers cite. Ask them to keep the question list stable, and to show the raw answers, not just a score.

Be wary of a pitch that starts work without a baseline, or that wants credit for the easy crawler and listing fixes you already made. Those were yours.

What to ask an AEO agency before signing

  • Will you use my second baseline as the starting point, and keep the same questions and assistants?
  • What, exactly, will you measure, and how often will I see the raw answers?
  • Which assistants are in scope, and which are not?
  • What work is included in the first 30 days, and what is out of scope (ads, review generation, and so on)?
  • How do you treat the quick technical fixes (robots.txt, bot checks, certificates, listings)? If those are still open, who does them, and are they billed as strategy?
  • What will you need from me, and what can you not do if a third-party site refuses to update?
  • How do you report when answers vary from run to run?
  • What happens if visibility doesn't move after the agreed period?

If the answers are vague, wait. A good agency should be comfortable being measured against a baseline you already have.

You don't need an agency to find out where you stand. Tools like Preferly's free check or others will get you the first audit. The important part is that you do it, fix what's obvious, and measure again before you pay someone else to take the credit.

The full version, with internal guides for robots.txt, Cloudflare, HTTPS and ChatGPT citations, is on preferly.ai.

πŸ“° Read the original article on Dev.to WebDev

Originally published by Dev.to WebDev. Aggregated on AIWithGhost for educational purposes β€” full credit and traffic to the original publisher.