Don’t lose your rankings in the relaunch
Silentfrog crawls your old site and your new one, matches every url and hands you a finished 301 redirect map — in 15 minutes instead of hours. No signup, no upload — results stay in your browser.
For agencies, freelancers and in-house teams shipping a relaunch — on Webflow or anywhere else.
free for the first 50 pages · no account · pay once per relaunch, never monthly
site settings → publishing → 301 redirects, or the data api
8 pages · 2 exact · 3 fuzzy · 1 need review · 0 unmatched · 4 verified
| ✓ | Match | ||||
|---|---|---|---|---|---|
| /produkte/seitenschneiderSeitenschneider 160 mm | review | 72% | 200 | ||
| /blog/relaunch-checklisteDie Relaunch-Checkliste | fuzzy | 88% | 200 | ||
| /blog/ladezeitLadezeit verbessern | fuzzy | 91% | 200 | ||
| /blog/301-vs-302301 oder 302? | fuzzy | 92% | 200 | ||
| /kampagne/sommer-2023Sommeraktion 2023 — 20 % auf alle Zangen | manual | 100% | 200 | ||
| /ueber-unsÜber uns | manual | 100% | 200 | ||
| /produkte/kombizangeKombizange 180 mm | exact | 100% | 200 | ||
| /kontaktKontakt | exact | 100% | 200 |
the tool in use: two urls entered, both sites crawled, the matched table filling up worst-confidence first, an unmatched row given a target from the path picker, a needs-review row confirmed, and the webflow csv exported.
Every url you forget becomes a 404. Every 404 is a ranking you paid for.
Old blog posts, discontinued products, campaign pages nothing links to any more. They still hold backlinks, and a crawler that only follows links will never see them. Finding them by hand is what eats the day — and missing one is what you notice three weeks after launch, in Search Console.
hours
for every relaunch, again
- export the old urls from a crawler or the cms
- crawl the new site and export that too
- match them in a spreadsheet, one row at a time
- find the pages nothing links to any more
- rebuild the file in the format the importer wants
15 min
at most — and most of that is you reviewing
- type two urls
- both sites are crawled, sitemaps included
- the table opens already matched, worst rows on top
- fix the handful the machine should not decide alone
- download the csv your importer reads as it is
Four steps, fifteen minutes
Point it at both sites
Two urls is all it needs. Robots.txt and the sitemaps are read for both sites, and you can paste your own url list — a crawler export, Search Console or server logs — for the pages nothing links to any more.
the crawl form with the old site url, the new site url, the page cap, the sitemap option and the field for your own url list.
Watch it match
Identical paths pair up instantly. The rest is scored on slug, title and h1 similarity, then sorted into exact, fuzzy, needs-review and unmatched — worst rows on top, so you start where a decision is actually needed.
crawling old site…
+ 1 seed urls from 1 sitemap
the progress panel: pages crawled and queued for each site, and how many extra seed urls the sitemaps added.
Fix the handful that matter
Send a whole directory somewhere in one move — /blog to /magazin, sub-paths kept — and see live how many pages it hits and which targets don't exist yet. Tick the wildcard box and it exports as one row that also covers urls the crawl never saw.
redirect a whole directory
map every crawled page below a directory at once — optionally as a single webflow wildcard rule that also covers urls the crawl missed.
3 pages · 3 targets exist on the new site · + wildcard /blog/(.*) → /magazin/%1
- /blog/relaunch-checkliste → /magazin/relaunch-checkliste
- /blog/301-vs-302 → /magazin/301-vs-302
- /blog/ladezeit → /magazin/ladezeit
the directory rule form mapping /blog to /magazin with sub-paths kept, exported as a wildcard, and a live preview of how many pages it affects.
Export and paste
Pick the importer and download the file it reads as it is: Webflow, Shopify, the WordPress plugins Redirection, Yoast and Rank Math, Squarespace url mappings, .htaccess, an nginx map, or plain path pairs for Wix and HubSpot. Pages that kept their url and rows still unmatched are left out of all of them, so nothing you did not decide gets imported. The generic csv next to it (source_url, target_url, status_code, confidence) is your audit trail.
site settings → publishing → 301 redirects, or the data api
the two export buttons — webflow csv and generic csv — next to the option that includes needs-review matches.
Built by a Webflow agency, on its own relaunches
Silentfrog is made by Goodaim, a Webflow agency in Munich run by Max Lorenz. It exists because we needed it: every client relaunch used to end with the same hours of matching old urls to new ones in a spreadsheet. We use it on our own projects, which is why it is built around the awkward parts — the pages nothing links to any more, the handful of matches a machine should not decide alone.
- Crawling runs in Frankfurt
- The hosted version fetches pages from a German region. The desktop app fetches from your own machine instead, so nothing passes through us at all.
- Results never leave your browser
- Matching, your edits and both csv files are produced in the tab you have open. We never store a crawl.
- No account, no upload
- Two urls start a run. There is no signup, no user table and no database behind any of this.
Who we are and how to reach us: imprint. What happens to your data, written from the code: data & privacy.
Not every url is worth the same
A relaunch drops a handful of pages that carry almost all the rankings, and a few hundred that carry none. Import a Search Console page export — or any csv with a url column and a number column — and every row gains clicks to sort by, so the review starts where it pays off. German and English exports, comma- or semicolon-separated, are both read.
traffic data
import a search console page export (or any csv with a url column and a number column) to see which redirects actually matter — the table gets a clicks column you can sort by.
10 urls imported · 8 matched onto crawled pages
2 urls get traffic but were not found by the crawl — they still need a redirect.
- /blog/werkstatt-tipps · 587 clicks
- /produkte/wasserpumpenzange · 233 clicks
the traffic import panel after a search console export was read: how many rows were joined onto matches, and the list of urls that have clicks but were never found by the crawl.
The pages nothing links to any more
Urls that have traffic but never turned up in the crawl are listed on their own and can be added as rows. That old workshop-tips post with 587 clicks and no inbound link was never crawled at all — a different problem from a matched page landing on the wrong target, and the one a relaunch loses quietly.
8 pages · 2 exact · 3 fuzzy · 1 need review · 1 unmatched · 2 verified
| ✓ | Match | |||||
|---|---|---|---|---|---|---|
| /kampagne/sommer-2023Sommeraktion 2023 — 20 % auf alle Zangen | unmatched | 940 | 31% | 200 | ||
| /produkte/seitenschneiderSeitenschneider 160 mm | review | 612 | 72% | 200 | ||
| /blog/relaunch-checklisteDie Relaunch-Checkliste | fuzzy | 421 | 88% | 200 | ||
| /blog/ladezeitLadezeit verbessern | fuzzy | 143 | 91% | 200 | ||
| /blog/301-vs-302301 oder 302? | fuzzy | 305 | 92% | 200 | ||
| /ueber-unsÜber uns | manual | 188 | 100% | 200 | ||
| /produkte/kombizangeKombizange 180 mm | exact | 274 | 100% | 200 | ||
| /kontaktKontakt | exact | 96 | 100% | 200 |
the results table with a clicks column joined from the traffic export, which can be sorted to put the pages with the most traffic on top.
The rest of what it does
search the whole table
Filter a few hundred rows by old path, target or page title. Combines with the bucket tabs.
re-map any row
Click a target to pick from every path on the new site, or remove the mapping. Manual picks count as confirmed.
verify in bulk
Tick a row that is right, or confirm everything the current filter and search leave visible in one click.
sort by path, confidence, status or clicks
Worst confidence first by default, so the rows that need a decision are already on top.
undo and reset
Every row edit, bulk verify and directory rule is one undo step. Reset goes back to the untouched crawl.
the file your importer reads
Webflow, Shopify, Redirection, Yoast, Rank Math, Squarespace, .htaccess, nginx or plain path pairs — pick one and the download is ready to import as it is.
wildcard rules
Export a directory as a single /blog/(.*) → /magazin/%1 row, in Webflow's own notation, that also covers urls the crawl never saw.
your session is kept
Results and edits are autosaved in the browser and restored on the next visit. Save the whole session as json to carry it to another machine or hand it over.
sitemaps, properly
Robots.txt and sitemap.xml for both sites, following sitemap indexes and .xml.gz.
bring your own urls
Paste a list or load a file — a crawler export, Search Console or server logs. Bare paths work too.
staging domains work
Point the new site at xyz.webflow.io and map the redirects before the relaunch goes live.
no account, no upload
The crawl runs from Frankfurt and the results stay in your browser. There is nothing to sign up for.
Start in the browser. Install it only if you have to.
One tool, three surfaces, the same matching underneath. Each one exists because of a limit in the one before it.
- START HERE
In your browser
Two urls and a browser tab. Nothing to install, nothing to sign up for — the first 50 pages of the old site are free, and you pay once for the relaunch only if it is bigger.
Start free →- No account, no upload, no installer.
- Only the fetching happens on our server, in Frankfurt. Matching, your edits and the csv stay in the browser.
- Your session is autosaved and picked up again on the next visit.
- One key per relaunch — it reopens the same project on another machine, so a review can move between people.
- WHEN THE BROWSER CAN’T REACH IT
On your own machine
The same tool with the server half moved inside it. It crawls completely locally — no page of either site is ever fetched by us — so it reaches whatever your machine reaches. 249 € once, for every relaunch you will ever do.
- Completely local: the crawler runs in the app, and no url you enter leaves your machine.
- Reaches staging behind an ip allowlist, an intranet, or localhost — sites the hosted version cannot see at all.
- One purchase covers every relaunch, on up to three devices at a time — for an agency or a freelancer, one key for every client.
- Talks to a server exactly once, when you paste your key. After that it never phones home — no expiry, nothing to re-check.
- Free to download and free for 50 pages, same as the browser.
- WHEN THE NEW SITE IS WEBFLOW
Inside WebflowSOON
A Webflow app for the Designer, where the new site is not crawled at all: its pages and cms collections come straight from the Webflow api, so the target list is exact and instant. Only the old site is crawled — which is the only thing the price counts anyway.
- The new site’s urls are read from the api, not guessed from a crawl.
- Redirects go into site settings directly where the workspace allows it, otherwise the same webflow csv plus a guided import.
- The same matching engine, the same directory and wildcard rules as the other two.
Pay per relaunch, not per month
A site gets rebuilt every few years. A subscription would fit nobody, so there isn’t one.
Free
free
up to 50 pages
Start free- the whole tool, only the page count is capped
- no account and nothing to upload
- enough to map a small site end to end
Medium
46 €
up to 150 pages
Start freeor buy a key now →- the size most relaunches turn out to be
- the key arrives by email and reopens the project anywhere
- one relaunch, paid once, no subscription
Unlimited
150 €
no page limit
Start freeor buy a key now →- for a site nobody can count beforehand
- the same price whatever the crawl turns up
- still one project, still no monthly bill
Lifetime
249 €
no page limit, every project
For agencies and freelancers: one key, every client.
See the app- every relaunch you will ever do, not just this one
- runs on your machine — staging, intranet and localhost included
- up to three devices at a time
- Only the old site counts.
- It decides how long the redirect list gets — crawling the new site comes along inside the same allowance.
- One purchase, one project.
- The key binds to your project the moment you redeem it, and covers that relaunch only. Lifetime is the exception: it covers every project.
- The key arrives by email.
- It reopens the same work on another machine, so a review can move between people.
- Not sure how big your site is?
- Start free — when the limit stops the crawl, Silentfrog names the plan that fits.
- Polar handles the payment.
- Polar.sh is the merchant of record: it takes the payment, emails you the key and sends the receipt or invoice.
Questions
- What counts as a page?
- Every url the crawler fetches on your old site — including ones that turn out to be redirects or 404s. The limit applies per site, so your new site gets an allowance of the same size. You never pay twice for one relaunch.
- Does it work outside Webflow?
- Yes. The redirects file downloads in the spelling of the importer you pick: Webflow, Shopify, the WordPress plugins Redirection, Yoast SEO Premium and Rank Math PRO, Squarespace url mappings, Apache .htaccess, an nginx map file, or plain path pairs for Wix, HubSpot and anything else. Nothing about the crawl or the matching is Webflow-specific; the picker only changes the header and how a directory rule is written.
- Does it work with Webflow staging domains?
- Yes. your-site.webflow.io works as the new site; it is an ordinary crawl of server-rendered html.
- What about query strings and trailing slashes?
- They are normalised away before anything is compared. /page?a=1 and /page count as one page, and trailing slashes, index.html and differences in upper- and lowercase are treated as the same url — on the old site and the new one — so the redirect map does not fill up with duplicates of the same page.
- How long does a crawl take?
- A few minutes for a few hundred pages. The matching itself is instant; the wait is the crawler fetching pages politely, five at a time. Reviewing the result — the handful of rows a machine should not decide alone — takes the rest, and the whole thing is done in fifteen minutes where the spreadsheet version took hours.
- The new site isn't finished yet — can I start?
- Yes. Point the new side at the staging domain (your-site.webflow.io works) and map what exists; the session is autosaved in your browser and picked up on your next visit, so you can run it again once the remaining pages are live. Only the old site's pages count toward your plan, so re-running the new side costs nothing.
- The old site is already offline — can I still map it?
- Yes, as long as you have a list of its urls. Choose "old site already offline", then upload the old sitemap.xml (several files at once are fine), a crawler or Search Console export, or paste the urls — Silentfrog builds the old page list from that instead of crawling. Those pages are matched on the url alone, since there are no titles left to read.
- What happens to my data?
- The crawl runs in your browser. Our server only fetches pages on your behalf, because a browser may not read another site's html. Results, edits and csv files stay in your browser — we never store them. The desktop app does not even do that: it fetches from your own machine, so nothing passes through us at all.
- My site is client-side rendered — will it find anything?
- The crawler reads server-rendered html only. On a purely client-rendered site the links stay invisible, so seed it from sitemap.xml or paste a url list.
- What if my site is bigger than I thought?
- Start free. When the limit stops the crawl, Silentfrog estimates the real size and names the plan that fits — you decide with the number in front of you.
- Our staging site is behind a login or an ip allowlist.
- Then the hosted version cannot see it — it crawls from Frankfurt. The desktop app can: it runs completely locally and reaches whatever your machine reaches, including an intranet or localhost.
- We build in Webflow. Is there something better than a csv?
- A Webflow app is on the way. In the Designer the new site is not crawled at all — its pages and cms collections come from the Webflow api, so the target list is exact. Until then the webflow csv imports under Site settings → Publishing → 301 redirects.
- Do I get an invoice?
- Yes — Polar sends it by email. Polar.sh is the merchant of record for Silentfrog: it takes the payment, emails you the license key and issues the receipt or invoice for that purchase.
- Can I get a refund?
- Write to hi@silentfrog.dev. There is no automated refund flow and no published policy — a person reads that address and answers within one working day. The free tier is there so you can see the whole matched table before you pay anything.