Use the Action Queue and Fix Generator

You’ve found an issue. Now you need a change you can review, apply and verify.

Queue helps you organize the work. Fix Generator, available with Pro, prepares supported drafts for review.

Use the workflow below to keep the original evidence connected to the change—and to check the live page after implementation.

1. Start with a finding you can explain

Open an issue and inspect the affected URL before adding work to Queue. Keep the source website and active crawl in mind, particularly after restoring saved results.

A useful task explains the observed problem and intended result. Avoid adding a vague site-wide instruction when the evidence only supports a change on a small group of pages.

2. Select the tasks you want to prepare

Open Queue and select the matching tasks or pages. Use the supported preparation action to move into Fix Generator.

The available draft depends on the task type and the evidence available for that page. Unsupported work needs manual investigation; the absence of an automatically generated fix does not mean the issue has been solved or that all evidence was sufficient.

3. Check every proposed replacement

Read the original content beside the proposed change where available. Check factual claims, intent, tone, page context and any structured-data values.

AI-assisted text is a draft, not a source of truth. Keep deliberate editorial choices and intentional indexing rules intact.

If you edit a replacement after reviewing it, review the changed version again before treating it as ready for implementation.

4. Export, then apply the reviewed change

Save reviewed work and use the available export action to produce implementation instructions or supported patches. Inspect the output before handing it to the person who manages the website.

Exporting a file does not publish a change. Apply the exact reviewed change through your website workflow, preserve a rollback option and confirm that the live URL reflects what you intended.

5. Verify what changed on the live page

Run a fresh check against the changed page after implementation. Use comparable scope and the same relevant evidence layer.

A manual completed status records your task management decision; it does not replace a measured verification result. If the page cannot be fetched or rendered completely, retain that limitation.

Changes in rankings or traffic after the fix can have other causes and should not automatically be attributed to the draft.

Quick reference

Continue learning

Ready for the next step? Start here: interpret findings, export useful evidence.

If you still need help, contact support with your app version and the steps you tried. Leave out passwords, API keys and private account details.

Published by LLMIC. Documentation reviewed on 24 September 2026.