A nonprofit organization reached out confused about why their site, full of genuinely useful resources, barely showed up in search at all. Their content team had been publishing consistently for over a year with almost nothing to show for it in organic traffic.
The Situation
The nonprofit had recently switched web platforms during a broader rebrand, and something in that migration had gone quietly wrong. Most of their pages, including brand-new ones, simply weren't appearing in Google's index at all.
What We Found
Their robots.txt file, likely left over from a staging environment during development, was blocking search engines from crawling almost the entire site. On top of that, there was no XML sitemap submitted through Google Search Console, meaning even the pages that weren't blocked had no clear map guiding search engines to find them efficiently.
What We Did
We corrected the robots.txt file to allow crawling of every page meant to be public, generated a proper XML sitemap and submitted it through Search Console, and used the URL inspection tool to manually request indexing for their highest-priority pages to speed up the recovery rather than waiting for Google to rediscover everything on its own schedule.
The Result
Within roughly ten days, indexed page count jumped from under 15 pages to over 200, and organic impressions began climbing almost immediately as pages that had been invisible for over a year finally started appearing in results.
The Takeaway
A blocked robots.txt file is one of the simplest, most catastrophic SEO mistakes, and it's exactly the kind of thing that gets left behind during a platform migration if nobody checks for it. It should be the very first item on any SEO audit checklist, before anything else gets reviewed.
Recently switched platforms or launched a redesign? Ask Rafenthic for a quick indexation check before assuming the worst.