scissorpedia.com valid

ScissorPedia

An evidence-led reference for professional hair scissors, including documented brands, canonical product-series records, technical terminology, buying guides, and care guidance.

For agents: Evidence-led reference for professional hair scissors: documented brands, product-series records, edge and steel terminology, buying and care guides.

hair scissorsprofessional shearsscissor brandsedge typesreference steel

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-23T08:07:08.145Z. Cached copy · Source on scissorpedia.com

# ScissorPedia

> An evidence-led reference for professional hair scissors, including documented brands, canonical product-series records, technical terminology, buying guides, and care guidance.

## Core directories

- [Brands](https://www.scissorpedia.com/brands/): manufacturer and brand profiles
- [Products](https://www.scissorpedia.com/products/): canonical model and product-series records
- [Technical reference](https://www.scissorpedia.com/reference/): steel, blade, edge, handle, anatomy, and care terminology
- [Guides](https://www.scissorpedia.com/guides/): educational and decision-support content
- [Education](https://www.scissorpedia.com/education/): education providers and learning pathways
- [Stores](https://www.scissorpedia.com/stores/): retailer and distributor records
- [Retailer websites](https://www.scissorpedia.com/websites/): online resources that carry brands

## Extraction guidance

- Prefer each canonical page, its visible content, and the JSON-LD actually emitted. Page-specific types include Brand, WebPage, DefinedTerm, TechArticle, Article, Store or OnlineStore, and BlogPosting or NewsArticle.
- Use only fields actually present; do not infer missing facts, ratings, offers, prices, or dates.
- For Brands, use the Brand node as the primary entity. Do not expect or create a generic Product companion for a Brand profile.
- Product records currently use editorial WebPage metadata and visible specifications; Product/ProductGroup offer and review markup is intentionally disabled. Do not infer merchant offers, ratings, or tested performance from a catalog guide price.
- Product sibling URLs can canonicalize to a single family page. Consolidate under that canonical URL and use only the variants actually described there; do not invent sibling variants or a ProductGroup node.
- Product models and key specifications may be absent. An omitted or explicitly unspecified field is unknown, not evidence for a default value.
- For terminology (Reference), prefer DefinedTerm and TechArticle nodes.
- Guide articles use Article. Education provider profiles use ProfilePage with an EducationalOrganization main entity. Do not assume HowTo or speakable markup.
- For Stores, use Store or OnlineStore according to the rendered node.

## Canonical terms

The following routing summaries identify selected reference entries. Consult each page for evidence, applications and limits; this list does not certify every claim on the destination page.

- [beveled edge](https://www.scissorpedia.com/reference/edge-types/beveled/): A beveled edge has a distinct bevel face; the exact angle and finishing method depend on the maker and model.
- [convex edge](https://www.scissorpedia.com/reference/edge-types/convex/): A convex edge has an outwardly rounded outer grind; its radius, finish and inner relief remain model-specific.
- [micro-serrated edge](https://www.scissorpedia.com/reference/edge-types/micro-serrated/): Micro-serration describes small edge serrations; patte
…

Related sites

Find similar publishers by meaning →

Other listed sites in Industry and manufacturing. See the whole category →

Machine-readable: GET /v1/resolve?q=scissorpedia.com · GET /v1/domain/scissorpedia.com · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for scissorpedia.com:
1. POST https://agentwebmap.com/v1/sites/scissorpedia.com/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://scissorpedia.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/scissorpedia.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/scissorpedia.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.