Refresh the crawl. See what changed.

Run the crawl again and Silkra keeps both versions side by side. Every added, removed, and changed page lands in one log, with anything that broke at the top.

From one crawl to a record of every change.

Each refresh becomes a new version beside the last. Silkra compares the two field by field, so you read what moved instead of hunting for it.

  1. Refresh the crawl

    Run it again from the version menu. The new pass reuses your settings and lands as the next version.

  2. Compare the versions

    Silkra lines up each URL against the previous version, from status and canonical to titles and body copy.

  3. Read the change log

    Every added, removed, and changed page is listed once, with status and indexing regressions sorted first.

See what a refresh did, fast.

The pages that broke come first, so you know in minutes whether a refresh needs your attention. Every edit is there to read when you want the detail.

Get started

See exactly what was rewritten.

Read the old and new copy side by side, with every added and removed line marked. You spot a thinned-out page or a rewritten pitch before it costs you traffic.

Review a sitewide change in one pass.

Rolled out new titles or canonicals? See every page it touched, before beside after, and spot the odd one out without opening pages one by one.

Know what changed, and whether it mattered.

Keep watch on your own site and your competitors'. Spot pages that drift off topic, and get a plain-language read on whether a refresh matters before you dig in.

Read the change log guide

Keep tabs on competitors

See when a competitor launches a page, drops one, or rewrites their pitch. Refresh their workspace whenever you want to check in, and the changes are waiting in the log you already use.

Catch a rewrite before it costs you.

An edit can quietly turn a page into something else. If one lands in a different topic group, the log shows where it came from and where it ended up.

Skip the triage.

The agent reads the log alongside the rest of the crawl and tells you which changes could cost you traffic and which are just copy edits.

Diff tracking, but for websites

How refreshing a crawl works

A crawl is only a snapshot

Most crawlers give you one snapshot. When you come back, you crawl again and compare two spreadsheets by hand, guessing at what moved in between.

Code solved this long ago with diffs. Websites deserve the same. In Silkra, every refresh is a new version and the change log is the diff: what changed, and whether it affects how pages are fetched and indexed.

Faster refreshes, lighter on the site

A full re-crawl is slow and heavy on the server. So a refresh starts by asking whether each page has changed since last time, using the same ETag and Last-Modified headers browsers rely on for caching.

If the server says "not modified", Silkra keeps the saved copy and moves on. Only pages that report a change, or can't say, get scraped again, so refreshes finish sooner and put far less load on the site.

Create your first workspace.

Turn websites into SEO knowledge bases. Free to start.