Feed URLs and Access
Each feed has a unique URL that advertising platforms use to fetch your product data. This guide explains feed URLs and access options.
Your Feed URL
Section titled “Your Feed URL”Each feed gets a unique URL like:
https://yourapp.smartfeed.app/feeds/abc123-def456-ghi789.xmlURL Components
Section titled “URL Components”| Part | Description |
|---|---|
| Domain | Feedy McFeed Feed hosting |
| /feeds/ | Feed endpoint |
| abc123… | Unique feed identifier |
| .xml | File format extension |
Getting Your Feed URL
Section titled “Getting Your Feed URL”- Go to Feeds
- Click on your feed
- Find Feed URL section
- Click Copy to copy URL
URL Formats
Section titled “URL Formats”The URL extension indicates format:
| Extension | Format |
|---|---|
.xml | XML format |
.tsv | Tab-separated values |
.csv | Comma-separated values |
Change format in feed settings—URL updates automatically.
Using Feed URLs
Section titled “Using Feed URLs”In Google Merchant Center
Section titled “In Google Merchant Center”- Go to GMC > Products > Feeds
- Add new feed > Scheduled fetch
- Paste Feedy McFeed Feed URL
- Set fetch schedule
In Facebook Commerce Manager
Section titled “In Facebook Commerce Manager”- Go to catalog > Data sources
- Choose Data feed > Scheduled feed
- Paste URL
- Configure schedule
In Other Platforms
Section titled “In Other Platforms”Most platforms accept feed URLs:
- Find “Add feed” or “Import products”
- Choose URL/scheduled fetch option
- Paste your Feedy McFeed Feed URL
Testing Feed URLs
Section titled “Testing Feed URLs”In Browser
Section titled “In Browser”Paste URL in browser to:
- Verify URL works
- Download feed file
- Inspect content
Using cURL
Section titled “Using cURL”curl -I https://yourapp.smartfeed.app/feeds/abc123.xmlCheck response:
- 200 OK = Success
- 404 = Feed not found
- 403 = Authentication required
URL Persistence
Section titled “URL Persistence”Feed URLs are persistent:
- URL stays the same when feed regenerates
- Content updates, URL doesn’t change
- Safe to share and configure in platforms
URLs change when:
- You delete and recreate the feed
- You change the feed format
- You enable/disable protection
Multiple Feeds, Multiple URLs
Section titled “Multiple Feeds, Multiple URLs”Each feed has its own URL:
| Feed | URL |
|---|---|
| Google US | /feeds/abc123.xml |
| Google UK | /feeds/def456.xml |
| /feeds/ghi789.csv |
Use the appropriate URL for each platform.
Feed URL Security
Section titled “Feed URL Security”Public Feeds (Default)
Section titled “Public Feeds (Default)”- Anyone with URL can access
- Simple to set up
- URL acts as password (don’t share publicly)
Protected Feeds
Section titled “Protected Feeds”Add token requirement:
https://yourapp.smartfeed.app/feeds/abc123.xml?token=your-secret-tokenSee Feed Security for setup.
Caching and Freshness
Section titled “Caching and Freshness”Platform-Side Caching
Section titled “Platform-Side Caching”Platforms may cache feeds:
- Google: Up to 24 hours
- Facebook: Up to 24 hours
- Others vary
Feedy McFeed Feed Caching
Section titled “Feedy McFeed Feed Caching”Feedy McFeed Feed caches generated feeds:
- Instant response for repeated requests
- Cache clears on regeneration
- No action needed
Forcing Fresh Content
Section titled “Forcing Fresh Content”To ensure platforms get latest data:
- Regenerate feed in Feedy McFeed Feed
- Manually trigger fetch in platform
- Or wait for next scheduled fetch
URL Access Logging
Section titled “URL Access Logging”Feedy McFeed Feed logs feed access:
- Go to feed > Access Log
- See recent requests
- View IP addresses and timestamps
Useful for:
- Verifying platform is fetching
- Identifying unauthorized access
- Troubleshooting fetch issues
Troubleshooting URL Issues
Section titled “Troubleshooting URL Issues”URL Not Working
Section titled “URL Not Working”| Issue | Solution |
|---|---|
| 404 error | Verify URL is correct |
| 403 error | Check authentication |
| Timeout | Large feed—wait longer |
| Empty response | Check feed has products |
Platform Can’t Fetch
Section titled “Platform Can’t Fetch”- Verify URL in browser
- Check for token if protected
- Ensure no firewall blocking
- Test from different network