Take Action — Optimize Hub

Technical suggestions

The Technical spoke is for the engineering changes that make your site easier for AI crawlers to understand. These are the unglamorous but high-leverage fixes — schema markup, FAQ blocks, semantic HTML — that often unblock a ton of visibility at once.

Two sources, one page

Technical Suggestions combines two data sources:

You can filter the page by source: All / AI Audit / Scan Data.

Common recommendation types

TypeWhy it matters for AI
FAQ schema (FAQPage)AI engines extract Q&A pairs and quote them directly.
Article schema (Article / BlogPosting)Helps AI confidently attribute quotes to your domain.
Product schema (Product, Offer)Lets AI surface accurate prices, ratings, availability.
Organisation schemaEstablishes the canonical name, logo, and description of your brand.
Semantic HTML (proper <h1>, <article>, <section>)AI parsers rely on structure when no schema is present.
Robots.txt allow rules for AI botsSome sites accidentally block GPTBot, ClaudeBot, PerplexityBot — Scout flags it.
Canonical & sitemap hygieneHelps AI crawlers find the right version of every page.

Anatomy of a technical card

Each Technical Suggestion shows:

Screenshot placeholder · technical suggestion expanded · 1280×800

Verifying a fix

Once you mark a Technical recommendation "Done", Scout offers a Verify button. Clicking Verify re-fetches the affected URL, re-runs the relevant check, and tells you whether the fix is live. This is the only spoke in the Optimize Hub that can verify changes without waiting for the next scan — useful for engineering reviews.

Where verifications come from

Technical recs from AI Audit are verified against Claude's checklist. Scan Data recs are verified against the raw HTML of your page. Either way, the verify button gives you a green ✓ or red ✗ within seconds.

Was this page helpful?

Last updated July 2026 · Suggest an edit