[VOID Agency](https://www.void-agency.com/)/[Working tool](https://www.void-agency.com/tools)/**Free Technical SEO Audit Checklist: 35 Checks + Template**

Working tool · published

# Free Technical SEO Audit Checklist: 35 Checks + Template

Flagship utility

## VOID Technical SEO Release Gate v1.0

Run 35 technical SEO release checks in a no-signup browser workspace. Save statuses and notes locally, then export CSV, JSON, Markdown, or print and save a PDF.

No signup is required. Statuses and evidence notes stay in this tab unless you choose Save locally, which uses this browser's local storage. Exports are generated in the browser; workspace values are not submitted to VOID. Analytics records the tool route and workspace action, not entered statuses or notes.

Version v1.0 · Reviewed September 10, 2026 · By [Sulayman Bowles](https://sulayman-bowles.dev/about)

Use the toolDownload templatesProblemWorkflowEvidenceExampleChecklistMethodBoundariesSources

Reusable artifact

## Download the 35-check technical SEO audit template.

Download the complete 35-check starter sheet for an offline review, or use the separate URL-level issue ledger to record evidence, severity, ownership, and validation.

Open either CSV in Excel or import it into Google Sheets. These are blank starter files, not exports of your saved audit. Use the workspace export controls for completed statuses and notes, or “Print / save PDF” for a PDF of your review.

Blank CSV downloads and the 35 checklist items are available without JavaScript. Changing statuses, saving locally, and exporting completed work require JavaScript. This is a manual review template, not an automated website crawl.

[Download all 35 checks (CSV) →](https://www.void-agency.com/downloads/technical-seo-audit-checklist.csv)[Download the technical SEO evidence template (CSV) →](https://www.void-agency.com/downloads/technical-seo-evidence-template.csv)

Methodology and sources

## A release decision, not a score.

The 35 checks cover access, indexation, canonicals, raw and rendered HTML, template ownership, internal links, structured data, performance evidence, and measurement. Each decision needs route-level evidence, an owner, and a recheck. Source context comes from Google Search Essentials plus official sitemap and crawlable-link guidance linked below.

What this gate cannot prove

## Keep outcomes separate.

A completed gate cannot prove that Google will crawl, index, rank, surface, or earn clicks for a page. It does not replace Search Console evidence, field performance data, accessibility or security review, or qualified lead measurement.

Version history

## Change log

**v1.0 · 2026-09-10:** Added a complete 35-check starter CSV and corrected printing to include every check and full evidence notes regardless of screen filters. The underlying release checks are unchanged.

**v1.0 · 2026-08-28:** Named the 35-check release gate, clarified local workspace handling, exposed print/save-PDF output, and documented the evidence boundary.

Local audit workspace

## VOID Technical SEO Release Gate v1.0: 35 checks

**0%Reviewed:** 0/35

**Pass:** 0

**Needs attention:** 0

**Unknown:** 0

**N/A:** 0

Status filterCategory filter

C01 · Access

Resolve HTTP, HTTPS, apex, and www variants and record every redirect hop.

Status

C02 · Access

Verify priority URLs return the intended 200, 3xx, 4xx, or 5xx status.

Status

C03 · Access

If the site uses robots.txt, verify its response and syntax. Test any sitemap URLs it declares.

Status

C04 · Access

Compare robots.txt, robots meta, and X-Robots-Tag. If exclusion relies on noindex, verify that Google can crawl the URL and read the directive.

Status

C05 · Access

Test representative pages with and without JavaScript and record material differences.

Status

C06 · Indexing

Keep only canonical, indexable, 200-status URLs in XML sitemaps.

Status

C07 · Indexing

Verify every indexable page has one self-referencing canonical on the preferred host.

Status

C08 · Indexing

Remove accidental noindex directives from pages intended to rank.

Status

C09 · Indexing

Identify soft 404s, thin shells, empty states, and misleading success responses.

Status

C10 · Indexing

Compare indexed and excluded route groups in Search Console, not only totals.

Status

C11 · Canonicals

Map duplicates caused by parameters, casing, trailing slashes, and alternate paths.

Status

C12 · Canonicals

Test redirects for single-hop behavior and preservation of the exact destination path.

Status

C13 · Canonicals

Align navigation, structured data, hreflang, sitemap, and canonical URLs.

Status

C14 · Rendering

Confirm raw HTML contains a unique title, H1, canonical, opening copy, and internal links.

Status

C15 · Rendering

Check that hydration does not remove, duplicate, or replace crawl-critical metadata.

Status

C16 · Rendering

Capture browser errors, blocked resources, and failed API dependencies on key templates.

Status

C17 · Templates

Assign one search intent and one canonical owner to every priority route.

Status

C18 · Templates

Check titles and descriptions for uniqueness, accuracy, and useful snippet propositions.

Status

C19 · Templates

Verify headings reflect the visible task instead of repeating navigation labels.

Status

C20 · Templates

Confirm pagination, filters, and empty states do not create indexable clutter.

Status

C21 · Links

Crawl internal href links and resolve broken URLs, redirect chains, and orphaned pages.

Status

C22 · Links

Give priority pages descriptive links from hubs, related guides, and commercial pages.

Status

C23 · Links

Confirm links remain crawlable anchors rather than click handlers without href values.

Status

C24 · Schema

Validate JSON-LD syntax and match every entity, claim, author, date, and URL to visible truth.

Status

C25 · Schema

Use one stable Organization identifier and connect only verified sameAs profiles.

Status

C26 · Schema

Check breadcrumbs, article dates, service details, and application fields against the page.

Status

C27 · Performance

Review field Core Web Vitals by template before treating one lab run as sitewide truth.

Status

C28 · Performance

Inspect image sizing, font loading, long tasks, and layout shifts on mobile.

Status

C29 · Performance

Record response time and HTML size for representative server responses.

Status

C30 · Measurement

Verify the analytics loader, consent behavior, and one page_view contract per route.

Status

C31 · Measurement

Test form, phone, booking, and diagnostic actions through to accepted outcomes.

Status

C32 · Measurement

Preserve route, source, and campaign context without sending personal data.

Status

C33 · Evidence

Record affected URLs, raw evidence, severity, owner, recommended fix, and confidence.

Status

C34 · Evidence

Separate verified defects from hypotheses, opportunities, and external platform delays.

Status

C35 · Validation

Re-crawl changed templates and save before-and-after evidence before closing an issue.

Status

Complete audit ledger: all 35 checks. Screen filters do not limit this printout.

### C01 · Access

Resolve HTTP, HTTPS, apex, and www variants and record every redirect hop.

**Status:** Not started

### C02 · Access

Verify priority URLs return the intended 200, 3xx, 4xx, or 5xx status.

**Status:** Not started

### C03 · Access

If the site uses robots.txt, verify its response and syntax. Test any sitemap URLs it declares.

**Status:** Not started

### C04 · Access

Compare robots.txt, robots meta, and X-Robots-Tag. If exclusion relies on noindex, verify that Google can crawl the URL and read the directive.

**Status:** Not started

### C05 · Access

Test representative pages with and without JavaScript and record material differences.

**Status:** Not started

### C06 · Indexing

Keep only canonical, indexable, 200-status URLs in XML sitemaps.

**Status:** Not started

### C07 · Indexing

Verify every indexable page has one self-referencing canonical on the preferred host.

**Status:** Not started

### C08 · Indexing

Remove accidental noindex directives from pages intended to rank.

**Status:** Not started

### C09 · Indexing

Identify soft 404s, thin shells, empty states, and misleading success responses.

**Status:** Not started

### C10 · Indexing

Compare indexed and excluded route groups in Search Console, not only totals.

**Status:** Not started

### C11 · Canonicals

Map duplicates caused by parameters, casing, trailing slashes, and alternate paths.

**Status:** Not started

### C12 · Canonicals

Test redirects for single-hop behavior and preservation of the exact destination path.

**Status:** Not started

### C13 · Canonicals

Align navigation, structured data, hreflang, sitemap, and canonical URLs.

**Status:** Not started

### C14 · Rendering

Confirm raw HTML contains a unique title, H1, canonical, opening copy, and internal links.

**Status:** Not started

### C15 · Rendering

Check that hydration does not remove, duplicate, or replace crawl-critical metadata.

**Status:** Not started

### C16 · Rendering

Capture browser errors, blocked resources, and failed API dependencies on key templates.

**Status:** Not started

### C17 · Templates

Assign one search intent and one canonical owner to every priority route.

**Status:** Not started

### C18 · Templates

Check titles and descriptions for uniqueness, accuracy, and useful snippet propositions.

**Status:** Not started

### C19 · Templates

Verify headings reflect the visible task instead of repeating navigation labels.

**Status:** Not started

### C20 · Templates

Confirm pagination, filters, and empty states do not create indexable clutter.

**Status:** Not started

### C21 · Links

Crawl internal href links and resolve broken URLs, redirect chains, and orphaned pages.

**Status:** Not started

### C22 · Links

Give priority pages descriptive links from hubs, related guides, and commercial pages.

**Status:** Not started

### C23 · Links

Confirm links remain crawlable anchors rather than click handlers without href values.

**Status:** Not started

### C24 · Schema

Validate JSON-LD syntax and match every entity, claim, author, date, and URL to visible truth.

**Status:** Not started

### C25 · Schema

Use one stable Organization identifier and connect only verified sameAs profiles.

**Status:** Not started

### C26 · Schema

Check breadcrumbs, article dates, service details, and application fields against the page.

**Status:** Not started

### C27 · Performance

Review field Core Web Vitals by template before treating one lab run as sitewide truth.

**Status:** Not started

### C28 · Performance

Inspect image sizing, font loading, long tasks, and layout shifts on mobile.

**Status:** Not started

### C29 · Performance

Record response time and HTML size for representative server responses.

**Status:** Not started

### C30 · Measurement

Verify the analytics loader, consent behavior, and one page_view contract per route.

**Status:** Not started

### C31 · Measurement

Test form, phone, booking, and diagnostic actions through to accepted outcomes.

**Status:** Not started

### C32 · Measurement

Preserve route, source, and campaign context without sending personal data.

**Status:** Not started

### C33 · Evidence

Record affected URLs, raw evidence, severity, owner, recommended fix, and confidence.

**Status:** Not started

### C34 · Evidence

Separate verified defects from hypotheses, opportunities, and external platform delays.

**Status:** Not started

### C35 · Validation

Re-crawl changed templates and save before-and-after evidence before closing an issue.

**Status:** Not started

Workspace controls become available when JavaScript runs.

No signup is required. Statuses and notes stay in memory unless you choose “Save locally.” Saved work uses this browser’s local storage; exports are created locally. Workspace values are not submitted to VOID. Do not enter credentials, customer data, or other private information.

01

## The task and the failure mode

**Built for:** Site owners, developers, and SEO practitioners who need a repeatable technical review with evidence another person can verify.

Technical audits often become long exports without a clear evidence standard, affected-route count, remediation owner, or proof that a fix worked.

02

## Workflow

1. **01**Define the canonical host, production environment, priority route groups, and measurement window.
2. **02**Test access, HTTP behavior, robots, sitemaps, canonicals, and representative raw responses.
3. **03**Compare raw HTML, rendered DOM, template ownership, internal discovery, schema, and mobile behavior.
4. **04**Record each verified defect in the downloadable evidence ledger with severity, impact, owner, and recommendation.
5. **05**Re-crawl the affected routes and retain before-and-after evidence before closing the item.

03

## Evidence to retain

- Timestamped headers and raw HTML for representative URLs in every affected template.
- Affected-route list, discovery method, severity, search impact, recommendation, owner, and validation status.
- Search Console, analytics, server log, browser, or conversion evidence where the claim requires it.

Sample

## Example finding: duplicate host chain

**Observed:** HTTP apex redirects through HTTPS apex before reaching HTTPS www.

**Evidence:** Timestamped response headers for the same path on all four host variants.

**Decision:** Reduce non-preferred variants to one permanent hop while keeping the exact path.

**Validation:** Repeat the four-host test and save the final status and Location headers.

05

## Boundaries and caveats

Crawler findings are hypotheses until verified on representative URLs and the delivered production response.

A clean audit, sitemap submission, or completed ticket does not guarantee crawling, indexing, rankings, clicks, or leads.

06

## Primary sources

1. [Google Search Essentials and SEO Starter Guide](https://developers.google.com/search/docs/fundamentals/seo-starter-guide)developers.google.com
2. [Google Search Central: Build and submit a sitemap](https://developers.google.com/search/docs/crawling-indexing/sitemaps/build-sitemap)developers.google.com
3. [Google Search Central: Make links crawlable](https://developers.google.com/search/docs/crawling-indexing/links-crawlable)developers.google.com
4. [Google Search Central: Block search indexing with noindex](https://developers.google.com/search/docs/crawling-indexing/block-indexing)developers.google.com

Continue the task

## Related working pages

[Test redirects, retained answers and enquiry receipts before a redesign launch →](https://www.void-agency.com/insights/website-redesign-seo-measurement-migration#worked-launch-sample)[What a paid audit should hand you: follow a sample finding →](https://www.void-agency.com/insights/technical-seo-audit-deliverables-agency#sample-handoff)[Audit XML Sitemap and Canonical Consistency →](https://www.void-agency.com/insights/xml-sitemap-canonical-consistency-audit)[Compare GA4 event delivery for offline leads →](https://www.void-agency.com/insights/ga4-data-manager-api-offline-service-leads)[Technical SEO audit: Plain-Language Definition →](https://www.void-agency.com/definitions/technical-seo-audit)[Crawlability: Plain-Language Definition →](https://www.void-agency.com/definitions/crawlability)[Indexability: Plain-Language Definition →](https://www.void-agency.com/definitions/indexability)[Plumbing Emergency Service-Page SEO Playbook →](https://www.void-agency.com/playbooks/plumbing/emergency-service-page-seo)[Dental Treatment-Page SEO Playbook →](https://www.void-agency.com/playbooks/dental/treatment-page-seo)[Law Firm Practice-Area Page SEO Playbook →](https://www.void-agency.com/playbooks/law-firm/practice-area-page-seo)

Commercial next step

## Need this implemented against your real site and lead path?

Start with a bounded diagnostic. VOID separates verified defects, measurement gaps, and implementation scope before making outcome claims.

[Review the relevant service →](https://www.void-agency.com/services/technical-seo-ai-search-visibility)

---
Source: https://www.void-agency.com/tools/technical-seo-audit-checklist · VOID Agency
