Assign a primary job to each route
A category page should explain a solution type, the comparison dimensions and a set of relevant options. A profile should answer who one participant is and where it fits. The overlap is intentional navigation, but the body content and evidence must differ. Link from category to profiles with a reason, and back from profile to the category's buyer task.
- Write one primary search task for each route.
- Place broad comparison dimensions on the category and entity-specific facts on the profile.
- Inspect GSC query families for overlap before expanding either page type.
Use Search evidence carefully
Search1001's public routes show this structural split. GSC query and page cuts can later reveal whether named-entity queries reach profiles and broader tasks reach category pages. If two URLs attract the same task and repeat the same answer, enrich one primary route before adding a third. The goal is distinct utility, not a larger URL count.
To carry this decision forward, decide whether another route is needed.
Intent-to-route decision table
| Decision field | Record or rule |
|---|---|
| Category | which kind of solution fits this task? |
| Profile | what is this specific participant and where does it fit? |
| Connection | category links to profiles; profiles explain category role. |
- 01Category
- 02Profile
- 03Connection
Link the two routes with purpose
A category page can introduce the comparison dimensions and link to profiles that meet them. A profile can explain why the entity appears in that category and link back to the broader task. The two pages share data but should not share an identical introduction, table and CTA. Review the GSC page and query cuts only after checking this content distinction. If both pages promise the same answer, choose one as the primary route and use the other for genuinely entity-specific facts or merge it.
Shared data must answer different tasks
If two routes answer the same question with near-identical text, enrich one and merge or redirect the other rather than publishing another thin page.
References and source notes
Original 1000&1 methodology reviewed and approved by the author. Public claims and historical measurements are bounded by the linked sources and dates.