Skip to content

Audit template

Start with what you will measure. End with what you checked after the fix.

Define the crawl, make sure it ran reliably, review related issues, sample representative pages, prioritize the work, assign the fixes, check production, and disclose anything the audit could not measure.

Request access Explore the platform
FIELD NOTE / TEMPLATEAudit template
NETRIX
Evidence
01
Decision
02
Action
03
Proof
04

How the work moves

Observed100% Reviewed78% Applied52% Verified48%
Example statuses only. These numbers are not benchmarks or customer results.

What to look for

Get the answer without losing sight of where it came from.

01

Before the crawl

Record domains, environments, URL sources, exclusions, rendering, authentication, rate limits, APIs, and the goal of the audit.

02

While reviewing the crawl

Check status, directives, canonicals, sitemaps, links, metadata, content, performance, structured data, security, and accessibility separately.

03

After the review

Record accepted work, owners, dates, implementation methods, QA results, unresolved dependencies, and reporting notes.

Made for real work

Start here, then shape it around the site in front of you.

The examples give you a useful structure. Replace them with the pages, people, findings, and decisions that belong to the project.

Audit template / What to include

  1. 01
    Before the crawl

    Record domains, environments, URL sources, exclusions, rendering, authentication, rate limits, APIs, and the goal of the audit.

  2. 02
    While reviewing the crawl

    Check status, directives, canonicals, sitemaps, links, metadata, content, performance, structured data, security, and accessibility separately.

  3. 03
    After the review

    Record accepted work, owners, dates, implementation methods, QA results, unresolved dependencies, and reporting notes.

From finding to follow-up

See where the work stands—and what still needs to happen.

  1. 01Found

    Netrix records the page and the issue it found.

  2. 02Reviewed

    Someone checks the finding in context.

  3. 03Approved

    The right person chooses what should change.

  4. 04Applied

    A supported connection accepts the change.

  5. 05Checked

    Netrix reads the public page again.

  6. 06Shared

    The report summarizes the audit and fixes currently marked applied.

A few things worth knowing

Netrix can prepare the work. Your team still makes the call.

  1. 01
    Nothing publishes itself

    AI drafts and supported SEO changes wait for an authorized person to act.

  2. 02
    A write is not proof

    Netrix records when a provider accepts a change, then checks the public page separately. If it cannot read the page, the result stays unknown.

  3. 03
    Limits belong in the open

    When a feature depends on another provider or stops short of a complete workflow, the page should say so.

Keep exploring

More on this part of the work

Browse all resources

Reporting template

Explain the audit clearly without turning the whole site into one score.

Structure a client-ready technical SEO report with scope, method, findings, priorities, page examples, remediation, and limitations.

Remediation template

Turn the recommendation into a change someone can own and test.

Plan technical SEO remediation with page details, priorities, exact targets, owners, approvals, dependencies, QA, and recovery.

QA template

Check the page visitors and crawlers receive after release.

Check response status, redirects, rendered metadata, directives, canonicals, links, schema, performance, and representative templates.

See how it fits your team

Bring the crawl, the review, and the follow-up together.

Request access