Website & SEO

Fix issues automatically

Search all guides

What this is: On an opportunity's detail page, Fix now writes a single fix straight into your live site, and Fix all does every fix the page can take in one pass. You always see exactly what will change before anything is written.

Prerequisite: WordPress or Webflow must be connected in Settings → Integrations, and the page has to exist in that CMS. Without a connection the buttons appear greyed out with the reason attached.

How it works

  1. Open an opportunity from the Opportunities tab and run Analyze opportunity.
  2. Each issue in the On-Page, Technical, E-E-A-T and Internal links tabs now shows a Fix now button when it can be applied automatically.
  3. Click it. A Review changes dialog opens showing every field that would change, with the current value beside the proposed one.
  4. Untick anything you don't want, then click Apply to live site. Changes are grouped by issue: when one issue needs several changes (for example alt text for each image on the page), they are applied together, so unticking one unticks all of them.

Fix all at the top of the page does the same thing for every fixable issue at once. Tick Show only issues that can be fixed automatically to hide the rest while you work.

Gotcha: On WordPress these changes go live immediately, with no draft step, which is why the review dialog exists. Read the proposed values before you apply them. On Webflow, if the item can't be published directly, the change is saved as a draft and goes live the next time you publish your site.

What can be fixed

This depends on which CMS you have connected, because the two platforms expose different things to us.

IssueWordPressWebflow
SEO title, meta description, canonical URL, social title and descriptionNoYes, when the field is mapped
Structured data (Article, FAQ, Breadcrumb, HowTo)YesNo
Image alt textYes, with the Airfleet SEO plugin activeYes, for images in the article body
TL;DR summary blockYesYes
Multiple H1 headings, H1 missing the keywordYesYes
Headings starting at H3YesYes
Underscores in the URLYesYes

Image alt text is written from the image itself, not from its file name. On WordPress it needs the Airfleet SEO plugin installed and active; without it the button stays greyed out and says so. An image we can't load or describe is left alone rather than given a guessed description.

On WordPress, your SEO plugin owns the title, meta description, canonical and social tags. They are not reachable through the WordPress API, so those rows stay greyed out with an explanation and you edit them in WordPress itself.

On Webflow, we edit the CMS collection item behind the page. Metadata fields work when you have mapped them under Settings → Integrations; a field you have not mapped says so. Structured data cannot be added because Webflow rich text strips script tags, and static (non-CMS) pages cannot be edited at all. Fixes only edit the article body field, so if your collection keeps the introduction in its own field the TL;DR fix is unavailable, and if those other fields contain headings the heading fixes are unavailable. Both say so and you make that change in Webflow.

Headings shown by your template. On most sites the page's H1 is the post title, rendered by your theme or Webflow template rather than written in the article body. So a "keyword missing from H1" fix renames the post title, and a "multiple H1" fix turns the H1 in the article body into an H2. Images in your template (logo, menu icons) can't be edited here, only images inside the article.

If there is nothing to change on the page for an issue, its button stays greyed out and hovering it tells you why.

Some issues are never applied automatically, and the button explains why when you hover it. Serving a page over HTTPS is a server setting. Adding section headings or a call to action is an editorial change. For those, use Apply with AI to draft the change and apply it yourself.

URL changes need care

A fix that changes the URL slug is unticked by default in the review dialog and marked in red. Changing a live URL breaks every existing link to that page unless you add a redirect from the old address first. Set up the redirect, then come back and tick it. Any other changes that belong to the same issue start unticked too, and tick together with the slug.

What gets written, and undoing it

Everything applied to a page is written in one pass, so a structured-data block, a TL;DR and a set of alt attributes become a single save rather than several.

Every change is recorded with the value it replaced.

If the page changed between previewing and applying, the fix is skipped rather than overwriting the newer content, and the dialog tells you to re-run the preview.

Related

Ready to publish on autopilot?

Start a 14-day free trial, or book a walkthrough.