HubSpot import guide
HubSpot website URL import format
Website fields are easy to overlook because they look like plain text. Clean URL values before import so HubSpot receives usable company or contact website data.
What the error means
A Website URL format problem means a value in the mapped Website column is not shaped like a usable URL, or it has extra spaces that should be trimmed before export. HubSpot may store bad website text as-is or reject it depending on the property and import flow.
Use consistent values such as https://example.com or example.com, and avoid notes, placeholders, pasted sentences, or broken URL fragments in the Website column.
Why Website values get messy
Website data often comes from forms, enrichment tools, or hand-edited spreadsheets. That creates extra spaces, copied labels, missing domains, and text that is not a website at all.
- Leading or trailing spaces can hide from view in spreadsheet cells.
- Values such as
not a urlare clearly not website addresses. - Placeholders such as
n/ashould not be treated as real websites. - Some malformed-looking values can still pass a basic URL parser, so final human review matters.
How to fix it manually
- Trim spaces around every Website value.
- Remove placeholders, notes, and values that are not websites.
- Use a consistent domain or full URL format across the column.
- Spot-check suspicious schemes, copied punctuation, and values from enrichment tools.
- Review the mapped Website column in HubSpot before committing the import.
How ReadyCSV flags Website URL issues locally
ReadyCSV suggests a safe trim cleanup as url_cleanup when the mapped Website value has leading or trailing whitespace. That finding is info-level and has canAutoApply enabled for the trimmed value.
ReadyCSV flags clearly invalid Website values as malformed_website warnings. Those findings are review signals with needs_review, not automatic URL rewrites.
Important limitation: ReadyCSV does not perform exhaustive URL validation. The current URL check catches values like not a url, but a typo'd scheme such as htp://example.com can still pass the local parser and should be reviewed manually.
For the wider file checklist, use how to format a CSV for HubSpot import and the CSV column format guide.
Related HubSpot import guides
How to format a CSV for HubSpot import
Use an end-to-end HubSpot contact CSV checklist before uploading: identity, headers, emails, dates, phones, owners, encoding, and enums.
HubSpot import date format errors
Fix HubSpot date columns that use Excel serials, written-out dates, dots, or unsupported formats.
HubSpot invalid email import error
Understand INVALID_EMAIL, INVALID_DOMAIN, duplicate emails, and additional email address imports.
HubSpot lifecycle stage import error
Check lifecycle stage and lead status values before HubSpot rejects an import row.
HubSpot import missing required fields
Fix contact rows missing First name, Last name, and Email before a HubSpot import.
HubSpot contact owner import error
Review Contact owner values that need an active HubSpot user email or internal owner value.
HubSpot CSV column format errors
Fix duplicate headers, blank headers, and rows with extra cells before importing a CSV.
HubSpot phone number format import
Review HubSpot phone number format import risks and use E.164-style values before uploading contacts.
HubSpot import special characters broken / UTF-8 encoding CSV
Fix CSV encoding workflows when HubSpot import special characters look broken, such as José instead of José.
HubSpot import duplicate contacts / duplicate email
Review duplicate emails, duplicate rows, and blank-email dedupe risk before importing HubSpot contacts.
HubSpot import unmapped / unrecognized columns
Review unmapped CSV headers, manual mapping risks, and local mapping suggestions before HubSpot import.
Check your CSV before importing
ReadyCSV preflights HubSpot contact CSVs locally in your browser. Your CSV contents stay on your device: no upload, no account, no AI calls, and no license server call for local checks.
It is still your responsibility to review every finding, cleaned export, Issue Report, and HubSpot import setting before importing. ReadyCSV cannot guarantee that HubSpot will accept every row.
Open ReadyCSV local preflight