Technical
Technical finds the problems on your website that stop search engines and AI assistants from crawling, understanding and citing your content. Fixing them clears the path so the content you work hard on can be found, ranked and quoted.
Accessing Technical
Go to Technical in the sidebar. The page answers three questions, top to bottom:
- Site Health: a score from 0 to 100 with one sentence on what holds it back, when the site was last audited, and where the work stands: how many issues are open and, once there are some, the fixes done in the last 30 days.
- Start Here: the three issue types worth doing first, each with what it costs you, the pages it is on and the site health it gives back.
- All Issues: every issue the audit found. Open lists what is left to fix, by issue or by page. Done lists what was resolved or fixed in the last 30 days, also by issue or by page.
Running an Audit
Click Run audit to check your site. Asky crawls your pages and inspects them for technical issues across many categories. The audit runs in the background. When it finishes, the results appear here.
By default the audit reads each page the way most crawlers do: the HTML your server sends, without running JavaScript, which is what ChatGPT, Claude and Perplexity read. The Configure Scan step has a switch, Prefer JavaScript rendering, that reads each page as a browser renders it instead, which is what visitors and crawlers like Googlebot and Bingbot see. A page that cannot be rendered is read without JavaScript, and the audit says how many pages that happened to and why. Each rendered page counts as two pages, and the crawl takes longer. See Crawlers and JavaScript for which crawlers run JavaScript.
How Issues Are Organized
Issues are grouped by type so you can see patterns at a glance, and the list is banded by how serious each type is, the most pages first within a band. Click a band to fold its issues away, and again to bring them back. The checkbox on a band ticks every issue under it, and shows what is ticked there while the band is folded.
| Type | Meaning |
|---|---|
| Critical | A site-wide problem with how search engines and AI assistants reach your site. Fix these first |
| Error | A clear problem that needs fixing |
| Warning | Worth reviewing, may affect some pages |
| Opportunity | A refinement that can improve how AI reads your content |
Each issue also carries a severity of High, Medium, or Low. It weighs into the site health score and the Start Here order, shows when you open an issue, and is one of the filters.
Working Through Issues
Under All Issues, for any issue you can:
- Read in one sentence what is wrong and what it costs, right under its name
- Expand it to see exactly which pages are affected, then expand a page to see what it has now
- On plans with technical fixes, see what Asky suggests instead and how it gets fixed on your site: Automatic (Asky writes it to your connected CMS), or Manual (you apply Asky’s suggestion, or follow the steps)
- Open About this issue to learn what it is, why it matters, and how to fix it
- Copy brief to hand the issue to a developer or an agency: the issue, how to fix it and the affected pages, ready to paste into an email or a ticket
- Mark it resolved once handled, or add it to your Plan
Search, switch between By Issue and By Page, and filter by type, severity, category and how it’s fixed to focus on what matters most right now. By Page lists the pages people see most in search first (with Search Console connected; without it, the pages with the most serious issues come first); click Errors, Warnings or Opportunities to put the pages with the most of those first, and Page to go back.
Suggestions, applying fixes to your site, bulk actions and undo are covered in Fixing Issues.
For a full catalog of every issue Asky can detect, with explanations and fixes, see the Issue Reference.
Next Steps
- Learn how Asky suggests and applies fixes in Fixing Issues
- Browse every detectable issue in the Issue Reference
- See how issues map to specific pages in Pages