Skip to content
SilktideHelp

Languages screen

Inventory > Languages is the audit and correction workflow for page language. For the model behind it - where a page's language comes from and which checks depend on it - see how languages work.

See which languages the website uses

The Content tab opens with a breakdown of the website's HTML pages by resolved language: how many pages use each language, their share of the total, and a chart of the mix. A note such as 15 ambiguous counts pages where Silktide had more than one plausible answer and had to choose, for example reading a plain es as Spanish (Spain).

Under the breakdown, How Silktide knows counts pages by where their language came from: a manual override, a URL rule, the page's own declaration, or the website default.

Select a language in the breakdown to show only its pages in the table below. Select it again to show every page. The table's Language filter does the same.

Review resolved page languages

The table lists each HTML page's resolved primary language, where that value came from, and the page's HTML lang value. Search, sort, or filter the table, then open a row in the Inspector when a page needs closer review.

Website language settings establish the languages Silktide expects. If Trust page-declared language is on in Advanced settings, Silktide can use a page's declared language when it is available. It starts on for websites on accounts that began on Silktide 5, and off for websites on accounts that came from Silktide 4, where every page without a rule or override uses the website default. See how languages work for which declarations are used.

Assign a language by URL

Use the Rules tab when a group of URLs should always use one language. Choose a match type, enter the URL pattern, select the language, and add the rule. Rules can optionally be case-sensitive.

The Languages Rules tab for assigning a language to pages that match a URL pattern.

A URL language rule takes precedence over the page's HTML lang value and the website default. A manual language override for an individual page takes precedence over a URL rule.

Use URL rules for stable patterns such as /fr/ or a language-specific subdomain. Use a per-page override for a genuine one-page exception. After changing a rule, run a new test and return to the Content tab to confirm the resolved language and source.

Relationship to readability

The resolved language, not the text on the page, determines which account-level readability formula applies. A page resolved to the wrong language is scored with that language's formula, or left unscored when its text is not in that language's alphabet. Pages resolved to one of the few languages Silktide does not score yet are not scored. Review the outcome in Content > Readability.

Last updated

Was this page helpful?