03 / 04
Every page crawled, every issue named.
Trafficmend crawls your site the way a search engine finds it: from your sitemaps, robots.txt and the links between your pages. It checks each page, follows each redirect, measures speed from your real visitors and turns the result into one health score.
In numbers
- 500 pages a scan
Pages found through links come first, sitemap-only URLs after.
- 19 checks
Nine technical and ten on-page, each with a fixed severity.
- 28 days of speed
Core Web Vitals from your real visitors, on mobile and desktop.
- 5 redirect hops
Followed one by one, so chains show up hop by hop.
[01]The crawl
How it finds your pages.
Nothing to install for this part. The crawler starts from the URL you add and works outwards, politely.
- 01
robots.txt and sitemaps
It reads robots.txt and the sitemaps it lists, or /sitemap.xml and then /sitemap_index.xml. Sitemap indexes, nested ones and .xml.gz files are all read.
- 02
Links, breadth first
From your start page it follows every same-site link, level by level. URLs that appear only in a sitemap are fetched after the linked ones.
- 03
Your rules, respected
It identifies itself as TrafficmendBot and obeys the robots.txt group for that name, or the one for every bot, with wildcards and longest-match rules.
- 04
Duplicates folded
Tracking parameters such as utm_*, gclid and fbclid are stripped, so one page tagged ten ways is crawled once.
Crawl limits
- Pages per scan
- 500
- Pages fetched at once
- 6
- Timeout per page
- 15 s
- Redirect hops followed
- 5
- Sitemap files read
- Up to 50
- Sitemap URLs
- Up to 5,000
Per page
- Status code and response time
- Every page
- Indexability (meta robots, X-Robots-Tag)
- Every page
- Title, description, headings, word count
- Every page
- Canonical, Open Graph, JSON-LD
- Every page
- Internal links in and out
- Every page
[02]Checks
Nineteen checks, each with a rule.
No vague warnings. Each check has a written rule and a fixed severity, and the report also says how many checks found nothing to fix.
Technical9 checks
Server errors
Critical
A 5xx response, a network error or no response within 15 seconds.
robots.txt
Critical / low
Critical if it blocks the whole site, low if there is none.
Broken internal links
High
Links on your pages to URLs that return a 4xx, a 5xx or nothing at all.
Noindex on pages that matter
High
A noindex page you list in your sitemap or that still earns search clicks.
No sitemap
Medium
Nothing listed in robots.txt, /sitemap.xml or /sitemap_index.xml.
Orphan pages
Medium
In your sitemap, but no crawled page links to them.
Redirect chains
Low / medium
Internal links that redirect; medium at two hops or more.
Missing canonical
Low
Indexable pages without a canonical tag.
Structured data
Low
More than half your indexable pages carry no JSON-LD.
On-pageOn indexable pages · 10 checks
Missing title
High
No <title>, or an empty one.
Duplicate titles
Medium
The same title on more than one page.
Title length
Low
Over 65 characters or under 20.
Missing meta description
Medium
No meta description on an indexable page.
Duplicate meta descriptions
Low
The same description on more than one page.
Missing H1
Medium
No H1 heading on the page.
More than one H1
Low
Two or more H1 headings.
Thin content
Medium
Under 300 words in the main content. The start page and utility pages are left out.
Image alt text
Low
Images without an alt attribute. alt="" counts as set.
Social preview tags
Low
No og:title or og:image.
[03]Speed
Speed as your visitors feel it.
Core Web Vitals come from real page views: the tracker measures each one, on mobile and desktop. When it has too few visits, Google's Chrome UX Report fills in with what Chrome users saw. Every crawled page also gets speed checks.
Measured
- Largest Contentful Paint (LCP)
- 75th percentile
- Interaction to Next Paint (INP)
- 75th percentile
- Cumulative Layout Shift (CLS)
- 75th percentile
- First Contentful Paint, Time to First Byte
- 75th percentile
- Image sizes, render-blocking files, server response
- Every crawled page
Where it comes from
- Your visitors, through the tracker
- Last 28 days
- Google's Chrome UX Report, when your visits are few
- Last 28 days
Flagged when
- LCP over 2.5 s, INP over 200 ms or CLS over 0.1
- Medium
- LCP over 4 s, INP over 500 ms or CLS over 0.25
- High
[04]Health score
One number, four parts.
The score is there to show direction between scans. Every point it loses traces back to an issue you can open.
Technical30%
Starts at 100 and loses points for each technical issue, more for severe ones and for issues on more of your pages.
Content25%
The same rule, for the on-page checks: titles, descriptions, headings, thin pages, alt text and previews.
Speed20%
The share of visits with good Core Web Vitals (LCP, INP and CLS) across your site, on mobile first.
Search25%
Starts at 85, moves with your Search Console click trend and gives up a capped amount for the search fixes found.
Parts without data are left out and the rest re-weighted, so a site without Google connected is scored on what it has. Beside the score, the pages table lists every URL with its status, sortable, filterable and split into all pages, pages with issues, pages not crawled and errors.
[05]How it fits
Four views, one list.
Each view feeds the next. Search Console clicks decide which crawl and speed issues rank first, and every finding ends up in the same ranked list of improvements.
[01]
Analytics
Live visitors, sources and goals, next to your Google Analytics traffic.
[02]
Search
Search Console queries and pages, and the rankings at positions 8 to 20.
[03]You are here
Audit
A crawl of up to 500 pages, with technical checks and Core Web Vitals.
[04]
Improvements
Every fix ranked by the clicks it is worth, with a brief to hand off.