Tilda automatically generates robots.txt and sitemap.xml for published sites, and provides page-level controls for titles, descriptions, human-readable URLs, indexing and social previews. Those capabilities reduce setup work but do not decide the right page structure or content.
Search visibility still depends on a coherent set of canonical pages, unique intent, helpful content, descriptive headings, internal links, valid redirects and a production site that search engines can crawl.
This checklist focuses on the last mile between a finished Tilda build and a clean indexation request. For broader SEO planning, use the complete SEO checklist.
Set one purpose and one primary URL per page
Define the search intent and business job for every page. Avoid creating several thin pages that compete for the same topic, and avoid hiding multiple unrelated intents in one page.
Use short, descriptive slugs. When changing a published slug, add a 301 redirect from the old path to the final relevant page. Keep lowercase conventions consistent.
Page inventory columns
- Page name and final URL
- Primary intent and topic
- Content owner
- Index or noindex decision
- Canonical destination
- Old URL redirect
- Linked service or article cluster
Write unique titles, descriptions and one H1
In Page Settings → SEO, customise the search result title and description for each important page. The title should distinguish the page; the description should accurately preview the value and encourage a relevant click.
Use one clear H1 near the top of the page, then H2 and H3 headings to organise sections. Do not choose heading levels only for visual size. Tilda’s own guidance recommends one H1 per page.
Metadata quality gate
Optimise content, images and mobile rendering
Answer the page’s main question with useful, original content. Add proof, process, FAQs or examples where they help the user decide. Do not repeat keywords unnaturally; Tilda’s guidance explicitly warns against overloading copy.
Add descriptive alt text to meaningful images and leave decorative images appropriately empty. Compress assets, use sensible dimensions and inspect the mobile version for hidden or reordered content.
Content review
- Search intent answered early
- Service value and audience clear
- Claims supported by examples or proof
- Contextual links use descriptive anchor text
- Image alt explains purpose, not decoration
- Mobile text and buttons remain usable
Control indexation and canonical signals
Open each page’s SEO settings and confirm whether search engines are allowed to index it. Keep utility, duplicate, test or private pages out of the index when appropriate.
Check the live canonical URL and make sure it uses the preferred HTTPS and host version. Custom code must not add a second conflicting canonical or robots directive.
Indexation checks
Validate robots.txt and sitemap.xml
Tilda generates both files automatically for published sites. Open /robots.txt and /sitemap.xml on the live domain and verify they load successfully.
The sitemap should contain the intended canonical indexable pages, not obsolete slugs or staging content. Robots rules should not block important pages or resources.
Live file test
Add redirects for changed or retired URLs
Use Tilda’s redirect settings for paths that have changed. Point each old address to the closest relevant live destination and avoid chains.
Update your own internal links to the final URL instead of relying on the redirect. For a major rebuild, follow the website redesign SEO checklist.
Redirect acceptance
Add structured data once and validate it
Use page-specific JSON-LD only when the visible content supports it. Articles can use BlogPosting and visible FAQs can use FAQPage; service pages require a different model.
Place one approved page-specific block in the Head and remove obsolete duplicates. Ensure URLs, dates, headline, image and organisation details match the live page.
Schema rules
- Valid JSON without comments
- One current version per page
- Absolute final URLs
- Visible FAQ wording matches the markup
- No invented ratings or unsupported claims
- Test in Google Rich Results Test and Schema.org validator
Build internal links around the SEO core
Connect service pages, supporting articles and proof so users can move from learning to evaluation. Use contextual anchor text that describes the destination.
A Tilda site can be technically crawlable and still leave important pages isolated. Confirm that every indexable page is reachable through meaningful site links and included in the intended cluster. Explore SEO growth marketing for ongoing optimisation.
Cluster pattern
Primary commercial destination.
Answers a supporting search intent.
Portfolio or case evidence.
Run live QA and request indexation
Republish all pages, use Tilda SEO Assistant and the broken-link checker, then manually test priority templates. Verify status codes, forms, navigation, mobile rendering and the final source output.
Connect Google Search Console, submit the sitemap and inspect the homepage plus representative service and article URLs. Request indexation only after the live URL passes the checks. See selected website work for examples of connected structure and presentation.
Launch sequence
Use Tilda’s controls as a system
Tilda makes many technical tasks accessible, but SEO quality still comes from page decisions and disciplined launch QA. Give every page one purpose, one canonical URL, useful content and a clear place in the internal-link structure.
After publishing, verify the live output rather than trusting editor settings alone. Then submit the sitemap and monitor Search Console as Google discovers the site.
Frequently asked questions
Does Tilda automatically create a sitemap and robots.txt?
Does Tilda automatically create a sitemap and robots.txt?
Yes. Tilda states that it automatically generates both files for published sites. You should still open them on the live domain and verify that the intended pages and rules are present.
Where do I set SEO titles and descriptions in Tilda?
Where do I set SEO titles and descriptions in Tilda?
Open Page Settings → SEO → Customize search results preview. Use a unique title and accurate description for each important page, then republish it.
How many H1 headings should a Tilda page have?
How many H1 headings should a Tilda page have?
Use one descriptive H1 for the main page topic. Organise the remaining sections with logical H2 and H3 headings.
Do I need custom JSON-LD on every Tilda page?
Do I need custom JSON-LD on every Tilda page?
No. Add structured data only when it accurately describes the visible page and provides information not already represented correctly. Avoid duplicate or conflicting blocks.