Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
If an important page is missing from Google Search, first find out whether Google has discovered it, can crawl it, and considers it eligible for indexing. Those are separate stages: crawling fetches a URL; indexing evaluates it for possible inclusion in Google’s index. A page can be crawled without being indexed or appearing in search results.
Use Search Console’s reports and URL Inspection to identify the specific issue, then fix that issue rather than repeatedly requesting indexing. Google does not guarantee that a page will be indexed or set a fixed timetable for doing so.
Start by identifying what “not indexed” means
Google’s guidance groups the reasons a page may be absent into three broad possibilities: Google has not found the URL, cannot access it, or does not consider it sufficiently valuable or in demand to include. A successful crawl therefore does not guarantee indexing. See Google’s crawling troubleshooting guidance and its technical requirements.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Before changing anything, check the exact URL you care about. A site-wide impression that “Google isn’t indexing the site” can mask a single blocked section, an isolated server problem, or a set of duplicate URLs competing with one another.
#1 Best Overall
- Keep track of everything from attendance to test scores
- Spiral bound
- Measures 8-1/2" x 11"
Use the right diagnostic for the question
| Tool or setting | What it helps diagnose or do | Important limitation |
|---|---|---|
| Page Indexing report in Search Console | Review reported indexing states across pages. | It does not replace checking the exact URL. |
| Crawl Stats report in Search Console | Look for crawl patterns and host-availability issues. | It can show different information from the Page Indexing report; use both when relevant. |
| URL Inspection in Search Console | Inspect an individual URL and, when appropriate, request recrawling. | Requires access to the Search Console property. Repeated requests do not make Google crawl faster. |
| Server logs | Check whether and when Googlebot requested particular URLs, alongside response codes and server behavior. | Logs show requests, not whether Google ultimately indexed a page. |
robots.txt |
Controls whether crawlers can access URL paths. | It is not a reliable way to remove a URL from Search; Google needs to crawl a page to read a noindex instruction. |
| Sitemap | Helps Google discover URLs intended for discovery. | Submission is a hint, not a guarantee of crawling or indexing. |
Google explains the distinction between crawling and indexing, and the roles of its reports, in its troubleshooting guide. Its recrawl instructions cover URL Inspection and sitemap submission.
Follow this troubleshooting sequence
- Check the reports. In Google Search Console, open the Page Indexing report to review page-level indexing states. Check Crawl Stats too if the issue may involve crawl activity or host availability; the reports do not necessarily show the same information.
- Inspect the exact URL. Use URL Inspection in the Search Console property that covers the page. Review the information Google provides and request recrawling if you have made a relevant fix. Submitting repeated requests does not speed up crawling.
- Confirm Google can reach the page. Review
robots.txt, authentication, access controls, and whether the page’s important rendering resources are available. A crawl block can prevent Google from fetching the page. - Check the response and rendered content. Google says pages served with HTTP 200 and indexable content can meet its technical requirements, subject to its policies. Look at what the rendered page actually shows: empty output, an error, missing critical resources, or content suggesting the page is gone can undermine the intended result.
- Check server health. Review logs, response times, host availability, and spikes in 5xx or 429 responses. Google says those responses can cause crawlers to slow down; persistent server errors can eventually result in URLs being removed from the index. Details are in Google’s documentation on HTTP status codes and its crawlers.
- Improve discovery. Keep the sitemap current, include URLs you want discovered, use accurate
<lastmod>values when content changes, and link to important pages from crawlable pages on your site. - Check duplicates and site changes. Look for unintended
noindexdirectives, conflicting crawl blocks, incorrect redirects, and outdated sitemap URLs—especially after a migration. - Monitor the result. After fixing the cause, allow time for Google to recrawl and evaluate the page. Google says recrawling can take from a few days to a few weeks; requesting it does not guarantee inclusion. Its recrawl guidance also cautions that same-day discovery is not a realistic expectation for most sites.
Match the fix to the cause
Google may not know the URL
Add the page to a current sitemap and link to it from relevant, crawlable pages. For several URLs, submit a sitemap; for a small number of specific URLs, use URL Inspection. A sitemap helps Google learn about URLs but does not compel indexing. As Google puts it, “Keep in mind that while a sitemap file can help us learn about your site, it does not guarantee indexing or increase your site’s ranking.” See its FAQ on crawling and indexing.
A crawl block or access restriction prevents fetching
Check robots.txt and remove an unintended rule that blocks the page. Also check whether a login, firewall, or other access control prevents Google from reaching it. If your goal is to keep a page out of Search, do not block crawling as a substitute for noindex: Google must be able to crawl the page to read a robots meta directive or an X-Robots-Tag header. Google documents the behavior in its robots meta tag specifications.
Free tools Windows power users keep installed
One-click scans. No signup required.
The URL returns an error or the server is struggling
Make sure the URL returns the status intended for its content. Google does not index a 4xx URL. 5xx and 429 responses can lead to temporary crawl slowdowns; persistent server errors can have more lasting consequences. Resolve overload, throttling, or application failures, then inspect the URL and server logs again. Refer to Google’s status-code documentation.
The page is a soft 404
A soft 404 is a page that appears to say its content is missing but returns HTTP 200. If the content is gone and has no replacement, return 404 or 410. If it moved, redirect to the relevant replacement. If it still exists, correct the rendering or content problem that makes it appear missing.
Duplicate URLs compete for the same content
Consolidate duplicate versions and establish which URL should represent the content. Check that redirects and canonical signals point to the intended destination, and avoid leaving multiple unnecessary variants discoverable. For example, if a site has moved to a new domain, Google recommends checking redirects and updating the sitemap as part of the move; see Google’s site-move guidance. Its crawling FAQ also identifies a 301 redirect as a way to direct users and crawlers to a preferred domain.
A migration left outdated signals behind
After a move, confirm old URLs redirect to their corresponding new destinations rather than to an unrelated page, remove unintended crawl blocks or noindex directives, and submit an updated sitemap containing the new URLs. Search Console can help diagnose the move, and Google’s migration guide discusses redirect checks and tools such as Screaming Frog for examining redirects.
When crawl budget matters—and when it probably doesn’t
Google defines crawl budget in terms of the URLs its systems can and want to crawl. Crawl capacity reflects the ability to fetch pages without overwhelming a host; crawl demand reflects Google’s interest in URLs. A missing page is not automatically a crawl-budget problem.
Google describes its detailed crawl-budget guidance as primarily aimed at sites with at least 1 million unique pages that change moderately often, or at least 10,000 pages that change very rapidly. These are rough audience-classification estimates, not exact cutoffs or research findings. For most sites, keeping a sitemap current and checking the Page Indexing report routinely are more useful starting points. For larger or rapidly changing sites, reduce URL traps and unnecessary duplicate variants, shorten redirect chains, improve response and rendering speed, and prioritize valuable, unique pages. See Google’s crawl-budget guide.
How long does indexing take?
Google says crawling can take anywhere from a few days to a few weeks. That is a general range, not a promise for a particular URL: a recrawl request does not guarantee that Google will crawl the page promptly or include it in Search. Once you have addressed a technical issue, use URL Inspection and the indexing reports to monitor rather than resubmitting the same request repeatedly. Google’s wording is direct: “Crawling can take anywhere from a few days to a few weeks.”
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errors
