NovAsia

A thin city page does not become useful by adding a thousand words

A city landing page needs a distinct user job, local data and a reason to exist beyond a filter. More generic copy cannot manufacture that value.

This article reflects the named expert’s practical perspective. See NovAsia’s editorial policy for how material is prepared and reviewed.

“Thin content” is often treated as a word-count problem because word count is easy to measure. A city page has 250 words, so the remediation plan asks for 1,200. The new version gets a history paragraph, five investment advantages, several neighbourhood descriptions, a FAQ and a conclusion. The page is much longer. It may still do exactly the same weak job.

Google’s people-first documentation explicitly says there is no preferred word count. Its current generative-AI guidance goes further by warning publishers not to create many pages for search variations merely to influence rankings or AI answers. That makes city pages a test of editorial discipline: does the city genuinely change the answer, or has the site produced another URL because the place name has search demand?

A city page needs a job that a filter does not already perform

Suppose a country catalogue already contains every project and lets users filter by city. A separate Phuket URL can still be valuable, but it should do more than preselect “Phuket” and add generic copy. It might expose project counts by type, meaningful budget bands, construction-stage distribution, district routes, and city-specific caveats. It might make the next choice easier in a way the global catalogue does not.

The current NovAsia Phuket and Pattaya catalogues offer a concrete example of a defensible city job. They show city-specific project totals, filters for type, stage and budget, pagination, and a clear warning that the catalogue is not guaranteed live inventory. That does not make every element perfect, but it creates a functional reason for the city level to exist.

A different page type can serve the same city without becoming a duplicate. NovAsia’s market-insights section is not another project catalogue. It groups dated comparisons around prices, owner costs, rental questions and transaction issues, and it tells readers that the figures are benchmarks, not valuations of a specific unit. The city name may appear on both surfaces, but the job changes.

The problem begins when one landing page tries to absorb every possible intent. It starts as a catalogue, then receives a 2,000-word lifestyle guide, then a market overview, then a legal summary, then a lead form. The team can point to its length, but the user has to work harder to find the thing they came for.

Local value has to survive a place-name substitution test

A useful editorial test is to replace the city name. If a Phuket page can become a Pattaya page after changing place names and a few numbers, most of the prose is not city value. Statements such as “the city attracts investors”, “infrastructure is developing”, “there are options for different budgets” and “rental demand can be strong” are especially easy to replicate without proving anything.

That does not mean every city must have a dramatic unique story. It means the page should not invent one. A shorter functional catalogue is better than a long page full of unsupported distinctions. If the evidence does not support a standalone city guide yet, the site can let the filter or stronger regional hub do the job until there is something real to add.

Useful depth normally comes from differences in data and decisions. A city catalogue can show its actual mix of condos, villas and other formats. A district guide can explain real spatial boundaries and daily routes. A market page can define its sample and date. A foreign-buyer legal guide can remain national if the rule does not change by city, instead of being copied into every location page.

This is where page architecture saves content work. Shared questions should live on the page that owns them. City pages should reference that answer when it adds value instead of reproducing a slightly altered version. The result may have fewer words but more information density.

More copy can make a thin page harder to maintain

Every added factual paragraph becomes a maintenance obligation. Prices expire. Project counts change. neighbourhood labels evolve. transport projects move through planning and construction. A claim about a district can become wrong while the catalogue data below it is current.

Mass-produced city copy therefore creates a hidden cost. The site does not only need to publish it; it needs to keep dozens of similar pages synchronized with reality. If those pages were created mainly to occupy search variants, maintenance tends to be the first thing that slips.

Google’s current generative-search guide calls for distinctive, useful, non-commodity content and explicitly says that producing many variations for fan-out-style queries is not a durable strategy. That is particularly relevant to programmatic location pages. Scale is not the problem. A large number of pages can be entirely justified when the underlying answer materially changes. The weak pattern is scale without changed substance.

For a property business, the best city pages often contain structured utility, not essay-length prose: real inventory segmentation, documented district links, city-relevant comparisons, current project states and honest unknowns. An extra thousand words may be useful if they explain those things. They are not useful merely because a content brief asked for a four-digit word count.

Sometimes the best city page is no city page

SEO planning often assumes that every meaningful location deserves a standalone URL. I treat that as a hypothesis, not a rule. If a location has too little inventory, no independent data and no distinct user task, a dedicated landing page can fragment the site without helping the reader.

The alternative may be a filter state, a section inside a stronger regional guide, or no indexable page at all until the dataset grows. That is not “giving up SEO”. It is refusing to create a page whose only independent feature is the city name.

My preferred test is to remove the introductory copy and look at what remains. Does the page still offer a useful city-level product—inventory, filters, comparisons, districts, evidence, or a specific decision route? If yes, add prose only where it helps people use that product. If nothing useful remains, the problem is not that the page needs more words. It needs a reason to exist.

That is a harder editorial decision than ordering another thousand words, but it creates a healthier site. Search engines then receive pages differentiated by real jobs and real data, while users spend less time discovering that several long city pages are the same article wearing different place names.

Sources

More articles by this expert

Faceted navigation can create thousands of near-duplicate URLs

Why a useful property filtering interface can create an enormous crawl space, and why the solution begins with deciding which filter states deserve to exist in search.

A URL in the sitemap is not an indexing strategy

Why submitting a URL in XML helps discovery but does not replace page quality, internal architecture, canonical consistency or indexing diagnosis.

A search snippet can expose what the page buries

Why query-specific search snippets can surface caveats, stale wording or secondary sections, and what that reveals about a page's information hierarchy.

Organic growth should be measured beyond the click

A framework for connecting search impressions and clicks to landing-page fit, useful next steps and downstream value instead of treating traffic as the final outcome.