Amplify troubleshooting for social posting issues

Diagnosis steps and fixes for the most common issues you may encounter while using Amplify to distribute content across social networks.

Link previews missing on social networks

Social networks fetch metadata directly from your site when you share a link. Amplify does not control this process. If the preview image or metadata (title, description) does not appear on Facebook, X, or LinkedIn, the problem is between the platform’s crawler and your server.

Common causes

• Missing or invalid Open Graph tags (og:image, og:title, og:description)
• robots.txt blocking the platform’s crawler
• Server blocking the crawler (e.g. 403 Forbidden)
• Cached or outdated data on the social platform

How to diagnose

Test with the exact URL Amplify would publish, not the clean article URL. Amplify appends query parameters for tracking, and some servers or CDNs handle parameterized URLs differently (redirects, blocks, stripped metadata). If you test only the base URL, you might miss the actual problem.

Amplify URLs follow this pattern:

https://example.com/article-slug/?utm_campaign=mrf-facebook-feedname&mrfcid=20260305...

Paste the full parameterized URL into the platform’s diagnostic tool:

Platform	Diagnostic tool	What to look for
Facebook	Sharing Debugger	Warnings, errors. Use Scrape Again to refresh.
X	Card Validator	Confirm og: tags are rendering correctly
LinkedIn	Post Inspector	If you see “We can’t access this content. It may be blocked by robots.txt”, the crawler is blocked

Fix crawler blocks in robots.txt

Each social network uses its own crawler to fetch link previews. If your robots.txt blocks any of them, previews will fail on that platform. Add the following rules to allow all social crawlers:

# Facebook (link previews and product catalogs)
User-agent: facebookexternalhit
Allow: /
User-agent: facebookcatalog
Allow: /

# X / Twitter (Twitter Cards)
User-agent: Twitterbot
Allow: /

# LinkedIn (links shared in posts, messages)
User-agent: LinkedInBot
Allow: /

# WhatsApp (chat previews, uses Facebook infrastructure)
User-agent: WhatsApp
Allow: /

# Pinterest (Rich Pins)
User-agent: Pinterest
Allow: /

# Telegram (chat previews)
User-agent: TelegramBot
Allow: /

# Reddit (post and comment previews)
User-agent: redditbot
Allow: /

# YouTube / Google (embedded link previews, also used for search indexing)
User-agent: Googlebot
Allow: /

After updating your robots.txt:

1. Use each platform’s diagnostic tool (see table above) to confirm the crawler can now access your pages
2. Click Scrape again or equivalent refresh option to clear cached data
3. Confirm your og:image tag points to a valid, accessible image
4. For LinkedIn specifically, verify the image meets LinkedIn’s requirements: minimum 1200 x 627 px, under 5 MB

Quick workaround

Switch Amplify to Photo mode instead of Link Preview. Amplify hosts the image directly, so it displays regardless of crawler issues while you resolve the underlying problem.

Facebook flagging comments as spam

Facebook’s anti-spam system flags repetitive comments. To avoid this, include dynamic text in your comments: the article’s og:title, og:description, or Marfeel Copilot prompts. Dynamic elements make each comment unique and more engaging, keeping you clear of spam detection.

If your account is already flagged

Action	Why it helps
Stop posting comments for a few days	Resets Facebook’s spam detection
Reduce posting frequency when you resume	Avoids re-triggering thresholds
Review recent posts for repetitive content	Identify patterns that triggered the flag
Avoid catchy, repeatable titles like “the 10 most XX”	Facebook recognizes clickbait patterns
Vary structure and phrasing across articles	Breaks repetition signals, even when using similar templates

WhatsApp integration disconnection

The WhatsApp integration may disconnect unexpectedly. This is triggered by changes on the connected device. If it disconnects, you need to reconnect your account to resume functionality.

Known causes

• Device unlinked explicitly from the mobile phone
• Phone not connected for 14 consecutive days
• Exceeding the maximum of 4 linked devices per account

The Amplify integration is identified as Firefox on Ubuntu in your WhatsApp linked devices list:

Important: WhatsApp's exact disconnection criteria are not fully transparent. Additional cases may occur beyond those listed above. If the integration disconnects, you need to reconnect it to resume functionality.

Meta API rate limit (error 613)

Error 613 (“Calls to this api have exceeded the rate limit”) means you have hit Meta’s API rate limits. This typically happens after changes to posting frequency or feed volume.

From Meta’s documentation:

“Indicates that we have noticed inconsistent behavior in the API request volume of your app. If you have made any recent changes that affect the number of API requests, you may be encountering this error.”

How to fix: Reduce the frequency of your API requests. If you recently changed your posting schedule or added new feeds, review whether the combined volume exceeds Meta’s thresholds. You can manage posting schedules and feed configurations from your Amplify settings.

Instagram “Suspicious Activity Detected” notifications

Instagram may flag automated activity as suspicious. For detailed diagnosis and resolution steps, see the dedicated troubleshooting guide.

Why are link previews missing when Amplify shares to social networks?

Social networks fetch metadata directly from your site, not from Amplify. Missing previews are usually caused by invalid Open Graph tags, robots.txt blocking the platform’s crawler, server errors like 403 Forbidden, or cached outdated data. Test with the exact parameterized URL Amplify publishes using each platform’s diagnostic tool.

Why does the WhatsApp integration keep disconnecting from Amplify?

WhatsApp disconnects when the linked device is removed from the mobile phone, when the phone is not connected for 14 consecutive days, or when you exceed the maximum of 4 linked devices per account. The Amplify integration appears as Firefox on Ubuntu in the WhatsApp linked devices list.

How do I fix Meta API rate limit error 613 in Amplify?

Error 613 means your app has exceeded Meta’s API rate limits. Reduce the frequency of API requests. If you recently changed your posting schedule or added new feeds, review whether the combined volume exceeds Meta’s thresholds.