Carrd SEO audit

Carrd\'s Pro plans support custom head code injection — enabling JSON-LD structured data, custom canonical tags, and GSC verification that most hosted builders block. Run a free audit to check your Carrd site\'s meta tags, structured data, Core Web Vitals, and AI visibility configuration.

Audit your Carrd site free →

What DeepSEOAnalysis checks on Carrd websites

Meta title, description, and Open Graph tags on Carrd

The audit checks Carrd's built-in meta tag output: the `title` tag (from Site Settings → Meta → Title), the `meta name="description"` tag, and Open Graph tags (og:title, og:description, og:image) that Carrd generates for social sharing. Common issues on Carrd sites: the default meta title is the site name without keyword context; meta description is left blank (causing Google to auto-generate snippets); og:image is not set (resulting in no image when pages are shared on social platforms — Carrd uses a generic placeholder by default). The audit verifies title length (50–60 characters optimal), description length (120–155 characters), and that Open Graph tags are populated. For Carrd Pro plans with custom head injection, the audit also checks whether custom meta tags (additional OG tags, canonical, structured data) have been correctly added and whether they conflict with Carrd's own auto-generated tags (duplicate canonical is a common issue when the site setting and a custom injected canonical both appear in `head`).

Custom domain and canonical configuration on Carrd

Carrd serves sites on subdomain.carrd.co by default. With a Carrd Pro plan, a custom domain (yoursite.com) can be connected. The audit checks canonical tag configuration: for custom domain Carrd sites, the canonical tag should reference the custom domain URL (https://yoursite.com/), not the carrd.co subdomain URL. A misconfigured canonical (pointing to carrd.co instead of the custom domain) would signal to Google that the carrd.co subdomain is the authoritative version, undermining the SEO value of the custom domain. Carrd may or may not auto-generate canonical tags — the audit checks the initial HTML response for a canonical tag and whether it is correctly formatted (absolute URL, matches the page's custom domain). On Carrd one-page sites, the canonical typically points to the root URL (https://yoursite.com/) since there is only one page. The audit also checks that HTTP redirects to HTTPS are in place (Carrd handles this automatically for custom domains via SSL provisioning).

Custom head code injection and structured data on Carrd

The most powerful technical SEO feature on Carrd Pro Standard and above is custom head code injection. The audit checks whether the `head` section contains: structured data JSON-LD (schema types appropriate to the page content); Google Search Console verification meta tag; custom canonical tag; hreflang tags (for multilingual single-page sites); and any additional meta tags beyond Carrd's defaults. For structured data, the audit validates: the JSON-LD is syntactically valid; the schema type is appropriate for the page content; required properties are present (for Person, Organization, LocalBusiness, FAQPage — the specific required properties vary by type); the structured data is present in the initial server-rendered HTML (not in a JavaScript bundle that loads asynchronously). Since Carrd renders HTML server-side, custom head code injection produces server-rendered structured data — auditable and visible to crawlers without JavaScript execution. The audit identifies schema errors at the property level with corrected examples.

Robots.txt and AI visibility on Carrd

Carrd's robots.txt is controlled by Carrd Inc. and cannot be customised by individual site owners. The audit checks the current state of Carrd's robots.txt (at carrd.co/robots.txt for carrd.co-subdomain sites, or at the custom domain root for custom domain sites — where Carrd typically proxies through its own robots.txt). Key checks: whether standard search crawlers (Googlebot, Bingbot) are allowed; whether AI crawlers (GPTBot, ClaudeBot, PerplexityBot, Google-Extended) are permitted or blocked. llms.txt placement is not possible on Carrd — the domain root is managed by Carrd, and individual publishers cannot create files there. On custom domain Carrd sites, a robots.txt at the domain root is controlled by Carrd's servers, not the publisher's DNS-level configuration. FAQPage JSON-LD (for AI citation in structured Q&A format) is possible via custom head code injection on supported plans. The question-heading ratio and content chunkability signals are under the publisher's control through Carrd's content editor.

Core Web Vitals for Carrd sites

Carrd's performance profile is generally strong for simple one-page sites. The platform uses a lightweight JavaScript builder, CDN-hosted assets, and server-rendered HTML. The audit surfaces CrUX field data for Carrd URLs: LCP (Largest Contentful Paint) is typically fast on Carrd's CDN — the main risk is large background images used in hero sections (Carrd's visual builder encourages full-screen backgrounds that can be 1MB+ if not optimised by the publisher before upload); CLS (Cumulative Layout Shift) — Carrd's JavaScript initialisation can cause minor layout shifts as sections animate into view (Carrd uses CSS transitions by default); INP (Interaction to Next Paint) — minimal for basic Carrd sites with no interactive elements, but Carrd sites using embedded forms, chat widgets, or video players inherit those third parties' JavaScript performance costs. One advantage of one-page sites: the entire page is typically pre-rendered, reducing JavaScript hydration overhead that multi-page React apps face. The audit provides page-level CrUX data to identify any real-user performance issues.

Sitemap and crawlability on Carrd

Carrd does not automatically generate a sitemap.xml for site owners. For a one-page site, a sitemap is less critical than for multi-page sites (there is only one URL to index), but it can still help Google discover and index the site faster. Carrd Pro plans with custom code injection can add a link to a manually-hosted sitemap file, but Carrd does not natively generate or serve sitemap.xml. The audit checks: whether a sitemap.xml is accessible at the domain root (unlikely for standard Carrd sites); whether the page is included in Google's index (via GSC URL Inspection results if connected); whether the canonical URL is accessible and returns a 200 status. On custom domain Carrd sites, verifying in GSC and using the URL Inspection tool to request indexing is typically the fastest path to ensuring the page appears in search results. For carrd.co subdomain sites, GSC verification is possible but SEO value is limited (all carrd.co authority is shared across all Carrd sites, not attributed to individual publishers).

Carrd SEO best practice workflow

  1. Upgrade to Pro Standard or above for custom head injection — the ability to inject custom code into `head` unlocks canonical tags, JSON-LD, GSC verification, and additional meta tags that are not available on the free or Pro Lite plans.
  2. Connect a custom domain — a custom domain builds domain authority on your brand rather than on carrd.co. Required for meaningful organic search presence beyond brand-name queries.
  3. Set your meta title and description in Site Settings → Meta — the title should be 50–60 characters with your primary keyword; the description 120–155 characters, action-oriented and informative.
  4. Add JSON-LD structured data via custom head injection — choose the schema type appropriate for your page (Person for portfolios, Organization/LocalBusiness for businesses, Product for product pages, FAQPage if you have a Q&A section) and inject it in Site Settings → Custom Code → `head`.
  5. Optimise hero images before upload — convert images to WebP format and compress to under 200KB before uploading to Carrd. Carrd serves images via its CDN but doesn't perform compression itself; large hero images are the primary LCP drag on Carrd sites.
  6. Verify in Google Search Console and request indexing — use the HTML meta tag verification method in GSC. After publishing, use URL Inspection → Request Indexing to expedite Google discovering your page.

Carrd SEO FAQ

Can Carrd one-page sites rank in Google?
Yes — Carrd sites can rank in Google, though the single-page format creates inherent SEO limitations. A one-page website has only one URL, which means all SEO effort (backlinks, content, meta tags) is concentrated on a single page rather than distributed across a site architecture with topical depth. For very targeted, single-purpose use cases (a personal portfolio, a product landing page, an event page, a newsletter sign-up) a Carrd one-page site can rank effectively for brand-name queries and low-competition niche terms. For competitive informational queries where topical authority and content depth matter, a single-page architecture is a structural disadvantage against multi-page sites. Carrd\'s custom code head injection (on Pro Standard and above plans) allows adding meta tags, canonical tags, and even JSON-LD structured data — enabling technical SEO configurations that go beyond what many hosted platforms allow.
Does Carrd support custom meta tags and SEO settings?
Carrd provides built-in meta title and meta description fields for the page (accessible under Site Settings → Meta). These cover the basic HTML `title` and `meta name="description"` tags. On Carrd Pro Standard, Pro Plus, and Pro plans, the custom head code injection feature (`head` embed) allows adding any custom HTML to the `head` section, including: custom canonical tags, structured data JSON-LD, Google Search Console verification meta tags, Open Graph / Twitter Card meta tags, Google Analytics or other tracking scripts, and any other `head` code. Free and Pro Lite Carrd plans have limited or no custom code injection. The free plan does not allow custom domains — all pages are served from subdomain.carrd.co — which significantly limits SEO value since domain authority accumulates on carrd.co, not the publisher.
Can I add structured data (JSON-LD) to a Carrd site?
Yes — on Carrd plans that support custom head code injection (Pro Standard and above), you can add JSON-LD structured data via the `head` embed in Site Settings. Supported schema types depend on your site\'s content: Person schema for personal portfolio sites; Organization or LocalBusiness for business landing pages; Product schema for product pages; FAQPage schema for pages with FAQ sections; Event schema for event pages. To add: go to Site Settings → Custom Code → `head` and paste your JSON-LD `script type="application/ld+json"` block. Because Carrd generates server-rendered HTML, the structured data added via head code injection is present in the initial HTML response — which means it is crawlable by Googlebot and AI crawlers without JavaScript execution. This is a technical advantage over some JS-heavy CMS platforms where schema is client-rendered.
How do I verify a Carrd site in Google Search Console?
Google Search Console verification for a Carrd site requires the HTML tag method (meta tag verification), since Carrd does not support uploading HTML verification files or adding DNS TXT records (unless you control the domain\'s DNS). Process: in GSC, choose "HTML tag" verification method → copy the verification meta tag (e.g., `meta name="google-site-verification" content="xxxxx"`) → paste it into your Carrd Site Settings → Custom Code → `head` field → publish the Carrd site → click "Verify" in GSC. This requires a Carrd plan that supports custom head code injection. For custom domain Carrd sites where you control DNS, DNS TXT record verification is also available and may be easier (no Carrd plan restrictions — verify the domain, not the HTML file). Note: on a custom domain Carrd site, verify the custom domain property in GSC (not the carrd.co subdomain), since you want to track performance on your domain.