Your Charleston pages are crawled and not indexed
Google rewrote the 'crawled, currently not indexed' help doc this week to call it normal. A day earlier John Mueller called the same pattern a quality issue.
Google published two things in about twenty four hours this week that point in opposite directions, and if you own a service business in Charleston, the one that sounds friendlier is the one that will cost you.
Here is Monday. Sarah Blocksidge, who does SEO for a living, asked John Mueller on Bluesky about a client site that got hacked last year, got cleaned up, and never recovered. Her words: "Only their homepage is indexed, and we can't get GSC to crawl any internal links or index any other pages on the site."
Mueller's reply, posted November 2 at 2:53pm UTC, verbatim: "It's impossible to say without more information :-), but off-hand, this sounds like a general quality issue that might be unrelated to the hack."
A general quality issue. Not a crawl bug, not leftover hack damage, not something a plugin fixes.
Now here is Tuesday. Google quietly rewrote the Search Console help documentation for the status called "Crawled - currently not indexed." Barry Schwartz caught it. The old text said the page may or may not get indexed later and there was no need to resubmit it. I pulled the live page myself rather than trusting the write-up, and the replacement text now reads: "The page was crawled by Google but not indexed. Google doesn't index all pages across the web, so this is a common message for many sites and doesn't necessarily indicate an issue that needs attention."
That screenshot is the cover on this post, read off support.google.com this evening.
So: one Googler telling a practitioner that unindexed pages signal site quality, and one Google help document, a day later, telling everybody that unindexed pages are common and probably fine. Both true. Both published this week. Only one of them is written for you.
What the status actually means
"Crawled - currently not indexed" means Googlebot came, fetched the page, read it, and decided not to put it in the index. That is a judgment, not an accident. The crawler worked. The URL was reachable. Nothing was blocked.
This is the part people get backwards, so it is worth separating cleanly from the thing I wrote about in September, when a Cloudflare setting started quietly blocking Googlebot for sites whose owners thought they were only blocking AI scrapers. That was a crawl problem. The bot never arrived. This one is the opposite. The bot arrived, looked, and passed.
Why the reassuring version is wrong for your site
Google's help docs are written for the whole web. The whole web includes an ecommerce catalog with 400,000 filtered URLs, a news archive going back to 1998, and a forum with two million thread pages. For those sites, yes, enormous chunks sit unindexed forever and that is completely normal. Nobody needs every faceted color variant of a sock in the index.
Your site is not that. A Mount Pleasant roofing company has a homepage, an about page, a contact page, six service pages, four neighborhood pages, and maybe a dozen posts. Call it twenty five URLs. Every single one was written on purpose, by a human, to be found.
When Google indexes nine of them, "this is a common message for many sites" is a technically accurate sentence that will lead you to do nothing about a real problem. The base rate does not transfer. A 2% indexation gap on a 400,000 URL catalog and a 60% indexation gap on a 25 page contractor site are not the same phenomenon wearing different clothes.
My stance, and you are free to disagree with it. On a small service business site, "crawled - currently not indexed" is almost never nothing. It means Google read the page and could not find a reason to keep it. On a site where you control every URL, that is the single most useful piece of feedback Google gives you for free, and Google just reworded the label so it sounds like weather.
At this point a lot of people are thinking: come on, Google wrote the doc, Google would know. Sure. Google also wrote both of these in the same week. The doc is Google's statement about the web in aggregate. Mueller's reply is Google's statement about one real site with a specific symptom, which is the situation you are actually in. (I notice the new wording also removes the prior nod to quality issues, which is the exact word Mueller used one day earlier. Make of that what you will.)
What to check this week, in order
Open Search Console, go to Indexing, then Pages, then click the "Crawled - currently not indexed" row. Export the list. Then work it like this.
- Count the ratio, not the number. Twelve unindexed URLs out of 400 is noise. Twelve out of 25 is a diagnosis. Write down both figures before you feel anything about it.
- Sort out the junk. Tag archives, paginated blog pages, author pages,
?utmduplicates, an old staging path. If most of the list is this, you are fine, and the real fix isnoindexor cleanup so the report stops lying to you. - Read three of the real pages out loud. Not skim. Read. If your Daniel Island page is your West Ashley page with the town name swapped, Google already noticed. I counted this pattern across competitor sites back when I found Charleston SEO pages being generated by the hundred, and the mass-produced ones are exactly the URLs that sit in this bucket.
- Check whether anything links to them. A service page reachable only from the XML sitemap is a page you told Google not to care about. Link to it from the nav, from the relevant neighborhood page, from a post.
- Only then hit URL Inspection and Request Indexing. Doing this first, on an unchanged page, is the most common wasted hour in small business SEO. The crawler already saw it. Asking again does not change the verdict.
If step 3 is where your list falls apart, that is good news, because it is fixable with writing rather than with developers. The fix is specificity: real job details, real streets, real prices, real photos of your own trucks. I went through what that looks like in practice when I found a competitor's Charleston SEO page with no Charleston in it, and the same test applies to your own service pages. If the page would read identically with "Savannah" pasted over "Charleston," it is thin, and thin is what this status is reporting.
The one that should actually scare you
Blocksidge's symptom, homepage indexed and nothing else, is the severe version. If that is your site, stop reading SEO checklists. That is Google declining to index your business, and no amount of resubmitting fixes it. It is a rebuild of what the pages say.
For most Charleston contractors and practices the situation is milder and more boring: four or five pages sitting in the bucket, usually the newest or the thinnest ones, usually because they were written to fill a slot in a menu rather than to answer anything. That is the kind of thing we untangle in our Charleston SEO work, and it is less glamorous and more effective than most of what gets sold as technical SEO.
Your move this week: pull that export, calculate the ratio, and read three pages out loud. If you cannot get through one of them without wanting to skip a paragraph, Google felt the same way.