A website can have useful content, a legitimate organization behind it, and even some Google visibility—and still have a serious SEO problem.
That was the situation we found with Little Falls Chapel, a non-denominational church in Falling Waters, West Virginia.
The church already had sermons, teaching articles, visitor information, event pages, prayer resources and local content. The problem was not a lack of material.
The problem was that Google was seeing only a small fraction of it.
This case study documents how Web Promote Pro established a measurable baseline, identified the crawl and indexing bottlenecks, cleaned up the site’s structure, and rebuilt the paths Google uses to discover its content.
Case study status: In progress. The official baseline was frozen September 4, 2026. Technical remediation was completed September 24, 2026. Google recrawl, indexing, organic-search and local-search results are still being monitored.
The starting point
We intentionally froze the starting condition before making major changes.
The September 4 baseline covered Little Falls Chapel’s website, Google Search Console, XML sitemap, mobile search visibility and local entity signals. Historical Search Console performance through September 2 was preserved so later changes could be measured against a fixed reference point rather than a moving target.
The baseline showed:
| Baseline metric | September 4, 2026 |
|---|---|
| Google Search clicks | 33 |
| Google Search impressions | 973 |
| CTR | 3.39% |
| Weighted average position | 19.0 |
| URLs shown as indexed in captured GSC report | 3 |
| URLs shown as not indexed | 4 |
| Sitemap entries | 79 |
| Google Maps rating | 5.0 |
| Google reviews | 3 |
The important number wasn’t simply the traffic.
It was the mismatch between the size of the site and what Google appeared to be indexing.
Little Falls Chapel had dozens of posts and pages available, but the captured Search Console report showed only three indexed URLs. The baseline specifically identified this as a discovery and indexation mismatch, not a content shortage.
A page could be perfectly indexable—and Google still didn’t know about it
One page gave us an especially useful example: Plan Your Visit.
At baseline, Google’s stored Search Console state reported the page as unknown. There was no referring sitemap and no referring page in the stored record.
But when we ran Google’s live URL test, the page was available, crawlable and indexable.
In other words, the page itself wasn’t fundamentally broken. Google simply hadn’t properly discovered or processed it yet. An indexing request was submitted on September 4, creating a clean before-and-after checkpoint for the case study.
That distinction shaped the rest of the project.
Rather than pumping out more content, we needed to make the content already on the site easier to find, understand and crawl.
The deeper Search Console audit
A broader read-only Search Console analysis made the problem even clearer.
Across the roughly 65 URLs inspected, only six were confirmed indexed at that point.
The six included the homepage, Plan Your Visit, About, Prayer and two teaching articles. Many of the sermon, event, ministry and local-content URLs were sitting in states such as found but not crawled or were still unknown to Google.
The longer 16-month Search Console history showed 312 clicks from 8,023 impressions, but traffic was highly concentrated. The homepage alone accounted for 296 clicks and more than 6,500 impressions.
That told us something important: the site had established some search relevance, but Google was leaning heavily on a tiny portion of the website.
The sermon library was a perfect example. The /sermons/ page existed, but it did not contain crawlable links to the sermon posts.
To a human visitor, the site had sermons.
To a search crawler following links, much of that library was effectively hidden.
The first repair: create real crawl paths
We started with the safest structural fixes.
The Sermons page was rebuilt into a real content hub. Existing published sermon and Bible-study posts were surfaced using normal HTML links. New posts could be added automatically rather than requiring a hand-maintained list.
That single change exposed 25 existing teaching posts that previously had no crawl path from the Sermons page.
We also strengthened internal links between Plan Your Visit, the church’s main informational pages, local content and individual teaching posts.
After the first crawl-discovery batch, the number of pages reachable through links from the homepage increased from 40 to 58.
No new broken links were introduced, no redirect loops appeared, and the sitemap remained valid.
Then we cleaned up the whole site
Once the discovery problem was addressed, we expanded the work rather than leaving the website half-cleaned.
The second cleanup batch dealt with canonical URLs, duplicate content, old pages, event handling, metadata, schema, automated draft generation and indexability.
The result was a leaner search architecture with fewer URLs competing for Google’s attention.
Before and after the technical cleanup
| Technical condition | Before | Final |
|---|---|---|
| Sitemap URLs | 60 | 48 |
| Indexable pages unreachable internally | 21 | 0 |
| Indexable pages with zero internal links | 5 | 0 |
| Maximum crawl depth | 5 | 4 |
| Posts exposed through /sermons/ | 0 | 25 |
| Duplicate titles | 1 | 0 |
| Pages with H1 structure problems | 14+ | 0 |
| Broken internal links | 0 | 0 |
| Indexable orphan pages | Present | 0 |
| Canonical conflicts | 0 | 0 |
The sitemap shrinking from 60 URLs to 48 was intentional.
SEO is not a contest to put the largest possible number of URLs into Google.
Expired events, retired duplicate content and utility pages that did not belong in search were removed from the indexing queue. The goal was to give Google a cleaner set of pages that were actually worth crawling and indexing.
Cleaning up duplicate teaching content
Several older articles covered nearly the same theme: opening your heart to God, connecting with God and developing a closer relationship with God.
One article had already earned substantially more Google visibility than the others, so rather than sending several overlapping pages to Google, we consolidated the strongest unique material into the primary article.
The weaker overlapping URLs were retired and permanently redirected to the stronger page.
A separate sermon with its own video and distinct purpose remained live.
This wasn’t about deleting content for the sake of deleting it. It was about reducing ambiguity while preserving material that actually added value.
Fixing the About page and old URLs
The church’s About page had also ended up at an awkward /about-2/ address.
We restored the cleaner /about/ URL, updated the site’s internal references and permanently redirected the old address to the new canonical version.
Other legacy URLs were handled according to what they actually represented.
Old Blog URLs now point to the current Sermons content when that is a genuine equivalent. An old prayer-request route points to the current Prayer page. A dead Bible-study route was repaired so that it no longer led through a broken redirect.
URLs without a legitimate replacement were not blindly redirected to the homepage.
That’s an important part of technical SEO cleanup: a redirect should represent a real relationship between the old page and the new one, not simply make a 404 disappear.
Restoring a useful Ministries page
The old Ministries URL had historical traffic but no current live page.
Instead of recreating outdated claims, we rebuilt /ministries/ using only ministry and church activity that could be supported by current first-party information.
Historical programs that could not be confirmed as active were deliberately left out.
That matters because SEO content still has to be accurate content.
A page is not improved simply because it contains more keywords or more claims.
Stopping automated duplicate drafts
The technical audit also uncovered a quieter problem inside WordPress.
A content automation was generating three draft articles every week based on content-gap topics, but it was not adequately checking whether similar drafts had already been generated.
Over time, that had produced dozens of overlapping drafts.
We traced the behavior to the site’s Rural Ranking AI workflow, stopped the weekly automated job without disabling the plugin entirely, exported the drafts for safekeeping, and moved 38 duplicate drafts to the trash.
Nothing was mass-published.
This was important because automatically generating more pages would have made the site’s existing crawl and topical-overlap problem worse rather than better.
Events, archives and pages that should not rank
Not every public URL needs to be indexed.
Past event pages were separated from upcoming events, clearly labeled and set to noindex,follow where appropriate. They can remain useful to visitors without asking Google to treat every expired event as a current search landing page.
Working utility pages such as the Privacy Policy and Discipleship Assessment remain available while staying outside the main search index.
Broken or empty utility pages were retired.
Pagination was also adjusted so that Google could continue following links even when a paginated archive itself did not need to appear in search.
Improving titles, metadata and page signals
The homepage previously used a repetitive title that essentially repeated the church’s name.
It was changed to better communicate what the organization is and where it is located:
Little Falls Chapel | Non-Denominational Church in Falling Waters, WV
The homepage description was also rewritten for a real visitor rather than a plugin score.
Important pages received clearer titles and descriptions, duplicate H1 structures were corrected, and structured-data output was reviewed.
Unverified social-profile references were removed from schema, while legitimate profiles were retained.
The goal was consistency: the same church, location and identity across the website’s visible content, metadata and structured data.
Local listings were audited separately
Website SEO wasn’t the only part of the project.
A September listing verification found six publicly accessible directory records that agreed with Little Falls Chapel’s canonical business information. One live directory, USCity.net, was confirmed to contain an address mismatch. Other scanner warnings could not be independently confirmed and were therefore treated as items to recheck—not automatically as errors.
That distinction matters.
Local listing tools can be useful, but a red warning inside a scanner is not the same thing as a verified live citation problem.
Our approach was to correct confirmed discrepancies rather than blindly pressing “fix all.”
What about Google Maps?
Little Falls Chapel already had some local visibility at the September 4 baseline.
For the captured search “non denominational church Falling Waters WV,” the chapel appeared in visible local results with a 5.0 rating from three Google reviews. The baseline also showed weaker visibility for another tested intent, “Bible teaching church Falling Waters WV.”
Later September screenshots showed Little Falls Chapel appearing in the first two visible Maps results for several local church searches, including one observed first position for a “church near Falling Waters” search.
We are documenting those observations, but we are not claiming that the website work caused those Maps positions.
Local results vary by location, device, personalization and query. The review count also remained at three, which makes it especially important to separate observation from causation.
What we are not claiming yet
This is where many SEO case studies get ahead of themselves.
The technical work is finished, but Google does not recrawl and reindex an entire website instantly.
So we are not claiming that rankings increased because of these changes.
We are not claiming that organic traffic has increased because of these changes.
We are not claiming that every one of the 48 intended search pages will be indexed.
And we are not claiming that the Maps observations were caused by the site cleanup.
What we can show today is the part that is directly measurable:
The website is materially easier to crawl, cleaner to interpret, less duplicative and better internally connected than it was before the intervention.
Google now gets a much clearer picture of which pages matter.
The next question is what Google does with that improved structure.
What we’re measuring next
The original baseline was designed for 30-, 60- and 90-day checkpoints, with longer-term comparison after that. Those checkpoints include clicks, impressions, CTR, average position, indexed-page counts, sitemap discovery, key-page indexing, organic visibility, local-pack observations, review count and meaningful visitor actions.
The most important progression to watch now is:
Discovered → Crawled → Indexed → Visible → Clicked
That is why this case study is being published before the final outcome is known.
We want the timeline preserved.
The September 4 baseline stays frozen. The September 24 remediation stays documented. Future updates will be compared with those dates rather than rewriting the starting point after the fact.
The larger lesson
The Little Falls Chapel project is a good reminder that “create more content” is not always the answer to an SEO problem.
Sometimes the content is already there.
The real problems may be orphan pages, weak hub pages, duplicate topics, old redirects, noisy sitemaps, inconsistent canonicals, expired content, poor internal linking or pages that Google simply has no strong reason to crawl.
Adding another 20 articles on top of that foundation can make the problem worse.
For Little Falls Chapel, the first job was not producing more pages.
It was making the existing website make sense.
Need help figuring out what Google is actually seeing?
If your website has dozens of pages but only a handful seem to appear in Google, the problem may not be your amount of content.
Web Promote Pro looks at the full picture: indexing, internal links, crawl paths, redirects, sitemap quality, metadata, local signals and the pages Google is actually choosing to process.
Before publishing more, find out what Google is missing.
Contact Web Promote Pro to have your website and local search visibility reviewed.
Case study update status: Technical remediation completed September 24, 2026. Google recrawl and indexing results are being monitored. This page will be updated as the 30-, 60- and 90-day checkpoints become available.