Playbook 15one job, start to finish

Is my page indexed? Check with Google's URL Inspection tool

Use Search Console's URL Inspection to see if Google has a page, read why not, run the live test, and fix one thing at a time.

By Eric Snyder, founder 3 min readUpdated Oct 6, 2026
Save this guidereceiptsgroup.com/guides/is-your-page-in-google
In this guide
  1. Start here: paste this into ChatGPT or Claude
  2. Why it matters
  3. The steps
  4. Copy this
  5. Example (made up)
  6. Mistakes to avoid

After this, you can check whether Google has a specific page of yours, and know what to do if it doesn't.

Start here: paste this into ChatGPT or Claude

Not technical? Start here. Copy this prompt into ChatGPT or Claude (the free versions work) and it walks you through the whole guide, one step at a time, in plain English. It asks before it assumes anything and checks with you before anything that costs money, reaches a real customer or deletes something. The rest of the page is the same guide, written out, if you'd rather do it yourself.

PromptThe walkthrough prompt (copy all of it)
Hi! Please be my patient guide for this step-by-step guide from Receipts Group: "Check if Google actually has your new page"
The guide is here: https://receiptsgroup.com/guides/is-your-page-in-google (open it if you can; if you can't, everything you need is below).

About me: I run a small business and I'm not technical. Use plain words and short sentences.

My goal: Check whether Google has a specific page of mine, and know what to do if it doesn't.

How to help me:
1. One step at a time. For each step, tell me in a sentence what it's for and exactly what to do (where to click, what to type, who to ask). Then stop and wait until I say "done" or tell you what I see.
2. Ask before you assume anything about my business, my tools, my team or my numbers. One question at a time.
3. If you use a technical word, explain it in plain English the first time.
4. Stop and check with me before anything that costs money, sends anything to real customers, or deletes anything.
5. Use only what I tell you or show you. Never make up numbers, names, results or quotes. If something's missing, ask me.
6. If I get stuck, or something looks different from what you expected, slow down and try another way.

The steps, from the guide:
Step 1. Get into Google Search Console.
It's Google's tool for site owners. You need access to your site in it. If you don't have that, ask whoever runs your website to add you.
Step 2. Inspect the page.
Paste the page's full address (with the https:// part) into the inspection bar at the top of any Search Console screen. That's URL Inspection.
Step 3. Read the answer and the reason.
You'll see something like "URL is on Google" or "URL is not on Google." If it's not, read the explanation before you touch anything. Don't start clicking things because one of them looks technical enough to help.
Step 4. Know which answer you're reading.
That first result comes from Google's last visit, not your page as it is today. So you can fix something and still see the old answer. Annoying? Yes. A reason to change five more things? No. Click "Test live URL" to check the page right now.
Step 5. Fix the one thing it points to.
Say the reason is "noindex." That's a setting telling Google to skip the page. Fine for a test page. Bad for your roof repair page. Have your developer confirm what the page should do and fix it, then run the live test again.
Step 6. Request indexing if it makes sense.
Once the live test looks right, you can click "Request indexing." Nothing guarantees the page gets in, or ranks. There's a daily limit, so save it for pages that matter.

The button names above match Google's URL Inspection help page as of writing. If your screen looks different, that help page is the reference.

When we get to it, use the "Copy this" text from the guide (fill in the blanks and brackets with my details):
---
Hi [name],

I checked [page address] in Search Console (URL Inspection).

What it says: [URL is on Google / URL is not on Google]
The reason it gives: [paste the explanation]
Live test ("Test live URL"): [paste what it says]

This page [should / should not] be in Google.
[It's our roof repair page. Customers need to find it.]

Can you confirm the intended setting, fix only what this
reason points to, and tell me when to run the live test again?

Thanks!
---

Watch out for these (the guide's mistakes to avoid):
- Treating "it opens for me" as "it's in Google."
- Panicking when the old answer doesn't change right after a fix. Run the live test.
- Changing five things at once. Then you'll never know which one mattered.
- Reading a good live test or a request as a promise. It isn't one, for getting in or for ranking.

When we're done, give me a short recap: what we did, what I decided, and the one thing to check again later.

Start by asking me a few quick questions about my business and what I already have, one at a time. Then begin with step 1.

Why it matters

Your page opens in your browser. That doesn't mean Google has it. Your browser loves your page. Google's pickier.

You don't need to become an SEO specialist to ask where the last piece of work went. Pick one important page and walk through this before you pay for ten more.

The steps

  1. Get into Google Search Console. It's Google's tool for site owners. You need access to your site in it. If you don't have that, ask whoever runs your website to add you.
  2. Inspect the page. Paste the page's full address (with the https:// part) into the inspection bar at the top of any Search Console screen. That's URL Inspection.
  3. Read the answer and the reason. You'll see something like "URL is on Google" or "URL is not on Google." If it's not, read the explanation before you touch anything. Don't start clicking things because one of them looks technical enough to help.
  4. Know which answer you're reading. That first result comes from Google's last visit, not your page as it is today. So you can fix something and still see the old answer. Annoying? Yes. A reason to change five more things? No. Click "Test live URL" to check the page right now.
  5. Fix the one thing it points to. Say the reason is "noindex." That's a setting telling Google to skip the page. Fine for a test page. Bad for your roof repair page. Have your developer confirm what the page should do and fix it, then run the live test again.
  6. Request indexing if it makes sense. Once the live test looks right, you can click "Request indexing." Nothing guarantees the page gets in, or ranks. There's a daily limit, so save it for pages that matter.

The button names above match Google's URL Inspection help page as of writing. If your screen looks different, that help page is the reference.

Copy this

Send this to your developer once you've run the inspection:

Copy this
Hi [name],

I checked [page address] in Search Console (URL Inspection).

What it says: [URL is on Google / URL is not on Google]
The reason it gives: [paste the explanation]
Live test ("Test live URL"): [paste what it says]

This page [should / should not] be in Google.
[It's our roof repair page. Customers need to find it.]

Can you confirm the intended setting, fix only what this
reason points to, and tell me when to run the live test again?

Thanks!

Example (made up)

Bayside Roofing, a fictional company, publishes a new roof repair page. It opens fine. The owner pastes it into URL Inspection: "URL is not on Google," and the explanation points to noindex.

Turns out the page was copied from a test page that was set to noindex on purpose. Right for the test page. Wrong for this one. The developer confirms that and removes the setting.

The owner checks again and still sees "not on Google." Plot twist: that's Google's last visit. The live test no longer shows the noindex problem. He clicks "Request indexing," then checks back later instead of changing five more things in the meantime. Whether it gets in is still Google's call.

Mistakes to avoid

  • Treating "it opens for me" as "it's in Google."
  • Panicking when the old answer doesn't change right after a fix. Run the live test.
  • Changing five things at once. Then you'll never know which one mattered.
  • Reading a good live test or a request as a promise. It isn't one, for getting in or for ranking.

You can see the page. Lovely. Now let's see if your customers can.

Rather skip the setup?

Want help setting this up?

Receipts Group builds these systems. Thirty minutes with Eric tells you which piece is worth building first, or that none of them are. The guides stay free either way.

Keep going

more free guides