WordPress language switch to homepage: what should a support report contain?
Published:
Published by: Hedou Bibi
Record a WordPress language switch to homepage with source, destination, translation status and repeatable steps.

A language switch that lands on the homepage does not prove that the whole translation system has failed. The current article may lack a counterpart, or the switcher may intentionally point to the language homepage. Capture the route before asking someone to change the installation.
Separate the expected result from the observed result
Copy the public source URL and record its heading, current language and the exact control used. State the expected destination, click once, then copy the final URL. Header navigation, a body link and a footer switcher can be separate controls. A report saying only “English is broken” leaves this distinction unresolved.
A small route log
This invented exercise is not a client incident. Add actual URLs, test time and browser details when using it.
Scroll horizontally or use the arrow keys to view the full table.
| Source | Expected | Observed | Next check |
|---|---|---|---|
| Chinese service detail | Equivalent English service | English homepage | Inspect the link and translation relationship |
| Chinese article | English counterpart | No English option | Confirm a published translation exists |
| English article | Same article in Chinese | A different Chinese article | Record the two IDs and saved association |
Check the content before the control
Ask the editorial owner to confirm that the counterpart is public and correctly associated. Similar titles do not establish a saved relationship. Use a bilingual page map to organise the evidence rather than recreating content on the live site.
The Polylang language switcher guide describes options to omit unavailable translations or force a homepage destination. These justify checking the actual configuration; they are not universal repair instructions for every theme. Custom navigation, caches and theme output may also affect the route.
Provide repeatable evidence
Repeat the route while logged out and compare header, footer and body controls separately. Note whether it occurs consistently or only in one browser or session state. Screenshots should show the page and address without exposing credentials or client information.
An authorised technician should test a proposed change on a suitable copy, recording its scope and rollback conditions. Retest both directions, target content and language annotations. Do not present clearing a cache or changing permalinks as a guaranteed fix.
Agree the acceptance result
A useful handover contains source, expectation, outcome, translation status and reproducible steps. Hedou Bibi can discuss an investigation scope based on the actual project. Confirm completion through the working public journey rather than a settings screenshot alone.
