What appears in this index
This index lists pages that are published and indexable. A page reaches that state only after passing every gate the platform applies: minimum useful depth, unique title, description, H1, and opening paragraph, a unique FAQ set, valid internal links, no unsupported factual claims, and near-duplicate scores below the configured thresholds.
Pages held in the registry that fail any of those gates are marked non-indexable and are excluded here, from the XML sitemaps, and from internal navigation. They are not quietly published at lower quality.
How the site is organised
Four main branches, each with a hub page and a set of pages beneath it.
- Services — one page per approved service, grouped by system
- Locations — Houston-area markets, with selected service pages beneath the markets that warrant them
- Industries — planning by property type and operating environment
- Guides — planning questions answered individually
What a page has to clear to appear here
The gates are automated and they run over the whole registry at once, because several of them are comparisons between pages rather than checks on a single page in isolation.
- A minimum useful word count for its page type, applied as a floor rather than a target
- Unique title, meta description, H1, opening paragraph, and FAQ set across the entire registry
- The content modules its page type requires, in a sequence that varies by type
- Near-duplicate scores below threshold on both raw text and entity-masked text
- At least three genuinely local elements on any page that names a city
- No unsupported factual claims about credentials, partnerships, pricing, or availability
- Internal links that all resolve to published pages
Why the published count is smaller than the candidate count
The platform maintains a registry of thousands of conceptually valid URLs. That registry exists for editorial planning, not publication. Candidates are not routable, not crawlable, and not present in any sitemap — requesting one returns a genuine 404. Pages move from candidate to published only when there is enough real content to justify the URL.
The entity-masked similarity check is the specific reason this index stays short. It replaces every service, city, and industry name with a placeholder and then compares pages again. Two pages that differ only by a swapped city name score near-identically on that pass and are demoted automatically, which makes the usual way of inflating a local service site structurally impossible here.
Frequently asked questions
Why is this index shorter than expected?
Because it only lists pages that passed the quality gates. The platform is built to support far more URLs than it publishes, and the difference is deliberate — a candidate URL with no distinct content behind it is a doorway page, and publishing it would make the site worse.
Does this page replace the XML sitemap?
No, they serve different readers. The XML sitemaps are segmented by page type for crawlers; this index is for people. Both draw from the same published set, so they cannot disagree.
