INDEXKIND / FIELD NOTES

How it works

The workflow, examples and limits behind every tool.

01

Robots tester ↗

The most specific matching user-agent groups are merged. Longest matching path wins; Allow wins equal-length ties. Supports * and trailing $.

Example: Disallow: /private/ blocks /private/a, while Allow: /private/public/ allows its more specific path.

Tests pasted rules only, not live website access. Unrecognized directives are reported; network responses, headers and indexing are not evaluated.

02

Sitemap builder ↗

Absolute HTTP(S) URLs are validated, deduplicated and required to share one origin; XML text is escaped.

Example: Two distinct URLs produce two loc entries; repeated URLs are included once.

Up to 500 URLs. No site crawling, URL status checking, or search-engine submission is performed.

03

Language tags ↗

Each language code must be unique; every supplied page should include the same full set, including self-reference. x-default is optional.

Example: en and zh-CN URLs generate two alternate links; add x-default for an explicitly chosen fallback.

Checks basic supported language/region codes, not remote reciprocal links. Install the tags on the actual pages and verify deployment separately.

04

Search preview ↗

The preview uses your entered text with a fixed visual layout. Character counts use Unicode code points.

Example: Enter an English title and description, then switch to a Chinese page to edit localized metadata.

Search engines may rewrite snippets and vary display by device. This is an illustration, not a pixel-perfect ranking or truncation predictor.

05

Local work, explicit limits

Each workspace reports its input and file limits. Imports validate the supported format before asking to replace saved work. Plain text is displayed as text, never executed as markup. Both languages use the same tools; the root address always opens in English, with Chinese under /zh/.

Back to the toolkit →