Use the Action Queue and Fix Generator
Organize LLMIC findings in Queue, prepare supported fixes, review drafts and separate export from website implementation and verification.
The Action Queue and Fix Generator connect audit findings with a deliberate review workflow. Queue helps organize selected work. Fix Generator prepares supported drafts and requires Pro access. The workflow is find, inspect, queue, prepare, review, export, implement and verify. Each stage answers a different question; producing a draft does not mean your website has changed.
What this guide helps you do
SEO content optimization works best when suggestions stay tied to the page evidence that created them. This guide shows how to review the Action Queue, prepare a change, inspect the draft and export only approved work.
Start from a specific finding
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.
Select the work to prepare
Open Queue and select the relevant 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.
Review originals and replacements
Read the original content beside the proposed change where provided. 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.
Export and implement deliberately
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.
Verify the outcome
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
| Stage | Evidence to check |
|---|---|
| Queue | Correct task, website and URL |
| Prepare | Supported task and sufficient input |
| Review | Accurate original and replacement |
| Export | Instructions match reviewed changes |
| Verify | Fresh live-page evidence after implementation |
Continue learning
Next, interpret findings, export useful evidence. Return to the documentation home to explore other guides. If the result differs from these instructions, contact support with your app version and the relevant steps. Remove private information from screenshots and never include API keys or passwords.
Frequently asked questions
Organize LLMIC findings in Queue, prepare supported fixes, review drafts and separate export from website implementation and verification.
Load a completed crawl that includes the pages you need to inspect. Confirm the crawl scope, capture time, rendering choice, and any filters before interpreting the result.
Review the affected URL, measured field, source or rendered evidence, and the rule that raised the item. Inspect nearby pages and templates because one shared component can create the same pattern across many URLs.
Create a task with the affected URL, observed evidence, intended outcome, smallest safe change, owner, and verification method. Keep the measured finding separate from the proposed fix.
Publish the approved change, run a fresh compatible crawl, and compare the new evidence with the saved result. A resolved local finding confirms the implementation changed; search performance requires separate observation over time.
The check cannot guarantee rankings, indexing, traffic, conversions, inclusion in an AI answer, or a future search-engine action. Interpret it with site context, search performance, and editorial judgment.
Save or export the evidence, assign the approved action, and use the related guides linked on the page for the next check. After implementation, repeat the same workflow against a fresh crawl so the result is comparable.