Test the checker with a known defect
A source-page audit is easier to trust when its checker has seen a broken input. The Suede AI evidence-page demonstration first checks the original HTML, then repeats the same checks on a controlled copy. That copy removes the document title and canonical tag and adds a noindex directive.
The dated report shows eight checks passing on the original page. On the controlled copy, Document title, Canonical address and Indexable directive are flagged. The other five checks keep their passing decisions. This gives you a concrete regression exercise for those three changes.
Inspect the declared address
The recorded Canonical address check compares the HTML declaration with the intended evidence-page URL. In your own checker, pass the expected page address explicitly so a copied template pointing at another route becomes a failed check.
Google describes canonicalization as a choice influenced by several signals. This source check verifies the address the page declares. Confirm the deployed response and inspect Search Console when your question concerns what Google selected. Keep those records alongside the source result, with their own dates.
Exercise the robots metadata
The checker collects robots meta values and flags any containing noindex. The controlled example therefore gives the assertion a clear negative input. The parsing is intentionally small and follows the HTML conventions used by this site.
Google also supports an X-Robots-Tag HTTP header. This source checker reads HTML, so include a response-header capture in a live indexing investigation. Google’s documentation explains that a crawler needs access to a noindex instruction to process it. A robots.txt rule and a noindex instruction answer different operational questions.
Inspect the named decisions
Use Node 22 or newer to read the public recorded report. The command prints the eight original decisions and the same decisions for the controlled three-defect copy. Compare the named failures before adapting the acceptance checklist to your own page.
report_file="$(mktemp)"
curl --fail --show-error --location --max-time 30 https://suedeai.ai/seo/assets/demonstrations/results.json --output "$report_file" &&
REPORT_FILE="$report_file" node --input-type=module <<'JS'
import { readFileSync } from 'node:fs';
const result = JSON.parse(readFileSync(process.env.REPORT_FILE, 'utf8'));
console.table(result.audit.checks);
console.table(result.audit.controlled_fixture);
JSHand the finding to the person making the repair
A useful ticket includes the expected page URL, the captured HTML hash, the failing check and the source location. After a repair, run your checker again and retain both results. Rehearse the three-defect case on a temporary copy of your own page.
On-Page SEO and AI Search Essentials with Semrush and AI Search Operating System are the relevant certificates of achievement in Jason Colapietro’s published inventory. The implementation connects that training to an inspectable source audit and repeatable repair check.
For your first page, choose a route a buyer uses to evaluate the business. Preserve its title, description, declared canonical, indexing directives, heading and next step in a dated report. Then verify the published response before moving to search-performance analysis.
- Expected URL and capture date.
- Original bytes or their retained artifact.
- Named failing assertion and source location.
- Repair result from the same checker.
Issued training connected to this exercise
- On-Page SEO and AI Search Essentials with Semrush · Semrush Academy · Certificate of achievement · issued .
- AI Search Operating System · Semrush Academy · Certificate of achievement · issued .
Inspect the full training inventory · Open the qualifications sheet
Source and recorded result
- Dated demonstration results
- Google canonical URL guidance
- Google noindex guidance
- Current public evidence page
The demonstration report is dated 2026-10-21. The commands and checklists above explain how to inspect that saved record or capture a new observation from a public page.
Put the workflow to work
Scope a technical search audit. Bring the workflow, source page or answer your team needs to check so the first deliverable has clear acceptance criteria.
Keep source and live evidence together · All three working demonstrations