Skip to content
netweft

Guides tagged site-audit

4 guides

  1. Checking a site migration in the first week

    Before a migration, audit the old site and run a rank check so there is a baseline. After it, crawl the new site and fix Broken internal link, Redirect chain, Page returns an error, Conflicting canonical and noindex first, then compare a fresh rank check and Search Console with the baseline.

  2. Auditing by template, not by page

    A large site is a few templates rendered many times, so a finding on forty product pages is usually one fault in one template. netweft groups URLs into shapes by replacing ids, dates and long slugs, measures performance once per shape, up to ten pages, and lists duplicates with the pages sharing them.

  3. Reading a site audit by severity

    Work critical first: server errors, broken internal links, missing titles and pages the crawler was blocked from. Warnings hold most of the ranking work, from duplicate titles to thin content and orphan pages. Info findings are often deliberate. A 403 or 429 means the crawl was refused, not that a page is broken.

  4. What a 500-page crawl costs, and why Lighthouse is opt-in

    A crawled page costs one credit, so a 500-page crawl is 500 credits. A Lighthouse pass costs 50 credits a page, so netweft measures a sample, the start URL and one page per URL shape up to 10, adding at most 500 credits. It is opt-in per audit.

All guides