Google is testing a way to pay some publishers when their work contributes to answers in AI Mode, AI Overviews and Gemini.
Google said in June that it was piloting partnerships with websites whose content helps keep generative AI responses fresh and factually grounded. On September 14, Digiday reported that invited publishers could see an AI contribution panel and monthly earnings in Search Console. Search Engine Land’s summary described a limited, early pilot.
The available sources do not publish the payment formula, general eligibility or a wider rollout plan. There is no clear payment opportunity here for an ordinary service business. The useful move is closer to the customer: make a service page help the right person decide whether to contact you, then make sure you can see what happened after they did.
Write from the questions that change the job
A useful service page starts with what the business actually needs to know. Pick one service and read a recent batch of calls, form submissions, estimate notes and lost-job reasons. Listen for the questions that change the recommendation, price, timing or whether the job is a fit.
Then put those answers on the page in the words the business uses. Say which work and locations fit. Explain what details affect the next step, what the customer should have ready and where a call or inspection is still needed. If a repair price depends on the equipment, access and a diagnosis, say so plainly.
Keep the page focused on the questions that move a real service decision forward, with somebody inside the business able to verify each answer.
Keep each claim easy to check
Google’s public description of its broader pilot talks about freshness and factuality. That does not tell us how its systems will select or value a particular page. It does point to a sound publishing habit: know where each important claim came from and when it was last checked.
Keep a simple record for claims that can change. Pair the public wording with its source, the person responsible for it and the review date. Licenses can link to current records. Warranty wording should match the live terms. Photos and customer quotes need the right permission. Service areas, offers and response times should match how the business works now.
When one of those facts changes, the record tells you which page needs attention. That is much easier than discovering an old promise after a customer has relied on it.
Follow the page into the inquiry record
Once the page is clearer, follow it into the inquiry record. Decide what a useful inquiry means for this service, such as a matching job type and location with enough detail for staff to choose the next step. Keep that definition stable long enough to compare results.
Carry the landing page, requested service and location into the CRM. Review the records after the normal sales cycle, separating an inquiry from an appointment and won work. Small counts deserve a look at the individual records. A page with fewer inquiries can still be useful when more of them fit the work.
When Glory Digital Solutions builds landing pages with the CRM connection, this is the exact handoff we work on: keep the page source and service request attached to the inquiry so the page can be reviewed against recorded outcomes. Your staff still handle the customer conversation and decide what happens next.
The data will not prove that one paragraph caused a sale, and the publisher pilot does not promise citations, placement or payment for a service site. It will give you a cleaner answer to a more immediate question: is this page helping the business get inquiries it can actually serve?
Start with the service page tied to work the business wants more of. Sit with the person who knows the service and check the page against recent calls and estimates. Then send one test form through the CRM and follow that record until it reaches the person who handles new inquiries. You can do that now, whatever Google eventually decides about the pilot.
Source note: Google’s June 18 article confirms the broader website-partnership pilot. Digiday reported the payment and Search Console details on September 14; its article was fully readable during the September 15 check but showed a two-free-article meter. Search Engine Land published an accessible summary. The available sources do not publish payment calculations or wider eligibility.