Technical SEO

Google Found Your Page and Skipped It. Here's Why.

July 29, 2026

Man in glasses studying a desktop monitor screen at his desk

A new physician joins the medical staff. Credentialing goes through, the file is complete, the name is in the system.

None of that produces a single referral.

Referrals start when a physician who already has standing in the practice picks up the phone and vouches for the new colleague to a patient.

Being on file and being recommended are two different events, and a lot of otherwise capable new physicians wait months for the second one.

Search Console runs that same two-step process on your website. Many practices only ever hear about the first step.

Two different messages that look like one problem

Open the Pages report in Search Console and you’ll find a status called “Discovered – currently not indexed.” Sitting right next to it is a similar-sounding one, “Crawled – currently not indexed,” and the two get treated as the same problem.

They’re different problems with different fixes.

“Crawled – currently not indexed” means Google visited the page, read it, and decided against putting it in search results.

That’s an evaluation, and it usually does point at the page itself: thin content, duplication, something on the page that didn’t earn its spot.

“Discovered – currently not indexed” is narrower, and on practice sites it’s far more common.

Google knows the URL exists, because it’s in your sitemap or another page links to it, and it hasn’t gotten around to crawling the thing yet.

There’s no verdict here. Google hasn’t read the page closely enough to render one. It looked at the URL, weighed how much it trusts the site sending it there, and decided its time was better spent somewhere else.

That’s the part practices get backwards.

The queue is priority-ordered. Nothing on your site has told Google this particular page is a priority, so it stays where it is.

Why the instinct to rewrite the page is usually wrong

The natural response to “not indexed” is to open the page and improve it. Add more copy. Rewrite the intro. Bolt on another FAQ.

For a crawled-not-indexed page that instinct is sometimes right. On a discovered page it’s aimed at the wrong target, because Google never evaluated the content in the first place, so there’s nothing about the content to fix.

You can triple the word count on a condition page and it’ll still sit there discovered-not-indexed if nothing internally is telling Google the page matters.

Google withholds crawl attention when a site hasn’t shown enough authority to justify spending it. And authority, in Google’s accounting, travels mostly through links, specifically links from pages Google already trusts.

What actually moves a page out of the queue

Finding a page for the first time is a sitemap and navigation problem.

Getting Google to prioritize a page it already knows about is something else, an internal-linking problem, and the two get confused constantly.

The pages on your site that already rank – your homepage, your most-visited service page, a condition page that’s been up for two years and gets steady traffic – carry weight with Google.

When one of those pages links to a newer or thinner page, some of that trust passes along the link.

That’s the physician referral again. The new page doesn’t have to prove itself from zero, because a page Google already believes in is vouching for it.

Most independent practice sites do the opposite by accident. The homepage links out to five or six top-level pages – Services, About, Contact – and stops there.

Then a new condition page goes up, gets added to the sitemap, and gets linked from nowhere except a blog index that itself isn’t linked from anywhere prominent.

So Google sees the URL, and nothing on the site tells Google to trust it, and it sits there discovered-not-indexed, sometimes for months.

Practical ways to pass that trust along:

Pull the Pages report in Search Console and split the two statuses apart. For anything marked “Discovered – currently not indexed,” hold off on rewriting it.

Go find the two or three pages that already rank (the Performance report will tell you, look for real impressions and clicks) and add a direct, in-body link from each of those into the stuck page.

Do that for five pages, then check the same report again in three weeks.

If the status flips to indexed and you never touched a word of the page itself, the diagnosis was right, and the pages you linked from are the ones carrying the authority on your site.

Questions practices ask about this

How do I know if my practice site actually has this problem?

Look at how long the skipped URLs have been sitting in Search Console. A page added last week showing as discovered and not indexed is normal, since crawling lags publishing. A page that's been in your sitemap six weeks or longer and still hasn't been crawled is the real signal, especially if it's a service or condition page patients would search for. Compare it with pages you published the same month that did get indexed.

Can my office handle this in house, or does it need a specialist?

Your office can handle the first pass if someone there can edit body copy in the CMS. The work is finding the pages with real impressions in the Performance report and adding a sentence from each one that links to the stuck page. Bring in a specialist when the site runs to hundreds of pages, or when the template locks body text so you can't add links inside it.

Can I just hit Request Indexing in Search Console instead?

You can, and it sometimes works for one page, but it doesn't address why the page was skipped. Request Indexing hands a single URL to a priority queue, it's capped at a few submissions a day, and a page pulled in that way can slip back out if nothing on your site points to it. Use it after you've added the links rather than in place of them.

How long after I add the internal links should I expect the status to change?

Three to six weeks is a fair point to judge whether the linking did anything, though there's no fixed window. Sites that publish regularly get revisited faster than ones sitting unchanged for months, and some pages never get picked up at all. Re-pull the whole Pages report rather than watching a single URL, since a batch of pages tends to move together.

Photograph: Jonathan Borba / Pexels