Technical

Use the Technical queue to fix what’s stopping AI crawlers from reading your site properly.

Technical overview

Technical is one of the three recommendation categories in the sidebar. The number next to it is how many items are still open.

Everything here comes from the site audit, so each item is about your website rather than about your Suparanku settings. The app’s description of the category: “Make your site easier for AI crawlers to read.”

These are also the items that move SRPS. A failing check in the audit and a card in this queue are the same finding seen from two angles — the audit tells you what’s wrong, the card tells you what to do about it.

What lands here

Items are raised from the audit’s failing checks. In practice they cluster into:

• Access — robots.txt blocking AI crawlers, so assistants can’t read your site at all.
• Identity — no Organization structured data, missing FAQ markup where the page is clearly a Q&A.
• Meta and social — a weak or templated meta description, a thin social card.
• Content signals — URLs that say nothing about the page, a stale year left in the copy, content that isn’t broken up enough to be extracted.
• Indexing — pages Google hasn’t indexed, where Search Console is connected.

Each card names where it applies: this page, domain-wide, or a count of affected pages.

Good to know Fix the items marked Blocker before anything else. While a blocker is failing, the page’s SRPS is 0 and its deep audit is skipped entirely — so the other cards for that page can’t improve anything yet.

How these are prioritized

Every card carries a priority of High, Medium or Low, with an estimated impact and an effort label, and the queue arrives already ordered.

Statuses work the same as everywhere else: Open, In progress, Done, Skipped, Resolved. Technical cards are the ones most likely to close themselves — once you’ve deployed the fix, the next audit stops detecting the problem and the card becomes Resolved without you touching it.

When the queue is empty the screen says “No technical blockers found — AI crawlers can read your site.”

How to work through them

Open a card to see The problem, Why this matters and How to do it. Where the fix is code, the card also carries a Ready-to-use snippet with a Copy button — structured data, meta tags, robots rules — already filled in with your brand’s details.

Most of these need whoever maintains the site. Two things make handing them over easier: the card lists the affected pages, and the page audit has a Copy brief for any AI agent button that packages the finding, the fix and the acceptance criteria in one block.

• To see the same findings check by check, open Page audit.
• To re-check after deploying a fix, re-run the audit on that page — see Site audit.
• For what the resulting score means, see SRPS.

For the queue mechanics, see Recommendations.

What it does not mean

An empty queue doesn’t mean AI cites you. It means nothing on your site is in the way. Removing obstacles is necessary and not sufficient — being worth citing is the other half, and it lives in the Content queue.

It isn’t a full technical audit of your site. These checks are about being found, read and quoted by AI assistants and search engines. Security, accessibility, code quality and browser compatibility are outside what the audit looks at, even where a finding touches them.

It isn’t a general SEO audit either. There’s overlap, and there are things a search-focused audit would flag that this one doesn’t, because they don’t affect whether an assistant can use the page.

Clearing it doesn’t move SRPS to 100 by itself. Some checks have no fix to recommend, some are yours to verify by hand, and some findings are informational.

It’s not a rewrite request. Almost everything here is markup, headers and configuration — the things that decide whether your existing content can be read, not what it says.