Understand the issue first
A report finding is a starting point. Before changing the site, ask which page or service is involved, what might happen to visitors, and what TrustyRunner actually observed.
Why a careful approach helps
A change made without context can break something useful: a security rule may block legitimate resources, a redirect may lead to the wrong page, and an email record may stop authorized messages. A useful fix addresses a verified issue while keeping the rest of the site working.
Check the evidence
Open the dedicated guide and separate observed fact, possible effect, and scan limit. For example, a header missing from one response does not show that it is missing from every page. If the check lacked enough data, resolve that uncertainty first.
Choose a priority
Start with the effect on the site: an important page that cannot be reached, an essential feature that does not load, and an expected protection that is absent may call for different responses. Reported severity helps orient you, but also consider how many pages are involved, how conclusive the evidence is, and who can act.
Change and test
- Find which configuration produces the result and involve your host or developer if needed.
- Change one thing at a time, preferably in a test environment or on a representative page.
- Check that the affected feature still works as intended; if the change does not help, restore the previous setup.
After the change
Run a new scan and compare the result, taking account of the portion of the site examined. Getting Started helps you choose where to begin; the Security Headers guide shows how to read a finding in the context of its observed response.