How to Ask Google to Reindex an Updated Page

You changed a price, rewrote some copy, or added new services to a page — but Google still shows the old version. It's frustrating, especially when customers are searching for exactly that information. The good news: you don't have to wait passively for Google to "notice" on its own. You can signal directly that the page has changed.

The honest news: nobody can guarantee Google will reindex within an hour or a day. Google decides on its own when it re-reads a page. What you can do is send it a clear signal through the official tools and make sure the page is actually eligible to be indexed. In this article I'll show you exactly which buttons to press, what to check first, and what to ignore from the "instant indexing" promises.

First, understand recrawl vs. reindex

To ask correctly, it helps to know what's actually happening.

• Recrawl: Google's bot (Googlebot) returns to the page and reads its current content.
• Reindex: Google processes what it read and updates its stored version — what people actually see in search results.

So you're not "forcing" a new result; you're asking Google to pass over the page again. The rest is up to it. How often Googlebot naturally returns varies a lot: important pages that change often get visited more frequently; a rarely updated page can go a long time between visits. That's why, when you make a meaningful change, it makes sense to signal it actively rather than just wait.

The direct method: URL Inspection in Search Console

The cleanest way to request reindexing is through Google Search Console (free). You need the site already verified there.

The steps:

• Open Search Console and select your property (your site).
• Paste the exact address of the updated page into the top bar ("Inspect any URL").
• Google shows you the current status: whether it's indexed and when it was last read.
• Click "Test live URL" to confirm the page is reachable right now.
• Click "Request indexing".

That's it. You've placed the page in a prioritization queue. You can do this for a limited number of URLs per day, so use it for changes that matter, not for every comma you tweak.

First check that the page CAN be indexed

There's no point requesting reindexing if the page technically tells Google to stay away. Before you press the button, check:

• The noindex tag: if the page has a meta robots "noindex" in its code, Google won't show it no matter how many requests you send. It has to be removed.
• The robots.txt file: if it blocks that address, Googlebot never reaches the content.
• The canonical tag: if the page points to a different URL as "canonical", Google will prefer that version. Make sure it points to itself (when appropriate).
• The response code: the page must return 200 (OK), not a strange redirect or an error.

The inspection tool tells you directly whether the page is "indexable" or not, and why. Read that message before anything else.

Help Google discover the change faster

The indexing request is the main signal, but you can strengthen discovery:

• Sitemap.xml with a modification date: if your site generates a sitemap with an updated "lastmod" field, Google gets a hint the page changed. Resubmit the sitemap in Search Console after your update.
• Internal links: add a link to the changed page from a page Google visits often (for example your homepage or a popular article). The bot follows links.
• IndexNow: a protocol used by engines like Bing for fast change notifications. Google doesn't officially use it, but for visibility in other engines it can help.

None of these "forces" anything, but together they shorten, in practice, the time until the change is noticed.

How long it takes and what NOT to do

Honestly: it can take from a few hours to a few days, sometimes longer. There's no "now" button. What slows you down: minor changes (Google treats them as unimportant), a new site with no history, or technical problems on the page.

What to avoid:

• Don't press "Request indexing" ten times for the same page — it doesn't speed anything up and burns your daily quota.
• Don't believe anyone who promises "guaranteed indexing in X minutes" or "#1 on Google". Nobody controls that.
• Don't confuse your browser cache with Google's index — clear your local cache to see the new version yourself, but that has nothing to do with what Google sees.

You can check what Google currently has by searching site:yourdomain.com on Google.

If nothing moves at all

Sometimes the problem isn't the "request" but something structural: the page loads slowly, the content is delivered only through JavaScript the bot doesn't read well, or the site has indexing errors you never noticed. In Search Console, the page indexing section shows exactly which pages are excluded and why.

At MPO Web Studio we build sites designed to be read easily by Google from the start — clean content, clear structure, a correct sitemap — and we work fully remotely, with transparent pricing. If you updated a page and it still isn't showing correctly, or you want a second opinion on the technical side, message us on WhatsApp and we'll look together, no obligation.