No. Import creates source inventory. Identity resolution and eligibility determine which entities or collections can support independent pages.
Use case — Directory pages
Give directory pages a quality threshold
A database row is not a search page. Decide which entities and collections have earned an independent page before the source inventory becomes a sitemap.
Page-family model
The decision path
Source records
Start with a real user decision and a maintained source relationship.
Resolved entities
Keep resolved entities attached to the page-family decision before scale.
Eligibility model
Keep eligibility model attached to the page-family decision before scale.
Profiles + collections
Keep profiles + collections attached to the page-family decision before scale.
Quality Gate
Keep quality gate attached to the page-family decision before scale.
Source evidence model
Set eligibility by page job, not a universal field count
Entity profiles and collections need different evidence. The threshold should match the decision each page helps a visitor make.
Page typeEligibility evidencePage job
EntityIdentity, active state, useful attributes, actionEvaluate one entity
CategoryStable definition and useful inventoryUnderstand and browse a class
BrowseExplicit inclusion rule and durable taskExplore a qualified subset
FacetDemand, stable inventory, distinct ownershipRefine without creating an infinite URL space
Evidence threshold
Rich and sparse entities need different page decisions
Sparse records can remain useful inside stronger collections without being inflated into thin independent profiles.
Rich
Independent profile
The entity can support evaluation, context, relationships, and a real next action.
Sparse
Keep inside collection
The record remains discoverable while evidence develops.
Duplicate / expired
Merge or retire
Normalize identity and lifecycle state before assigning or preserving a public URL.
Defensible inventory
Eligibility branches the inventory
Example source inventory: 20,000 records resolve to 18,420 entities. The eligibility model can support 6,280 profiles and 184 stable collections as separate outputs, with Review and Blocked records held for decisions.
Directory hub→Category / Browse→Entity→Facet states
20,000 source records↓18,420 resolved entities↓Eligibility model
↙ 6,280
Eligible profiles184 ↘
Stable collections
Eligible profiles184 ↘
Stable collections
Review and Blocked remain decisions, not automatic pages.
Where pSEO Guard fits
Review entity and collection inventories as one system
Keep normalization, eligibility, hierarchy, freshness, and lifecycle decisions visible before imported records turn into public URLs.
Page Matrix
Available nowModel entity and collection candidates without pretending every imported row is a page.
pSEO Audit
Available nowSurface sparse, duplicate, incomplete, and measurable content-risk patterns across the inventory.
Existing Site Guard
Available nowCheck proposed directory targets against covered live categories, profiles, and landing pages.
Who uses this page model
Connect the model to the operating team
Go deeper on the page model
From commercial decision to implementation detail
How to Qualify Marketplace and Directory Pages
Go deeper on entity thresholds, category jobs, browse logic, facets, normalization, freshness, and lifecycle decisions.
Questions
Decisions before scale
They can remain visible inside a useful parent collection, stay out of the index, or wait for stronger evidence instead of receiving manufactured depth.
No. They are separate outputs of the eligibility model. A collection can be stable even when some entities remain sparse, and a rich entity can qualify independently.
No. Stable IDs and entity resolution belong in the source model. pSEO Guard helps surface weak identity and content patterns before the resulting page inventory scales.
Most facets should remain interface states. Promote only combinations with durable demand, useful inventory, a clear selection rule, and one place in the hierarchy.
Free audit