Your New Page Went Live Weeks Ago. Google Still Has Not Indexed It.

A driving instructor in Roscommon published a new page in early January: an intensive-course landing page, timed to catch New Year resolution searches before the good slots filled up. This account is a composite drawn from a pattern we see repeatedly in support tickets, not one specific business, but the mechanics play out the same way almost every time. Six weeks later, the page had not turned up in a single Google search for her business name plus "intensive course." Nor for the exact sentence sitting in her own H1.

She had not made an obvious mistake. The page loaded fine. The content was clear and specific. By any normal measure it was a good page. It just was not there, as far as Google was concerned, and a landing page nobody can find through search is not really a landing page. It is a page.

Being Live Is Not the Same as Being Found

Here is the distinction that trips up most business owners: publishing a page and Google indexing it are two separate events, and the gap between them can run from hours to weeks depending on what happens in between. Google's own Search Console documentation is direct about it. A new page needs to be discoverable before it can be crawled, which means it has to be linked from somewhere Google already knows about, or listed in a sitemap ^[1].

That sounds obvious once someone says it. It is also the single most common reason a new page goes quiet. The Roscommon instructor had shared her new page on Facebook and nowhere else. Her own website navigation did not link to it. To a human visitor arriving from social media, that made no difference at all. To Googlebot, which discovers pages largely by following links, the page effectively did not exist on her site.

If you want to check whether this is happening on your own site, the Page Indexing report in Search Console is the first place to look. We have covered how to get set up with that tool and read the report properly in our guide to Google Search Console for business owners, and it is worth ten minutes if you have never opened it.

Being indexed is also the floor, not the finish line. One large-scale study by Ahrefs, examining billions of pages, found that the overwhelming majority never receive any organic search traffic at all, and most of that comes down to backlinks and search demand rather than indexing status specifically. Worth knowing, so a business owner does not mistake "indexed" for "done."

Why New Pages Get Missed

Once an orphaned page is ruled out, a handful of conflicts show up again and again in our own diagnostics:

• No internal link path. A page only linked from an email newsletter or a social post has no route in from Googlebot's perspective.
• A stale sitemap. If the sitemap was not regenerated after deployment, the new URL is not in it, and the sitemap is one of the two ways Google finds pages it does not already know about ^[2].
• A leftover noindex tag. Pages built in a staging environment sometimes carry a noindex directive that never gets removed on the push to production. The page looks fine to a visitor and invisible to Google.
• Slow or unreliable server responses. Google explicitly ties crawl capacity to how fast and consistently a site responds. If the production environment is slow or throwing errors, Google's own documentation says the crawl limit goes down, not up ^[3].
• A canonical pointing elsewhere. If a duplicate or draft version of the page carries a canonical tag pointing to a different URL, Google may defer to that version and skip yours entirely.

I recommended a sitemap ping to a client three years ago and told them indexing would follow within a day or two. It took eleven days. I do not give indexing timelines anymore. I give ranges, and I tell people to check the report instead of trusting a promise nobody can actually control.

What Actually Moves the Needle

None of this requires guesswork. Search Console's URL Inspection tool lets a site owner request a crawl directly, and Google's own guidance confirms that request moves the URL into a priority queue rather than skipping the line altogether ^[4]. A request does not guarantee same-day indexing, and treating it as an on-demand button is where most of the frustration comes from.

The fix that resolved the Roscommon case was simpler than any Search Console request. Once the page was linked from the site's own services menu, on top of the Facebook post, Google found it through normal crawling within about a week, no manual request needed. By then the New Year rush that page was built to catch had mostly passed. The fix worked. It just worked roughly three weeks later than the traffic it was written for.

For any new page, in rough order of impact:

1. Link to it from at least one page Google already indexes, ideally the homepage or a relevant service page.
2. Verify the sitemap includes the URL and was regenerated after deployment.
3. Check the page does not carry a leftover noindex tag from a staging build.
4. Submit the URL through Search Console's inspection tool if it still has not appeared after a week or so.

The Indexing API Is Not a Shortcut Here

Google does run a genuine Indexing API, and it is tempting to assume it is the fast lane for any page. It is not. Google's own documentation scopes it specifically to job posting pages and livestream video pages, nothing else ^[5]. Using it outside that scope sits outside the terms, and misuse can lead to API access being revoked rather than pages being indexed faster. If a plugin or agency promises "instant indexing via the Indexing API" for an ordinary service page, that claim does not match what Google built the tool to do. The honest path for a normal business page is still sitemaps, internal links, and Search Console requests, in that order of usefulness.

Where Server Speed Fits In

Crawl capacity is not just a discovery mechanic, it is an operational one. Google adjusts how much it crawls based on how a server behaves under load. Fast, consistent responses keep the crawl limit healthy. Slow responses or server errors bring it down ^[3]. For a small site publishing the odd new page, that rarely matters day to day. It compounds for anyone publishing regularly, or running a large catalogue of product pages.

This is part of why the hosting stack underneath a site is not a purely cosmetic decision. Web60's managed WordPress stack runs Nginx, PHP-FPM, Redis object caching, and FastCGI page caching specifically to keep response times fast and consistent under real traffic, which is the exact condition Google's own crawl budget documentation points to as healthy. It will not fix an orphaned page with no internal links. Nothing fixes that except linking to the page. But a properly managed hosting stack removes server performance from the list of things quietly working against a business while it tries to get found.

For the fuller picture of how WordPress performance affects everything from crawl behaviour to bounce rate, our complete guide to WordPress performance for business owners goes through the caching layers and what each one actually does.

Roughly two in three enterprises in Ireland now have basic information about their goods or services on a website, according to the Central Statistics Office ^[6]. Having a website is no longer the differentiator it was a decade ago. Whether Google can actually find the pages on it increasingly is.

Conclusion

A page that is live but not indexed has not failed at marketing. It has failed at the one mechanical step before marketing starts: being findable. Link the new page from somewhere Google already knows, keep the sitemap current, check for a stray noindex tag, and treat the Search Console request as a nudge rather than a guarantee. None of it is complicated once it is on the checklist. What it takes is checking, not hoping the page turns up on its own.

Frequently Asked Questions

How long does it take for Google to index a new WordPress page?

It varies widely. Well-linked pages on established sites are sometimes indexed within hours. New or poorly linked pages can take one to two weeks, occasionally longer. If a page has not appeared after two to three weeks, check the Page Indexing report in Search Console rather than continuing to wait.

Why does Search Console say "Discovered, currently not indexed"?

This status means Google knows the page exists but has not crawled and indexed it yet, often because of limited crawl priority, thin content, or competing demands on crawl capacity elsewhere on the site. It is not usually a technical error, more a queue position.

Does submitting a sitemap guarantee my page will be indexed?

No. Google is explicit that a sitemap is a hint, not an instruction ^[2]. It helps Google discover the URL faster but does not force indexing or ranking.

Can I use Google's Indexing API to get a normal business page indexed faster?

No. The Indexing API is officially scoped to job posting and livestream video pages only ^[5]. Using it for other page types is outside its intended use and will not speed up indexing for a standard service or product page.

Does my website's speed actually affect whether Google indexes new pages?

Indirectly, yes. Google ties crawl capacity to how quickly and reliably a server responds. A consistently slow or error-prone site can see its crawl limit reduced, which affects how quickly new pages across the whole site get picked up ^[3].

What is the single most effective thing I can do to get a new page indexed?

Link to it from a page Google already has indexed, ideally the homepage or a relevant existing page. Internal links are the main way Google discovers new URLs on a known site, and they matter more than most standalone indexing tools.

Sources