Check the pages behind an answer

Follow the evidence

Start from the exact link in the recorded answer. Save the address and the passage before assuming the page explains the whole reply.

If the page won't load, record that. Don't fill the gap with a guess about what it used to say.

Copy the address from the saved answer itself, not from a fresh search for the page. A similar page on the same site is not the same evidence.

If the answer gives no link at all, note that. You can still check the claim, but there is no page to trace.

A delivery page might give a timing while another policy lists exceptions. Read both before you decide something is missing or wrong.

Try it on a phone. A customer should be able to read the detail without signing in or tapping something that doesn't work.

Note the date the page gives, if it gives one. An undated page with old details is worth checking before a recently updated one.

Check the page in a private window as well. A signed-in view can show details a customer never sees.

Compare one fact at a time

Compare like with like, such as one location's opening time on a particular day. A general company page may describe a different service.

Decide where the problem sits, in the AI answer, on your page or on someone else's page. Each needs a different fix.

Use your record as it stood on the day of the answer. If your price changed after that, the answer may have been right at the time.

Note which of the three places holds the problem, and say how you know. Another reviewer should reach the same conclusion.

Is the source your own page, another publisher or a page with no clear owner? Who can correct it depends on the answer.

If you can't find the statement on the page, say so. A link nearby doesn't mean the page backs the claim.

If several statements need checking, take them one at a time. Mixing them makes it harder to see which source caused which error.

Choose the right route for a correction

For your own page, prepare a change for the website owner. For another site's page, use its published correction process if it has one.

Keep the request factual and limited to the wrong detail. Asking doesn't mean the page will change.

If the page belongs to a directory or listing service, look for a route to claim or update your listing. Record what you find rather than assuming one exists.

If the error is in the AI answer alone and the sources are right, use the assistant's own feedback option. Record that you used it and when.

Leave a useful record

Keep the old text, the proposed text, the source and the person responsible. Note the date any change goes live.

Check again after publication. If a page is down, save it as unavailable and don't mark it corrected.

Give each correction a status, such as proposed, published, requested or declined. A status makes it clear what still needs doing and who is waiting on whom.

Store the record where the person responsible can find it. A correction nobody can trace is hard to check later.

Pages with no clear owner

Look for a publisher and a correction route. An unlabelled page needs further checking before you treat it as a business record.

A copied page may repeat your old wording exactly. Compare it with your earlier versions to see roughly when it was taken.

If you find no route, record the page as unresolved with the date you looked. Don't spend more time on it than the claim deserves.

Put your effort where you have control. A clear, current page of your own gives any reader a better source to compare against.

Check unresolved pages again at your next review. Some get taken down, and some gain an owner you can contact.

Check what a crawler receives, not just what you see

A detail you can see in a browser may not be in the page a crawler reads. It might load only after a click, sit inside an image or depend on a script.

Google lists keeping important content available in text among its basics for AI features in Search. A price shown only inside an image doesn't meet that.

If a detail sits in a downloadable document, check that the page text states it too. A customer reading on a phone may never open the file.

If you manage the site in Search Console, the URL Inspection tool can show a rendered version of a page. It also shows the HTML Google received when it crawled.

The tool separates the indexed version from a live test. Google says the indexed result reflects the version it last saw, which may differ from the page today.

Use what you find to brief your website maintainer. Keep the fix to the specific detail that is missing from the text.

• Google guidance on AI features
• Search Console Help, URL Inspection tool

Find every copy of the fact

A detail often appears in more than one place. Check your footer, contact page, booking pages, downloadable documents and old news posts.

Check any structured data on the page as well. Google lists structured data that matches the visible text among its basics, and its policies say not to mark up hidden content.

Then check your Business Profile, which Google lists among the same basics. Its Business Profile help says complete details tell customers where you are and when to visit.

Change every copy in the same round. A page fixed while the footer still carries the old detail leaves two versions for any reader.

Keep a list of where each key fact lives. The next correction then starts from that list rather than a search.

• Google guidance on AI features
• Google structured data policies
• Google Business Profile guidance

Handle pages you don't own

You can prepare a factual correction request, but the publisher controls the edit. Record a request as a request until the page changes.

Note what you asked and when. Don't assume the request was accepted, and don't mark the page corrected until you've looked.

A publisher may decline or take a while. Treat that as a separate task from changes to your own site, because they have different owners.

Ask for one change at a time and keep the request polite. Quote the wrong passage, give the correct detail and link to the page where you publish it.

Write a correction request someone can act on

Start with the page address and the exact passage, quoted word for word. The publisher should be able to find it without searching.

Give the correct detail in one sentence and link to the page where you publish it. Say who you are and why you can confirm the fact.

Ask for one change per request. A list of unrelated complaints is harder to act on and easier to set aside.

Keep the tone factual. Thank them, give a way to reach you and save a copy of what you sent.

Note where you sent it, such as a form, an email address or a listing dashboard. Some publishers reply only through the route you used.

Treat a customer review differently. The opinion belongs to the customer, so a public reply that states the facts is usually the fitting route.

When another site's page has changed or gone

Sometimes the page that carried a wrong detail has been changed or removed, but Google Search still has the old version. Google offers a Refresh Outdated Content tool for this case.

Its help page says the tool is for pages you don't own. For your own pages, it points you to a recrawl request instead.

It also says the tool only updates Google's search result. It doesn't remove or change the page on the web, and a request can take a few days to process.

Find the right address before you start. The help page asks you to copy the link from the Google Search result, not from the page in your browser.

The tool concerns Google Search results only. Keep checking other assistants' answers separately, and record each request with its date and status.

• Search Console Help, Refresh Outdated Content tool

Check the correction in public

Once your owner publishes a change, open the public address again. Check redirects, the visible text and any other page that repeats the fact.

Keep a short before and after record with the publication date. A draft in an editing tool shows nothing about what customers can read.

If an answer still repeats the old detail, save a new recording. Report the page correction and the answer separately.

Search your own site for the old detail as well. An old news post or a downloadable price list can repeat what you've just corrected.

Then record a fresh answer to the same question, with the same set-up as before. Keep it beside the earlier one, not in its place.

After publishing, ask Google to crawl the page again

Once a corrected page is live, you can ask Google to crawl it again. Its guidance gives two routes, depending on how many pages changed.

For a few addresses, use the URL Inspection tool in Search Console. You need to be an owner or full user of the property to request indexing.

For many addresses, submit a sitemap. Google notes that hosted platforms often submit new content automatically, so check yours first.

Google says crawling can take from a few days to a few weeks, and a request doesn't mean the page will be included. Asking again for the same address won't speed it up.

Record the date of the request beside the correction. It helps explain any gap between publishing and the next answer you record.

• Google Search Central, Ask Google to recrawl your URLs
• Search Console Help, URL Inspection tool

Sources and method

A Carqo review method. Provider statements link to the relevant documentation.

• Google guidance on AI features Link checked 4 November 2026
• Search Console Help, URL Inspection tool Link checked 4 November 2026
• Google structured data policies Link checked 4 November 2026
• Google Business Profile guidance Link checked 13 October 2026
• Search Console Help, Refresh Outdated Content tool Link checked 29 October 2026
• Google Search Central, Ask Google to recrawl your URLs Link checked 29 October 2026

Suggest a correction