Skip to content

Sitemap guide

Your sitemap should list the pages the site actually wants indexed.

Compare every listed URL with its response, indexability, canonical target, and internal discovery. A perfectly valid XML file can still send mixed signals when it includes redirects, noindex pages, duplicates, or alternate URLs.

Request access Explore the platform
Change historyEXAMPLE / TRACE
Example evidence, review, and verification states
StateEvidenceOwner
FoundSitemap guideOriginal page and available evidence recordedAudit
ReviewedDecision recordedA person checked the target and proposed valueHuman
CheckedPublic page readLive result recorded separatelyNetrix
Product illustration only. It shows how statuses work, not a customer result.

What to look for

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

01

Check the sitemap files

Review response status, XML syntax, supported elements, file size, URL count, and sitemap index references.

02

Request every URL

Confirm that listed pages return 200, are intended for indexing, and agree with their canonical.

03

Compare the sitemap with the crawl

Find indexable pages missing from the sitemap and listed URLs with no internal path.

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 library
01

Check the sitemap files

Review response status, XML syntax, supported elements, file size, URL count, and sitemap index references.

02

Request every URL

Confirm that listed pages return 200, are intended for indexing, and agree with their canonical.

03

Compare the sitemap with the crawl

Find indexable pages missing from the sitemap and listed URLs with no internal path.

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 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

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

Request access