★★★★★ 4.7 CE

Tilda SEO & Core Web Vitals 2026

Tilda is SEO-complete for a small builder, on static crawlable pages: meta, canonical, wildcard 301s, sitemap and an SEO audit. Performance is undocumented.

Website BuildersVerified today

Full review Pricing Official site ↗

Tilda SEO & Core Web Vitals verdict

Verified today·5 sources checked

Tilda is unusually SEO-complete for a small builder, on static crawlable pages.

Its SEO guide is the deepest of any small site builder we covered. It spans per-page meta and canonical, user-friendly slugs, wildcard 301s, an auto robots.txt and sitemap.

What it means for your rankings

Choose Tilda when on-page SEO control and clean, crawlable static pages matter more than a guaranteed performance pipeline. It is excellent for content and marketing sites that need granular meta, canonical, redirects and an SEO audit out of the box. Be ready to own performance yourself, keeping pages light and testing in PageSpeed, and add schema by hand, since neither is a documented platform feature.

Honest limits

Tilda serves static long-scroll HTML, so content is in the initial response and crawlable, unlike a client-rendered app, though field CWV data is sparse because its base is mostly small sites.
Performance is undocumented, with no speed or image-optimization article, so WebP, caching, lazy-loading and Core Web Vitals are not platform guarantees. Structured data is not native, since JSON-LD is added only through a custom HTML (T123) block.
301 redirects are same-domain with wildcards and no documented bulk CSV, and robots.txt editability is not documented.

Page type: Static long-scroll HTML
Indexability: Crawlable from initial HTML
SEO controls: Deepest of the small builders
Structured data: Custom HTML only
Performance docs: None (gap)

View sources

This page covers Tilda's SEO output and page performance. Migration and pricing live on their own pages.

Do real Tilda sites pass Core Web Vitals?

Real-site SEO & performance evidence

What Google sees and controls on Tilda

Rendered HTML: static long-scroll HTML; content present in the initial response, not JS-deferred
Meta titles & descriptions: per-page in SEO settings; titles should be unique
URL slugs: user-friendly slugs replace the default /pageNNNN.html
Canonical tags: auto on the connected domain, editable per page
301 redirects: wildcards, same-domain only, no bulk CSV
Per-page / whole-site noindex: checkboxes in SEO settings
robots.txt & sitemap: auto-generated, viewable (editability not documented)
Structured data (JSON-LD): no native field; via a custom HTML (T123) block

Hard limits on Tilda

Performance undocumented, no speed or image-optimization article; WebP, caching, lazy-load and CWV are not stated features.
Sparse field data, Tilda's base is mostly small sites, so population CrUX is thin; judge speed from your own pages.
Schema is manual, structured data only via a custom HTML block, not a native field.

Technical SEO configuration in Tilda

Tilda has no native schema generator, so JSON-LD is added through a custom HTML block (T123), which supports HTML, JavaScript and CSS. Drop a script tag with your schema onto the page; this is the only documented way to get structured data on Tilda.

Structured data via custom HTML (T123)html

<!-- Tilda T123 custom-HTML block (no native schema field) -->
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "LocalBusiness",
  "name": "Your Business",
  "url": "https://your-domain.com"
}
</script>

Inject site-wide head code via Site Settings, More, HTML code for the head section, or per-page via Page Settings, Additional. Use it for verification meta, Open Graph overrides or third-party scripts that belong in the head.

Head code + meta tagshtml

<!-- Site Settings, More, HTML code for the <head> section (site-wide) -->
<meta name="google-site-verification" content="YOUR_TOKEN">
<meta property="og:type" content="website">
<!-- Per page: Page Settings, Additional, HTML code for the <head> section -->

Tilda auto-generates robots.txt and an XML sitemap. Confirm they respond at the site root, and remember crawl control is via the per-page and whole-site noindex switches rather than editing robots.txt (editability is not documented).

Verify crawl filesbash

# Tilda auto-generates these; confirm they respond:
curl -I https://your-domain.com/robots.txt
curl -I https://your-domain.com/sitemap.xml
# Crawl control: use the SEO noindex switches, not robots.txt edits (not documented).

How sites built on Tilda rank and load

Tilda pages are static long-scroll HTML that is auto-indexed, so the content Google needs is present in the page itself rather than rendered later
Independently, Google indexes the rendered HTML of a page, and because Tilda emits the content as static HTML up front, that requirement is met from the initial response, the opposite of a client-rendered app
The SEO control surface is unusually complete for a small builder: per-page title and description, user-friendly slugs, canonical tags, 301 redirects with wildcards, per-page and whole-site noindex, a custom 404 and a built-in SEO Assistant
The honest limit is performance documentation: Tilda's help center publishes no speed or image-optimization article, so WebP, caching, lazy-loading and Core Web Vitals are simply not documented as platform features

How Google sees a Tilda site

Googlebot reality (independent)	On Tilda	Why it matters	Source
Indexing model	Crawl, render, index	Tilda pages go through Google's normal pipeline; nothing exotic	Google Search Central
Content in initial HTML	Present (static)	Tilda emits static long-scroll HTML, so the content is there before any render, unlike a SPA	Tilda + Google
What gets indexed	The rendered HTML	Tilda's HTML is the rendered HTML, so the requirement is met from the first response	Google Search Central
Auto-indexing	Yes (by design)	Tilda states its build is auto-indexed by search engines	Tilda docs
Crawl control	noindex + robots	Per-page and whole-site noindex, plus an auto robots.txt, gate what is indexed	Tilda docs
Field CWV data	Sparse (small-site base)	Few Tilda full-site origins meet the CrUX traffic threshold, so this is indexability, not a CWV average	Google Search Central

SEO controls you actually get in Tilda

SEO control	On Tilda	How it works	Source
Meta title & description (per page)	Built-in	Page Settings, SEO, Customize search results preview; each page's title should be unique	—
User-friendly URL slugs	Built-in	Replace the default /pageNNNN.html with a readable slug in Page Settings	—
Canonical tags	Auto + editable	Your connected domain auto-acquires rel=canonical; editable per page in SEO settings	—
301 redirects (wildcards)	Built-in (same-domain)	Site Settings, SEO, 301 redirects; /blog/* wildcard; same-domain only, no bulk CSV documented	—
noindex (page + whole site)	Built-in	Per-page checkbox in SEO settings, plus a whole-site disable-indexing switch	—
SEO Assistant + broken-link checker	Built-in	Audits indexing errors against search-engine recommendations; finds broken links site-wide	—
robots.txt & XML sitemap	Auto (viewable)	Generated automatically; view at /robots.txt and /sitemap.xml (editability not documented)	—
Structured data (JSON-LD)	Not native	No native schema generator; achievable only via a custom HTML (T123) block	—

Tilda performance levers you control

Lever	Tilda behavior	Effect on speed	Source
Page architecture	Single long-scroll HTML	All content ships as one static page; fast to crawl, but heavy pages load everything at once	—
HTTP to HTTPS redirect	Built-in	Forces HTTPS, which is required for HTTP/2 and a ranking signal	—
Custom CDN paths (export)	On code export	Exported sites can use your own CDN paths for images, CSS and JS	—
Image optimization / WebP	Not documented	No image-optimization or WebP article exists; you cannot rely on it as a platform feature	—
Caching / lazy-load / CWV	Not documented	No performance guide is published, so caching, lazy-loading and Core Web Vitals are on you	—

What to verify before you commit to Tilda

Performance is undocumented: there is no speed or image-optimization article, so WebP, caching, lazy-loading and Core Web Vitals are not platform guarantees, test your published pages in PageSpeed yourself
Structured data is not native: schema must be hand-added through a custom HTML block, so a forgotten page simply has no JSON-LD
Redirects are same-domain and manual: 301s with wildcards work within your current domain only, and there is no documented bulk-CSV import, so a large migration is hand-entered
Field CWV data is sparse because Tilda's base is mostly small sites, so judge speed from your own pages rather than a platform average, and treat the indexability picture above as the reliable independent signal

Tilda SEO & Core Web Vitals FAQ

Is Tilda good for SEO?

Yes, it is the most SEO-complete of the small builders. Its SEO guide covers per-page meta titles and descriptions, user-friendly slugs, canonical tags, and 301 redirects with wildcards. It adds per-page and whole-site noindex, an auto robots.txt and sitemap, a custom 404, alt text, heading control, a built-in SEO Assistant audit and Search Console integration. The pages are static HTML, so Google reads the content from the initial response. The gaps are native structured data, custom HTML only, and hreflang.

Are Tilda sites fast / good on Core Web Vitals?

Tilda does not document performance, which is the honest answer. There is no speed or image-optimization article, so WebP, caching, lazy-loading and Core Web Vitals are not stated platform features. And because Tilda's base is mostly small sites, real-user field data is sparse. The one architectural fact is the single long-scroll page, which loads as one document. Treat speed as your responsibility: keep pages light and test them in PageSpeed yourself.

Can I add schema / structured data on Tilda?

Only by hand. Tilda has no native schema generator, so you add JSON-LD through a custom HTML block, the T123 block, which supports HTML, JavaScript and CSS. Paste a script tag with your structured data onto the page. It works, but it is manual per page rather than a generated field, so audit your pages to make sure each one carries the schema you intend.

Does Tilda handle redirects and canonical tags?

Yes. Your connected domain automatically acquires the rel=canonical link and you can edit the canonical per page. For redirects, Site Settings, SEO, 301 redirects supports wildcards like /blog/*, plus HTTP-to-HTTPS and non-WWW-to-WWW switches. The limits are that redirects work within your current domain only and there is no documented bulk-CSV import, so a large URL migration is entered by hand.

Will a Tilda site get indexed by Google?

Cleanly, yes. Tilda states its sites are automatically indexed because the build is static long-scroll HTML. Independently, Google indexes the rendered HTML of a page, which on Tilda is present in the initial response with no deferred JavaScript render to wait on. That is the structural opposite of an app builder. You control what is indexed with the per-page and whole-site noindex switches and the auto robots.txt.

Sources & verification

Verified by ComparEdgeMethod: Vendor docs, official pages, and selected independent sources

Source	What was checked	Last checked
Tilda Official	Official product page	July 10, 2026
Google Javascript Javascript Seo Basics	Independent reference	July 10, 2026
Tilda Support	Search Engine	July 10, 2026
Tilda Support	Export	July 10, 2026
Tilda Support	Html	July 10, 2026

Every fact on this Tilda page is tied to a named source and a verification date. Freshness-sensitive figures trace to the sources above; verify against the vendor before relying on them.