Skip to content

Crawl controls

Know what the crawler checked—and what it could not.

Set collection choices and crawl-rate limits for the account. Netrix records which capabilities were available, so a report can tell the difference between a healthy page and a check that never ran because its crawl mode or dependency was missing.

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

Choose what to collect

Turn resource and audit surfaces on or off based on the work the account needs to review.

02

Set a considerate crawl rate

Control threads and URLs per second instead of placing hidden pressure on a customer's server.

03

Keep gaps in the report

Missing dependencies and partial crawls remain visible and can stop Netrix from offering a change it cannot support.

How it works in Netrix

Give the team enough context to make the next call.

Find the source, see who owns the work, and understand what the current status actually means before moving it forward.

01 / In the product

Choose what to collect

Turn resource and audit surfaces on or off based on the work the account needs to review.

02 / In the product

Set a considerate crawl rate

Control threads and URLs per second instead of placing hidden pressure on a customer's server.

03 / In the product

Keep gaps in the report

Missing dependencies and partial crawls remain visible and can stop Netrix from offering a change it cannot support.

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

Technical SEO audits

Turn your next technical audit into a clear list of work.

Crawl a site, review technical SEO findings by page, and turn the issues that matter into work your team can follow through.

SEO remediation

Move from “we found it” to “we fixed it” without losing the thread.

Review technical SEO findings, prepare fixes, approve supported changes, and check what reached the live site.

Controlled deployment

Know exactly what will change before you click Deploy.

Send approved title and meta-description fixes through WordPress or Cloudflare, with ownership checks, recorded write attempts, and a current live-check state.

See how it fits your team

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

Request access