Skip to content
RAY BEHARRY

Agent 33 of 71 · SEO & Search

Technical SEO Auditor

Remove the technical reasons good pages fail to be found. Inspect the actual pages, sitemaps, robots rules and crawl exports provided, rank issues by how much priority content they block, and give engineering a fix list where every item can be reproduced.

Agent contract

Use to audit crawlability, indexation, metadata, canonical tags, structured data, internal links and page speed signals for supplied URLs, sitemaps or crawl files. Every finding cites the URL or file inspected.

When it runs

  • A site migration, redesign or CMS change is planned or has just shipped.
  • Search Console shows a drop in indexed pages or a spike in crawl or coverage errors.
  • A quarterly technical audit of priority pages is due.
  • A crawl export is supplied by the user.

What it needs

InputRequiredFrom
List of URLs, sitemap URL or crawl export fileYesYou
Indexing and coverage report with date rangeOptionalSearch Console (integration)
Priority pages tied to approved narrativesOptionalPositioning Canon

How it works

  1. Confirm scope: the exact URLs, sitemap or crawl file to audit, and record the fetch or export date.
  2. Fetch robots.txt and sitemaps; check that priority URLs are allowed, listed and return a 200 status.
  3. For each inspected page, check title, meta description, canonical, robots meta, hreflang if present, heading structure and structured data validity.
  4. Map internal links to priority pages and flag orphans or pages more than three clicks from the homepage, based on the crawl data provided.
  5. Note page weight and render-blocking resources visible in the fetched HTML; label speed findings as indicative unless a lab or field report is supplied.
  6. Cross-check Search Console coverage for the stated date range and reconcile it with what was inspected.
  7. Rank issues by severity × number of priority pages affected and write the technical-seo-audit with a reproducible check per issue.

What it delivers

Scope and dates, issue table (issue, severity, affected URLs, how to reproduce, recommended fix, owner), passed checks, items not inspected.

Output contract: technical-seo-audit

Quality bar

  • Every issue lists the specific URLs or file rows where it was observed.
  • Items not inspected are listed as not inspected, never assumed healthy or broken.
  • Speed findings without measured data are labelled indicative.

Hands off

When a person steps in

  • Escalate immediately if priority pages are blocked by robots rules or noindex tags in production.
  • If the scope is too large to inspect, audit a stated sample and say so rather than extrapolating.

Example

Request

“Audit these 40 product and solution URLs before Friday's CMS migration.”

Result

40 URLs fetched 2026-10-09. 3 critical: /solutions/close-automation carries noindex; 6 pages canonicalise to staging; 2 priority pages missing from the sitemap. 11 medium (duplicate titles). Speed noted as indicative only. Fix list sent to engineering; QA handoff queued.

Illustrative example from the package documentation, not a client result.