What's in a Technical SEO Audit? Full Deliverables List

A technical SEO audit is not a tool report. It is a written punch list your engineering team can execute on Monday morning, with priorities, effort estimates, and the raw data behind every recommendation. Use this list to compare what I ship in the technical SEO audit service against any other quote on your desk. The pricing companion is how much does technical SEO audit cost.

I am Ignacio (IGNAX), Spain-born and Paraguay-based, a solo full-stack developer and SEO/AEO specialist. The audits below are the ones I deliver on real client engagements.

What does the audit include?

Seven artifacts ship, in this order:

1. Crawl report (XLSX): every URL with status, title, meta, H1, canonical, hreflang, schema types, content length.
2. Lighthouse pass per page template (mobile + desktop), with CWV targets and gap analysis.
3. Schema validation pass: Rich Results Test + Schema.org validator results, screenshots saved.
4. Indexing snapshot: GSC and Bing data, URL coverage, recent crawl errors.
5. Prioritized fix list: P0/P1/P2 with effort estimates and a recommended sequence.
6. AEO readiness scorecard: per-page: Quick Answer present, FAQ schema, llms.txt entry, Person sameAs.
7. AI-engine citation baseline: 10–20 target prompts probed across ChatGPT, Perplexity, Gemini, Claude.

Plus a 60-minute handover call and a written runbook for the weekly maintenance loop.

What does the crawl report look like?

The crawl report is the foundation of every other artifact. I run Screaming Frog (free tier for sites under 500 URLs, paid for larger) and export the full URL inventory.

Columns in the XLSX:

• URL: full path.
• Status code: 200, 301, 404, etc.
• Title: what is in the <title> tag.
• Title length: characters; flag <30 or >60.
• Meta description: flag >155 chars or missing.
• H1: count and content; flag duplicates or missing.
• Canonical: what URL the page declares as canonical.
• Hreflang siblings: list of declared alternates.
• Schema types detected: JSON-LD types present (Article, FAQPage, Service, etc.).
• Internal inbound links: how many other pages link to this URL.
• Word count: content length.
• LCP / INP / CLS from Lighthouse.

Each column tells a story. URLs with 404 status codes are broken internal links. URLs with missing H1 are template bugs. URLs with no internal inbound links are orphaned and indexable but not discoverable.

The XLSX is the single source of truth for the audit. Every fix-list item references a row.

What does the Lighthouse pass cover?

One Lighthouse run per page template, not per URL. Running 1,000 pages through Lighthouse is wasteful when the templates are identical, so I cover one representative URL per template:

• Homepage.
• Service page template.
• Article page template.
• Case study template.
• About page.
• Sitemap and llms.txt endpoints.

Each template gets a mobile and a desktop run. Metrics:

• LCP, INP, CLS with the score breakdown.
• Performance score with diagnostics.
• Accessibility score with violations.
• Best Practices score with issues.
• SEO score with warnings.

The deliverable is the JSON report saved per page plus a written summary table with target metrics. For the CWV detail and remediation patterns see Core Web Vitals on Cloudflare Pages.

The canonical reference for the metrics is the web.dev Core Web Vitals documentation.

What does schema validation cover?

Every JSON-LD block on every key page, validated through:

• Google Rich Results Test (search.google.com/test/rich-results): confirms eligibility for rich result features.
• Schema.org Validator (validator.schema.org): strict schema compliance.

Screenshots saved per validation pass. Errors and warnings logged with the URL and the schema type. Common issues I catch:

• Article schema missing author or publisher.
• FAQPage with malformed mainEntity structure.
• Service schema with missing provider or areaServed.
• Person schema with empty or invalid sameAs URLs.
• BreadcrumbList with broken item positions.
• Duplicate JSON-LD blocks (often two plugins inserting their own).

The output is a written list per page: schema types present, validation status, errors with line numbers, recommended fixes. The Schema.org documentation is the canonical type list.

What does the indexing snapshot include?

Pulled from Google Search Console and Bing Webmaster Tools:

• Indexed URL count: total and per category (services, articles, case studies).
• Excluded URL list: URLs Google has crawled but chosen not to index, with the exclusion reason.
• Crawl error report: server errors, redirect loops, missing pages.
• Sitemap coverage: URLs in the sitemap vs URLs indexed.
• Recent indexing events: what got added or dropped in the last 30 days.

If GSC is not connected I set it up as part of the audit (Domain property via DNS verification). Same for Bing Webmaster.

For the broader context see Cloudflare Pages SEO setup.

What does the prioritized fix list look like?

This is the deliverable clients spend the most time on. Format:

Priority	Issue	URLs affected	Effort	Sequence
P0	Article schema missing author on /articles/*	12	1 hour	Week 1
P0	LCP > 4s on mobile for /services/*	7	4 hours	Week 1
P1	12 broken internal links	12	2 hours	Week 2
P1	FAQ schema malformed on /about	1	30 min	Week 2
P2	Add llms.txt entry for case studies	n/a	1 hour	Week 3
P2	Image alt text missing on /services/*	28	4 hours	Week 3

P0 issues block ranking or indexing, fix immediately. P1 issues meaningfully affect performance, fix within a sprint. P2 issues are polish, fix when convenient.

The list is concrete enough that a developer who has never touched the site can execute it. No "improve performance"; instead "convert /portrait.jpg to /portrait.webp, set width=480 height=640, add fetchpriority=high".

What is the AEO readiness scorecard?

A per-page table showing whether each AEO element is present:

URL	Quick Answer	FAQ schema	Person sameAs	llms.txt entry	H2-as-questions	Score
/	✓	✗	✓	✓	✗	3/5
/services/saas-mvp	✓	✓	✓	✓	✓	5/5
/articles/what-is-aeo	✓	✓	✓	✓	✓	5/5
/about	✗	✗	✓	✓	✓	3/5

The scorecard makes the AEO surface visible at a glance. Pages scoring under 4/5 get prioritized in the fix list. For the underlying methodology see what is AEO and how to get cited by ChatGPT.

What is the AI citation baseline?

Ten to twenty target prompts probed across ChatGPT (browsing on), Perplexity, Gemini, and Claude. For each probe:

• The prompt (the way a buyer would actually type it).
• Whether the client's domain was cited.
• If not cited, who was cited instead.
• The full LLM response saved as a screenshot.

The baseline is the Day-1 starting point. The weekly loop re-runs the probes monthly and tracks delta. The methodology is the same one I run on ignax.dev itself, see the growth engine case study.

What does the handover include?

A 60-minute video call covering:

• Walkthrough of every artifact.
• Discussion of P0 fixes and what implementing them looks like.
• Decision: implement yourself, hand to me, or hand to your team.
• Q&A on anything in the report.

Plus a written runbook committed to your repo or shared via Notion. The runbook is the weekly maintenance loop, what to do every Monday to keep the gains compounding.

What is NOT in the audit?

To be explicit about scope, these items are out:

• No deep backlink campaign work. Light backlink analysis is included; outreach is a separate engagement.
• No content strategy. I report on technical issues with existing content, not on what to write next.
• No competitor reverse-engineering. Audit is your site, not theirs.
• No paid media or PPC analysis. Organic only.
• No design or UX recommendations beyond what affects CWV or accessibility.

Adding any of these is possible as a separate engagement. Keeping them out of the core audit keeps the deliverable focused.

What external references should I read?

• Google Search Central, SEO starter guide.
• Schema.org documentation: canonical schema type reference.
• web.dev, Core Web Vitals: metrics and remediation patterns.
• Bing Webmaster Tools: secondary index, important for AI citation.

The audit deliverable is concrete artifacts your team can execute. No dashboards. No retainers required. For pricing see how much does technical SEO audit cost and the service page.

Ready for an audit? Email hello@ignax.dev with your URL. I crawl the site before our call so the first 30 minutes are productive.