Guide

How to Use Your SIGNALS Fix File with Any AI Agent

Last updated: May 28, 2026

A SIGNALS fix file is a pre-formatted AI prompt containing all your page-specific AEO fixes — paste it into Claude, ChatGPT, or Cursor and the AI rewrites your page with the BLUF, FAQ, H2s, and JSON-LD applied, ready to drop into your site in minutes.

Your fix file is the signals-fix-package-*.md you download from the Generated Fixes tab in your SIGNALS dashboard (the ⬇ Download Fix File button). It contains five sections — your BLUF opening paragraph, an FAQ block, H2 heading rewrites, sourced key facts, and JSON-LD schema — each with plain-English instructions. The fastest way to apply it is to hand the whole file to an AI agent and let it do the editing. Here is exactly how, for the four most common tools.

How do I use a SIGNALS fix file with Claude?

Claude is the easiest option for non-technical users — it reads the whole file and returns finished HTML you can paste straight into your site.

Claude

Claude.ai

  1. Download your fix file from the SIGNALS dashboard (Generated Fixes tab → ⬇ Download Fix File).
  2. Go to claude.ai and start a new chat.
  3. Click the paperclip / attach icon and upload the .md file (or just paste its contents into the message).
  4. Paste your page's current HTML or content below it, then send this prompt:Apply every change in this SIGNALS fix file to my page. Add the BLUF as the opening paragraph, insert the FAQ section near the bottom, update the H2 headings, and add the JSON-LD in the <head>. Return the complete updated HTML.
  5. Copy the updated HTML Claude returns — it has the BLUF, FAQ, H2s, and JSON-LD applied. Give it a quick once-over, then move on to “After the AI applies your fixes” below.

Can I use my SIGNALS fix file with ChatGPT?

Yes. The workflow is nearly identical to Claude — the fix file is plain Markdown, so any model reads it.

GPT

ChatGPT

  1. Download your fix file from the dashboard.
  2. Open chatgpt.com and start a new chat (GPT-4o or later works best).
  3. Click the + / attach button and upload the .md file, or paste its contents.
  4. Send this prompt, then paste your existing page HTML when asked:This is a SIGNALS AEO fix file. Apply all of its fixes — BLUF, FAQ, H2 rewrites, key facts, and JSON-LD — to my web page and output the final HTML I can paste into my site.
  5. Copy ChatGPT's output. Verify the BLUF, FAQ, and JSON-LD are all present before you publish.

How do I apply SIGNALS fixes in Cursor or VS Code?

If you edit your site's code directly, an in-editor AI agent can apply the fixes to your source files with a reviewable diff. Cursor and GitHub Copilot both work this way.

Cursor

Cursor

  1. Save the fix file into your project, e.g. docs/signals-fix.md.
  2. Open the file you want to change (your page's index.html, component, or template).
  3. Open Cursor Chat (⌘L / Ctrl+L) and reference both files with @:Apply all fixes from @signals-fix.md to @index.html — add the BLUF as the opening paragraph, insert the FAQ section, update the H2 headings, and add the JSON-LD in the <head>.
  4. Review the diff Cursor proposes and click Apply / Accept.
  5. Save the file and run your dev server to confirm the page renders correctly.
Copilot

GitHub Copilot (VS Code)

  1. Save the fix file into your repository alongside your page files.
  2. Open Copilot Chat in VS Code (the chat icon in the activity bar).
  3. Add both files as context using #file, then send:Using #signals-fix.md, apply the BLUF, FAQ, H2 rewrites, and JSON-LD to #index.html and show me the edits.
  4. Accept the suggested edits in the editor (use the inline Accept controls).
  5. Commit the change so it's ready to deploy.

What do I do after the AI applies my fixes?

Once the AI hands back your updated content, three short steps take it live:

  1. Verify the changes. Confirm the BLUF is now your first paragraph, the FAQ section is present, your H2s read as buyer questions, and the JSON-LD sits inside the <head>. Paste the JSON-LD into Google's Rich Results Test to confirm it validates with no errors.
  2. Re-upload to your hosting. In WordPress, paste the body content into the page editor (use a Custom HTML block for the FAQ) and add the JSON-LD via your theme's header-scripts box or an SEO plugin. In Webflow, use an Embed element; in Shopify, edit the page's HTML. For a static site, save the file and commit-and-deploy. (On paid plans, the SIGNALS Apply tab can push BLUF, FAQ, and JSON-LD to WordPress, Shopify, and Webflow for you.)
  3. Re-audit on SIGNALS. Run the same page through SIGNALS again to confirm the fixes registered and your score moved.

How do I know if my fixes worked?

Re-audit the page on SIGNALS. Your structural readiness score updates immediately — the BLUF, FAQ, H2, and JSON-LD signals are all things SIGNALS can detect on the next crawl, so a correctly applied fix file moves the number right away. If the score did not change, the most common cause is that the JSON-LD landed in the page body instead of the <head>, or the FAQ was added as an image/screenshot rather than real text — re-check both.

AI citation frequency follows on its own timeline. ChatGPT, Claude, and Perplexity re-crawl and re-index pages on their own schedules, so new citations typically appear within 2–6 weeks of publishing the fixes — not instantly. The SIGNALS score is your immediate, controllable proxy; citations are the lagging outcome.

Frequently asked questions

What is a SIGNALS fix file?

A SIGNALS fix file is a single Markdown file that bundles every page-specific AEO fix SIGNALS generated for your page — a rewritten BLUF opening paragraph, a buyer-language FAQ section, question-style H2 headings, sourced key facts, and ready-to-paste JSON-LD schema. It is formatted as a plain-English prompt, so you can hand it to any AI assistant and it will apply the changes for you.

Which AI tools does the SIGNALS fix file work with?

Any large-language-model agent. The file is plain Markdown, so it works with Claude (claude.ai and Claude Code), ChatGPT, Cursor, GitHub Copilot, Gemini, and Perplexity. For non-technical users, Claude or ChatGPT is easiest — paste the file plus your page content and the AI returns finished HTML. Developers can use Cursor or GitHub Copilot to apply the fixes directly in their codebase.

Do I need to know how to code to use it?

No. With Claude or ChatGPT you paste the fix file and your current page content, and the AI returns the complete updated HTML — you copy that into your CMS. Coding tools like Cursor and GitHub Copilot are an optional path for developers who want the edits applied directly to their source files.

How long does it take to apply the fixes?

A few minutes for most pages. The AI does the rewrite and hands you finished HTML with the BLUF, FAQ, H2s, and JSON-LD applied — you drop it into your site (a WordPress block, a Webflow embed, a Shopify page, or a commit-and-deploy for static sites) and re-audit to watch your score move. Citations in AI answers then build over the next 2–6 weeks as the engines re-crawl.

What happens to my SIGNALS score after I apply the fixes?

Your structural readiness score improves immediately — re-audit the page on SIGNALS and you will see the new number right away. Actual AI citation frequency in ChatGPT, Claude, and Perplexity typically rises within 2–6 weeks as those engines re-crawl and re-index your page on their own schedules.

Ready to apply your fixes?

Download your fix file from the Generated Fixes tab, hand it to your AI agent, and re-audit to watch your score climb.

← Back to your SIGNALS dashboard