The Gospel on Blogger but Google ignores it.

I Published the Gospel on Blogger. Bing Found It. Why Did Google Leave So Much Behind?

The firsthand Blogger account behind the “Does Google Hate Jesus?” investigation

I have pressed Blogger’s orange Publish button hundreds of times. Each time, the platform did what it promised to do. It created a public page, assigned that page a permanent address, added the article to the archive, and made the words available to anyone who had the link.

The strange part came afterward. A page could be public without becoming discoverable. It could exist on a platform owned by Google, appear in Blogger’s own archive, open normally in a browser, and still be remarkably difficult to locate through Google Search. That is the practical problem behind my larger investigation, Does Google Hate Jesus? A documented investigation into why my Gospel library is so hard to find.

This Blogger article is not a shortened copy of that investigation. It is the view from inside the publishing process. It is about what I actually did, what I expected to happen, what did not happen, what I tried to repair, and why I am preserving this Blogger library while qualified people examine it.

The campaign title asks a deliberately provocative question: Does Google hate Jesus?

The question is not a declaration that Google discriminates against Christians. I have not proven that. I have not seen an internal Google instruction aimed at Gospel content. I cannot tell you that a human being at Google decided to hide my work. The problem may have nothing to do with religious hostility. It may involve crawling, indexing choices, Blogger’s structure, my publishing volume, repeated template elements, cross-platform similarity, canonicalization, quality classification, or a technical cause I have not identified.

But the absence of a proven motive does not erase the practical condition. I built a large public Gospel and New Testament library on Blogger. Bing appears to find and index at least some of that material. Google has left much of it difficult to discover, and at one documented point in my private Search Console account, the gap was extreme.

I want to understand why.

The Blogger Button Worked

When a publisher says a page is “not showing up,” people sometimes assume the page was never published correctly. That is not what happened here.

The Douglas Vandergraph Christian Encouragement library on Blogger is public. Its homepage opens. Its archive can be browsed. Its posts have individual URLs. Its pages display titles, publication dates, article bodies, navigation, and links. A reader who already possesses a direct URL can open the page without asking for permission or signing into an account.

In the narrowest sense, Blogger completed its job. It hosted the pages.

That is what makes the next part confusing. Publishing and discovery are not the same thing. Blogger can successfully place an article on the public web without Google Search deciding to include that article in its searchable index. The fact that Blogger and Google belong to the same corporate ecosystem does not change that. Blogger publishing does not come with a promise of Google indexing.

I understand that distinction now more clearly than I did when I began. I also understand why ordinary publishers are confused by it.

Blogger presents itself as an easy way to publish on the web. You write, format, add links, select a title, and press Publish. The result looks complete. It is natural to assume that Google, the company behind both Blogger and Google Search, will at least recognize and process the page efficiently.

That assumption may be understandable, but it is not a guarantee.

A page can live on Google’s platform while remaining outside Google’s index. Google’s explanation of how Search works separates discovery, crawling, processing, indexing, and serving. A sitemap can tell Google that the URL exists without causing Google to crawl or store it. A public page can satisfy basic technical requirements without being selected. A page can even be crawled and still be left out.

Those facts do not automatically mean anything improper happened. They do mean that the publishing experience and the search experience can become radically disconnected.

I Was Not Publishing Empty Pages

The library at the center of this investigation is not made of blank entries, one-paragraph placeholders, or pages created only to point somewhere else.

The articles include substantial Gospel commentary, New Testament chapter explanations, Christian encouragement, faith-based stories, and practical discussions of Scripture. The project grew from a clear mission: make biblical encouragement available to people facing real struggles and build a connected public library that could outlast a single social post or video.

The four representative Gospel pages selected for this campaign demonstrate what I mean.

The Matthew example, When Jesus Sat Down and Heaven Stood Up: A Heart-Changing Journey Through Matthew 5, is a substantial article about the Sermon on the Mount. It discusses the Beatitudes, mercy, righteousness, light, reconciliation, and the demanding way of life Jesus described.

The Mark example, The Night Love Learned the Cost of Staying, walks through Mark 14 and the movement toward betrayal, Gethsemane, arrest, failure, and costly love.

The Luke example, The Morning That Changed the World, explores Luke 24, the empty tomb, the road to Emmaus, the risen Jesus, and the moment grief began turning into witness.

The John example, A Midnight Conversation That Changed Eternity: The Truth Jesus Revealed in John Chapter 3, examines Nicodemus, new birth, belief, judgment, light, and the meaning surrounding John 3:16.

Those four articles are not offered as a scientific sample of the entire library. They are representative public pages that anyone can open and inspect. Each comes from a different canonical Gospel. They were published on different dates. Their narratives and spiritual movements differ. They contain visible, chapter-specific content.

They establish something simple but important: the pages are real.

They do not establish why Google handled them as it did. They do not prove that Bing indexes every one of them today. They do not prove religious discrimination. They provide stable examples around which specialists can build a fair investigation.

A Public Page Can Still Be Functionally Invisible

Before working through this problem, I used “published,” “indexed,” and “searchable” almost as though they described one event.

They do not.

Publishing means Blogger placed the page online.

Discovery means a search system learned that the URL existed.

Crawling means a search engine requested the page.

Rendering and processing mean the system examined what the page contained and how it was structured.

Indexing means the system selected the page, or a canonical version of it, for storage and potential retrieval.

Ranking and serving determine whether that indexed material appears for a particular search.

Those stages matter because a page can succeed at the first stage and fail or stall later. When I say that much of my Blogger library has been invisible through Google, I do not mean the pages were literally erased from the internet. I mean that a person relying on Google Search could have great difficulty discovering pages that were openly available through direct links and the Blogger archive.

That is functional invisibility.

A book can sit on a public shelf and still be almost impossible to locate if it is missing from the catalog. The book exists. A person who knows the exact shelf and position can retrieve it. Most readers, however, begin with the catalog.

Google Search is one of the most influential catalogs humanity has ever built.

That is why this matters. I am not arguing that every article deserves a top ranking. I am asking why so much public material appeared not to move from discovery into meaningful Google visibility, particularly when Bing appeared to treat at least part of the same property differently.

What Google Search Console Reported to Me

The most striking piece of private evidence is historical.

On May 8, 2026, my Google Search Console account for the Blogger property showed 637 discovered URLs and zero indexed URLs.

That statement needs careful boundaries.

Search Console is a private publisher tool. A member of the public cannot independently open my property report. I am describing what I recorded in my account on that date. I am not presenting 637 and zero as the current totals. I am not claiming that those numbers explain Google’s reasoning. I am not claiming that the report proves an intentional action against Christian content.

I am saying that the report existed and that it was alarming.

The word “discovered” means Google knew the URLs existed. It does not necessarily mean Google successfully crawled and evaluated all 637 pages. Some may have been known primarily through the sitemap, feeds, internal links, archives, or other discovery paths. Google’s official sitemap documentation explains that a sitemap helps a search engine learn about URLs but does not guarantee that the URLs will be crawled or indexed.

That limitation is real. It also leaves the central question unanswered.

Why did awareness of hundreds of URLs reportedly produce an indexed total of zero at that moment? Was Google delaying crawls because of the publication pace? Was the system deciding that the pages did not add enough unique value? Was Blogger producing canonical or rendering signals that redirected the index elsewhere? Was the theme weakening the pages? Was the entire property being evaluated as lower priority? Were some pages being clustered with related versions on other platforms?

“Indexing is not guaranteed” tells me Google has discretion. It does not tell me which signals controlled that discretion in this case.

The Sitemap Was Not a Magic Door

Like many publishers, I once thought sitemap submission was close to saying, “Here are the pages. Please add them.”

That is not what a sitemap does.

A sitemap is an organized list of URLs that helps a search engine discover the structure and contents of a site. It can be important, especially for large properties and rapidly growing archives. But it is an invitation to inspect, not an order to index.

I report that the Blogger property was submitted through sitemaps and extensively troubleshot. The public site also exposes the kinds of feeds and archive pathways associated with Blogger. Yet discovery and inclusion remained different stages.

This matters because “submit your sitemap” is often the first advice given to someone with an indexing problem. It is reasonable first advice. It becomes inadequate after the sitemap has already been recognized and the system has reported hundreds of discovered URLs.

At that point, repeating the same instruction is not troubleshooting. It is restarting a completed step.

The same is true of requesting indexing again and again. A request can place a URL in a processing queue, but it does not force a decision. Repeated requests do not repair a structural problem, make similar pages more distinct, correct a conflicting canonical, or increase the usefulness of the article.

The practical lesson is not that sitemaps are useless. The lesson is that they solve discovery problems, not every indexing problem.

The H1 Rabbit Hole

One of the most time-consuming parts of this experience involved the H1 heading structure.

Bing Site Scan reportedly identified warnings related to H1 elements and long titles. That created a plausible technical theory: perhaps Blogger’s theme was producing multiple top-level headings, confusing page structure, or weakening the way search engines interpreted the main article title.

I tried to address it more than once.

The changes did not produce the broad indexing improvement I was seeking.

That does not prove headings are irrelevant. A well-structured page is better for readers, accessibility tools, browsers, and automated systems. A theme can surround a carefully written article with site titles, widgets, navigation blocks, labels, and repeated headings that the writer never placed in the body.

But an H1 warning is not the same thing as a sitewide indexing prohibition.

This distinction matters because technical warnings can become convenient villains. A dashboard reports multiple H1 elements, and suddenly the entire mystery feels solved. The publisher edits the theme, waits, sees no improvement, and either repeats the experiment or becomes more frustrated.

The evidence suggests we should be more disciplined.

The correct question is not, “Does this page have more than one H1?” The better questions are:

• Which elements are being marked as H1?
• Does the article title remain clear?
• Does the theme place repeated content before the article?
• Is the main body recognizable in rendered mobile output?
• Are the title element, visible heading, structured data, and canonical URL consistent?
• Does Bing index pages even while warning about their headings?
• Did the heading change alter crawling or index selection in a measurable way?

Several attempted fixes did not solve the larger condition. That weakens the theory that H1 count alone explains everything. It does not clear the theme of all possible responsibility.

For now, the most responsible choice is to preserve the Blogger site rather than continue making uncontrolled changes.

Why I Am Not Changing the Blogger Site During the Campaign

When something is not working, I want to fix it. That instinct has served me well in project management, operations, technology, and life. It can also make an investigation harder.

If I replace the theme today, rewrite hundreds of titles tomorrow, remove internal links the next day, and modify robots settings after that, I will no longer know which version specialists are evaluating. If Google begins indexing pages, I will not know what caused the improvement. If the situation worsens, I will have introduced several new suspects.

The Blogger library is therefore being preserved during the initial campaign.

That means I am not deleting it, migrating it, redirecting its URLs, republishing every article, or replacing the theme while the baseline is being discussed. Preservation is not surrender. It is evidence control.

The four Gospel pages give technical reviewers a shared starting point. They can inspect the same public URLs discussed in the WordPress pillar and this Blogger article. They can compare headings, canonicals, mobile variants, internal links, metadata, and search behavior. If they recommend a controlled test, one limited variable can be changed on a limited set of pages.

That is how the result becomes meaningful.

Changing everything might eventually produce a better-looking site. It would not necessarily produce an answer.

Bing Makes “The Site Is Broken” an Incomplete Explanation

My experience with Bing is what keeps this from being a simple story about a universally inaccessible blog.

I have seen Bing find and index some Blogger material that remained difficult to locate through Google. Public results can change, so I am not claiming that Bing currently returns every article or that every Google absence has a matching Bing result. I am describing a repeated publisher observation that deserves reproduction.

If Bing can retrieve and surface a page, several possibilities follow.

The page is not universally unreachable.

The article body can be processed by at least one major search system.

The clean URL can function as a searchable resource somewhere.

A structural warning may exist without acting as an absolute barrier.

Google and Bing may be making different decisions from the same public input.

That last possibility is the most important.

Search engines are not identical windows onto one universal index. They use different crawlers, storage choices, ranking systems, duplicate detection, quality thresholds, and interpretations of site architecture. Bing indexing a page does not force Google to index it. Google excluding a page does not prove Bing is correct.

But the difference helps narrow the investigation.

If both systems fail, the site or page itself becomes a stronger suspect. If one system succeeds and another does not, engine-specific processing and selection become more relevant. That can include canonical choices, crawl priority, page clustering, quality classification, or different tolerance for repeated structures.

This is why public search results, Bing URL Inspection, Bing Site Scan, Google Search Console, and Google URL Inspection must not be mixed together.

A public result shows what a searcher saw for one query.

A webmaster inspection tool reports information to a verified publisher about a particular URL.

A site scan reports technical findings.

Those are related forms of evidence, but they do not answer the same question.

Could My Publishing Volume Be Part of the Problem?

Yes.

That is not an admission that the project is spam. It is an acknowledgment that scale changes systems.

The public Blogger archive contains hundreds of entries. The larger project includes all 260 New Testament chapters, multiple platform treatments, videos, social distribution, faith-based stories, and related encouragement. I have published at a pace that most independent creators would consider unusually high.

A search engine may respond to that pace in several ways.

It may discover URLs faster than it crawls them.

It may allocate limited crawl attention because the property has not yet demonstrated enough demand or authority.

It may decide that many pages cover closely related subjects.

It may see repeated titles, templates, signatures, internal link patterns, or calls to action across the library.

It may cluster Blogger articles with related versions on WordPress, Medium, Google Sites, or other platforms.

It may decide that some pages are not sufficiently distinct to justify separate storage.

Those possibilities must be examined honestly.

At the same time, volume alone does not tell you why the pages were created. A large ministry library can grow because the creator is committed to explaining Scripture, not because the creator is trying to manufacture empty pages. Search systems still have to evaluate the result, but the existence of many articles is not by itself proof that the work lacks value.

The practical question is whether my purpose and the pages’ actual structure are communicating the same thing.

I know why I created the library. An automated system sees patterns. It sees publication frequency, page similarity, titles, links, templates, repeated phrases, and relationships across domains. If those signals make human-created, mission-driven work look less distinct than it really is, the solution may involve architecture and differentiation rather than simply publishing more.

That possibility deserves serious attention.

Cross-Platform Publishing Can Help Readers and Confuse Search Systems

I do not publish everywhere because I believe every platform is interchangeable.

Blogger is meant to carry practical, lived-faith application. Google Sites emphasizes Scripture-centered clarity. Medium leans toward emotional recognition. WordPress allows reflective depth. Ghost reframes assumptions. Write.as creates a more intimate voice. Substack feels like a direct letter. Tumblr brings vivid immediacy. LinkedIn examines leadership, responsibility, and professional implications.

When those lanes are followed well, each platform article serves a different reader experience.

When they are not followed well enough, search systems may see several pages discussing the same biblical chapter and conclude that they are alternate versions of the same thing.

That could matter to Blogger.

A Blogger article does not exist in isolation. It participates in a connected content network. Repeated anchor text, titles, signatures, descriptions, and subject matter can help humans navigate the library while simultaneously creating similarity signals. A system may select a WordPress page as the representative version and leave the Blogger URL out. It may cluster several versions. It may give one domain more crawl attention than another.

That would be a platform and canonicalization issue, not proof that the underlying Gospel subject was rejected.

It would still matter.

The Blogger platform is supposed to have its own role in my publishing system. If Blogger pages are consistently displaced because other versions appear stronger, I need to know that. I can then improve differentiation, hierarchy, and the clarity of each platform’s purpose without deleting the library.

This campaign itself is designed to demonstrate that approach. The WordPress pillar investigation contains the full evidence framework, technical definitions, competing hypotheses, and public correction policy. This Blogger article stays close to the publisher’s lived experience: pressing Publish, troubleshooting the theme, seeing pages exist without being found, and deciding not to destroy the evidence in frustration.

The subject is the same. The article is not.

What I Can Prove From the Public Blogger Pages

Anyone can verify several facts without entering my Search Console or Bing Webmaster Tools accounts.

The Blogger homepage is public.

The archive contains hundreds of entries.

The four Gospel test pages open without authentication.

Each page has a normal Blogger article URL.

Each page contains substantial visible text related to a specific Gospel chapter.

Each page displays a title and publication date.

The pages exist as more than social captions or link-only placeholders.

Those facts matter because they eliminate a few easy explanations. The pages were not merely saved as drafts. They were not hidden behind a login. They were not all empty. The domain itself was not completely unavailable.

Public facts also have limits.

A human opening the page cannot see which canonical Google selected internally.

A public page cannot reveal whether Google last crawled it six months ago or yesterday.

An ordinary browser does not display the full reason Google declined to index a URL.

One exact-title search does not expose an engine’s complete internal index.

The fact that a page opens does not prove that the mobile crawler receives the same rendered content.

The fact that the page is long does not prove that a search system considers it uniquely valuable.

The fact that an article is Christian does not prove that religion caused its treatment.

A fair campaign has to hold both sets of truths at the same time. The pages are real and the technical reason remains unresolved.

What I Am Reporting as the Publisher

Some evidence cannot be independently obtained from public pages.

I report that the Blogger property was submitted through sitemaps.

I report that extensive troubleshooting was performed.

I report that H1-related changes were attempted more than once without resolving the broad indexing problem.

I report that Bing appeared to index some Blogger content that was not comparably visible through Google.

I report that on May 8, 2026, Google Search Console showed 637 discovered URLs and zero indexed URLs for the Blogger property.

These claims are part of the record because they explain why the campaign exists. They should not be inflated beyond what they establish.

The Search Console figure is dated, not current.

The sitemap report does not prove Google was obligated to include every URL.

The failed H1 attempts do not prove the theme is innocent.

The Bing observation does not prove Bing indexes the entire library.

None of these observations proves motive.

I am asking specialists to use them as leads.

The Questions I Need Blogger Specialists to Answer

Blogger specialists understand that a page is more than the words typed into the editor. The final document includes the theme, site title, navigation, widgets, archive links, labels, scripts, feeds, mobile variants, structured data, and platform-generated metadata.

That is why I am asking experienced Blogger publishers and developers to inspect these questions:

Does the theme make the article title unmistakably clear?

Are multiple H1 elements coming from the site title, post title, widgets, or hidden mobile structures?

Does the clean .html URL declare itself as canonical?

Does the ?m=1 mobile version create a conflicting representation?

Is the complete article body present when the page is rendered as a mobile crawler?

Are archive, label, feed, and parameter URLs creating excessive alternate pathways?

Do internal links point consistently to the clean canonical URLs?

Does the page return the same status and content to search crawlers that it returns to an ordinary reader?

Is structured data present, valid, and aligned with the visible article?

Could the publication pace have caused a discovery backlog that Blogger’s default architecture handles poorly?

Is there a known Blogger limitation affecting large, rapidly growing archives?

Do the four test pages share a structural condition that would explain broad exclusion?

I do not need a generic statement that Blogger can rank. I need an explanation tied to these pages and this property.

The Questions I Need Search Specialists to Answer

Technical SEO and search specialists can help determine where the process is stopping.

Are the pages discovered but not crawled?

Are they crawled and not indexed?

Are they indexed under another canonical?

Are they clustered with cross-platform versions?

Is the unique content being outweighed by repeated template material?

Is Google spending crawl attention on lower-value archive and parameter URLs?

Does the site lack a strong enough internal hierarchy for hundreds of chapter-level pages?

Is the domain’s publishing velocity far ahead of its crawl demand?

Do titles, descriptions, and internal links appear over-optimized at scale?

Are the pages technically eligible but losing at the index-selection stage?

Why does Bing appear to treat at least part of the property differently?

What single controlled change would produce the most useful test?

A credible answer should identify signals and propose a way to falsify the theory. It should not begin and end with “Google does not guarantee indexing.”

I already know that.

The Questions I Need Other Blogger Publishers to Answer

This investigation should not remain only about me.

Other Blogger publishers can help determine whether the pattern is specific to my library or reflects a broader platform problem.

If you operate a substantial Blogger site, especially one that has been active for months or years, compare a few representative pages in Google and Bing. Use the same clean URL and exact title in both systems. Check whether Search Console reports discovery without indexing. Look at whether your mobile and desktop versions agree. Record whether Bing reports technical warnings while still indexing the page.

Do not send guesses. Send reproducible observations.

A pattern across unrelated topics would weaken the theory that Christian subject matter is central and strengthen the theory that Blogger architecture, crawl priorities, publishing scale, or search-engine thresholds are responsible.

A pattern concentrated in particular kinds of religious publishing would justify deeper comparative research.

Either result would teach us something.

Why I Will Not Call This Persecution Without Evidence

The campaign title is sharp because the underlying situation deserves attention. Sharp language also creates responsibility.

Christian history contains real persecution. People have lost jobs, homes, freedom, safety, and life because of their faith. Using that word casually for an unresolved indexing problem would diminish what persecution means.

A search engine excluding pages can still have consequences. It can reduce reach, distort discovery, and make a public library harder to find. Those effects deserve investigation without being mislabeled.

There is also a practical reason to avoid unsupported accusations: credible specialists will not engage seriously with an investigation that has already convicted the system it claims to examine. They will spend their energy rejecting the premise instead of studying the pages.

I want the technical answer more than I want the most inflammatory answer.

If the evidence eventually points toward an unfair content-classification pattern, it should be documented carefully. If the evidence points toward my theme, site architecture, publishing scale, or cross-platform similarity, that should be documented just as openly.

Truth does not become less Christian when it corrects me.

The Spiritual Lesson Hidden Inside a Technical Problem

There is something humbling about spending months building a public Christian library and discovering that “public” does not mean “found.”

Faithful work often begins without visible results. A person can plant, water, teach, write, serve, encourage, and pray without receiving immediate evidence that the effort reached anyone. Christians know that obedience cannot be reduced to analytics.

But that spiritual truth should not become an excuse for technical passivity.

If a microphone is disconnected, faith does not require the speaker to keep talking into it without checking the cable. If a church sign points in the wrong direction, humility does not require leaving it that way. If a public library’s catalog is malfunctioning, patience does not forbid investigation.

Trusting God and troubleshooting a publishing system are not opposites.

I can believe that God can use one article to reach one person and still ask why hundreds of articles remain difficult to discover. I can refuse to measure spiritual worth by traffic while still recognizing that distribution affects whether human beings encounter the work.

The lesson is not “algorithms do not matter.” The lesson is “algorithms are not sovereign.”

That distinction gives me freedom to investigate without fear. If Google indexes the library tomorrow, the Gospel does not become more true. If Google never indexes it, the Gospel does not become less true. Yet as a steward of the work, I should understand the tools, correct genuine problems, and make the library as accessible as reasonably possible.

What Happens Next

The Blogger property will remain intact while this campaign proceeds.

This WordPress-to-Blogger progression is deliberate. The canonical WordPress investigation establishes the central evidence record. This Blogger article documents what the problem looks like from the platform where the library was built.

The next campaign articles will approach the issue through their own platform lanes. Google Sites will explain the indexing process in Scripture-centered, accessible language. Medium will examine the emotional experience of creating work that is publicly present but difficult to find. Ghost will challenge the headline and test competing explanations. Write.as will make the experience more personal. Substack will become an open letter to engineers, publishers, and journalists. Tumblr will make the evidence immediate. LinkedIn will examine platform risk, operational accountability, and the implications for independent publishers.

Every article will return to the WordPress pillar. None should merely duplicate it.

The goal is not to flood the web with copies of one accusation. The goal is to create a coordinated body of independent angles that gives the right people several reasons to take the investigation seriously.

My Request to Google, Bing, and Blogger Experts

I am not asking Google to index every page because I demand it.

I am asking experts to explain the pattern.

Why did my Search Console account report 637 discovered URLs and zero indexed URLs on May 8, 2026?

Why does Bing appear to surface at least some pages that Google does not?

Is Blogger producing technical signals that I cannot fully control?

Did my publishing volume exceed Google’s crawl interest?

Are cross-platform versions being clustered?

Are template elements making distinct articles look too similar?

Is a mobile, canonical, robots, header, or rendering issue hiding in plain sight?

Did Google simply make a quality decision that Bing did not make?

What evidence supports the answer?

If the problem is mine, show me where it is. I will not be insulted by a technically supported correction.

If the problem is Blogger’s, identify the limitation so other publishers can recognize it.

If the problem is Google’s index-selection system, explain the signals as clearly as the available evidence allows.

If the answer is that several causes are interacting, show how they connect.

Do not give me reassurance. Give me a test.

I Am Leaving the Pages Where They Are

The easiest response to poor visibility would be to abandon Blogger and move on.

I am not doing that during this investigation.

The pages will remain public. The Gospel examples will remain at their existing URLs. The archive will remain available. Specialists will be able to inspect the actual environment instead of a reconstructed memory of it.

The Matthew 5 commentary will remain where it was published.

The Mark 14 commentary will remain where it was published.

The Luke 24 commentary will remain where it was published.

The John 3 commentary will remain where it was published.

Those pages are not accusations. They are evidence.

They show the work. They show the platform. They give specialists something concrete to examine. They keep this campaign grounded in public material instead of emotion alone.

The Question Remains Open

Does Google hate Jesus?

I do not know, and the evidence currently available does not prove that it does.

I know that I published a large Christian library on Blogger.

I know that the pages are public.

I know that hundreds of URLs were reported as discovered in my private Search Console account.

I know that the indexed total shown to me on May 8, 2026, was zero.

I know that Bing has appeared to find some of the material that Google has not made comparably discoverable.

I know that multiple H1-related fixes did not solve the broader problem.

I know that publishing volume, site structure, platform limitations, canonicalization, similarity, and quality classification are all legitimate subjects for scrutiny.

I also know that dismissing the issue with “indexing is not guaranteed” is not the same as explaining it.

The headline asks whether Google hates Jesus because a quiet headline would be easy to ignore. The investigation refuses to claim that answer because truth matters more than attention.

Maybe the final explanation will be technical and ordinary.

Maybe it will expose a weakness in my publishing system.

Maybe it will reveal a broader Blogger problem affecting creators in every subject.

Maybe it will show how two search engines apply very different inclusion thresholds.

Maybe it will raise harder questions about automated classification and the visibility of religious archives.

Whatever the answer is, I want it supported by evidence.

Until then, I will keep the Blogger library public. I will keep asking fair questions. I will correct mistakes when they are demonstrated. I will not turn uncertainty into an accusation, and I will not turn humility into silence.

The articles exist.

Bing has found some of them.

Google has left much of the library behind.

Now I am asking people who understand these systems to help explain why.

Your friend,

Douglas Vandergraph

Explore the complete Douglas Vandergraph Master Index:
https://douglasvandergraph.com/douglas-vandergraph-master-index/

Watch Douglas Vandergraph’s faith-based videos on YouTube:
https://www.youtube.com/@douglasvandergraph