In short
- Start with the problem you need to solve, then follow the relevant chapters below.
- Keep citations separate from recommendations when deciding whether your brand appears in an answer.
- Use the 30/60/90-day plan as a review schedule, with results left open to measurement.
An AI answer names your competitors. Your team wants a plan before spending more on content. Begin by saving that answer and its question. You'll need something concrete to investigate.
We recommend choosing a route below, then writing down the first decision it should help you make. You don't need to read every chapter before fixing an obvious error.
My brand isn't cited
Start with how AI answers choose their sources. Establish whether your concern is a missing source link or an absent recommendation. ChatGPT's Sources panel can contain both cited sources and other relevant links, so inspect the answer itself. 1
Then check technical foundations. Google's guidance covers crawler access through both robots.txt and hosting infrastructure. It also asks for important information in text. 2
If access looks sound, examine pages that answer for your brand. Choose a buying question your business can answer. Compare your public explanation with the information a customer would need to decide.
For questions that don't name you, continue with the sources AI engines read. Inspect the actual sources in the answers you're studying. Use Reddit in AI answers when those sources or your customers' questions lead to relevant discussions.
Your first deliverable should be a diagnosis tied to a question and a page. For example, identify an unexplained product limitation before commissioning another general article.
I'm choosing an agency
Read what works, graded by evidence before comparing proposals. Ask each provider to distinguish required access work from experiments. Have it explain which promised outcomes depend on systems it doesn't control.
Next, use choosing a GEO agency to evaluate the work you would receive. Request a sample recommendation for one of your pages. Establish who implements the change and how the agency checks the published result.
The existing proposal review article provides another way to inspect scope and responsibilities. Apply the same scrutiny to a Red-engage proposal.
Leave this route with a shortlist based on inspectable work. A proposed volume of articles doesn't tell you whether the team has diagnosed your problem.
I need to measure
Go to measuring AI visibility before changing the site. Choose the questions that matter to your business and identify which already name your brand. Record the engines and markets you intend to follow.
We recommend keeping the complete answers beside the numbers. A source link, a brand mention and a recommendation should have separate fields. Record website visits and business enquiries separately too.
Agree what would change your next decision. If the goal is accurate pricing answers, record incorrect claims against the current pricing page. If the goal is discovery, examine questions that don't supply your name.
A practical 30/60/90-day plan
These are suggested checkpoints for managing work. They aren't deadlines for an engine to cite or recommend your business.
Days 1 to 30: establish what needs fixing
Save a baseline before publishing changes. Agree the questions and observation conditions with whoever will read the report. Keep answers where your brand is absent.
Inspect the public pages behind your main offers. Check crawler access and record the evidence for each issue. In Search Console, inspect the property's Search generative AI control, including any inherited setting. Google documents this separately from ordinary Search inclusion. 3
By the first review, aim to have a small list of confirmed problems. Give each an affected page and an acceptance check.
Days 31 to 60: publish useful corrections
Work through confirmed errors first. Make product descriptions specific enough for a buyer to assess. Where pricing needs explanation, state the conditions behind it.
Have a knowledgeable person review the changes before release. Google explicitly calls for human checking of AI-generated content, including metadata. 4
Save the earlier version and record when each change goes live. Limit simultaneous experiments so you can interpret later observations. Your checkpoint is a verified improvement to the page.
Days 61 to 90: review what changed
Repeat observations under the agreed conditions. Read the new answers alongside the baseline. Note product changes or campaigns that could also explain a difference.
Keep useful corrections even when citations don't move. Stop experiments that add maintenance without helping customers or producing useful evidence. Choose the next question from what remains unresolved.
Finish with a decision you can explain from the saved answers.
Sources
- OpenAI, Searching the web with ChatGPTAccessed Back to the text, first mention of source 1
- Google Search Central, AI features and your websiteAccessed Back to the text, first mention of source 2
- Google Search Console Help, Search generative AI controlAccessed Back to the text, first mention of source 3
- Google Search Central, Guidance on using generative AI contentAccessed Back to the text, first mention of source 4
