Can Google access and index your pages?
Separate access, crawling and indexing issues, and know when to ask a developer for help.
A page that customers can open is not necessarily readable or indexable by Google. Check its actual status before changing settings.
The basics to remember
- Search Console is Google’s website search monitoring tool. URL Inspection shows a page’s indexing information and can test its current accessibility.
- robots.txt is a rules file telling automated programs which areas they may access. noindex is a marker asking search engines not to index a page. They have different purposes.
- A sitemap lists important URLs to help discovery. Public pages also need to work and offer readable content. Meeting these requirements does not guarantee indexing.
See Google: URL Inspection and Google: Blocking indexing .
Check specific addresses and actual content
robots.txt rules match URL paths. After adding a language, check actual addresses such
as
/zh/service
. Rules for
/service
do not automatically cover every translation. Ask the developer to maintain and test
actual language paths. Blocking crawling and preventing indexing are separate actions,
not substitutes. See
Google: Creating robots.txt
.
At publication, check important pages for accidentally retained noindex markers. Unfinished content can remain unindexed, but private material also needs login or other access restrictions; noindex is not protection. Open the sitemap to check for error pages, testing domains or dead addresses, and check its processing in Search Console. See Google: Building and submitting sitemaps .
HTML is the document format browsers receive to display pages. A developer can check whether the initial HTML response contains the main content. If not, inspect what Google obtains after running scripts. JavaScript is the scripting language used for interactions; Google can process many scripted pages. Missing text in source code alone does not prove a page cannot be indexed. Use URL Inspection to test the rendered result and locate missing content. See Google: JavaScript SEO basics .
Pages may be generated from templates and data or prepared in advance. Google does not require a physical HTML file with the same name on the server. Check whether each public URL returns the correct body, title and links and is accessible. These delivery checks are more reliable than judging SEO from a framework’s name.
Open public pages while logged out too. If only logged-in users can open them, or only some people get errors, check restrictions, configuration and official outage information before identifying the affected range. One error does not prove an entire service is blocked or must move.
An XML sitemap lists URLs in a defined file format. Use complete production addresses,
such as
https://example.com/service
, not just
/service
. It differs from a directory for readers; both need real, accessible destinations. See
Google: Building sitemaps
.
Typing
site:your-domain
in Google restricts results to a website; adding a path narrows them further. This is
not a complete indexing list. A missing result alone does not establish that a page is
unindexed. Investigate with URL Inspection. See
Google: The site operator
.
If the homepage is not indexed, check a few important inner pages too. One page cannot represent the whole site. Ordinary internal and external links and sitemaps can help Google discover addresses; a request is one method and does not guarantee next-day indexing. Sites accepting public submissions should also review content and monitor anomalies to prevent spam and manufactured links. See Google: Preventing user-generated spam .
Walk through an example
| Check | Before (hypothetical) | After or appropriate action |
|---|---|---|
| Access | Page returns an error | Repair and check again |
| Indexing setting | noindex added accidentally | Remove after confirming it should be public |
| Internal entry | No links to the page | Link from relevant pages |
Suppose a live service page retains a noindex marker used during testing. The developer confirms it should be public, then removes the marker. Its indexing status may change after Google reads it again. Do not do this to private pages.
Common misunderstandings
Do not block a page with robots.txt and expect Google to read its noindex marker; Google may not see it. Indexing does not need to reach 100%, because duplicates or private pages may not belong in search.
See also Google: robots.txt and Google: Sitemaps .
Read next
- How does Google find your business website?
- Search and discovery: all modules
- SiteMonk technical SEO standards
Official sources checked on October 2, 2026. Tables and scenarios are illustrative, not real business results.