Webtrace is an SEO analytics tool. It audits a site, compares an old site with its redesign or new domain, and digs into a site's history through the Wayback Machine.

Each run produces a self-contained report that opens with a plain-English verdict, plus an Excel workbook with every finding. The reports below come from real runs on public sites.

Example reports

Three modes, five public sites. Open any report: the summary at the top says what matters, and every finding links to its evidence.

SEO auditAction Required

crawler-test.com

A site built on purpose to test SEO crawlers: redirect chains, canonical traps, noindex pages, duplicate titles. A good stress test for every check.

31 of 97 pages have at least one priority problem.
  • All 85 pages carry no structured data (JSON-LD).
  • 96 of 97 pages have fewer than 300 words.

Crawled October 23, 2026

SEO auditNeeds Attention

books.toscrape.com

A practice online bookstore made for scraping exercises. A realistic look at what a catalog site gets right and wrong.

Mostly sound: 3 of 100 pages have a priority problem and 97 need smaller fixes.
  • All 100 pages carry no structured data (JSON-LD).
  • 50 of 100 pages have fewer than 300 words.

Crawled October 23, 2026

Side-by-sideAt Risk

React docs: reactjs.org to react.dev

React moved its documentation to a new domain and a new design in 2023 and kept the old site online. Webtrace matches old pages to new ones and checks where every old address leads today.

14 of 97 old pages carried over; 14 improved, 0 got worse, and 83 have no counterpart.
  • 14 of 97 old pages have a counterpart on the new site; no counterpart was found for 83 among the 100 pages crawled from the new site.
  • 99 of 100 pages on the new site have no meta description, leaving search engines to choose snippet text on their own.

Crawled October 23, 2026

Site historyAt Risk

kde.org: 2018-19 vs today

The KDE community's site as the Wayback Machine kept it up to mid-2019, compared with the live site today, with every redesign and platform change since dated on a timeline.

44 of 100 pages from the July 2018 archive have a counterpart today; 56 do not.
  • 44 of the 100 pages archived in July 2018 have a counterpart on today's site; no counterpart was found for 56 among the 100 pages crawled from today's site.
  • 54 of 100 checked old URLs no longer reach their content (homepage, soft 404, 404, 410 or loop).

Crawled November 1, 2026

Site historyAt Risk

python.org: late 2013 vs today

python.org was redesigned in 2014. This report compares the last archived version of the old design with today's site and shows what carried over.

26 of 100 pages from the November 2013 archive have a counterpart today; 74 do not.
  • 26 of the 100 pages archived in November 2013 have a counterpart on today's site; no counterpart was found for 74 among the 101 pages crawled from today's site.
  • 95 pages on today's site share the same meta description.

Crawled October 23, 2026

What it checks

75+ checks per page

Titles, descriptions, headings, canonicals, robots rules, structured data, images, links, social tags and speed, ranked by priority.

Executive summary

A verdict in one sentence, the findings that matter with real counts, and the first three fixes.

Indexability

For every page: can a search engine list it, and if not, which signal is stopping it. Redirect chains drawn hop by hop.

What changed

Old page next to new page, word by word, for everything search engines read. Changes that can cost traffic are flagged.

Old URL check

Visits each old address on the live site today: does it land on the right page, the homepage, a fake "not found" page, or nowhere?

Site history

Every redesign, platform switch, analytics change and domain move, dated on a timeline from archived captures.

Site-level checks

The site-wide mistakes that sink relaunches: blocked crawlers, broken host forwarding, catch-all error pages, dropped analytics.

Strategy and reach

A 0 to 100 score across location, topic depth, authority, technical foundation and competitive signals.

How it's built

About these examples: each site was crawled once, gently (100 pages at most, a two-second pause between requests, robots.txt honored), and the reports are snapshots from the date shown. Findings are automated observations, not judgments of the sites or the people behind them. Webtrace is not affiliated with any of them.