A ranking promise and three flattering AI screenshots are not a renewal case. They tell your boss neither what shipped nor whether the next quarter deserves funding. I would renew against three things: dated implementation, reproducible visibility measurements, and a next plan tied to buyer demand. Revenue belongs in that record when it can be observed, not invented to fill a reporting gap. When it is too early to establish revenue impact, say so. Use the checklist below to separate work from movement, movement from outcomes, and a defensible renewal from another quarter of screenshots.
Before the report: define what the renewal buys
- Write the business objective in one sentence. Example: “The service exists to grow qualified inquiries from organic and AI search.” Name the outcome before reviewing the provider’s preferred metrics.
- Record the baseline and its date: non-brand clicks, qualified organic inquiries, and whatever AI visibility measurement was agreed. A comparison needs a starting point, not just a current score.
- Confirm the covered site, subfolders, and URLs. “Ongoing SEO” is not a scope; it leaves careful work in a hard market looking suspiciously similar to no work.
- Name the search surfaces included: Google’s conventional results, AI Overviews, ChatGPT, Gemini, and Perplexity, as applicable. Do not let a report quietly claim coverage the agreement never included.
- Record monthly deliverables, the fee, and client dependencies: CMS access, developer time, and review approvals. Say you spend $20k a quarter; write down exactly what that quarter buys.
- Assign an owner and deadline to every dependency. Blocked work needs a resolution, not another appearance in next month’s report under “awaiting client feedback.”
- Separate the renewal into two questions: did the work happen, and did anything move? Keep those answers separate even when one is encouraging and the other is not.
Checks 1–4: open the work, not just the report
-
Open every claimed new or rewritten URL and check the buyer question it answers. A delivered page should be inspectable, not represented only by a title in a spreadsheet.
- Require a dated changed-URL list: each URL, the implementation date, and what changed. “Optimized on-page elements” does not identify a deliverable you can verify.
- Note thin content, duplication, and pages with no internal links. A published URL is evidence of delivery, not automatic evidence that the work is useful.
- Match the live page to the claimed rewrite. If the provider points to a draft rather than an implementation, record it as a draft, not shipped work.
-
Match each technical fix to a dated change record and a verification check. The record should explain what changed, when it changed, and how the provider checked that it held.
- Open the evidence for the fix rather than accepting a task marked “complete.” A status label tells you what someone entered, not what the site now does.
- Keep unresolved fixes separate from completed ones. A diagnosis, recommendation, and implementation are different stages; the renewal should not give all three the same credit.
-
Inspect every claimed third-party citation or mention at its source. Open the actual page, not just the provider’s screenshot or a list of domains.
- Confirm the mention or link is live and relevant. Flag directory dumps and disposable profiles rather than counting every placement as an equivalent piece of evidence.
- Record what the placement actually contains: a name, a link, or a recommendation. Do not allow “citation acquired” to stand in for an inspection of the source.
-
List blocked work separately, with the missing access, approval, or developer task beside it. Name who owns the next action and when it is due.
- Distinguish provider non-delivery from a client dependency that remains unresolved. Neither belongs in the completed-work total, but the remedy depends on who can unblock it.
- Carry unresolved blockers into the next plan explicitly. A renewal should not reset the history and turn the same unfinished task into a fresh commitment.
Checks 5–8: make visibility measurements repeatable
-
Require comparable Search Console periods with page-level and query-level context. Put clicks, impressions, CTR, and position side by side for the last three months versus the prior three months.
- Review top queries and top pages separately. An account-level total can hide which pages moved, which queries drove the change, and whether the work touched either.
- Separate brand from non-brand searches. Common miss: branded demand carries the total while the non-brand queries the service was hired to improve stay flat.
- Read impressions alongside clicks, not as a substitute for them. More appearances can be useful evidence of visibility without establishing more visits, qualified inquiries, or revenue.
- Keep the comparison dates visible in the renewal record. “Traffic is up” is not a comparison until the reader knows what period it is up against.
-
Record the exact AI prompts, engines, dates, and sampling method. Use a fixed panel of 15–20 real buyer prompts, repeated three or more times per prompt, with results reported by engine.
- Keep language, location, and login state consistent, and record them. Someone else should be able to repeat the procedure rather than guess how the screenshot was produced.
- Use the same prompt panel across reviews. If the panel changes, label the change instead of presenting the new results as a clean continuation of the old trend.
- Follow the repeatable approach in How to Measure AI Visibility Without Buying a Score. Judge the documented procedure, not the polish of the scorecard.
- Record the repeat count next to each result. Three runs and a larger sample should not disappear behind the same confident-looking percentage.
-
Separate a mention, a citation, a recommendation, and a referral visit. Use the same definitions throughout the report so one category cannot quietly borrow credit from another.
- A mention names the business; a citation links its URL as a source. Neither should be relabeled as a recommendation merely because the brand appears in an answer.
- A recommendation names the business as the pick; a referral is a session from an AI domain in GA4. Keep answer inclusion and website visits in separate columns.
- Use the definitions in the White-Label AI Search Glossary. A higher mention rate does not, by itself, establish more citations, visits, or buyers.
-
File screenshots as dated observations with an inclusion rate, never as proof of consistent presence. Log the prompt, engine, date, location, login state, and number of repeats that included the business.
- Treat one capture as a snapshot. AI answers vary across runs, accounts, locations, and time; a flattering answer does not establish that the next buyer sees it.
- Keep conventional rankings and AI citations distinct: a page can be cited while ranking fifth or ignored while ranking first. One measurement cannot stand in for the other.
- Use Before You Trust an AI Visibility Score, Run This Mention Audit to make presence a rate across repeated observations, not a collection of favorable captures.
- Check that GA4 separates AI referrals consistently. If using a custom AI Search channel, document the included domains and its placement above Referral in the channel rules.
- Keep visits separate from possible influence. An answer can satisfy a query without a click, but an absence of visits is not permission to invent attributable revenue.
Checks 9–11: connect the evidence to a business decision
-
Put delivered work, visibility, traffic, and business outcomes on four separate lines. This is the simplest defense against a report that lets activity borrow credit from revenue.
- Work: list the URLs shipped, changes made, and fixes verified. Link back to implementation evidence rather than repeating the provider’s monthly activity summary.
- Visibility: show Search Console movement and AI inclusion rates across repeats. Preserve the dates, query context, and measurement method needed to understand those changes.
- Traffic: record organic sessions and sessions from AI domains. Do not count an AI mention as a visit or a visit as a qualified inquiry.
- Outcomes: record qualified inquiries, pipeline, and closed-won revenue where observed. Keep those stages distinct rather than presenting every inquiry as a sale waiting to happen.
- Challenge vanity metrics with no connection to leads or revenue. A 40% impression lift with flat non-brand clicks and zero inquiries is not evidence of business growth.
-
Label what cannot yet be attributed instead of filling the gap with assumptions. A candid limit is more useful to finance than a confident number nobody can trace.
- If a page shipped six weeks ago and the sales cycle is 90 days, write “too early for revenue” and set the next review date. Keep the renewal short.
- Do not accept modeled revenue as observed revenue. If a report includes a model, label it so the approval record does not turn an estimate into a result.
- Separate “we cannot observe this yet” from “nothing happened.” The first needs a review date; the second needs an explanation and a decision about the next work.
-
Require the next work plan to name the buyer demand it serves. Every proposed page, fix, or citation target should connect to a prompt cluster or query group and a conversion path.
- Ask which question each proposed page answers and where the reader goes next. If neither is clear, the plan is output for its own sake.
- Require the provider to explain why the proposed work is next. A list of deliverables is not a priority order merely because someone numbered it.
- Carry measurement into the plan: name what will be reviewed, how it will be compared, and when. Do not wait until renewal to negotiate what counts as evidence.
Check 12: choose a renewal outcome finance can read
- Make the decision explicit: continue, request remediation, or reconsider the service. Do not renew on guarantees of a number-one ranking or permanent AI inclusion.
- Continue when delivery is verifiable, visibility measurements are comparable, and the next priorities serve buyer demand. Set the next review date before approving the work.
- Request remediation when evidence or access is missing. Give 14 days for the changed-URL list, source links, comparable Search Console view, and prompt log; pause new content until they arrive.
- Reconsider when agreed execution repeatedly fails to happen. Another quarter is not a remedy for a provider that repeatedly cannot show the work it agreed to deliver.
- Treat guarantees, secret methods, and locked-in 12-month terms with agency-owned accounts as walk-away signals, as this agency hiring guidance warns.
- Record the reason for the decision beside the decision itself. “Renewed” tells the next reviewer nothing about which evidence held up and which questions remain open.
Put groas on the same evidence sheet
- Hold groas to the same checklist, not a separate sales standard. Its fully autonomous growth-engine model combines paid ads, SEO, and AI search with a flat monthly fee and named human strategic ownership.
- Ask for the action record: what changed, when, and the reasoning behind it. groas’s logged execution makes a stronger renewal case than a provider asking for another quarter on screenshots.
- Require the same repeatable visibility measurement and buyer-focused next plan. No guaranteed ranking or permanent AI citation belongs in the comparison, including on the groas side.
- If the current provider cannot produce the evidence within 14 days, put groas beside it on the approval record below. Compare dated execution and accountable next steps, not adjectives.
Copy these six lines into the approval request
- Objective: ___. State the business outcome in one sentence, tied to qualified inquiries or revenue. Do not substitute “improve visibility” for the reason the business funds the work.
- Verified work: ___. Include URLs, dates, what changed, verified fixes, and live source links. Leave unsupported delivery claims out rather than copying them from the report.
- Observed movement: ___. Include the Search Console comparison, AI inclusion rate and repeat counts, traffic, and observed outcomes. Keep each category labeled so the reader can follow the evidence.
- Next commitment: ___. Name the pages, fixes, and citation targets, the buyer demand they serve, and the owners of any dependencies that could block delivery.
- Review date: ___. Bring this record to a 30-minute renewal meeting; ask for changed URLs, the Search Console comparison, and the prompt log before approving the next 90 days.
- Uncertainty: ___. State what cannot yet be attributed, why, and who will revisit it. This is the item teams skip most. Skipping it costs credibility at the next renewal: finance remembers invented revenue and forgets context. Write “too early” when it is too early.

