Separate public search routes from protected areas
Avoid treating access controls as SEO errors.
Use this for: Public pages and their required resources within the sampled template or URL group.
List pages intended for public search and routes that must stay private. Include required public assets separately. Search visibility is not a reason to open account, admin, staging or internal API routes. Use the public/private boundary as a requirement for every later fix.
Compare the same URL and intended public state. Record a short finding only if it helps you or the person making the fix; no screenshot or evidence upload is required to complete this checklist.
Hypothetical example: A public guide needs access, while its CMS admin panel must remain restricted.
- Identify public templates.
- List deliberately protected areas.
- Confirm the boundary with the site or security owner.
More help and optional notes
Before you begin: Permission to inspect the relevant site or diagnostic account.
If it fails: Define explicit scope before changing any rule.
Retest: Repeat the same comparison after the change, then check another URL using the same template or rule.
Not applicable: The tested feature or response variant does not exist.
Keep in mind: A passing sample does not establish that every URL behaves correctly or guarantee indexing.
Optional: URL, time, expected result, observed result and next action. Keep confidential data out of shared exports.
Changing this result updates your checkmark and progress immediately. Notes are optional.

