After the diagnosis: what you actually do #
Every Lens diagnosis ends with a triage route telling you what to do next. The route comes from the rule engine: it reads the CSS evidence and determines the most likely fix path based on what it found. Some problems you can resolve yourself in a few minutes. Some need a developer. Here’s what each route looks like and how to act on it.
Route 1: DIY override #
Lens generates an exact CSS rule you can copy and paste. This route applies when the fix is a straightforward override: a more specific selector that will beat the conflicting rule, scoped as tightly as possible so it doesn’t affect other elements.
Lens only offers this route when it’s confident the override is correct and safe. It won’t generate a rule that might break other elements, and it won’t reach for !important unless that’s genuinely the only option given the specificity situation.
How to use it:
- Copy the CSS rule from Fight View or the Triage Page.
- In WordPress, go to Appearance > Customize > Additional CSS, or to your Page Builder’s custom CSS field for the specific page or element.
- Paste the rule and save.
- Reload the page and confirm the problem is resolved.
If the fix doesn’t take effect after pasting, clear your Caching Plugin’s cache and your Browser Cache before testing again. Cached pages often serve the old CSS even after you’ve saved a new rule.
The Triage Page may show up to 3 variants of the override: a base version, a version scoped to the current page only, and a version that updates a CSS Variable at its definition point. See The Override Prescription for when each variant applies.
Route 2: Developer handoff #
The fix requires code-level work. This applies when the conflict can’t be safely resolved with a CSS rule you paste in: custom code conflicts, theme template issues, plugin bugs, JavaScript-injected styles, or situations where adding an override would be the wrong approach.
Lens gives you 2 things:
- A pre-written message that explains the problem in specific terms your developer can act on immediately. It names the conflict, the origin of each competing rule, and the recommended fix approach.
- The capture file, which contains the full CSS context your developer needs to locate the problem and write a fix without asking follow-up questions.
Copy the message, download the file, and send both. See The Lens Capture File for what your developer receives.
Route 3: Capture insufficient #
Lens captured the element but didn’t find enough information to produce a confident diagnosis or a safe override. This happens when the element’s CSS state is ambiguous: the data is there but doesn’t match a known problem pattern clearly enough to act on.
A capture-insufficient result isn’t a failure. The capture file still contains the full CSS picture. Download it from the Triage Page and share it with a developer. The data is complete even when the automated classification isn’t.
When the triage doesn’t fit your situation #
If the suggested route doesn’t work for your setup (for example, Route 1 suggests pasting CSS but you’re on a managed platform without a custom CSS field), use the capture file. Download it from the Triage Page and share it with your developer or your platform’s support team. The file contains everything needed to understand and fix the problem regardless of which route Lens suggested.