How Long Does GEO Take to Work?

Google's recrawl guidance, checked October 19, 2026, says crawling a changed page can take a few days to a few weeks, while its broader search guidance allows anything from hours to months for changes to take effect. Neither range tells you when an AI assistant will recommend your business. The useful question is which stage has moved: has the source been processed, does the business appear repeatedly, and do those appearances lead to customers?

Last verified: October 19, 2026.

For a service business, I would agree on those three measures before agreeing on a deadline. A corrected phone number, a cited service page and a booked job are different results. This guide explains how to judge progress between them. For the work itself, use the AI visibility cleanup plan.

Start the clock from the live change

Record the URL or profile you changed, what you changed and when the correction became publicly visible. A document waiting for approval has not started a crawl or measurement window. If a directory publishes your update later than your website, give that source its own start date.

Keep the original evidence. For a plumbing branch, that might be a saved page showing the old service area, the corrected page and a dated note explaining the change. For a multi-location brand, keep a separate entry for each branch. Otherwise, a prompt about a branch you never updated can make successful work elsewhere look ineffective.

Then choose the customer questions you want to follow. Include the service and place a buyer would name, and distinguish an urgent job from a planned project. Keep the same wording and engine when comparing later observations. Changing the question halfway through makes the comparison harder to interpret.

Crawling is the first checkpoint

Google's recrawl documentation gives the days-to-weeks range. It also says a request does not guarantee inclusion in results. Submitting the same URL repeatedly will not accelerate crawling.

Use Search Console's URL Inspection tool to check the published URL. Look at the last crawl and indexed version, rather than relying on the date you pressed a request button. If the version Google has processed still contains the old information, an absent change in a later search answer tells you little about the quality of the new page.

For Google AI Overviews and AI Mode, a supporting page must be indexed and eligible for a search snippet, according to Google's AI features documentation. Eligibility still does not guarantee a supporting link. Check access, canonical selection and the visible answer before rewriting a page that has not reached that checkpoint.

This Google check covers Google's systems. Record ChatGPT, Gemini and Perplexity observations separately. A Google crawl date does not establish when another engine read a source or how it will select a business. The guide to engine source differences explains why each deserves its own comparison.

An appearance needs a repeatable comparison

Once you can verify the corrected source, begin comparing answer observations with your baseline. Save the prompt, engine, date, location context, answer and cited URLs. Record whether the business is named and whether the source you improved is actually cited. Treat an answer naming another branch as a different observation.

Google says AI Mode and AI Overviews can use different models and techniques, so their responses and links vary. One favorable screenshot is useful evidence of that appearance. It does not establish that visibility improved across your customer questions.

Choose a repeat schedule you can maintain. A weekly check of a fixed question set is a practical starting point, not an engine processing promise. Keep failed checks and unanswered prompts in the log. Compare like-for-like observations across more than one check, and explain changes in the sample instead of quietly removing difficult questions.

Suppose you changed the drain-service page for one branch. The next observation cites that page for a drain question in its city, but the following observation names competitors. You have evidence that the page appeared once. You still need more observations to judge whether the change made a lasting difference. That is a hypothetical example of how to read the log, not a benchmark or customer result.

Traffic and booked work need their own clock

Decide what customer action matters before interpreting traffic. An emergency service branch may care about a qualified call that reaches the right dispatcher. A remodeling branch may care about a consultation. Check the working contact route as soon as the page is live, so a broken form does not consume the observation window.

Google includes traffic from its AI features within Search Console's overall Web search performance. Its separate Search Generative AI performance report reports impressions across AI Overviews and AI Mode. Those impressions measure visibility; they do not establish which feature caused a click or a qualified enquiry. Keep observed citations, referral sessions and completed work separate. Use the AI traffic measurement guide to build the reporting view.

A buyer can discover a business in one place and contact it through another. When attribution is unclear, record the outcome as unattributed rather than assigning it to GEO. If calls rise while offers, advertising or service capacity also change, keep those changes alongside the report. They affect how confidently you can connect an outcome to the content work.

Reassess the stage that is stuck

Google's SEO Starter Guide recommends allowing a few weeks before assessing beneficial search effects and notes that some changes take months. That is guidance for Google Search, not a universal GEO waiting period. Use it to avoid reacting to every daily fluctuation while still investigating a concrete fault promptly.

If the corrected page has not been processed, investigate access and indexing. If it has been processed but relevant answers keep citing other sources, inspect those sources and compare the information they give a buyer. If the business appears but enquiries do not follow, check the offer, service fit and contact path. Waiting longer does not repair a wrong phone number.

Avoid rewriting everything at once after a disappointing check. Keep the working evidence, select the next supported change and record its live date. For several branches, a comparison with branches you did not change can help frame the question, but differences in demand and competition still limit the conclusion. A single before-and-after screenshot cannot isolate cause.

For a supplier review, ask for the dated change log, the fixed question set, the original answers and a separate customer-outcome report. A deadline should specify what will be delivered and measured. It should not promise that an independent engine will select a particular business by that date.

The free AI Visibility Grader can give you a starting snapshot for one business profile. Save that result, then use a separate, consistent question set to track broader appearances over time. The first useful result is knowing which stage needs attention; the commercial result is whether the right customer can find and choose the business.

Sources

The timing ranges above come from Google's public documentation, checked October 19, 2026. They describe crawling and Google Search changes. This article does not present a measured time-to-result study of GEO customers. The weekly check and change-log approach are editorial recommendations for evaluating your own work.

• Ask Google to recrawl your URLs, Google Search Central. Crawl timing, request limits and inclusion caveat.
• SEO Starter Guide, Google Search Central. Search-impact timing and assessment guidance.
• AI features and your website, Google Search Central. Eligibility, response variation and Web search reporting.
• Search Generative AI performance report, Google Search Console Help. AI-feature impressions and reporting scope.

Dylan Allen-Arnegård is the CEO & Co-Founder of Cheers, the local search platform for multi-location service businesses.