Technical
Use Technical recommendations to investigate site findings, apply a fix and recheck the relevant evidence.
Technical queue overview
Technical turns site findings into remediation work. One issue can affect the domain, one page or a group of pages. Check the scope before handing it to your website maintainer.
Standard and deep audits supply findings with different coverage. Connected Search Console URL inspections can also create indexing recommendations. A manual index-verification item is a separate request for your own confirmation.
What lands here
Findings can concern access and bot blocks, indexing and canonical addresses, metadata, structured data, internal links, content extraction or deep-audit content/performance checks. Several affected pages can share one card rather than repeat the same issue.
When an automatic domain blocker fails, secondary findings are suppressed until that access problem is addressed. A page blocker can also prevent its deep analysis. See Site audit and Page audit for measured coverage and dates.
How these are prioritized
Cards show High, Medium or Low priority. Within a band, affected-page scope and the other ranking evidence help order the work. Separate impact and effort labels are not displayed.
Read the audit date alongside the queue. A finding absent from the next audit disappears from the Technical queue rather than becoming a Resolved achievement in its completed list. Marking an automatic finding Done does not prove the website passed a new check.
How to work through them
Open a card and expand View all when it lists affected pages. Linked URLs open their page audits. Read the problem, How to fix and any caution. Some instructions are ready immediately; findings requiring generated analysis offer a brief-generation control instead. Available code blocks have a copy icon. Review the values before applying them to the website.
Give the responsible maintainer the finding, all affected URLs and the acceptance steps. You can coordinate the work in Tasks. After deploying a fix, rerun the relevant standard or deep audit; a saved older deep result is not verification of the change.
For manual indexing checks, verify the stated search engine yourself before recording Done. Google/Bing manual confirmations are advisory for SSPS. Connected Search Console inspections refresh through the Google integration, rather than through a manual verdict. Queue completion, skip and reopen controls are covered in 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 SSPS to 100 by itself. Some checks have no fix to recommend, some are yours to verify by hand, and some findings are informational.
It isn’t limited to code and configuration. Technical recommendations can concern markup, headers and settings, but deep-audit findings can also call for changes to existing page content: clearer headings, a direct answer or supporting sources. Follow the specific finding rather than treating every card as a request to rewrite the whole page. The Content queue covers separate content opportunities; a Technical finding does not replace that work.