How to bulk upload URL redirects to HubSpot from a csv

In Silentfrog, pick plain path pairs (wix, hubspot, other) under for in the export and the download is already this file: a from,to csv the mapping step reads straight away, with directory rules written out row by row. Pages that kept their url, rows still unmatched and unverified needs-review rows are left out of it, so nothing gets imported that nobody looked at (the two downloads). The rest of this page says what is in the file and how the import behaves, and it works just as well for a two-column csv of path pairs from anywhere else.

The generic csv next to it is the audit trail: absolute urls, confidence, match type, the unmatched rows with an empty target. Keep it with the project, do not import it.

• Download HubSpot’s sample csv from the import dialog once and copy its headers, so the mapping step recognises the columns without help. The two you need are the original url and the redirect destination; redirect type and a note are optional.
• Paths, not full urls, in the original column. A full url pins the rule to one domain, a path applies wherever the site is served.
• 140 characters at most per url in a bulk upload. Sort the left column by length and look at the longest few; a very old campaign url with parameters can exceed it and has to be added by hand.
• No wildcard rows. The plain path pairs file has none; a directory rule is written out as its rows. If a csv from elsewhere has a row with (.*) on the left, it fails the whole upload. Folders are better done as pattern redirects anyway, next section.
• Split at 500 rows. Number the files so a failed one is easy to find again.

A directory rule in Silentfrog is a flexible pattern redirect in HubSpot: add a redirect in the tool, choose the flexible pattern type, and enter /blog/:slug as the original url and /insights/:slug as the destination. The variable name is yours to choose; it has to be the same on both sides.

Order matters in the tool: a pattern rule for /blog/:slug also matches /blog/tag/name and would send it to /insights/tag/name. Add the more specific rule for /blog/tag/:slug first, or give tag and author paths their own rule pointing at the blog index, and check the priority order in the list afterwards.

What a pattern cannot know is whether the target exists. Silentfrog’s directory preview lists the slugs the new site does not have; those get a row of their own in the csv, pointing at the closest page, and the csv rows take precedence over the pattern when they are listed above it.

The URL Redirects tab lists what is there, including rules from earlier moves. The import dialog offers to overwrite existing redirects with the same original url; tick it when the new map should win. Then read the old list for chains: a rule whose destination is an original url in your new file should be changed to the final target.

• A failed upload imports nothing and puts an error spreadsheet in your notifications. Fix the rows it names and upload the file again in full.
• Crawl the old url list against the live site: one 301, then 200. Open one url under each pattern redirect by hand, including one that should hit a more specific rule.
• A redirect for a url that is still a published page does nothing; unpublish it first.
• Watch Search Console for the following weeks: pages with redirect up, not found flat.

• Settings, Content, Domains & URLs, URL Redirects, Import; map your two columns to original url and destination.
• Paths, 140 characters at most, 500 rows per upload; an upload succeeds or fails as a whole.
• Folders are flexible pattern redirects with :slug on both sides, made in the tool, with specific rules above them.
• Tick overwrite existing redirects when the new map should win; flatten chains in the old list.
• After the upload, crawl the old urls against the live site and test one url per pattern.