Fixing Issues

Asky does more than list technical issues. For each affected page it works out what should change, shows you the exact new value, and, where your connected CMS allows it, writes the change to your site when you apply it.

How Each Issue Gets Fixed

Every issue type is labeled by how it gets fixed on your site, based on the CMS you connected and how that CMS is set up.

Without a connected CMS, every issue is Manual: you still get the suggestions and the steps.

A page on a site Asky is not connected to, such as a subdomain run by another team, is always Manual, even when the issue type is Automatic on your main site. The page shows that site’s address so you can tell them apart.

The Technical Overview

Technical opens on an overview of your site’s technical health:

• Open issues, Automatic, Manual: how many pages are affected, and how many of them Asky can fix for you
• Done in 30 days: the technical tasks marked done on your Plan in the last month, including the ones Asky fixed for you. Click it to see them
• Last audit: when the site was last checked, and how many pages the audit covered
• Open issues over time: a chart of how many issues were open per day or per week, which moves when an audit runs or a fix goes live
• Start here: the few issue types worth doing first. Asky weighs how serious each one is and how many pages it affects, and puts a quick automatic win ahead of an equal one you would do by hand
• In your plan: the technical tasks already open on your Plan

Click any card or item to open Site issues with the matching filter applied (Done in 30 days opens the Plan instead). A Start here or In your plan item opens just that one issue type.

Site Issues

Site issues lists every open issue type with the pages it affects. Filter by type, severity, category and status, and use How it’s fixed to show only Automatic or only Manual issues.

Expand an issue type to see its pages. Expand a page to see:

• what the page has now, for example its current meta description
• what Asky suggests instead, which you can edit before applying
• where the fix stands: no suggestion yet, suggested, kept as is, or fixed

Suggestions

Asky treats every fix as a judgment, not a rule. For each page it reads the page itself, your site’s other pages and, where connected, your Search Console data, then decides one of two things:

• Change: the exact new value, written in your page’s own words, keeping its terms, numbers and spelling
• Keep: a short reason the page is better left as it is. A title one character over a length guideline that reads well is kept, not rewritten. Mark the issue as resolved to make that stick, or ask for a change anyway

Some fixes come with a choice rather than a single value. For generic link text such as “click here”, Asky either moves the link onto words already in the sentence or proposes new link text that fits it, and tells you when a sentence needs rewording instead.

Applying a Fix

1. Review the suggestion and edit it if you want to.
2. Click Apply. Asky asks you to confirm before anything is written.
3. Asky writes the change through your CMS, clears the page cache where it can, and checks the live page.
4. The page shows Fixed by Asky. The issue closes once the live page confirms the change.

Asky never writes a change you have not approved, and it records the value it replaced, so you can Undo an applied fix and put the old value back. Each change also appears on the issue’s task in your Plan, completed by Asky.

For a Manual issue, Copy the suggestion (or the prompt), make the change in your CMS, and mark the issue as resolved, or let the next audit confirm it.

Working in Bulk

Tick pages across one or several issue types to act on them together:

• Suggest writes suggestions for every ticked page that has none yet. Large runs happen in the background, and Asky works once per shared item: an image used on 40 pages gets one alt text, not 40
• Apply applies every ticked page whose fix is Automatic, after one confirmation
• Mark as resolved closes the ticked pages

Asking the Asky Agent

You can also ask the in-app agent, for example “fix the missing meta descriptions on our site”. It finds the issues, proposes the fixes in one card for you to review, and applies them only after you approve. The agent’s counts match the ones on Site issues.

What Can Be Automatic

What Asky can write depends on your CMS and how it is set up. Asky scans your CMS when you connect it and labels every issue type for your site, so the labels on Site issues are the answer for your setup. The WordPress, Webflow and Sanity pages say what each CMS needs.

Next Steps

• See every issue Asky detects in the Issue Reference
• Set up WordPress, Webflow or Sanity so Asky can apply fixes
• Track technical work on your Plan