Why would Google keep a single location page in “Discovered – currently not indexed” for over a year while all sibling location pages index normally?
I’m troubleshooting a single page indexing issue that doesn’t seem to align with typical explanations around timing, quality, or technical setup.
The site has multiple location-based service pages, and almost all of them indexed normally. One page, however, remains stuck.
Situation
Indexed location pages on the same site include:
- Montreal
- Miami
- Fort Lauderdale
- New York City
- Philadelphia
All of these pages indexed relatively quickly after publishing.
However, the New Jersey service page has been live for over a year and still has not been indexed.
Current Search Console status:
Current Search Console Signals
Search Console shows:
- URL is known to Google
- Sitemap detected
- Discovery source detected
- Crawl fields currently show N/A (no recent crawl)
So Google appears to know the page exists, but it has not been crawled again in the current indexing cycle.
The page also appears when doing a site search, which further suggests Google is aware of the URL.
Steps already taken
Things that have already been verified or implemented:
- Page is indexable (no
noindex, no robots issues) - Self-referencing canonical confirmed
- Included in XML sitemap
- Structured data / schema markup present
- FAQ schema added
- Internal links added from NJ-related blog posts
- Page rewritten to be clearly New Jersey specific
- Explicit wording that the company serves NJ as a service area (not claiming a physical office)
- Manual indexing request submitted
- External citation referencing the page exists (MapQuest listing)
The page itself is a service page for a video production company serving New Jersey, primarily commercial and branded video production work across cities like Newark, Jersey City, and Princeton.
What makes this unusual
Several newer location pages indexed within days, including NYC and Philadelphia.
Yet the New Jersey page — which is older and internally linked — remains in the discovered but not indexed state.
Working theory
One possibility I’ve been considering is geo overlap evaluation, since:
- NYC and Philadelphia pages exist
- New Jersey geographically overlaps those markets
But the timing still feels unusual given the page has existed for over a year.
Curious if anyone has seen similar cases where
- State-level location pages are deprioritized when nearby city pages exist
- Pages remain discovered but not crawled for extended periods
- Google delays indexing one regional page even when sibling pages index normally
Would appreciate any technical insight beyond the standard indexing checklist.
[link] [comments]
from Search Engine Optimization: The Latest SEO News https://ift.tt/sh1J8Qw
Comments
Post a Comment