1. LandOffer
  2. Blog
  3. All articles
  4. Carrd Review for a Job-Search Portfolio: One-Page Proof, Custom Domains, and Paid Limits

Job search

Carrd Review for a Job-Search Portfolio: One-Page Proof, Custom Domains, and Paid Limits

Official Carrd plan and sharing documentation with two completed fictional portfolio-content and feature-purchase decisions.

9 min readLandOffer team

Carrd can work as a compact job-search portfolio when one readable page can explain your contribution and link to the supporting work. Choose a plan around the specific features you need: a custom domain, a form, analytics or password protection. Paying for a higher tier does not make a project more credible or prove a recruiter will review it.

Start with the evidence you need to present. Compare recent roles on LandOffer.ai, select a relevant project, and write its contribution summary before choosing a template. A useful one-page portfolio should communicate something meaningful even when the reader does not open every external link.

An editorial illustration shows one concise portfolio page linked to a specific project notebook and supporting evidence

Review Carrd as a one-page presentation tool

We checked current official Carrd documentation on October 20, 2026, including full native browser reads of plan details, custom-domain requirements and password protection. We did not create an account, build or publish a Carrd site, buy a domain, change DNS, upload private files, enable analytics or submit a contact form. The worked cases below are fictional design and purchasing decisions.

Carrd's homepage describes responsive one-page sites and a free Basic experience with up to three sites. That is a provider description, not our test of every template or device. A job-search portfolio still needs deliberate content selection and a review of the actual page before sharing.

Carrd's sections documentation says named regions can be linked and switched to simulate multiple pages. Plan for navigation within a one-page site, not an assumption that you have a full multipage publishing system. If your work requires many independent case studies, complex documentation or an application backend, evaluate that scope separately.

For a focused portfolio, a short introduction, one or two relevant projects, clear contribution details and a contact route may be sufficient. Explain each selected thumbnail with the project purpose and your contribution.

Choose a paid tier by the feature you actually need

The official plan guide lists these entry tiers. Prices are annual figures checked for this review; confirm the selected offer before a purchase.

Documented entry tier Annual price and site allowance Relevant boundary
Pro Lite $9; three sites Removes Carrd branding and adds other presentation features, but does not include custom domains or forms
Pro Standard $19; ten sites Adds custom domains, contact/signup forms, embeds and analytics
Pro Plus $49; twenty-five sites Adds advanced features, including custom forms, password protection and downloadable site files

Do not equate an unbranded Carrd-provided URL with your own registered domain. Nor should a basic contact form and a custom workflow integration be treated as the same feature. Select the tier around the required function rather than assuming every feature is available on every Pro plan.

The extra site allowance is not automatically valuable to an individual applicant. If you intend to maintain one portfolio, begin with its actual requirements. Additional capacity can be useful for separate projects, but an allowance for ten sites does not mean you need ten versions of your application story.

Worked one-page proof: make the contribution inspectable

Consider fictional backend applicant Dina, who wants to present a personal cache-expiry prototype. The data and project conditions here are invented; we did not run the prototype or create its Carrd page. Dina's proposed portfolio should show the behavior she designed without claiming production scale or measured speed improvements.

Proposed page area Completed content decision Why it earns space
Opening Identify Dina's backend focus and the prototype's purpose Establish the context without a broad unsupported expertise claim
Main project Explain fixed expiry from insertion, with hits not extending the expiry Give the reader one precise behavior to inspect
Evidence Provide a synthetic request timeline and identify the intended source function Connect the behavior to an implementation discussion
Ownership State that Dina wrote the cache logic and explanatory example Separate her contribution from libraries and surrounding tooling
Limitations/contact State untested concurrency and production use; provide an appropriate contact route Keep the claim bounded and the next step understandable

Dina's completed project description reads: “I designed a personal cache-expiry prototype to explore how fixed lifetimes differ from refreshing expiry on each hit. In this example, an entry inserted at time zero has a thirty-second lifetime. A read at twenty seconds returns the cached value without extending that lifetime. A read at thirty-five seconds must treat the entry as expired. The intended source-reading route starts at the expiry check and insertion timestamp. I wrote the cache behavior and explanation; this example does not establish thread safety, distributed consistency or production performance.”

The accompanying synthetic timeline contains three events: insert value A at zero seconds; read at twenty seconds and expect A; read at thirty-five seconds and expect an expired-entry path. These are the fictional design’s expected states; we did not execute the prototype. Dina does not add a “99% faster” label, because no benchmark is supplied.

The one-page decision is therefore complete: lead with this bounded example, omit unrelated tutorial screenshots, and leave deeper code discussion behind a clearly labeled source link. The contribution and expiry rule remain understandable without a repository visit.

Keep external destinations as deliberate as the page

A Carrd page can be readable while its repository, PDF or demonstration is inaccessible. Check the purpose and audience of every destination before an actual share. “View code” should point to the intended code sample rather than an account home page or private workspace that the recipient cannot inspect.

State whether the intended source or demo destination requires access the reader does not have. If source is unavailable, explain the implementation in a permitted summary instead of presenting a broken link as evidence. If a live demonstration is optional, give a short path through the behavior and a readable explanation of what it should show.

Review media for the same claim boundaries. A screenshot should identify the relevant state or version; a visual from an older prototype should not silently illustrate the current implementation. Avoid including employer dashboards, credentials or proprietary records merely to make a personal page look substantial.

We checked Carrd documentation, not Dina's fictional links. No external artifact was uploaded or tested as part of the example. A completed layout decision is not a completed access or runtime check.

Connecting a custom domain does not register it

Carrd's custom-domain guide requires Pro Standard or higher and says the domain must already be registered. It describes pointing DNS records at the Carrd site through the domain provider. Purchasing Carrd access and obtaining the domain are separate tasks with separate costs and renewal responsibilities.

If you already own an appropriate domain, determine which hostname you intend to use and which DNS records Carrd actually supplies for that site. Do not copy an example IP address from an article. A domain purchase also does not establish that the correct site is serving at the intended address.

For a job seeker, the domain is mainly an address and presentation choice. It does not prove ownership of the linked project, improve the underlying contribution summary or guarantee search visibility. A readable permitted page on a Carrd-provided address may be enough while you decide whether the extra setup is worthwhile.

No registration, domain lookup, DNS change, publishing action or SSL verification was performed for this review. Before a real share, verify the resulting destination rather than treating a saved configuration as evidence of public availability.

An editorial illustration separates a registered domain nameplate, the portfolio page it points toward and a distinct paid-feature gate

Worked feature decision: a domain is needed, a gate is not

Now assume Dina wants one public portfolio on a domain she already owns. She wants a basic contact form but does not need payments, an automated workflow, downloadable site sources or a password gate. These requirements are hypothetical and do not describe an account we inspected.

Her completed choice is Pro Standard at the documented $19 annual entry price. Lite fails the custom-domain and form requirements. Plus includes additional features, but none of the extra functions is required for this stated scope. Owning a domain does not make Lite sufficient, because Carrd's connection feature still has its own tier requirement.

Dina's budget note separates the $19 Carrd subscription from the existing domain's renewal charge, which is unknown in this exercise. She does not describe the total as $19 or invent a registrar price. If she did not already own the domain, registration would be an additional unresolved cost and action.

Then change one requirement: Dina wants the portfolio itself password-protected. The documented password feature requires Plus. She must reassess the tier and the reader's access route; she cannot assume Standard includes it because Standard supports custom domains.

Her final decision is to keep the public version limited to material she is permitted to share and retain the Standard scope. She excludes a proprietary employer screenshot rather than buying a password gate to justify uploading it. The gate question changes access requirements, but it does not grant publication permission for confidential content.

Password protection changes the reader's route

The password-protection guide describes a site-level username and password combination on Pro Plus or higher. That is not described as individual recruiter accounts, a confidentiality agreement or proof that linked external files have the same protection.

Decide whether the added access step fits the material and recipient. If you choose a gated route, the reader needs the appropriate instructions through an authorized channel. Do not call a page unrestricted or publicly reviewable when it requires a credential the recipient does not have.

A password also does not turn restricted employer material into an authorized portfolio sample. Review the content's sharing rights separately. This article neither sets a password nor assesses the security of any particular site or linked asset.

Forms and analytics are optional additions

Carrd's contact-form documentation requires Standard or higher. It describes routing messages to the account email or selected recipients. Check that destination before using a form as your contact route; a visible form is not evidence that a message was delivered to the intended inbox.

You may prefer a simpler contact method when a form adds no useful function. Do not ask a recruiter to provide unnecessary personal information or upload confidential material merely to reach you. Keep the request proportionate to a professional inquiry.

The analytics guide says tracking is not enabled by default and requires Standard or higher. It supports native analytics and third-party providers, whose data policies need separate review. Traffic counts do not automatically identify a recruiter, establish that a project was read or measure an application's success.

We enabled no tracking and submitted no form. Any later delivery or analytics test should be labeled as the specific check performed, rather than a guarantee of ongoing behavior.

Check the trial and renewal model before relying on paid features

Carrd's trial documentation offers seven days without payment details and describes a subset of Pro features, including a 150-element limit. Do not call it unrestricted access to every paid feature or assume a trial-built site remains within the plan you eventually select.

Its renewal guide describes optional auto-renewal through an account balance, with a saved payment method able to fund that balance. We did not inspect an account's renewal setting. Record the actual selected plan and renewal state if you later subscribe.

Carrd is a reasonable candidate for a concise portfolio when its feature gates and one-page structure fit your evidence. Compare recent roles on LandOffer.ai, write the contribution clearly and choose the functions your intended sharing route requires.

Sources and Further Reading