Fix SEO issues automatically on your live site
VectraSEO’s Implement button turns a site-health issue or a Search Console recommendation into a published fix. It reads the current live page, builds the smallest patch that resolves the issue, re-checks it against the metadata and content-quality gates, republishes through your connected CMS and requests a recrawl. Pages it cannot write to get a change set you apply yourself, and if the live page cannot be read safely the fix is skipped rather than overwrite it.
Updated
What gets fixed
On a Site health monitor, the Implement button appears on four kinds of issue. Three of the fixes are deterministic: they change only what the issue names and use no AI model. One is written by a model and is grounded in what the article already says.
- Broken links — Unwraps links whose destination is confirmed dead and keeps the link text. A link it cannot confirm is left alone.
- Missing structured data — Adds a schema.org Article JSON-LD block built only from data the post already has.
- Images missing alt text — Adds alt text only from what the page already says: a caption, the image title or a descriptive filename.
- AEO answer structure — Adds a 40-80 word answer block after the first heading. This one is model-written.
Your live page is the source of truth
For a published post, VectraSEO patches the page as it is live now, not a stored copy, so an edit you made in your CMS or by hand is kept. If the live page cannot be read, or its editable content cannot be isolated with confidence, the fix is skipped and the page is left untouched.
A successful update response is not taken as proof. After republishing, VectraSEO re-reads the live page. If your CMS accepted the update but the page did not change, which usually means a static site that does not rebuild on update, the fix is reported as unverified instead of published.
Three kinds of page
What Implement can do depends on whether VectraSEO can write to the page.
- Written by VectraSEO — A post VectraSEO generated. The fix is applied to the live page and republished through your CMS.
- Your connected CMS — A page VectraSEO did not write but your connected CMS can find and update. Applies to single-issue fixes that change the page body; WordPress supports finding a page by its URL.
- No write access — Any other page. VectraSEO builds a change set: the patched HTML plus instructions. Nothing is published.
How to fix a site-health issue on your live page
Open Site health
In your project, choose Site health in the project menu and open a monitor. Run a scan first if the monitor has none.
Expand an issue
Under SEO issues or AEO readiness issues, select an issue group to expand it and see the affected pages.
Select Implement
Select Implement next to the page. The fix starts straight away and the button reads Working… while it runs.
Read the outcome
A successful fix reads “Published the fix. Recrawl requested.” Other outcomes say what happened: unverified when the live page has not changed yet, held back when a quality check failed, or skipped with the reason. Select Retry to try again.
Apply a change set where there is no write access
For a page VectraSEO cannot write to, it says “No write access — here’s a change set you can apply.” Use Copy for the instructions or Download HTML for the patched content, and apply it in your own editor.
Rewrite a title or meta description from Recommendations
Choose Recommendations in the project menu, select Open action on a recommendation, pick one of the suggested titles or meta descriptions, then select Implement title rewrite, Implement meta rewrite or Implement title + meta rewrite. The drawer shows the before and after text.
Frequently asked questions
Will a fix overwrite changes I made in my CMS?
No. For a published post, VectraSEO reads the live page and patches that version, so edits made outside VectraSEO are kept. If it cannot read the live page or cannot isolate its editable content, it skips the fix instead of republishing an older copy.
What does an unverified fix mean?
Your CMS accepted the update, but the live page had not changed when VectraSEO re-read it. This usually means the site does not rebuild when a post is updated. Rebuild or redeploy the site, then check the page.
Which CMS platforms can take a fix?
Fixes to posts VectraSEO wrote republish through any of its CMS adapters. Wix updates carry only the title and excerpt, so a fix that changes a post body cannot be republished to Wix, while metadata fixes can. A Custom API endpoint must accept PUT {publish_path}/{id} for fixes to land.
Do fixes need a paid plan?
The deterministic fixes for broken links, structured data and image alt text work on every plan. Model-written fixes, such as answer blocks and title or meta rewrites, need a paid plan or an active trial.
Can I fix every page with the same issue at once?
Yes, through the API or the MCP server. The implement-batch endpoint fixes every page one rule flagged in a scan as one job, and apply-all applies Search Console recommendations, with a dry run first. Both are described in the one-click fixes section of the docs.