Test my install
On this page
The install check looks at your live page the way a visitor's browser would receive it, and tells you what is wrong. Open your site page in the dashboard and choose Test my install. It is also available to programs: see Sites in the API.
What it does#
- It loads one page of your site. By default that is your home page. You can name another page, but it must be on one of the origins listed in your site settings.
- It also loads your robots.txt, the loader file, and the translation manifest from each delivery address (your site, CDN 1, CDN 2).
- It then runs about 30 checks and gives each one a result, a fix and a link to a help article. At the top it shows a score from 0 to 100.
What it does not do#
- It does not run JavaScript. It reads the page's HTML and headers. If your theme adds a line with JavaScript after the page loads, the check cannot see it. A "browser check" that runs the page in a real browser is a possible later step: OPEN.
- It never connects to private or internal addresses.
- It does not keep your page. It stores only the findings and short notes of the last check for each site. The next check replaces them.
How to read the result#
| Result | Meaning |
|---|---|
| Pass | This is right. |
| Review | It works, but could be better or could break later. |
| Fix | This stops translation or hurts your visitors or search results. |
| Note | Something to know. It is not counted in the score. |
| Not checked | The check could not run, and the reason is shown. |
A page that has a Fix on something essential (the script, its keys, the policy, the manifest or its signature) is shown as Not working yet, and its score stays below 50 until that is fixed.
The checks#
- The script: it is on the page once, in the head, with your site key and the right verification key, over https, and not delayed or rewritten by a speed plugin.
- Your content security policy: it lets the script, the translation files and the switcher's styles through. See Content security policy.
- Delivery: the manifest is reachable from each address, signed with your key, the same version everywhere, and cached for a short time only. See If our servers are down.
- Page and search: the language switcher is visible, the page has the right
langanddir, the hreflang and canonical links agree with your languages, nothing says "noindex", and robots.txt does not block the translation files. See hreflang. - Conflicts: another translation plugin on the same page, or a page builder or framework that rebuilds the page. See Other translation plugins.
Limits#
You can run the check a few times every ten minutes for each site, and a limited number of times per hour for your account. If you reach the limit, the page shows when you can try again.
When it says the page cannot be checked#
- 403 or a login page: a firewall or maintenance mode is in front of the page. Allow the checker (ResilientLangBot) or test a public page.
- robots.txt disallows the checker: allow ResilientLangBot for this page.
- Redirects to another site: add that site to your allowed origins, or test the final address.
- Too slow or too large: try a lighter page.
The detection of other plugins and page builders uses the markup they are known to leave on a page. It can miss one, or name one that left old files behind: verify on your own page.