Tilda Integration
Connect Forest SEO to Tilda using the Feeds API for automated content publishing with session-based authentication.
Connect Forest SEO to your Tilda website's blog using the Feeds API for automated content publishing.
Authentication Method
Tilda doesn't have an official API. This integration uses browser session authentication via cookies, which need to be extracted from your browser and renewed periodically when they expire.
Prerequisites
Before starting, ensure you have:
- Active Tilda account with admin access
- Blog/Feed enabled on your Tilda site
- Chrome, Firefox, or Safari browser with Developer Tools
- Login credentials for your Tilda account
Required Credentials
You'll need to obtain these credentials from Tilda:
| Credential | Description | Format Example |
|---|---|---|
| Feed UID | Unique identifier for your blog feed | 412774359142 |
| PHPSESSID | Session cookie from feeds.tilda.ru | kfi4p30gqm4h94cgc1epnr4kf1 |
| tildacommonsessid | Session cookie from .tilda.ru domain | 407880916_1744193454.5556.2HI552UDF4DG56NK |
| User Agent | Your browser identification string | Mozilla/5.0 (Macintosh...) |
Optional (for image uploads):
| Credential | Description | Format Example |
|---|---|---|
| publickey | CDN authentication key | shgBjffb264Vds65 |
| uploadkey | CDN upload token | 41213338-3965-8733-a631-421437346139 |
Setup Guide
Step 1: Get Feed UID
What is Feed UID?
The Feed UID is a unique numeric identifier for your Tilda blog feed. It's used to identify which feed Forest SEO should publish content to.
- Go to your Tilda project
- Click Site Settings → More → Built-in services
- Find "Feeds (news, events, posts)" service
- If not activated, click to enable it
- Click "Create feed" or select an existing feed (e.g., "Blog")
- Click on the feed to open it
- Look at the browser URL:
https://feeds.tilda.ru/getfeed?feeduid=412774359142 ↑ This is your Feed UID - Copy the numeric value after
feeduid=
Step 2: Extract Session Cookies
Security Warning
Session cookies provide full access to your Tilda account. Never share them publicly or commit them to version control. Treat them like passwords.
For Chrome / Edge:
- Open your feed page:
https://feeds.tilda.ru/posts/?feeduid=YOUR_FEED_UID - Make sure you're logged in to Tilda
- Press F12 (or Ctrl+Shift+I / Cmd+Option+I)
- Go to Application tab (or click
>>if hidden) - Reload the page (F5 or Cmd+R)
- In left sidebar: Storage → Cookies → https://feeds.tilda.ru
- Find PHPSESSID cookie:
- Look for domain:
feeds.tilda.ru - Copy the Value (e.g.,
kfi4p30gqm4h94cgc1epnr4kf1)
- Look for domain:
- Find tildacommonsessid cookie:
- Look for domain:
.tilda.ru(with a dot) - Copy the Value (e.g.,
407880916_1744193454.5556.2HI552UDF4DG56NK)
- Look for domain:
For Firefox:
- Open feed page and press F12
- Go to Storage tab
- Reload page (F5)
- Navigate: Cookies → https://feeds.tilda.ru
- Copy PHPSESSID and tildacommonsessid values
For Safari:
- Enable Developer Tools: Safari → Preferences → Advanced → Show Develop menu
- Open feed page and press Cmd+Option+I
- Go to Storage tab
- Reload page (Cmd+R)
- Navigate: Cookies → https://feeds.tilda.ru
- Copy PHPSESSID and tildacommonsessid values
Step 3: Get User Agent
Why User Agent is Required
Tilda links session cookies to specific browser User-Agent strings for security. Using a different User-Agent will cause authentication to fail even with valid cookies.
In Developer Tools Console:
- With DevTools still open, click the Console tab
- Type:
navigator.userAgentand press Enter - The console will display a string like:
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36... - Copy the entire string
Quick Copy Method:
copy(navigator.userAgent)This automatically copies it to your clipboard.
Step 4: Get CDN Upload Keys (Optional)
When do you need this?
CDN upload keys are only required if you want Forest SEO to upload images directly to Tilda's CDN. Without these, you can publish text content, but image uploads won't work.
- Open any post in your feed with DevTools open
- Switch to Network tab
- In the feed editor, click "Upload image" and upload any test image
- In Network tab, find a request named "upload" or containing "upload" in URL
- Click the request and look at the Request URL:
https://static.tildacdn.com/api/upload/?publickey=shgBjffb264Vds65&uploadkey=41213338-3965-8733-a631-421437346139 - Copy the publickey value (e.g.,
shgBjffb264Vds65) - Copy the uploadkey value (e.g.,
41213338-3965-8733-a631-421437346139)
Step 5: Configure in Forest SEO
- Go to Dashboard → Settings → Integrations
- Click "Add Integration" → Select "Tilda"
- Fill in the form:
Required Fields:
- Name: Descriptive name (e.g., "My Tilda Blog")
- Feed UID: Paste from Step 1
- PHPSESSID: Paste from Step 2
- tildacommonsessid: Paste from Step 2
- User Agent: Paste from Step 3
Optional Fields:
- Public Key: Paste from Step 4 (if you need image uploads)
- Upload Key: Paste from Step 4 (if you need image uploads)
- Click "Test & Save" to validate the connection
- If successful, you're ready to publish!
Publishing Content
Once configured, you can publish content to Tilda:
- Generate or select content in Forest SEO
- Click "Publish" → Choose your Tilda integration
- Click "Publish Now"
- Content will appear in your Tilda feed
Content Mapping
| Forest SEO | Tilda Feed |
|---|---|
| Title | Post title |
| Content | Post HTML body |
| Excerpt | Description |
| Slug | URL slug |
| Featured Image | Cover image |
| Published Date | Publication timestamp |
Session Management
Cookie Expiration
Session cookies typically expire after 24-48 hours of inactivity or when you log out of Tilda. Set a reminder to refresh them weekly to avoid publishing disruptions.
Renewing Expired Sessions
When you see "401 Unauthorized" errors:
- Log out and log back in to Tilda in your browser
- Repeat Step 2 and Step 3 to extract new cookies and User-Agent
- Update your integration:
- Go to Settings → Integrations
- Click Edit on your Tilda integration
- Paste the new credentials
- Click "Test & Save"
Troubleshooting
401 Unauthorized Error
Cause: Session cookies expired or invalid
Solution:
- Logout from Tilda completely
- Login again and extract fresh cookies (see Step 2)
- Update integration with new cookies
- Verify User-Agent matches your current browser
Cookie Format Errors
Cause: Incorrect cookie values or format
Solution:
- PHPSESSID: Should be lowercase letters and numbers only (e.g.,
kfi4p30gqm4h94cgc1epnr4kf1) - tildacommonsessid: Should contain numbers, dots, underscores, and uppercase letters (e.g.,
407880916_1744193454.5556.2HI552UDF4DG56NK) - Make sure you copied the entire value without extra spaces
Image Upload Failed
Cause: CDN upload keys not provided or invalid
Solution:
- Follow Step 4 to get upload keys
- Update integration with publickey and uploadkey
- Test by publishing content with images
Content Not Appearing in Tilda
Cause: Wrong Feed UID or feed not activated
Solution:
- Verify the Feed UID is correct (check URL in Step 1)
- Make sure the feed is activated in Tilda settings
- Check if the feed is visible on your public Tilda site
Best Practices
✅ Refresh cookies weekly to prevent expiration issues
✅ Store credentials securely in password manager
✅ Test connection before bulk publishing
✅ Use descriptive integration name if you have multiple feeds
✅ Set up CDN keys for better image performance
❌ Don't share session cookies with anyone
❌ Don't commit credentials to version control
❌ Don't use expired cookies (test regularly)
Next Steps
Need Help?
Having issues with Tilda integration? Check out:
-
Open DevTools
- Press
F12orCmd+Option+I(Mac) - Go to Application tab
- Select Cookies →
https://tilda.cc
- Press
-
Copy Session IDs:
phpsessid:
- Find cookie named
PHPSESSID - Copy the Value column
- Format: lowercase letters and numbers only
- Length: typically 26 characters
- Example:
kfi4p30gqm4h94cgc1epnr4kf1
tildacommonsessid:
- Find cookie named
tildacommonsessid - Copy the Value column
- Format: numbers, dots, underscore, uppercase letters
- Length: typically 43 characters
- Example:
407880916_1744193454.5556.2HI552UDF4DG56NK
- Find cookie named
-
Copy User Agent (Optional but Recommended):
- Go to Console tab
- Type:
navigator.userAgent - Press Enter
- Copy the entire string
- Example:
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36...
Step 3: Get CDN Upload Keys (Optional)
For media uploads to Tilda CDN:
- Open Network Tab in DevTools
- Upload a test image in Tilda
- Find upload request in Network tab
- Check request headers/body:
- publickey: 16-character string
- uploadkey: UUID format (36 chars with hyphens)
Step 4: Connect in Forest SEO
In Forest SEO Dashboard:
-
Navigate to Settings → Integrations
-
Click "Add Integration"
-
Select "Tilda"
-
Fill in required fields:
| Field | Value | Example |
|---|---|---|
| Name | Integration identifier | "My Tilda Blog" |
| Feed UID | From Step 1 | abc123xyz |
| PHP Session ID | From Step 2 | kfi4p30gqm4h94cgc1epnr4kf1 |
| Tilda Common Session ID | From Step 2 | 407880916_1744193454... |
| User Agent | From Step 2 | Mozilla/5.0... |
- (Optional) Fill in CDN upload keys:
| Field | Value |
|---|---|
| Public Key | 16-char string |
| Upload Key | UUID (36 chars) |
- Click "Test Connection" to verify
- If successful, click "Save Integration"
⚙️ How It Works
Session Cookie Authentication
Cookie Format Validation
Forest SEO validates cookie formats:
phpsessid:
Pattern: /^[a-z0-9]+$/
Min length: 10 characters
Example: kfi4p30gqm4h94cgc1epnr4kf1
└─ Only lowercase letters and numbers
tildacommonsessid:
Pattern: /^[0-9_\.A-Z0-9]+$/
Min length: 10 characters
Example: 407880916_1744193454.5556.2HI552UDF4DG56NK
└─ Numbers, dots, underscore, uppercase letters
🔄 Session Management
Cookie Expiration
Session cookies typically expire after:
- Inactivity: 24-48 hours
- Logout: Immediately
- Security refresh: Periodically by Tilda
Renewing Sessions
When you see "401 Unauthorized" errors:
- Re-login to Tilda in your browser
- Extract new cookies using DevTools (Step 2 above)
- Update integration in Forest SEO:
- Go to Settings → Integrations
- Click Edit on your Tilda integration
- Paste new session cookies
- Click Save
💡 Tip
Set a reminder to refresh session cookies weekly to avoid disruptions.
📝 Content Publishing
Content Mapping
| Forest SEO Field | Tilda Feed Field | Description |
|---|---|---|
| Title | Post title | Article headline |
| Content | Post HTML | Full article body |
| Excerpt | Description | Short summary |
| Slug | URL slug | SEO-friendly URL |
| Featured Image | Cover image | Main post image |
| Published Date | pub_date | Publication timestamp |
Supported Content
Text Formatting:
- ✅ HTML content
- ✅ Paragraphs and headings
- ✅ Lists (ordered/unordered)
- ✅ Bold, italic, underline
- ✅ Links
Media:
- ✅ Images (uploaded to CDN if keys provided)
- ✅ Image captions
- ⚠️ Videos (limited support)
🖼️ Media Handling
With CDN Upload Keys
If you provided publickey and uploadkey:
- Images are uploaded to Tilda CDN
- CDN URLs are embedded in content
- Images are optimized by Tilda
- Faster loading and better SEO
Without CDN Keys
Images are referenced by external URL:
- Must be publicly accessible
- No Tilda CDN optimization
- May affect loading speed
🧪 Testing Your Integration
Connection Test Checklist
- Click "Test Connection" in integration settings
- Verify:
- Feed UID is correct
- Session cookies are valid (not expired)
- User agent matches your browser
- Tilda API is reachable
- Review test results
- Fix any issues
- Save integration
Test Publish
Steps:
- In Forest SEO, select a test article
- Click "Publish" → "Tilda"
- Click "Publish Now"
- Wait for confirmation
- Check Tilda:
- Login to Tilda admin
- Go to your blog/feed
- Find the published post
- Verify content and images
🔧 Troubleshooting
Common Issues
401 Unauthorized
Problem: Session cookies expired or invalid
Solutions:
-
Refresh Cookies:
- Logout from Tilda completely
- Clear browser cookies for
tilda.cc - Login again
- Extract new session cookies
- Update integration
-
Check Cookie Format:
phpsessid: Only lowercase a-z, 0-9tildacommonsessid: Numbers, dots, underscore, uppercase
Cookie Format Errors
Invalid phpsessid:
✅ Valid: kfi4p30gqm4h94cgc1epnr4kf1
❌ Invalid: Kfi4p30gqm4h94cgc1epnr4kf1 (uppercase K)
❌ Invalid: kfi4p30gqm4h94cgc1epnr4kf1- (dash at end)
Invalid tildacommonsessid:
✅ Valid: 407880916_1744193454.5556.2HI552UDF4DG56NK
❌ Invalid: 407880916-1744193454.5556.2HI552UDF4DG56NK (dash instead of underscore)
❌ Invalid: 407880916_1744193454.5556.2hi552udf4dg56nk (lowercase letters)
Image Upload Issues
Problem: Images not uploading to Tilda CDN
Causes:
- Missing upload keys
- Invalid public/upload keys
- CDN permissions
Solutions:
| Issue | Fix |
|---|---|
| No keys provided | Extract publickey and uploadkey from DevTools |
| Invalid keys | Re-extract keys from a fresh upload |
| CDN errors | Images will use external URLs instead |
📊 Monitoring
Check Integration Health
In Forest SEO:
- Go to Settings → Integrations
- Check Tilda integration status:
- 🟢 Active — Working normally
- 🟡 Degraded — Some requests failing
- 🔴 Disconnected — Needs attention
Session Expiration Monitoring
Signs of expired sessions:
- 401 errors in publish logs
- "Unauthorized" in test connection
- Failed publications to Tilda
Action: Refresh session cookies immediately
🔗 Integration with Features
With Content Generation
- Generate AI content
- Auto-publish to Tilda feed
- Optimize for Tilda's format
With Schedules
- Automate publishing workflow
- Batch operations
- Scale content production
📚 Resources
💡 Best Practices
Session Management
- Refresh regularly — Update cookies weekly
- Monitor health — Check integration status daily
- Keep backups — Save working cookie values
- Test after refresh — Always test after updating cookies
Content Publishing
- Test with drafts — Verify format before publishing
- Use CDN keys — Faster images, better SEO
- Check feed — Review published content in Tilda
- Monitor performance — Track Tilda analytics
Security
- Keep cookies private — Never share session IDs
- Use HTTPS — Always access Tilda over HTTPS
- Logout when done — End sessions in public places
- Regenerate if compromised — Get new cookies immediately
⚠️ Limitations
Session-Based Authentication
- ✅ Simple to set up
- ⚠️ Requires periodic renewal
- ⚠️ Expires on logout
- ⚠️ Browser-dependent
Content Support
- ✅ Full HTML support
- ✅ Images and media
- ⚠️ Limited video embedding
- ⚠️ No interactive elements
Scalability
- ✅ Suitable for regular publishing
- ⚠️ Manual cookie refresh needed
- ⚠️ Rate limits on Feed API
- ⚠️ Session sharing not recommended