Discussion starter: a programmatic SEO question, posted with an answer from Niraj Raut to open the thread. If you have dealt with this on a site, reply with what you saw, especially where it differs.
- Indexing
- Technical SEO
A job board has ‘[role] in [small town]’ pages with one listing. Noindex, redirect to a broader page, or keep them indexable with nearby jobs?
Disclosure: Niraj Raut, who posted this answer, runs the SEO consultancy linked at the end of it.
1 reply
-
adminAdmin
The short answer: don’t redirect a town page just because it has one listing today, and don’t decide page by page based on today’s listing count. Keep the URL live for users, and make indexability a rule driven by two things: whether people actually search for that role in that town, and whether the page can show a useful, honest set of jobs most of the time, counting genuinely commutable nearby jobs. Pages that pass get indexed and include nearby jobs. Pages that fail get
noindex, or are never generated as crawlable URLs in the first place.The qualification is about “nearby”. Adding nearby jobs works for an isolated town where commuting to the next centre is normal. It works badly for clusters of small towns or suburbs, because every page in the cluster ends up showing the same regional jobs. At that point you have many near-identical pages targeting different place names, which is close to what Google’s spam policies describe as doorway abuse. There the answer is consolidation to an area page, not padding.
Why a single listing is the wrong thing to judge
A page with one job today is a page with zero jobs in a month, when that listing expires. Job inventory churns, so the risk on a small-town page is less about thin content today and more about the page switching repeatedly between one listing, zero listings and a few listings. Empty listing pages served with a 200 status are commonly flagged as “Soft 404” in the Page indexing report, and near-identical pages tend to end up as “Crawled - currently not indexed” or “Duplicate, Google chose different canonical than user”. On a board with thousands of roles and thousands of towns, that churn is multiplied across millions of combinations.
So the useful unit of measurement is the page’s typical state over a window, such as the median number of relevant active jobs over the last 60 to 90 days, not the count on the day you audit it.
Important distinction:
A location page is a list page, and it will never be eligible for Google’s job search experience in its own right. Google’s JobPosting guidelines limit the markup to pages that contain a single job posting, and tell you not to add it to pages intended to present a list of jobs, such as search result pages. Your job detail pages carry that visibility. The town page only earns its place in the blue links if it serves the searcher better than a regional page would.
What each option actually does
Option What happens When it fits Main risk Keep indexable, add nearby jobs Page stays eligible for “[role] in [town]” searches and shows local plus commutable jobs Real search demand, an isolated town, nearby jobs within a realistic commute Neighbouring town pages converge on the same content; empty or padded states look like Soft 404s or doorways noindex, keep the pageUsers and internal navigation keep the page; Google drops it from the index over time Little or no search demand, or supply too thin to produce a useful page most of the time Slow to reverse: removing noindexneeds a recrawl before the page can return301 to a broader page Town URL disappears; signals consolidate to the area or city page The town will never have its own supply, or it is really part of a larger search area (suburbs of one city) If the town later gets supply, you have no page for it. Switching the redirect on and off with inventory is the worst of both. Canonical to a broader page A hint that the pages are duplicates Rarely: the content is not a duplicate Google may ignore it because the pages differ Don’t generate the URL No crawlable page until the combination qualifies The long tail of role and town combinations with no demand Needs an explicit generation rule in the platform Where “nearby jobs” crosses into doorway territory
Google’s spam policies describe doorway abuse as pages created to rank for specific, similar queries that lead users to intermediate pages less useful than the final destination. One of the listed examples is having pages targeted at specific regions or cities that funnel users to one page. The scaled content abuse section also covers stitching together content from other pages without adding value.
A town page is not a doorway just because it targets a place name. Job seekers do search by town, and a page that answers “what can I apply for from here?” is useful. The risk comes when 20 towns within 30 km all show the same 15 regional jobs under 20 different headings. At that point each page is an intermediate step to the same set of jobs, and the town name is the only real difference. In practice Google often declines to index most of them anyway, so the pages cost crawl activity and add little.
A practical uniqueness test: compare each town page’s job set against its neighbours. If most of the jobs on a page also appear on several neighbouring town pages, the cluster should be one area page, with the towns named on it and in its filters, and the town URLs redirected permanently or never generated.
Hypothetical example:
A board has “aged care nurse jobs in [town]” pages across a rural region. Town A is 60 km from the nearest regional centre, has consistent search impressions for the role, and usually has one or two local listings plus five to eight within a 40 km radius. That page stays indexed, with the local jobs first and the nearby jobs labelled by distance (“1 job in Town A, 7 within 40 km”). Towns B to F sit within 15 km of each other on the edge of the regional centre, have almost no searches of their own, and all show the same regional jobs. Those pages are consolidated into a single “[role] jobs in [region]” page that names the towns it covers, with permanent redirects from the old town URLs.
A rule that scales to millions of combinations
Manual review does not work at job-board scale, so the decision needs to be a rule the platform applies automatically. The structure I would use:
Is there search demand for this role in this town (Search Console impressions, internal search, keyword data)?βOver the last 60 to 90 days, does the page usually have enough relevant jobs, local plus within a realistic commute?βIs its job set meaningfully different from neighbouring town pages?βAll three yes: index, with nearby jobs. Demand but no supply: noindex, and link to the area page. No demand: don’t generate a crawlable URL. Not distinct: consolidate into an area page.Two implementation details matter more than the thresholds themselves.
First, use different thresholds for switching indexing on and off. For example (hypothetical numbers), index when the 60-day median reaches five relevant jobs, but only noindex when it has sat below two for 60 days. Without that gap, pages near the line flip between states every few weeks, and each flip needs a recrawl before Google acts on it. Only list indexable pages in XML sitemaps, so the sitemap reflects the current rule.
Second, handle the empty state deliberately. When an indexed page temporarily has no local jobs, show nearby jobs with distances, a job alert sign-up, and links to the area page, and make the title and heading honest (“Aged care nurse jobs near Town A” rather than claiming jobs in the town that are not there). If a page is empty with no useful nearby jobs for a sustained period, the rule should noindex it rather than leave an empty page in the index.
Watch for this:
Don’t use robots.txt to handle the long tail of combinations you have already noindexed. If Google cannot crawl a URL, it cannot see the
noindex, and blocked URLs can still be indexed from links without content. Usenoindexfor pages you want out of the index, and control generation and internal linking for pages that should never exist. Also keep remote jobs out of the “nearby” set unless they are labelled as remote; Google’s guidelines handle remote roles on detail pages withjobLocationTypeset toTELECOMMUTE.Evidence to check before changing anything
- What Google already does with these pages. Put the location pages in their own sitemap and filter the Page indexing report by it. If most one-listing pages are already “Crawled - currently not indexed” or “Soft 404”, Google has partly made the decision for you, and a
noindexrule mostly tidies up. - Which town pages earn clicks. Group Search Console performance data by URL pattern and by listing-count bucket. Small-town pages often get impressions for the town name even when keyword tools report no volume, so trust your own data over tool estimates.
- Where Googlebot spends its time. Logs will show whether crawling of location pages is crowding out job detail pages, which are the pages that expire and change fastest. Google’s crawl budget guide is written for sites at this scale.
- What converts. Measure applications started from organic landings on town pages, not just sessions. A one-listing page that sends qualified applicants to a paying employer may be worth more than its traffic suggests.
How to test it rather than argue about it
Take two matched cohorts of small-town pages (similar demand, similar supply, different regions to limit overlap). In one, apply the full rule: nearby jobs with distance labels on qualifying pages,
noindexon failing ones, and consolidation of clusters. Leave the other unchanged. Run it for 8 to 12 weeks, avoiding the start-of-year hiring peak if your market has one. The primary metric is organic applications across the whole cohort, including the regional pages that should pick up town searches. Secondary metrics are indexed pages, clicks and the share of location pages in “Soft 404”.The result that would change the decision: if the test cohort holds or grows applications while indexed page count falls, roll the rule out. If applications fall, look at which town pages lost traffic. That usually means demand thresholds are set too high, not that the approach is wrong.
The practical position
If this were my board, I would never redirect a town page because of today’s inventory, and I would never pad a one-listing page with distant jobs to make it look substantial. I would index town pages that have real demand and usually have enough relevant jobs within a realistic commute, noindex the ones with demand but no supply, merge clusters of overlapping towns into area pages, and stop generating crawlable URLs for combinations nobody searches. That keeps the index focused on pages that can satisfy the searcher on most days, which is what a one-listing count cannot tell you.
Need help with this on your own site?
Niraj Raut works with businesses in Nepal, Australia, the UK, Europe and the US on technical SEO, ecommerce SEO, local SEO and AI search.
- What Google already does with these pages. Put the location pages in their own sitemap and filter the Page indexing report by it. If most one-listing pages are already “Crawled - currently not indexed” or “Soft 404”, Google has partly made the decision for you, and a
Add a reply Cancel reply
Replies are open to approved members. Log in or apply to join.