Skip to content

Template library

Give recurring SEO work a structure the whole team can follow.

A good template keeps the facts and decisions another person needs to pick up the work. These examples focus on scope, current state, intended result, ownership, live checks, and limitations—not empty scorecards.

Request access Explore the platform
ControlSystemHumanClient
Collect evidence✓——
Review meaning—✓✓
Approve action—✓✓
Verify output✓✓—
Permissions depend on the person's account role, ownership of the site, the connected provider, and the change being requested.

What to look for

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

01

Fields the team will need later

Capture targets, values, people, dates, dependencies, and results.

02

Summaries clients can read

Keep the decision-maker's context separate from the detail needed by the people doing the work.

03

A format you can adapt

Use the structure with Netrix or another careful process; the templates are not locked to the product.

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.

Template library / What to include

  1. 01
    Fields the team will need later

    Capture targets, values, people, dates, dependencies, and results.

  2. 02
    Summaries clients can read

    Keep the decision-maker's context separate from the detail needed by the people doing the work.

  3. 03
    A format you can adapt

    Use the structure with Netrix or another careful process; the templates are not locked to the product.

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

Resource library

Dig into the checks, methods, and tools behind Netrix.

Browse practical Netrix guides, SEO check explanations, templates, browser tools, integration references, and product details.

Netrix guides

Clear methods for the work that happens after you find an issue.

Read Netrix guides on technical audits, local search, remediation, change management, agency workflows, and client reporting.

Free tools

Check one piece of the work without running a full crawl.

Use focused tools for search snippets, titles, descriptions, canonicals, redirects, robots.txt, sitemaps, audit scope, and reports.

See how it fits your team

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

Request access