Site architecture guide
Internal links help people move through the site—and show which pages matter.
Look beyond the total number of links. Find broken or redirected destinations, isolated pages, excessive depth, noisy template links, and important sections that have no useful path from the rest of the site.
| State | Evidence | Owner |
|---|---|---|
| Found | Site architecture guideOriginal page and available evidence recorded | Audit |
| Reviewed | Decision recordedA person checked the target and proposed value | Human |
| Checked | Public page readLive result recorded separately | Netrix |
What to look for
Get the answer without losing sight of where it came from.
Check every destination
Separate broken, redirected, canonicalized, and non-indexable targets instead of grouping them as link errors.
Look at the shape of the site
Compare crawl depth, incoming-link distribution, navigation, breadcrumbs, and relationships between content.
Fix the link at its source
Update the page that contains the link instead of relying on a redirect chain forever.
Put the guide to work
Understand the issue, check the page, and choose the next step.
The strongest audits leave room for context. Confirm what happened, rule out the common false positives, decide who owns the fix, and check the page again afterward.
Open the full check libraryCheck every destination
Separate broken, redirected, canonicalized, and non-indexable targets instead of grouping them as link errors.
Look at the shape of the site
Compare crawl depth, incoming-link distribution, navigation, breadcrumbs, and relationships between content.
Fix the link at its source
Update the page that contains the link instead of relying on a redirect chain forever.
From finding to follow-up
See where the work stands—and what still needs to happen.
- 01Found
Netrix records the page and the issue it found.
- 02Reviewed
Someone checks the finding in context.
- 03Approved
The right person chooses what should change.
- 04Applied
A supported connection accepts the change.
- 05Checked
Netrix reads the public page again.
- 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.
- 01Nothing publishes itself
AI drafts and supported SEO changes wait for an authorized person to act.
- 02A 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.
- 03Limits 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
Technical SEO guide
A good technical audit tells the team what to do next.
A practical technical SEO audit process for setting scope, checking crawl quality, prioritizing issues, planning fixes, and reporting results.
Workflow guide
Plan the audit around the handoffs where work usually gets lost.
Connect crawl findings, review, assignment, implementation, QA, and client reporting in one practical SEO audit process.
Prioritization guide
Severity matters, but it does not decide what your team should fix first.
Prioritize technical SEO findings by impact, reach, confidence, page value, implementation risk, and the effort required to check the fix.
See how it fits your team