Church Website Pages Not Showing in Google: An Indexing Checklist
A church site's pages can be uncrawled, crawled but unindexed, or indexed with no impressions. Here is what a volunteer team can verify in Search Console, and what a paid indexing service can and cannot do.
Brand promotion: this article introduces Guangsuan's GSI Google indexing promotion service. It is a vendor introduction, not an independent review or a commissioned evaluation.
Consider a congregation that rebuilt its website on a new theme. A visitor opens the page in a browser and it loads; a pastor pastes the address into a message and it works. Weeks later, searching for the church by name plus a phrase from its own homepage returns nothing. In that situation the first question is not "who do we pay to fix this?" It is "which of three different problems are we actually dealing with?"
Those three problems need different evidence and lead to different decisions, and only one of them is something a paid service can act on. This guide walks through the checks a volunteer team can run without a developer, the pages worth submitting first on a small church site, and what a URL-scale indexing service does and does not promise.
Short answer with conditions
Discovery, crawling, indexing and showing up in results are four separate stages. A page can pass the first three and still appear for nothing, because appearing for a query depends on relevance and competition, not on index state alone.
Before anyone quotes you a price, confirm three things about the exact URL. It is publicly reachable and returns the real page, not a login wall or an empty template. Nothing in the site rules asks Google to leave it out of results. And Google has a path to find it, through an ordinary crawlable internal link or a current sitemap. If any of those three fails, fix it first, because no amount of crawl activity repairs a blocked, excluded or mis-pointed page. If all three pass and Search Console still shows Google has not fetched the URL, promoting discovery and crawling is a reasonable next step. Whether and when the URL is indexed stays Google's decision.
Three problems that all get called not indexed
Search Console's own documentation and Guangsuan's indexing notes describe the same three situations, and keeping them apart is what stops a team from buying crawl activity for a content or configuration problem.
1. Google has not crawled the page
Google knows the URL exists but has not fetched it. In URL Inspection this appears as a discovered, currently not indexed state, with no crawl date yet. The things to look at are the paths into the page: whether the sitemap actually contains that address, whether an ordinary link leads to it, and whether the server is stable and the site is unusually large. Guangsuan's own indexing guidance names the same three checks, site links, server stability and page scale, as the discovery-side items worth reviewing.
2. Google crawled it and did not index it
The page was fetched and read, and still did not go into the index. This one points at the page rather than at the entry path: whether the content earns its place, whether it duplicates another page, which canonical Google selected, and whether the page is indexable at all. The label by itself is not a verdict about your writing. Google's documentation treats not indexed as a status that can follow either from an indexing error or from a legitimate reason such as a robots.txt block or a duplicate page, so read the label as a pointer to the next check.
3. It is indexed and still shows up for nothing
Here the indexing work is finished, and the problem is relevance and competition. Google's documentation is also blunt about expectations: you should not expect every URL on a site to be indexed, only the canonical versions, and being indexed makes a page eligible to appear rather than certain to appear for any given query. Before treating this as an indexing problem, check whether the page's title, opening paragraph and headings actually answer the question someone types. Keep the measurement honest too: an impressions figure in Search Console counts queries Google served to your own pages, not the size of the market for those queries.
What a volunteer can check this weekend
None of the steps below need a developer, a plugin or a budget. Work through them in order, because each one is quick and each one removes a possible cause.
Step 1: Fetch the exact page while signed out
Open the address in a private window, not the editor preview and not a shortened link. Record the final address after any redirect, and confirm the page text itself comes back in the delivered HTML rather than appearing only after a script runs. A page that returns a success status with a login wall, a challenge screen or an empty template has not been delivered to Google either. Check the page source for a meta robots directive and check the response headers for X-Robots-Tag. A correct setting in the admin panel does not prove the public response is clean, because page, server and CDN caches can keep serving the older instruction for a while.
Step 2: Read the robots rule that matches that path
Two different controls are constantly confused. robots.txt mainly controls crawling, and it cannot reliably stop an already-discovered URL from appearing in results. A noindex directive controls indexing, and Google has to be able to read the page to see it. If a page is blocked in robots.txt and you rely on a noindex tag, the exclusion is only half applied, because Google cannot fetch the page to read the tag. When you read robots.txt, check the rule that matches the specific path and the user agent involved, not the file as a whole.
Step 3: Check who is outputting noindex
On WordPress, open Settings, then Reading, and look at the option that asks search engines not to index the site. Then check the SEO plugin's per-post and post-type settings, which are separate switches. After a rebuild, the suspects worth checking are a staging-era setting that was never turned off, a post type excluded from indexing, and a template that still carries the directive. Compare a newly published page with an older one: if several pages share the same noindex or the same fetch error, look at the shared setting first; if only one URL is odd, look at that page's own content, canonical and configuration.
Step 4: Find the sitemap that is actually in effect
Do not assume the file you submitted is the file being served. A theme, a plugin and an old static file can each maintain a different version, so open the exact address you submitted in a signed-out browser and confirm it returns XML rather than a login page or an error page served with a friendly status. Then check its contents, not just its status. It should list the final canonical addresses you want in search, with absolute URLs whose protocol, host, case and trailing slash match the live pages, and without redirects, 404s, duplicate variants or noindexed pages left in as normal targets. Keep one current file, because a second older file still advertised by a plugin or by robots.txt splits the signal. Two format limits are worth knowing: a single uncompressed file should stay within 50 MB and 50,000 URLs, and Google ignores priority and changefreq fields, so a lastmod date should only move when the page genuinely changed. The sitemap file itself may carry a noindex directive, which is normal, because it is a list for search engines to read rather than a page that needs to appear in results.
Step 5: Check internal links and the canonical
Every page you want found should have at least one ordinary crawlable link pointing to it from elsewhere on the site. An address that exists only in the sitemap has a weaker path in. Then compare the canonical you declared with the canonical Google selected, and use canonical only for duplicate or near-duplicate content. Pointing a unique page, such as a sermons archive or a giving page, at the homepage tells Google the page you care about is a copy of the home page, and it stops treating the original as a target.
Illustration: one symptom, three different jobs
The following is a hypothetical example used to show the method. It is not a client site and not a measured result. A congregation rebuilds its site, and a new What to Expect on Sunday page does not appear in a search for the church name, while the homepage does.
- Case one: the page returns its own text, but the declared canonical points to the homepage. Google is being directed to a different address, so the page will not be indexed as itself. The work is the canonical, not crawl volume.
- Case two: the page returns its own text, but a robots.txt rule blocks that path and a noindex tag is also set. Google cannot fetch the page, so it never reads the tag, and the URL stays in the discovered state. Remove the rule, then decide deliberately whether the page should carry noindex at all.
- Case three: the page returns its own text, carries no noindex, is linked from the homepage and is listed in the sitemap, and Search Console shows it as crawled but not indexed while a near-identical copy of the same page is indexed under another address. The work is to consolidate the two and point the canonical at the one you want to keep.
Three pages, one symptom, three different jobs. That is the whole argument for checking before paying.
Write down the before state
Before changing anything, save one row per important page. Without it, the only comparison available later is an impression that things look better.
| Field | What to record |
|---|---|
| URL | The exact address, including case, trailing slash and meaningful parameters |
| Page type | Homepage, first-visit page, service times, giving, sermons index, contact |
| Final status | The response after redirects, and the final destination |
| Canonical | The one you declared, and the one Google selected if they differ |
| Indexability | The robots rule for that path, any meta robots tag or X-Robots-Tag header, and any login requirement |
| Search Console state | Status and last crawl date, together with the date you read them |
| Last substantive change | The date of the last real edit, not the last save |
Which pages to submit first on a small church site
Build the list from the pages a visitor actually needs: the page a first-time visitor lands on, the service times and location page, the giving or contact page, and the index of sermons or events. These are the pages that carry a question someone would type into a search box. Submit that short list in priority order rather than the whole site, and attach the purpose of each page to its row so whoever does the work can tell a thin announcement page from the page your congregation actually needs to find.
Two habits make the list work. Upload in one small batch instead of piling URLs in, because the fewer URLs you submit the more concentrated the resources are, and split larger sets into batches by page priority rather than pushing volume blindly. Second, record what each page is for. A page that only lists a date is a weak target; the page that explains what happens on a Sunday morning, where to park and what to do with children is the one worth a crawl.
One important limit sits before any of this. URLs should be reachable and free of obvious crawl blocks, noindex directives, redirects or duplicate-canonical problems before they are submitted for indexing promotion. If a page is blocked, excluded or pointed at another address, the page itself is the work.
What a URL-scale indexing service can and cannot do
Guangsuan's GSI, its own name for Google Speed Indexing, is not a Google product, an official partnership or a priority indexing permission. The published description is that the service works around the URLs you submit to encourage discovery and crawling, supported by the company's GPC crawler pool and related link structures. That description sets a hard boundary, and it is worth reading before you pay:
- It can address whether Google finds and fetches pages that are already reachable and indexable.
- It does not decide whether a URL is indexed, when it is indexed, or how long it stays indexed. Those remain Google's judgement.
- It does not bypass Google's quality judgement, and it does not replace content, duplicate, canonical or access repairs.
- Submission is not indexing, and indexing is not ranking. Being indexed makes a page eligible to appear; it does not produce impressions, clicks or enquiries.
- Guangsuan's published scope states plainly that it does not promise fixed rankings, index counts or enquiry numbers.
- The periods published alongside its URL-volume packages are reference ranges affected by page quality, site state and Google's processing, not fixed completion dates.
Guangsuan's monthly crawler-pool product covers the same ground for larger volumes and states the same limit: it solves discovery and crawling and does not replace page quality or on-site technical work. The pool figures in those package tiers are nominal configuration rather than current measured values, so they cannot be converted into Googlebot visits or indexed pages for your site. Google's own Indexing API is documented for job-posting pages and for broadcast video pages, so an ordinary church page is not covered by it, and a current sitemap, real internal links and normal recrawling remain the documented route.
Where the fix is a template, plugin or robots.txt rewrite, that is a development job rather than a crawl job. Guangsuan's one-time on-site technical service is described as covering access status, robots, noindex, canonical, XML sitemaps, redirects and dead links, delivered as diagnosis, changes and a re-check.
How to check whether anything changed
With access to the property, the verification route is Search Console's URL Inspection tool together with the page indexing report. If nobody on the team holds that access, agree before the work starts how results will be checked, because a third party without access cannot read those reports.
Read the before state you saved, then read both the origin response and the public response after each change, and watch over weeks rather than days. Report three things separately: whether URLs moved from discovered to crawled, whether they became indexed, and whether they began to earn impressions and clicks. The first can happen without the second, and the second without the third.
Two habits waste a Saturday: resubmitting a sitemap that has not changed, and repeatedly asking Google to crawl the same URL. Google recrawls pages automatically, so a recrawl request is worth making only after an important change that Google seems to have missed for a week or more. For a small set of important new or substantially changed pages, a request from URL Inspection is reasonable; for many URLs, use the sitemap. Repeating either one does not make Google crawl faster.
Where Guangsuan fits
If your pages are reachable, indexable and linked, and Search Console still shows Google has not fetched the URLs you care about, Guangsuan publishes its GSI Google indexing service page with the flow, the URL conditions, the volume tiers, the verification route and the stated limits. For teams who would rather run a monthly pool than a per-project submission, the same company describes its GPC crawler pool as a discovery and crawling layer with its own stated boundaries. Both pages are worth reading before a call, because both say the same thing this article does: promotion covers discovery and crawling, and Google makes the indexing decision. Google's own Search Console documentation on the page indexing report is the reference for the status labels used above.
Frequently asked questions
Do we need to resubmit the sitemap every week?
No. If the file was read successfully and nothing in it changed, resubmitting repairs nothing. Fix the page or the access problem that the URL Inspection state points at, and let normal recrawling continue.
The page is indexed but never appears for our church name. Is that an indexing problem?
Not mainly. Once a URL is indexed, appearing for a query depends on relevance, competition and how results are assembled for that searcher. Check whether the page answers that question in its title, opening paragraph and headings, and whether another page on the site already covers the same intent.
Is there an API that will index our pages for us?
Google documents the Indexing API for job-posting pages and for broadcast video pages. Ordinary church pages fall outside it, so crawlable internal links, a current sitemap and a recrawl request for a few important URLs remain the documented route.
Does a submission guarantee the page will be indexed?
No. The service promotes discovery and crawling around the URLs submitted. Whether a URL is indexed, when, and for how long it stays indexed is Google's decision, and Guangsuan's published scope does not promise fixed rankings, index counts or enquiry numbers.
Can a volunteer team do this part on their own?
Most of it, yes. Fetching a URL while signed out, reading the robots rule for that path, checking the site's own indexing switch, reading the sitemap you actually serve, and confirming internal links and canonicals are all doable in a browser. What usually needs a developer is a template or plugin change, a robots.txt rewrite, or a server-level fix after a rebuild.
One church-website idea in your inbox every Tuesday morning.
Join 38,500 pastors and comms directors who get the screenshot, the copy, and the template — ready to ship by Sunday.