AEO NIUEXA

Auto-Fix

8 min read

How Auto-Fix Works

Auto-Fix turns a page's failed checks into fix rules and delivers them three ways. Pick the one that matches who needs to see the change:

Script tag

One line in your site's head. The script applies the fixes in the visitor's browser when the page loads. Crawlers that run JavaScript (Googlebot, partly Bingbot) see them; most AI fetchers do not run scripts and will not.

Cloudflare Worker

If your site runs through Cloudflare, a worker writes the fixes into the HTML before it is sent, so every crawler sees them.

Permanent fix

Copy permanent fix gives you the change as plain HTML or JSON-LD to paste into your own template, where it stays for every crawler.

Create and Install a Script

  1. Scan the page, then choose Generate Auto-Fix script on its report's Overview tab, or Generate new script in the Auto-Fix workspace and pick the page
  2. Choose Embed code and add the script tag inside your site's head. Site-wide fixes apply on every page; page-specific fixes only on the page that was analyzed
  3. Follow the install guide for your platform: WordPress, Shopify, Wix, Google Tag Manager, plain HTML or the Cloudflare Worker
  4. Choose Check installation (next section)
  5. Turn single rules on or off under Manage fixes at any time
<script async src="https://aeo.niuexa.ai/api/v1/autofix/script/YOUR_TOKEN.js"></script>
The Auto-Fix workspace: one active script with 23 fix rules on 3 observed pages, with the actions Manage fixes, Embed code, Check installation, Analytics, Download llms.txt and Pause.
The Auto-Fix workspace: each script with its rules, its install status and its actions.

Checking the Installation

Check installation fetches one of your public pages and looks for the script tag in its HTML. The answer is found, not found or could not fetch. A script added through a tag manager is not in the page's HTML, so "not found" is a hint, not proof: open the page and look in your browser's developer tools. The check also lists the fixes a Cloudflare Worker wrote into the page. You can run it 10 times an hour.

Once the script is installed, the status shows when and on how many pages it was last seen, and Analytics lists the pages it ran on and the fixes it applied.

What Auto-Fix Can Change

Rules are created only for checks the page failed. Each rule can be turned off on its own.

Manage fix rules: 22 of 23 rules enabled, with rules such as Add alt text to 2 images, Add ARIA landmark roles and Add Person schema, each with a checkbox, and Copy permanent fix under the alt text rule.
Manage fix rules: switch rules on or off, and copy permanent fixes where they exist.
Area Fixes
Structured data Organization, WebSite and Article markup; FAQ, HowTo, author, date and contact schema where the page has that content
Head tags Meta description and other missing meta tags, Open Graph tags, the canonical link, resource hints
Accessibility Image alt text, ARIA landmarks, skip links, form, table and SVG accessibility
Links Safe attributes on links that open new windows
Content Answer blocks from an approved article (see Content briefs and articles); a generated llms.txt to download and publish yourself

Permanent Fixes

For structured data, meta tags, Open Graph tags, the canonical link and alt text, a rule has a Copy permanent fix button. It gives you the same change as plain HTML or JSON-LD to paste into your own template, so it is in the page itself for every crawler. Values we cannot know are left out rather than invented, and alt text comes as guidance, because only you know what each image shows. The snippet uses the address the page publishes. Other fix types are built in the visitor's browser and have no copy-and-paste version, so keep the script installed for them. Developer tickets on the site dashboard carry the same snippets.

Cloudflare Worker

For sites whose traffic goes through Cloudflare's proxy (the orange cloud on your DNS records). The worker adds structured data, meta and social tags, the canonical link and image descriptions to your pages' HTML before they are sent, so every visitor and every crawler gets them, including crawlers that do not run JavaScript.

The Cloudflare Worker tab of the install guide: what the worker does, the Download worker file button and the steps to create the worker in Cloudflare and add the route.
The Cloudflare Worker install guide.
  1. In Embed code, open the Cloudflare Worker tab and download the worker file
  2. In Cloudflare, open Workers & Pages → Create, create a worker from the Hello World template, then choose Edit code, replace all the code with the downloaded file and Deploy
  3. In the worker's Settings → Domains & Routes, add a route for your domain followed by /*, and a second one with www. if your site uses it
  4. Run Check installation: it lists the fixes it found in the page's HTML
  • The worker only adds what is missing: it never replaces a canonical, a JSON-LD type or a tag the page already has, and marks what it adds with data-aeo-fix="worker".
  • It only touches successful HTML pages on your script's hosts. If anything goes wrong, it sends the page unchanged.
  • The fixes are written into the file when you download it: download it again after you change your fixes.
  • Other fixes, such as answer blocks, still need the script tag.

llms.txt and Pausing

Download llms.txt gives you a generated llms.txt file to review and publish at your site's root if you want one. llms.txt is optional and unproven: no major AI engine is shown to use it, and the check is not scored. Pause stops a script from serving fixes until you resume it: your pages stop receiving the fixes, and the script tag can stay where it is.